31720.1.1.0/24 ISIS 15 84 10.1.1.2 Vlan1221.1.1.0/24 ISIS 15 84 10.1.1.2 Vlan1221.1.1.2/32 ISIS 15 84 10.1.1.2 Vlan12127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0Issue the display ip routing-table vpn-instance command on PE 3 and PE 4. The output shows thatthe routes of the remote VPN customers are present in the VPN routing tables. Take PE 3 as anexample:[PE3] display ip routing-table vpn-instance vpn1Routing Tables: vpn1Destinations : 3 Routes : 3Destination/Mask Proto Pre Cost NextHop Interface100.1.1.0/24 Direct 0 0 100.1.1.2 Vlan11100.1.1.2/32 Direct 0 0 127.0.0.1 InLoop0120.1.1.0/24 BGP 255 0 6.6.6.9 NULL0PE 3 and PE 4 can ping each other:[PE3] ping 20.1.1.2PING 20.1.1.2: 56 data bytes, press CTRL_C to breakReply from 20.1.1.2: bytes=56 Sequence=1 ttl=252 time=127 msReply from 20.1.1.2: bytes=56 Sequence=2 ttl=252 time=97 msReply from 20.1.1.2: bytes=56 Sequence=3 ttl=252 time=83 msReply from 20.1.1.2: bytes=56 Sequence=4 ttl=252 time=70 msReply from 20.1.1.2: bytes=56 Sequence=5 ttl=252 time=60 ms--- 20.1.1.2 ping statistics ---5 packet(s) transmitted5 packet(s) received0.00% packet lossround-trip min/avg/max = 60/87/127 msCE 3 and CE 4 can ping each other:[CE3] ping 120.1.1.1PING 120.1.1.1: 56 data bytes, press CTRL_C to breakReply from 120.1.1.1: bytes=56 Sequence=1 ttl=252 time=102 msReply from 120.1.1.1: bytes=56 Sequence=2 ttl=252 time=69 msReply from 120.1.1.1: bytes=56 Sequence=3 ttl=252 time=105 msReply from 120.1.1.1: bytes=56 Sequence=4 ttl=252 time=88 msReply from 120.1.1.1: bytes=56 Sequence=5 ttl=252 time=87 ms--- 120.1.1.1 ping statistics ---5 packet(s) transmitted5 packet(s) received0.00% packet lossround-trip min/avg/max = 69/90/105 msConfiguring nested VPNNetwork requirementsThe service provider provides nested VPN services for users, as shown in Figure 83.
