Configuring A Dvpn Route; Displaying And Maintaining Dvpn; Dvpn Configuration Example; Dvpn Configuration Example For Full-Mesh Networks - 3Com MSR 50 Series Configuration Manual

3com msr 30-16: software guide
Hide thumbs Also See for MSR 50 Series:
Table of Contents

Advertisement

Configuring a DVPN
Route
Displaying and
Maintaining DVPN
DVPN Configuration
Example
DVPN Configuration
Example for Full-Mesh
Networks
For details about the interface tunnel, ip address and source commands, refer
to
"Tunneling Configuration" on page
For details about the ospf network-type and ospf dr-priority commands, refer
to
"OSPF Configuration" on page
For details about VPN multi-instance configuration, refer to
Configuration" on page
After you establish private networks across the public network using DVPN, you
need to perform routing configurations for devices in the private networks. In
private networks of this type, route-related operations, such as neighbor discovery,
route updating, routing table establishment, are done through DVPN tunnels.
Routing information is exchanged between Hubs or Hubs and Spokes only (that is,
it is not exchanged between Spokes.) Currently, OSPF can be used in DVPN
networks.
For information about performing OSPF configuration on DVPN clients, refer to
"OSPF Configuration" on page
To do...
Display the information about
client address mappings
registered on the VAM server
Display the statistics on the
clients currently registered
with the VAM server
Display the information about
an VAM client
Display the information about
a DVPN tunnel
Display the configuration of
an IPSec profile
Remove DVPN tunnels
Network requirements
In the full-mesh networks, the primary VAM server (main) and the secondary
VAM server (backup) manage and maintain information about the nodes. The
AAA server takes charge of VAM client authentication and accounting. The
two Hubs provide redundancy for packet forwarding and routing information
exchange.
Permanent tunnels are established between the Spokes and the Hubs.
Spokes in the same VPN exchange data through dynamically established
tunnels between them.
693.
917.
1459.
917.
Use the command...
display vam server address-map { all |
vpn vpn-name [ private-ip private-ip ] }
display vam server statistic { all | vpn
vpn-name }
display vam client { address-map | fsm }
[ client-name ]
display dvpn session { all | interface
interface-type interface-number
[ private-ip ip-address ] }
display ipsec profile [ name
profile-name ]
reset dvpn session { all | interface
interface-type interface-number
[ private-ip ip-address ] }

Configuring a DVPN Route

"MPLS L3VPN
Remarks
Available in any
view
Available in user
view
1571

Hide quick links:

Advertisement

Table of Contents

Troubleshooting

loading

Table of Contents