Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Upgrading an MX960 to Use the SCBE-MX

 

This topic describes how to upgrade your MX960, MX480, or MX240 router to use the SCBE-MX without taking the router offline. This “in-service” upgrade only works for MX routers with DPC, MS-DPC, MPC1, MPC2, or MPC3 line cards. If your MX router has another type of line card, you’ll need to take the router offline before you do the upgrade.

Note

Junos OS does not support in-service upgrades to the SCBE-MX on routers with an MX-MPC3E-3D or MX-MPC3-3D MPC. If your MX router has these MPCs, you’ll need to shutdown the system before you do the upgrade. An in-service upgrade can result in service disruption.

Before you do the upgrade, open a telnet session to the master Routing Engine CLI operational mode and issue the configure exclusive command. This command locks the configuration to prevent accidental changes during the upgrade process. .lock the current configuration there are no changes to the CLI during the upgrade process.

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.

Prepare for the Upgrade

Prior to upgrading to the SCBE-MX:

  1. Verify that the system runs Junos OS Release 11.4 or later by issuing the show version command on the master router. Here’s an example for the MX960:
    user@host> show version
    Note

    The SCBE-MX 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.

  2. Verify that SCB-MX boards are installed:
    user@host> show chassis hardware

    SCB-MX details are displayed as above, along with other hardware components.

  3. Establish console connections to both Routing Engines. You can use a telnet session to connect to the router console by issuing the <router name>-con command. For example, if the router name is juniper, you can connect to RE0 and RE1 consoles by issuing the telnet juniper-con and telnet juniper1-con commands.
  4. Ensure that graceful switchover (GRES), commit synchronize (required for nonstop 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.

  5. Set the upgrade flag on and start the SCB-MX upgrade by issuing the set chassis state cb-upgrade on command.
    user@host# configure
    user@host# set chassis state cb-upgrade on
    user@host# commit
  6. Determine the order to replace the existing SCB-MXs with upgraded ones. SCB 0, SCB 1, and SCB 2 are available for the MX960. SCB 0 is associated with RE0, SCB 1 is associated with RE1, and SCB 2 is the spare SCB. The SCB upgrade order for the MX960 is:
    • Upgrade the SCB in the Spare Slot 2 (SCB 2)

    • Upgrade the SCB in the Backup Routing Engine Slot 1 (SCB 1)

    • Upgrade the SCB in the Master Routing Engine Slot 0 (SCB 0)

    Note

    Do not add or remove any router hardware during the upgrade procedure.

Upgrade the SCB-MX in the Spare Slot 2 (SCB 2)

  1. Take the fabric plane offline by issuing the request chassis fabric plane 4 offline command.
  2. Verify that fabric plane 4 is offline by issuing the show chassis fabric summary command.
    user@host> show chassis fabric summary
  3. Take the next fabric plane offline by issuing the request chassis fabric plane 5 offline command, and then verify that the fabric plane is offline by issuing the command given in Step 2.
  4. Take the SCB-MX in slot 2 offline by issuing the request chassis cb offline slot 2 command.
  5. Verify that the control board is offline by issuing the show chassis environment cb 2 command:
    user@host> show chassis environment cb 2
  6. Attach an electrostatic discharge (ESD) grounding strap to your bare wrist, and connect the strap to one of the ESD points on the chassis.
  7. Remove and replace the SCB-MX in slot 2 on the router (SCB 2) with the SCBE. Use the procedure described in Replacing an MX960 SCB.
  8. Verify that the installation is successful and the SCBE is online:
    user@host> show chassis environment cb 2
  9. Verify that the fabric planes come online correctly by issuing the show chassis fabric summary command:
    user@host> show chassis fabric summary
  10. Verify the alarms:
    user@host> show chassis alarms

    Because only one SCB-MX has been upgraded, the alarm indicates that the SCBs are of mixed type. This alarm is cleared after all the control boards are upgraded.

Upgrade the SCB-MX in the Backup Routing Engine Slot 1 (SCB 1)

  1. Power down the backup Routing Engine from the master Routing Engine by issuing the request system power-off other-routing-engine command.
  2. Ensure that the Routing Engine is powered down by issuing the show chassis routing-engine 1 command. The slot of the Routing Engine may be 0 or 1, and is shown as 1 in this example:
    user@host> show chassis routing-engine 1

    Verify that the Current State is Present, which indicates that the Routing Engine is offline.

  3. Take the first fabric plane of the backup Routing Engine offline by issuing the request chassis fabric plane 3 offline command.
  4. Verify that the fabric plane is offline by issuing the show chassis fabric summary command.
    user@host> show chassis fabric summary

    Check if the state of plane 4 is Offline.

  5. Take the next fabric plane offline by issuing the request chassis fabric plane 2 offline command and verify that the fabric plane is offline by issuing the command in Step 4.
  6. Take the SCB-MX in slot 1 offline by issuing the request chassis cb offline slot 1 command.
  7. Verify that the SCB-MX is offline by issuing the show chassis environment cb 1 command:
    user@host> show chassis environment cb 1
  8. Attach an electrostatic discharge (ESD) grounding strap to your bare wrist, and connect the strap to one of the ESD points on the chassis.
  9. Remove and replace the offline SCB-MX on the router with the SCBE.
  10. Verify that the installation is successful and the SCB is online by issuing the show chassis environment cb 1 command:
    user@host> show chassis environment cb 1

    Other details, such as power, are also displayed along with the state.

  11. Verify that the fabric planes 2 and 3 come online correctly by issuing the show chassis fabric summary command:
    user@host> show chassis fabric summary
  12. Verify that the backup routing engine is back online by issuing the show chassis routing-engine 1 command:
    user@host> show chassis routing-engine 1

Upgrade the SCB-MX in the Master Routing Engine Slot 0 (SCB 0)

To upgrade the SCB-MX in the master Routing Engine slot:

  1. Ensure a Graceful RE Switchover (GRES) to gracefully switch between the master and backup Routing Engines, so that the backup RE becomes the master RE, by issuing the request chassis routing-engine master switch command.
  2. Log in to the new master Routing Engine after the switchover.
  3. Switch the configuration mode to ensure that you are still in configure exclusive mode by issuing the exit command and then the configure exclusive command, from the old master Routing Engine.
  4. Log in to the current master Routing Engine again and issue the configure exclusive command.
  5. Power down the backup Routing Engine from the master Routing Engine by issuing the request system power-off other-routing-engine command.
  6. Ensure that the Routing Engine is powered down by issuing the show chassis routing-engine 0 command. The slot of the Routing Engine may be 0 or 1, and is shown as 1 in this example:
    user@host> show chassis routing-engine 1

    Verify that the Current State is Present, which indicates that the Routing Engine is offline or powered down.

  7. Take the first fabric plane of the backup Routing Engine offline by issuing the request chassis fabric plane offline 1 command.
  8. Verify that the fabric plane is offline by issuing the show chassis fabric summary command.
    user@host> show chassis fabric summary

    Verify that the state of plane 1 is Offline.

  9. Take the next fabric plane offline by issuing the request chassis fabric plane offline 0 command and verify that the fabric plane is offline by issuing the command given in Step 2.
  10. Take the SCB-MX in slot 0 offline by issuing the request chassis cb offline slot 0 command.
  11. Verify that the control board is offline by issuing the show chassis environment cb 0 command:
    user@host> show chassis environment cb 0
  12. Attach an electrostatic discharge (ESD) grounding strap to your bare wrist, and connect the strap to one of the ESD points on the chassis.
  13. Remove and replace the offline SCB-MX on the router with the SCBE. Use the procedure described in Replacing an MX960 SCB.
  14. Verify that the installation is successful and the SCBE is online by issuing the show chassis environment cb 0 command:
    user@host> show chassis environment cb 0
  15. Verify that the fabric planes 0 and 1 come online correctly by issuing the show chassis fabric summary command:
    user@host> show chassis fabric summary
  16. Verify that the backup Routing Engine is back online by issuing the show chassis routing-engine 0 command:
    user@host> show chassis routing-engine 0
  17. Verify the alarms by issuing the show chassis alarms command:
    user@host> show chassis alarms

    The major alarm has changed from CB fabrics are of mixed types to CB fabric links require upgrade/training, as a SCB-MX requires training to change the link speed from 3G to 6G for the SCBE-MX. This alarm is displayed until the 3G to 6G link transition is completed.

Complete the SCBE-MX Upgrade

  1. Verify if there are any MPCs running at 3G instead of 6G:
    user@host> request chassis fabric upgrade-bandwidth info

    In this example, the results indicate that slot 0 does not support the upgrade and slot 1 needs upgrade.

    Note

    The SCBE line card supports only DPC, MS-DPC, MPC1, MPC2, and MPC3 line cards for the upgrade-bandwidth. If line cards that do not support the command option are present in the chassis during the SCB-MX to SCBE-MX upgrade, the request chassis fabric upgrade-bandwidth commands will return Upgrade not supported for the slot(s) that contain the unsupported line card(s).

  2. Upgrade the bandwidth of all MPCs by issuing the request chassis fabric upgrade-bandwidth fpc all command. If you want to control the MPC line card upgrade, go to Step 3.Caution

    Use this command only if you are not concerned with the slot upgrade order or if only one old MPC is present in the chassis. Running this command may result in a loss of traffic across that MPC. Using this method may increase that loss, as it does not consider any redundancy or graceful switchover strategies that you may have configured on the system.

  3. Issue the request chassis fabric upgrade-bandwidth fpc slot 1 command to upgrade the MPC in slot 1.
  4. Verify that the MPC is upgraded:
    user@host> request chassis fabric upgrade-bandwidth info
  5. Verify the fabric plane state for all MPCs:
    user@host> show chassis fabric summary
  6. Verify the state of MPCs:
    user@host> show chassis fabric fpcs

    Fabric plane details of all MPCs are similarly displayed.

  7. Verify if the show chassis fabric summary command output shows fabric planes in the 'check' state. This indicates that the fabric plane has an error. You can try to recover the fabric plane to normal operation by issuing the request chassis fabric plane <#> offline command, followed by the request chassis fabric plane <#> online command, where <#> equals the fabric plane in error.Note

    After you issue the request chassis fabric plane <#> offline and request chassis fabric plane <#> online commands, issue the show chassis fabric summary command to verify that the fabric plane errors are rectified and to verify the current state of the fabric planes.

  8. Verify if there are any major alarms:
    user@host> show chassis alarms

    In this example, the major alarms are no longer displayed, and the upgrade is successfully completed.

  9. Disable the upgrade configuration by issuing the set chassis state cb-upgrade off command and then the commit command.
  10. Disable the upgrade configuration by issuing the set chassis state cb-upgrade off command.
  11. You can delete the upgrade configuration by issuing the delete chassis state cb-upgrade command and then the commit command.Warning

    Deleting the chassis state cb-upgrade on configuration before disabling the SCB-MX upgrade using the set chassis state cb-upgrade off command can cause unexpected errors in the fabric.

  12. Verify the SCBE-MXs are installed by issuing the show chassis hardware command:
    user@host> show chassis hardware

    As shown in the example, the MX960 now has MX SCBEs.