
Customizing OSPF Services
117356-E Rev 00
6-5
Configuring the Soloist and Backup Soloist on a Slot
The OSPF protocol is implemented as a soloist -- that is, as a single process
running on a single slot of a router. When you add an OSPF interface to a circuit,
the router enables OSPF on a slot. If the slot on which the OSPF soloist is running
goes down, the router tries to run OSPF on another slot.
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 soloists occurs without relearning routing
information from the network.
By default, the router uses any available slot for the OSPF soloist. You can use the
BCC or Site Manager to specify a slot.
By default, OSPF does not maintain a copy of the link state database (LSDB) for
the backup soloist. You can use the BCC or Site Manager to enable this feature.
Using the BCC
To specify a slot for the OSPF soloist, navigate to the global OSPF prompt (for
example,
box; ip; ospf
) and enter:
slot-mask
<slot>
slot
is
all-slots
(the default) or an integer from 1 through 14 to indicate a slot.
5. Set the
Router ID
parameter. Click on
Help
or see the parameter description on
page A-36
.
6. Click on
OK
. You return to the Configuration Manager
window.
Site Manager Procedure
(continued)
You do this System responds
Komentáře k této Příručce