Configuring An Ospfv3 Virtual Link; Configuring Ospfv3 Network Types - HP 4800G Series Configuration Manual

Table of Contents

You cannot remove an OSPFv3 area directly. Only when you remove all configurations in area

view and all interfaces attached to the area become down, can the area be removed.

All the routers attached to a stub area must be configured with the stub command. The keyword

no-summary is only available on the ABR of the stub area.

If you use the stub command with the keyword no-summary on an ABR, the ABR advertises a

default route in an Inter-Area-Prefix-LSA into the stub area. No AS-external-LSA,

Inter-Area-Prefix-LSA or Inter-Area-Router-LSA is advertised in the area. The stub area of this kind

is also known as a totally stub area.

Configuring an OSPFv3 Virtual Link

You can configure a virtual link to maintain connectivity between a non-backbone area and the

backbone, or in the backbone itself.

Follow these steps to configure a virtual link:

Enter system view

Enter OSPFv3 view

Enter OSPFv3 area view

Configure a virtual link

Both ends of a virtual link are ABRs that must be configured with the vlink-peer command.

Do not configure virtual links in the areas of a GR-capable process.

OSPFv3 classifies networks into four types upon the link layer protocol:

You can change the network type of an OSPFv3 interface as needed. For example:

An NBMA network must be fully connected. That is, any two routers in the network must be directly

reachable to each other through a virtual circuit. In the event no such direct link is available, you

need to change the network type through a command.

If direct connections are not available between some routers in an NBMA network, the type of

interfaces associated should be configured as P2MP, or as P2P for interfaces with only one

Use the command...

ospfv3 [ process-id ]

area area-id

vlink-peer router-id [ hello seconds |

retransmit seconds | trans-delay seconds |

dead seconds | instance instance-id ] *

Table of Contents