294Destinations : 8 Routes : 8Destination/Mask Proto Pre Cost NextHop Interface10.0.0.0/24 BGP 255 0 2.2.2.9 NULL010.1.1.0/24 Direct 0 0 10.1.1.2 Vlan210.1.1.2/32 Direct 0 0 127.0.0.1 InLoop010.2.1.0/24 BGP 255 0 2.2.2.9 NULL010.3.1.0/24 BGP 255 0 2.2.2.9 NULL010.4.1.0/24 BGP 255 0 2.2.2.9 NULL0127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0# Spoke-CE 1 and Spoke-CE 2 can ping each other. The TTL value indicates that traffic fromSpoke-CE 1 to Spoke-CE 2 passes six hops (255-250) and is forwarded through the Hub-CE.Take Spoke-CE 1 as an example:[Spoke-CE1] ping 10.2.1.1PING 10.2.1.1: 56 data bytes, press CTRL_C to breakReply from 10.2.1.1: bytes=56 Sequence=1 ttl=250 time=3 msReply from 10.2.1.1: bytes=56 Sequence=2 ttl=250 time=3 msReply from 10.2.1.1: bytes=56 Sequence=3 ttl=250 time=2 msReply from 10.2.1.1: bytes=56 Sequence=4 ttl=250 time=2 msReply from 10.2.1.1: bytes=56 Sequence=5 ttl=250 time=2 ms--- 10.2.1.1 ping statistics ---5 packet(s) transmitted5 packet(s) received0.00% packet lossround-trip min/avg/max = 2/2/3 msConfiguring inter-AS option ANetwork requirements• CE 1 and CE 2 belong to the same VPN. CE 1 accesses the network through PE 1 in AS 100 andCE 2 accesses the network through PE 2 in AS 200.• Inter-AS MPLS L3VPN is implemented using option A, where the VRF-to-VRF method is used tomanage VPN routes.• The MPLS backbone in each AS runs OSPF.
