Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Unified ISSU Process on the TX Matrix Plus Router

Points to Remember

• The master Routing Engine and backup Routing Engine must be running the same software version before you can perform a unified ISSU.
• You cannot take any PICs online or offline during a unified ISSU.
• You can verify the unified ISSU-compatibility of the software, hardware, and the configuration on a device by issuing the request system software validate in-service-upgrade command. This command runs the validation checks, and shows whether the operating system, device components, and configurations are ISSU compatible or not. For more information about the request system software validate in-service-upgrade command, see .request system software validate-in-service-upgrade.
• Unicast RPF-related statistics are not saved across a unified ISSU, and the unicast RPF counters are reset to zero during a unified ISSU.

Note: The scale supported on T640-FPC2-E, T640-FPC2-E2, T640-FPC3-E, and T640-FPC3-E2 Flexible Port Concentrators (FPCs) is less than that supported on T640-FPC1-ES, T640-FPC2-ES, T640-FPC3-ES, T1600-FPC4-ES, and T640-FPC4-1P-ES FPCs due to differences in hardware configuration. Therefore, when unified ISSU is performed, if the configured scale on any of the FPC is more than what is supported on that FPC, FRU upgrade of that FPC fails. To check the current hardware configuration of an FPC, run the show chassis fpc operational command.

• Juniper Networks Operating System, which provides system control and all the features and functions of the Juniper Networks router that executes in the Routing Engines.
• Juniper Networks Packet Forwarding Engine, which supports the high-performance traffic forwarding and packet handling capabilities.
• Interface control.

Performing Unified ISSU

1. Enable graceful Routing Engine switchover (GRES) and nonstop active routing (NSR). Verify that the Routing Engines and protocols are synchronized.
2. Download the new software package from the Juniper Networks Support website and then copy the package to the router.
3. Issue the request system software in-service-upgrade command on the master Routing Engine.

1. The management process (mgd) on the master Routing Engine of the TX Matrix Plus router (global master) checks whether NSR and GRES are enabled in the current configuration.
2. After successful validation of NSR and GRES configuration, the management process copies the new image to the backup Routing Engines on the TX Matrix Plus router and the connected LCC.
3. The kernel synchronization process (ksyncd) on the backup Routing Engines synchronizes the kernel on the backup Routing Engines with that of the master Routing Engines.
4. The backup Routing Engines are upgraded with the new software and are rebooted. After rebooting, the backup Routing Engines are once again synchronized with the global master Routing Engine.
5. The unified ISSU control moves from the management process to the chassis process (chassisd). The chassis process informs the software processes about the unified ISSU and waits for responses from various software processes.
6. After receiving messages from the software processes indicating that the processes are ready for unified ISSU, the chassis process on the global master Routing Engine sends messages to the chassis process on the routing nodes (TX Matrix Plus router or its connected LCC) to start the unified ISSU.
7. The chassis process on the router sends ISSU_PREPARE messages to the field replaceable units (FRUs), such as FPC and intelligent PICs.
8. On receiving an ISSU_PREPARE message, the Packet Forwarding Engines save the current state information and download the new software image from the backup Routing Engines. Next, each Packet Forwarding Engine sends ISSU_READY messages to the chassis process.
9. On receiving an ISSU_READY message from the Packet Forwarding Engines, the chassis process sends an ISSU_REBOOT message to the FRUs. While the upgrade is in progress, the FRUs keep sending ISSU_IN_PROGRESS messages to the chassis process on the routing nodes. The chassis process on each router, in turn, sends an ISSU_IN_PROGRESS message to the chassis process on the global master Routing Engine.
10. After the reboot, the Packet Forwarding Engines restore the saved state information and connect back to the router; the chassis process on each router sends an ISSU_READY message to the chassis process on the global master Routing Engine. The ISSU_READY message from the chassis process on the router indicates that the unified ISSU is complete on the FRUs.
11. The unified ISSU control moves back to the management process on the global master Routing Engine.
12. The management process initiates Routing Engine switchover on the master Routing Engines.
13. Routing Engine switchover occurs on the TX Matrix Plus router and the connected LCC.
14. After the switchover, the FRUs connect to the new master Routing Engines, and the chassis manager and PFE manager on the connected LCC’s FRUs connect to the new master Routing Engines on the connected LCC.
15. The management process on the global master Routing Engine initiates the upgrade process on the old master Routing Engines on the connected LCC.
16. After the old master Routing Engines on the connected LCC are upgraded, the management process initiates the upgrade of the old global master Routing Engine, that is, the old master Routing Engine on the TX Matrix Plus router.
17. After a successful unified ISSU, the old master Routing Engine on the TX Matrix Plus router and the connected LCC are rebooted.