H3C Technologies H3C SR8800 - Manual (Page 311)

300
2.2.2.9/32 OSPF 10 3125 172.1.1.2 POS5/1/2
10.2.1.0/24 Static 60 0 20.1.1.1 Tunnel0
20.1.1.0/24 Direct 0 0 20.1.1.1 Tunnel0
20.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
172.1.1.0/24 Direct 0 0 172.1.1.1 POS5/1/2
172.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0
172.1.1.2/32 Direct 0 0 172.1.1.2 POS5/1/2
172.2.1.0/24 OSPF 10 3124 172.1.1.2 POS5/1/2
[PE1] display ip routing-table vpn-instance vpn1
Routing Tables: vpn1
Destinations : 3 Routes : 3
Destination/Mask Proto Pre Cost NextHop Interface
10.1.1.0/24 Direct 0 0 10.1.1.2 GE3/1/1
10.1.1.2/32 Direct 0 0 127.0.0.1 InLoop0
10.2.1.0/24 BGP 255 0 2.2.2.9 NULL0
The CEs can ping each other.
[CE1] ping 10.2.1.1
PING 10.2.1.1: 56 data bytes, press CTRL_C to break
Reply from 10.2.1.1: bytes=56 Sequence=1 ttl=253 time=41 ms
Reply from 10.2.1.1: bytes=56 Sequence=2 ttl=253 time=69 ms
Reply from 10.2.1.1: bytes=56 Sequence=3 ttl=253 time=68 ms
Reply from 10.2.1.1: bytes=56 Sequence=4 ttl=253 time=68 ms
Reply from 10.2.1.1: bytes=56 Sequence=5 ttl=253 time=67 ms
--- 10.2.1.1 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 41/62/69 ms
Configuring inter-AS option A
Network requirements
• CE 1 and CE 2 belong to the same VPN. CE 1 accesses the network through PE 1 in AS 100 and
CE 2 accesses the network through PE 2 in AS 200.
• Inter-AS MPLS L3VPN is implemented using option A. That is, the VRF-to-VRF method is used to
manage VPN routes.
• The MPLS backbone in each AS runs OSPF.