Ipv4 Multi-Hub-Group Advpn Configuration Example - HP FlexNetwork MSR2003 Configuration Manual

[Spoke1] display advpn ipv6 session
Interface
Number of sessions: 2
Private address
192:168::1
192:168::2
The output shows that Spoke 1 has established a permanent hub-spoke tunnel to Hub 1 and Hub 2.
# Verify that Spoke 1 can ping the private address 192:168::4 of Spoke 2.
[Spoke1] ping ipv6 192:168::4
Ping6(56 data bytes) 192:168::4 --> 192:168::4, press CTRL_C to break
56 bytes from 192:168::4, icmp_seq=0 hlim=64 time=3.000 ms
56 bytes from 192:168::4, icmp_seq=1 hlim=64 time=0.000 ms
56 bytes from 192:168::4, icmp_seq=2 hlim=64 time=1.000 ms
56 bytes from 192:168::4, icmp_seq=3 hlim=64 time=1.000 ms
56 bytes from 192:168::4, icmp_seq=4 hlim=64 time=1.000 ms
--- Ping6 statistics for 192:168::4 ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.000/1.200/3.000/0.980 ms

IPv4 multi-hub-group ADVPN configuration example

Network requirements
As shown in
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 Hub 1, Hub 2, and Hub 3.
Hub group 1 contains Hub 1, Hub 2, Spoke 1, and Spoke 2. Hub 1 and Hub 2 back up each
other.
Hub group 2 contains Hub 3, Spoke 3, and Spoke 4. Hub groups 1 and 2 use full-mesh
networking.
•
Allow any two spokes to establish a direct spoke-spoke tunnel.
: Tunnel1
Public address
1::1
1::2
Figure 150, the primary and secondary VAM servers manage and maintain VAM client
Port Type State
-- S-H Success
-- S-H Success
379
Holding time
0H 46M 8S
0H 46M 8S