R0106-HP MSR Router Series Layer 3 - IP Services Configuration Guide(V7)

337
[Spoke1] display advpn session
Interface : Tunnel1
Number of sessions: 2
Private address Public address Port Type State Holding time
192.168.0.1 1.0.0.1 -- S-H Success 0H 46M 8S
192.168.0.2 1.0.0.2 -- S-H Success 0H 46M 8S
The output shows that Spoke 1 has established a permanent hub-spoke tunnel to Hub 1 and Hub 2.
# Ping the private address 192.168.0.4 of Spoke 2 from Spoke 1.
[Spoke2] ping 192.168.0.4
Ping 192.168.0.4 (192.168.0.4): 56 data bytes, press CTRL_C to break
56 bytes from 192.168.0.4: icmp_seq=0 ttl=255 time=4.000 ms
56 bytes from 192.168.0.4: icmp_seq=1 ttl=255 time=0.000 ms
56 bytes from 192.168.0.4: icmp_seq=2 ttl=255 time=0.000 ms
56 bytes from 192.168.0.4: icmp_seq=3 ttl=255 time=0.000 ms
56 bytes from 192.168.0.4: icmp_seq=4 ttl=255 time=1.000 ms
--- Ping statistics for 192.168.0.4 ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.000/1.000/4.000/1.549 ms
# Display ADVPN tunnel information on Spoke 1.
[Spoke1] display advpn session
Interface : Tunnel1
Number of sessions: 3
Private address Public address Port Type State Holding time
192.168.0.1 1.0.0.1 -- S-H Success 0H 46M 8S
192.168.0.2 1.0.0.2 -- S-H Success 0H 46M 8S
192.168.0.4 1.0.0.4 -- S-S Success 0H 0M 1S
The output shows that:
• Spoke 1 has established permanent hub-spoke tunnels to Hub 1 and Hub 2.
• Spoke 1 and Spoke 2 have established a temporary spoke-spoke tunnel.
IPv6 full-mesh ADVPN configuration example
Network requirements
As shown in Figure 137, the primary and secondary VAM servers manage and maintain VAM client
information for all hubs and spokes. The AAA server performs authentication and accounting for VAM
clients. The two hubs back up each other, and perform data forwarding and route exchange.
Each spoke establishes a permanent ADVPN tunnel to each hub.
Any two spokes in the same ADVPN domain can dynamically establish a temporary ADVPN tunnel.