417
[Hub1] display advpn session
Interface : Tunnel1
Number of sessions: 3
Private address Public address Port Type State Holding time
192.168.1.2 1.0.0.2 18001 H-H Success 0H 46M 8S
192.168.1.3 1.0.0.3 18001 H-S Success 0H 27M 27S
192.168.1.4 1.0.0.4 18001 H-S Success 0H 18M 18S
Interface : Tunnel2
Number of sessions: 2
Private address Public address Port Type State Holding time
192.168.0.2 1.0.0.2 18001 H-H Success 0H 46M 8S
192.168.0.3 1.0.0.3 18001 H-H Success 0H 27M 27S
The output shows that Hub 1 has established a permanent tunnel to Hub 2, Hub3, Spoke 1, and
Spoke 2.
# Display IPv4 ADVPN tunnel information on Spoke 1 and Spoke 2. This example uses Spoke 1.
[Spoke1] display advpn session
Interface : Tunnel1
Number of sessions: 2
Private address Public address Port Type State Holding time
192.168.1.1 1.0.0.1 18001 S-H Success 0H 46M 8S
192.168.1.2 1.0.0.2 18001 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.
# Display IPv4 ADVPN tunnel information on Spoke 3 and Spoke 4. This example uses Spoke 3.
[Spoke3] display advpn session
Interface : Tunnel1
Number of sessions: 1
Private address Public address Port Type State Holding time
192.168.2.1 1.0.0.3 18001 S-H Success 0H 46M 8S
The output shows that Spoke 3 has established a permanent hub-spoke tunnel to Hub 3.
IPv6 multi-hub-group ADVPN configuration example
Network requirements
As shown in Figure 153, 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.
• Configure three hub groups to accommodate all ADVPN nodes:
{ Hub group 0 contains Hub1, Hub2, and Hub3.
{ Hub group 1 contains Hub1, Hub2, Spoke1, and Spoke2. Hub 1 and Hub 2 back up each
other.
{ Hub group 2 contains Hub3, Spoke3, and Spoke4. Hub groups 1 and 2 use full-mesh
networking.
• Allow any two spokes to establish a direct spoke-spoke tunnel.
To Next Page
Loading...
Need help?
General
