Defining areas, Assigning the area index, Defining areas 75 – Nortel Networks WEB OS 212777 User Manual

Page 75

Advertising
background image

Web OS 10.0 Application Guide

Chapter 4: OSPF

n

75

212777-A, February 2002

Defining Areas

If you are configuring multiple areas in your OSPF domain, one of the areas must be desig-
nated as area 0, known as the backbone. The backbone is the central OSPF area and is usually
physically connected to all other areas. The areas inject routing information into the backbone
which, in turn, disseminates the information into other areas.

Since the backbone connects the areas in your network, it must be a contiguous area. If the
backbone is partitioned (possibly as a result of joining separate OSPF networks), parts of the
AS will be unreachable, and you will need to configure virtual links to reconnect the parti-
tioned areas (see

“Virtual Links” on page 79

).

Up to three OSPF areas can be connected to a Web switch with Web OS 10.0 software. To con-
figure an area, the OSPF number must be defined and then attached to a network interface on
the Web switch. The full process is explained in the following sections.

An OSPF area is defined by assigning two pieces of information—an area index and an area
ID
. The command to define an OSPF area is as follows:

N

OTE

The

aindex

option above is an arbitrary index used only on the switch and does not

represent the actual OSPF area number. The actual OSPF area number is defined in the

areaid

portion of the command as explained in the following sections.

Assigning the Area Index

The

aindex

<area index> option is actually just an arbitrary index (0-2) used only by the

Web switch. This index does not necessarily represent the OSPF area number, though for con-
figuration simplicity, it should where possible.

For example, both of the following sets of commands define OSPF area 0 (the backbone) and
area 1 because that information is held in the area ID portion of the command. However, the
first set of commands is easier to maintain because the arbitrary area indexes agree with the
area IDs:

n

Area index and area ID agree

/cfg/ip/ospf/aindex 0/areaid 0.0.0.0

(Use index 0 to set area 0 in ID octet format)

/cfg/ip/ospf/aindex 1/areaid 0.0.0.1

(Use index 1 to set area 1 in ID octet format)

n

Area index set to an arbitrary value

/cfg/ip/ospf/aindex 1/areaid 0.0.0.0

(Use index 1 to set area 0 in ID octet format)

/cfg/ip/ospf/aindex 2/areaid 0.0.0.1

(Use index 2 to set area 1 in ID octet format)

>> #

/cfg/ip/ospf/aindex

<area index>

/areaid

<n.n.n.n>

Advertising