7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
System management
This method of availability has both advantages and disadvantages. Nonstop forwarding continues to
forward packets using the existing stale forwarding information during a failure. This may cause routing
loops and black holes; surrounding routers must adhere to separate extension standards for each protocol.
Each vendor must support protocol extensions for router interoperability.
6.2.1.2.2 Nonstop routing on 7210 SAS-R6 and 7210 SAS-R12
The Nonstop Routing (NSR) feature on 7210 SAS devices ensures that routing neighbors are unaware of
a routing process fault. If a fault occurs, a reliable and deterministic activity switch to the inactive control
complex occurs; the routing topology and reachability are not affected, even during routing updates. NSR
achieves HA through parallelization by maintaining up-to-date routing state information, at all times, on the
standby route processor. This is achieved independent of protocols or protocol extensions and provides a
more robust solution than graceful restart protocols between network routers.
The NSR implementation on the 7210 SAS routers supports all routing protocols. It allows existing
sessions (BGP, LDP, OSPF, and others) to be retained during a CFM or CPM switchover, including the
support for MPLS signaling protocols. No change is visible to the peers.
Protocol extensions are not required. There are no interoperability issues and defining protocol extensions
for each protocol is not required. Unlike nonstop forwarding and graceful restart, the forwarding information
in NSR is always up to date, which eliminates possible black holes or forwarding loops.
Traditionally, addressing HA issues has been patched through nonstop forwarding solutions. The NSR
implementation overcomes these limitations by delivering an intelligent, hitless failover solution. This
enables a carrier-class foundation for transparent networks that is required to support business IP services
backed by stringent SLAs. This level of HA support poses a major issue for conventional routers whose
architectural design limits or prevents them from implementing NSR.
6.2.1.3 CPM switchover on 7210 SAS-R6 and 7210 SAS-R12
During a switchover, system control and routing protocol execution are transferred from the active to the
standby CPM.
An automatic switchover may occur under the following conditions:
• a fault condition that causes the active CPM to crash or reboot
• the active CPM is declared down (not responding)
• online removal of the active CPM
A manual switchover may occur under the following conditions:
• To force a switchover from an active CPM to a standby, use the admin redundancy force-switchover
command. You can also use the config system switchover-exec and admin redundancy force-
switchover now CLI commands to configure a batch file that runs after a failover.
6.3 Temperature threshold alarm and fan speed
The following table lists the over-temperature thresholds for 7210 SAS devices.
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
251
SPACER TEXT
To Next Page
Loading...