Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation
Table of Contents
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Effect of Taking the MX960 Host Subsystem Offline

    The host subsystem is taken offline and brought online as a unit. Before you replace an SCB or a Routing Engine, you must take the host subsystem offline. The host subsystem is hot-pluggable.

    Normally, if two host subsystems are installed in the router, Routing Engine 0 (RE0) functions as the master and Routing Engine 1 (RE1) functions as the backup. You can remove the backup host subsystem (or either of its components) without interrupting the functioning of the router. If you take the master host subsystem offline, the backup host subsystem becomes the master (the router might reboot, depending on your configuration). If the router has only one host subsystem, taking the host subsystem offline causes the router to shut down. The effect of taking the master host subsystem offline varies depending on your configuration of high availability features.

    Table 1 explains the effect of taking the host subsystem offline.

    Table 1: Effect of Taking the Host Subsystem Offline

    Type of Host Subsystem

    Effect of Taking the Host Subsystem Offline

    Nonredundant host subsystem

    The router shuts down.

    Backup host subsystem

    The functioning of the router is not interrupted. The backup host subsystem is hot-removable and hot-insertable.

    Master host subsystem

    The backup host subsystem becomes the master. The backup Routing Engine assumes Routing Engine functions. The master host subsystem is hot-pluggable. Removal or failure of the master Routing Engine affects forwarding and routing based on the high availability configuration:

    • Dual Routing Engines without any high availability features enabled—Traffic is interrupted while the Packet Forwarding Engine is reinitialized. All kernel and forwarding processes are restarted. When the switchover to the new master Routing Engine is complete, routing convergence takes place and traffic is resumed.
    • Graceful Routing Engine switchover (GRES) is enabled—Graceful Routing Engine switchover preserves interface and kernel information. Traffic is not interrupted. However, graceful Routing Engine switchover does not preserve the control plane. Neighboring routers detect that the router has restarted and react to the event in a manner prescribed by individual routing protocol specifications. To preserve routing without interruption during a switchover, graceful Routing Engine switchover must be combined with nonstop active routing.
    • Nonstop active routing is enabled (graceful Routing Engine switchover must be configured for nonstop active routing to be enabled)—Nonstop active routing supports Routing Engine switchover without alerting peer nodes that a change has occurred. Nonstop active routing uses the same infrastructure as graceful Routing Engine switchover to preserve interface and kernel information. However, nonstop active routing also preserves routing information and protocol sessions by running the routing protocol process (rpd) on both Routing Engines. In addition, nonstop active routing preserves TCP connections maintained in the kernel.
    • Graceful restart is configured—Graceful restart provides extensions to routing protocols so that neighboring helper routers restore routing information to a restarting router. These extensions signal neighboring routers about the graceful restart and prevent the neighbors from reacting to the router restart and from propagating the change in state to the network during the graceful restart period. Neighbors provide the routing information that enables the restarting router to stop and restart routing protocols without causing network reconvergence. Neighbors are required to support graceful restart. The routing protocol process (rpd) restarts. A graceful restart interval is required. For certain protocols, a significant change in the network can cause graceful restart to stop.

    Note: Router performance might change if the backup Routing Engine's configuration differs from the former master's configuration. For the most predictable performance, configure the two Routing Engines identically, except for parameters unique to each Routing Engine.

    To configure Routing Engine-specific parameters and still use the same configuration on both Routing Engines, include the appropriate configuration statements under the re0 and re1 statements at the [edit groups] hierarchy level and use the apply-groups staement. For instructions, see the Junos OS Administration Library for Routing Devices.

    To configure Routing Engine-specific parameters and still use the same configuration on both Routing Engines, include the appropriate configuration statements under the re0 and re1 statements at the [edit groups] hierarchy level and use the apply-groups staement. For instructions, see the Junos OS Administration Library for Routing Devices.

    Note: For information about configuring graceful Routing Engine switchover, graceful restart, and nonstop active routing, see the Junos OS High Availability Library for Routing Devices.

    Note: The first supported release for both graceful Routing Engine switchover and nonstop active routing on the router is Junos OS Release 9.0. Graceful restart software requirements depend on the routing protocols configured on the router. For the minimum software requirements for graceful restart, see the Junos OS High Availability Library for Routing Devices.

     

    Related Documentation

     

    Published: 2014-03-25

    Previous Page Next Page