Configuring A Virtual Link; Configuring Ospf Network Types - HPE FlexNetwork HSR6800 Configuration Manual

Layer 3-ip routing configuration guide
Hide thumbs Also See for FlexNetwork HSR6800:
Table of Contents

Advertisement

NOTE:
Virtual links cannot transit a stub area or totally stub areas.

Configuring a virtual link

Non-backbone areas exchange routing information through the backbone area. Connectivity
between the backbone and non-backbone areas and within the backbone must be available.
You can configure virtual links to ensure the connectivity when physical links are not enough. Virtual
links cannot transit a stub area, a totally stub area, an NSSA area, or a totally NSSA area.
MD5/HMAC-MD5 authentication supports key rollover. For more information, see
OSPF
authentication"
To configure a virtual link:
Step
Enter system view.
1.
Enter OSPF view.
2.
Enter area view.
3.
Configure a virtual link.
4.

Configuring OSPF network types

OSPF classifies networks into the following types based on the link layer protocol:
Broadcast—When the link layer protocol is Ethernet or FDDI, OSPF considers the network
type as broadcast by default.
NBMA—When the link layer protocol is Frame Relay, ATM, or X.25, OSPF considers the
network type as NBMA by default.
P2P—When the link layer protocol is PPP, LAPB, or HDLC, OSPF considers the network type
as P2P by default.
Follow these guidelines when you change the network type of an interface:
When an NBMA network becomes fully meshed (any two routers in the network have a direct
virtual circuit in between), change the network type to broadcast to avoid manual configuration
of neighbors.
If some routers in a broadcast network do not support multicasting, change the network type to
NBMA.
An NBMA network must be fully meshed. If it is partially meshed, change the network type to
P2MP to simplify configuration and save costs.
If a router on an NBMA network has only one neighbor, change the network type to P2P to save
costs.
Command
system-view
ospf [ process-id | router-id
router-id | vpn-instance
vpn-instance-name ] *
area area-id
vlink-peer router-id [ hello
seconds | retransmit seconds |
trans-delay seconds | dead
seconds | { simple [ plain |
cipher ] password | { md5 |
hmac-md5 } key-id [ plain |
cipher ] password } ] *
66
"Configuring
Remarks
N/A
N/A
N/A
Configure this command on both
ends of a virtual link.
hello and dead intervals must be
identical on both ends of the virtual
link.

Advertisement

Table of Contents
loading

Table of Contents