H3C Technologies H3C SR8800 User Manual
Page 407

396
[CE1] display ip routing-table
Routing Tables: Public
Destinations : 16 Routes : 16
Destination/Mask Proto Pre Cost NextHop Interface
1.1.1.9/32 ISIS 15 10 10.1.1.2 POS2/1/1
2.2.2.9/32 Direct 0 0 127.0.0.1 InLoop0
5.5.5.9/32 ISIS 15 74 11.1.1.2 POS2/1/2
6.6.6.9/32 ISIS 15 74 11.1.1.2 POS2/1/2
10.1.1.0/24 Direct 0 0 10.1.1.2 POS2/1/1
10.1.1.1/32 Direct 0 0 10.1.1.1 POS2/1/1
10.1.1.2/32 Direct 0 0 127.0.0.1 InLoop0
11.1.1.0/24 Direct 0 0 11.1.1.1 POS2/1/2
11.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0
11.1.1.2/32 Direct 0 0 11.1.1.2 POS2/1/2
20.1.1.0/24 ISIS 15 74 11.1.1.2 POS2/1/2
21.1.1.0/24 ISIS 15 74 11.1.1.2 POS2/1/2
21.1.1.2/32 ISIS 15 74 11.1.1.2 POS2/1/2
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
# Issue the display ipv6 routing-table vpn-instance command on CE 1 and CE 2. The output shows
that the VPN routing tables do not contain the VPN routes that the customer carrier maintains.
# Issue the display ip routing-table command on PE 3 and PE 4. The output shows that the internal
routes of the customer carrier network are present in the public network routing tables. Take PE 3
as an example:
[PE3] display ip routing-table
Routing Tables: Public
Destinations : 11 Routes : 11
Destination/Mask Proto Pre Cost NextHop Interface
1.1.1.9/32 Direct 0 0 127.0.0.1 InLoop0
2.2.2.9/32 ISIS 15 10 10.1.1.2 POS2/1/2
5.5.5.9/32 ISIS 15 84 10.1.1.2 POS2/1/2
6.6.6.9/32 ISIS 15 84 10.1.1.2 POS2/1/2
10.1.1.0/24 Direct 0 0 10.1.1.1 POS2/1/2
10.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0
10.1.1.2/32 Direct 0 0 10.1.1.2 POS2/1/2
11.1.1.0/24 ISIS 15 20 10.1.1.2 POS2/1/2
20.1.1.0/24 ISIS 15 84 10.1.1.2 POS2/1/2
21.1.1.0/24 ISIS 15 84 10.1.1.2 POS2/1/2
21.1.1.2/32 ISIS 15 84 10.1.1.2 POS2/1/2
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
# Ping PE 3 from PE 4 and ping PE 4 from PE 3. PE 3 and PE 4 can ping each other:
[PE3] ping 20.1.1.2
PING 20.1.1.2: 56 data bytes, press CTRL_C to break
Reply from 20.1.1.2: bytes=56 Sequence=1 ttl=252 time=127 ms
Reply from 20.1.1.2: bytes=56 Sequence=2 ttl=252 time=97 ms
Reply from 20.1.1.2: bytes=56 Sequence=3 ttl=252 time=83 ms
Reply from 20.1.1.2: bytes=56 Sequence=4 ttl=252 time=70 ms