
Configuring OSPF Services
4-3
Each time the OSPF soloist is restarted, all of the routing information is lost and
must be relearned from the network. The
OSPF backup soloist
provides a method
of preserving information learned from the network in the event of an OSPF crash
or slot removal, avoiding the time-consuming and resource-intensive process of
relearning routing information. In the event of a crash or slot removal, transition
between the OSPF primary and backup soloist occurs without relearning routing
information from the network.
Specifying Network Types
OSPF interfaces support four types of network:
• Point-to-point
• Broadcast
• Nonbroadcast multiaccess
• Point-to-multipoint
A
point-to-point network
joins a single pair of OSPF routers. An example of such
a network would be a network of synchronous lines.
A
broadcast network
supports multiple routers and can address a single physical
message to all attached routers. Examples of such a network are Ethernet, FDDI,
and Token Ring.
A
nonbroadcast multiaccess
(NBMA) network supports multiple routers and
cannot address a single physical message to all routers. Examples of such a
network are Frame Relay and X.25.
A
point-to-multipoint network
supports multiple routers in a partial mesh
configuration. (Bay Networks supports the standard OSPF point-to-multipoint
interface and also provides a proprietary point-to-multipoint solution for routers
running OSPF in star Frame Relay topologies.)
For instructions on customizing the way the OSPF soloist runs on a router, see “Editing
OSPF Global Parameters” on page 4-35.
Site Manager allows you to specify a slot or slots on which the router can restart the
OSPF soloist. For instructions, see the OSPF Slot parameter on page 4-38.
To disable and enable the OSPF backup soloist, see the Backup Enable parameter on
page 4-39.
Comentarios a estos manuales