Network requirements – H3C Technologies H3C SR8800 User Manual
Page 298

287
CEs of the same VPN can ping each other, whereas those of different VPNs can not. For example,
CE 1 can ping CE 3 (10.3.1.1), but cannot ping CE 4 (10.4.1.1):
[CE1] ping 10.3.1.1
PING 10.3.1.1: 56 data bytes, press CTRL_C to break
Reply from 10.3.1.1: bytes=56 Sequence=1 ttl=253 time=72 ms
Reply from 10.3.1.1: bytes=56 Sequence=2 ttl=253 time=34 ms
Reply from 10.3.1.1: bytes=56 Sequence=3 ttl=253 time=50 ms
Reply from 10.3.1.1: bytes=56 Sequence=4 ttl=253 time=50 ms
Reply from 10.3.1.1: bytes=56 Sequence=5 ttl=253 time=34 ms
--- 10.3.1.1 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 34/48/72 ms
[CE1] ping 10.4.1.1
PING 10.4.1.1: 56 data bytes, press CTRL_C to break
Request time out
Request time out
Request time out
Request time out
Request time out
--- 10.4.1.1 ping statistics ---
5 packet(s) transmitted
0 packet(s) received
100.00% packet loss
Configuring MPLS L3VPNs using IBGP between PE and CE
Network requirements
•
CE 1 and CE 3 belong to VPN 1. CE 2 and CE 4 belong to VPN 2.
•
VPN 1 uses VPN target attribute 111:1. VPN 2 uses VPN target attribute 222:2. Users of different
VPNs cannot access each other.
•
IBGP is used to exchange VPN routing information between CE and PE.
•
PEs use OSPF to communicate with each other and use MP-IBGP to exchange VPN routing
information.