H3C Technologies H3C SR8800 - Manual (Page 344)

333
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 69/90/105 ms
CE 5 and CE 6 can ping each other successfully.
[CE5] ping 130.1.1.1
PING 130.1.1.1: 56 data bytes, press CTRL_C to break
Reply from 130.1.1.1: bytes=56 Sequence=1 ttl=252 time=102 ms
Reply from 130.1.1.1: bytes=56 Sequence=2 ttl=252 time=69 ms
Reply from 130.1.1.1: bytes=56 Sequence=3 ttl=252 time=105 ms
Reply from 130.1.1.1: bytes=56 Sequence=4 ttl=252 time=88 ms
Reply from 130.1.1.1: bytes=56 Sequence=5 ttl=252 time=87 ms
--- 130.1.1.1 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 69/90/105 ms
CE 3 and CE 6 cannot ping each other.
[CE3] ping 130.1.1.1
PING 130.1.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
--- 130.1.1.1 ping statistics ---
5 packet(s) transmitted
0 packet(s) received
100.00% packet loss
Configuring HoVPN
Network requirements
There are two levels of networks, the backbone and the MPLS VPN networks, as shown in Figure 82 .
• SPEs act as PEs to allow MPLS VPNs to access the backbone.
• UPEs act as PEs of the MPLS VPNs to allow end users to access the VPNs.
• Performance requirements for the UPEs are lower than those for the SPEs.
• SPEs advertise routes permitted by the routing policies to UPEs, permitting CE 1 and CE 3 in VPN
1 to communicate with each other and forbidding CE 2 and CE 4 in VPN 2 to communicate with
each other.