The virtual interface connecting SW2 and SW1 belongs to vpn-instance instance 12, and the virtual interface connecting SW2 and SW3 does not belong to any vpn-instance instance.
The user hopes that after the device adopts the relevant address configuration shown in the section, the SW1 1.1.1.1/32 network segment belonging to VPN instance 12 can communicate with the SW3 3.3.3.3/32 network segment of the non-VPN instance.
#
ip route-static 1.1.1.1 32 vpn-instance 12 12.1.1.1
ip route-static 3.3.3.3 32 23.1.1.3
ip route-static vpn-instance 12 1.1.1.1 32 12.1.1.1
ip route-static vpn-instance 12 3.3.3.3 32 23.1.1.3 public
#
[H3C]dis ip routing-table 1.1.1.1
Summary count : 1
Destination/Mask Proto Pre Cost NextHop Interface
1.1.1.1/32 Static 60 0 12.1.1.1 Vlan12
[H3C]dis ip routing-table 3.3.3.3
Summary count : 1
Destination/Mask Proto Pre Cost NextHop Interface
3.3.3.3/32 Static 60 0 23.1.1.3 Vlan23
[H3C]ping -a 1.1.1.1 3.3.3.3
Ping 3.3.3.3 (3.3.3.3) from 1.1.1.1: 56 data bytes, press CTRL_C to break
56 bytes from 3.3.3.3: icmp_seq=0 ttl=254 time=2.067 ms
56 bytes from 3.3.3.3: icmp_seq=1 ttl=254 time=2.894 ms
56 bytes from 3.3.3.3: icmp_seq=2 ttl=254 time=1.218 ms
56 bytes from 3.3.3.3: icmp_seq=3 ttl=254 time=1.245 ms
56 bytes from 3.3.3.3: icmp_seq=4 ttl=254 time=1.595 ms
ip route-static vpn-instance 12 3.3.3.3 32 23.1.1.3 public
When adding routes to non-VPN instance network segments in the VPN instance routing table, please add the public parameter to ensure that the relevant routes can take effect.
No comments
✖
案例意见反馈
亲~登录后才可以操作哦!
确定你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作