sfc option introduced for the TX Matrix Plus router
in JUNOS Release 9.6.
Description
For routers with multiple Routing Engines, control
which Routing Engine is the master.
Caution:
(Routing matrix based on the TX Matrix or TX Matrix
Plus routers only) Within the routing matrix, we recommend that all
Routing Engines run the same JUNOS Software release. If you run different
JUNOS releases on the Routing Engines and a change in mastership occurs
on any backup Routing Engine in the routing matrix, one or all T640
routers (in a routing matrix based on the TX Matrix router) or T1600
routers (in a routing matrix based on a TX Matrix Plus router) might
become logically disconnected from the TX Matrix router and cause
data loss. For more information, see the TX Matrix Router Hardware Guide or
the JUNOS High Availability Configuration Guide.
Note:
Successive graceful Routing Engine switchover
events must be a minimum of 240 seconds (4 minutes) apart after both
Routing Engines have come up.
If the router displays a warning message similar to “Standby
Routing Engine is not ready for graceful switchover. Packet Forwarding
Engines that are not ready for graceful switchover might be reset,”
do not attempt switchover. If you choose to proceed with switchover,
only the Packet Forwarding Engines that were not ready for graceful
switchover are reset. None of the FPCs should spontaneously restart.
We recommend that you wait until the warning no longer appears and
then proceed with the switchover.
Options
acquire — Attempt to
become the master Routing Engine.
release — Request that
the other Routing Engine become the master.
switch — Toggle mastership
between Routing Engines.
all-chassis — (TX Matrix
and TX Matrix Plus routers only) On a routing matrix composed of a
TX Matrix router and the attached T640 routers, switch mastership
on all the Routing Engines in the routing matrix. Likewise, on a routing
matrix composed of a TX Matrix Plus router and the attached T1600
routers, switch mastership on all the Routing Engines in the routing
matrix.
all-lcc — (TX Matrix
Plus routers only) Request to acquire mastership for all line-card
chassis (LCC).
lcc number — (TX Matrix and TX Matrix Plus routers only) On a TX
Matrix router, the T640 router (or LCC) that is connected to the TX
Matrix router (or switch-card chassis). On a TX Matrix Plus router,
the T1600 router (or LCC) that is connected to the TX Matrix Plus
router (or switch-fabric chassis). Replace number with a value from 0 through 3.
no-confirm — (Optional)
Do not request confirmation for the switch.
sfc — (TX Matrix Plus
routers only) TX Matrix Plus router (or switch-fabric chassis).
force — (Optional) Available
only with the acquire option. Force the change to a new master Routing
Engine.
Additional Information
Because both Routing Engines are always
running, the transition from one to the other as the master Routing
Engine is immediate. However, the changeover interrupts communication
to the System and Switch Board (SSB). The SSB takes several seconds
to reinitialize the Flexible PIC Concentrators (FPCs) and restart
the PICs. Interior Gateway Protocol (IGP) and BGP convergence times
depend on the specific network environment.
By default, the Routing Engine in slot 0 (RE0) is the master
and the Routing Engine in slot 1 (RE1) is the backup. To change
the default master Routing Engine, include the routing-engine statement at the [edit chassis redundancy] hierarchy
level in the configuration. For more information, see the JUNOS System Basics Configuration Guide
To have the backup Routing Engine become the master Routing
Engine, use the request chassis routing-engine master switch command. If you use this command to change the master and then restart
the chassis software for any reason, the master reverts to the default
setting.
Note:
Although the configurations on the two Routing Engines
do not have to be the same and are not automatically synchronized,
we recommend making both configurations the same.
warning: Traffic will be interrupted while the PFE is re-initialized
warning: The other routing engine's file system could be corrupted
Reset other routing engine and become master ? [yes,no] (no)
warning: Traffic will be interrupted while the PFE is re-initialized
Toggle mastership between Routing Engines ? [yes,no] (no) yes
Resolving mastership...
Complete. The other Routing Engine becomes the master.
Switch mastership back to the local Routing Engine:
warning: Traffic will be interrupted while the PFE is re-initialized
Toggle mastership between routing engines ? [yes,no] (no) yes
Resolving mastership...
Complete. The local routing engine becomes the master.
