Juniper MX960 Hardware Manual page 444

MX960 3D Universal Edge Router Hardware Guide
414
NOTE: Do not make other changes to the CLI during the entire upgrade
process. You can ensure that you will not make such changes by opening a
telnet session to the master RE CLI operational mode and issuing the
exclusive command. This command locks the configuration procedure.
NOTE: When you are upgrading an SCB to SCBE on a MX960 router with an
MPC3 installed in it, ensure that the Junos OS Release is 12.3 or later.
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
MX SCB
MX SCB
MX SCB
<router name>-con
and commands.
telnet juniper1-con
Copyright © 2017, Juniper Networks, Inc.
configure
command. For