Juniper MX960 Hardware Manual page 459

Copyright © 2017, Juniper Networks, Inc.
TIP: To prevent traffic loss during the upgrade process, we recommend that
you operate the line cards at 50% line rate. This 50% limit must be
maintained per PFE on each line card.
To prepare the MX960 router for the MX SCBE upgrade:
Verify that the system runs Junos OS Release 11.4 or later by issuing the show version
1.
command on the master router.
user@host> show version
Model: mx960
Junos Base OS Software Suite [11.4-20110530];
NOTE: The MX SCBE is supported only in Junos OS Release 11.4 or later.
The latest software ensures a healthy system—that is, Routing Engines, control boards,
and FPCs—before the upgrade.
Verify that MX SCB boards are installed by issuing the show chassis hardware
2.
command.
user@host> show chassis hardware
Item Version Part Number Serial Number Description
CB0 REV 07 710-021523 ABBC8281
CB1 REV 07 710-021523 ABBC8323
CB2 REV 07 710-021523 ABBD1410
SCB details are displayed as above, along with other hardware components.
Establish console connections to both Routing Engines. You can use a telnet session
3.
to connect to the router console by issuing the
example, if the router name is juniper, you can connect to RE0 and RE1 consoles by
issuing the
telnet juniper-con
Ensure that graceful switchover (GRES), commit synchronize (required for nonstop
4.
routing), and nonstop routing (NSR) are enabled or configured by running the set
chassis redundancy graceful-switchover, set system commit synchronize, set
routing-options nonstop-routing commands.
NOTE: These commands are mandatory for this upgrade and may be
removed, if desired, after the upgrade.
Set the upgrade flag on and start the SCB upgrade by issuing the
5.
cb-upgrade on command.
Chapter 27: Replacing Switch Fabric Components
MX SCB
MX SCB
MX SCB
<router name>-con
and commands.
telnet juniper1-con
command. For
set chassis state
429