Master Node Operation; Slave Node Operation - Bay Networks Baystream 7 Notice

Resilient NNI does not support the following:
•
•
•
•
•
•

Master Node Operation

The master node controls the selection of which link it will attempt to activate.
This selection is based initially upon a pre-configured administrative preference.
This preference value is locally significant. This value is not dynamically
exchanged between the master and slave nodes. The administrative preference is
used to bias the selection of the active link. If the preferred link is unable to be
initialized, this protocol will automatically select and activate the backup link. If
the backup link is activated, traffic will continue to be sent over the backup link
until the link fails or network management intervention reverts traffic back to the
primary link.
The slave node does not have administrative preference and will not bias on the
link selection process. Network management intervention to manually select and
activate the link will take place on the master node only.

Slave Node Operation

In a Resilient NNI configuration, the Bay Networks BayStream switch is
configured as a slave node and the other vendor's switch is configured as a master
node. In this document, only the slave node operations are discussed; the master
node operations are mentioned only where applicable to slave node operations.
115385-D Rev 01
Line cards other than HSSI
Dual port HSSI line cards
Resilient Master Mode operations
SVCs using FRF.10 signaling
Link management types other than Annex A
Transporting and/or mapping CUG information across the RNNI interface.
BayStream Multiservice Software Version 7.3
BayStream 7.3 Documentation Change Notice
15