JUNOS High Availability

Chapter 8. JUNOS Post-Upgrade Verifications

Congratulations! If you are reading this chapter, you must have followed the pre-upgrade procedures in Chapter 6 and the painless software upgrade recommendations in Chapter 7. You have:

• Identified an appropriate JUNOS release based on current and future network requirements and on the contents of the release notes for that revision.

• Confirmed that the JUNOS release is compatible with your network hardware.

• Formulated a strategy and timeline for rolling the new JUNOS out to the target devices in the network.

• Checked the configuration of the target devices to make sure the proper configuration elements are in place to take advantage of hardware component redundancies and In-Service Software Upgrade (ISSU) features where available.

• Prepared for the upgrade by capturing and storing configuration and state information for each device.

• Downloaded a copy of the new JUNOS release and, using the provided MD5 hash, prepositioned the image on the target chassis.

• Just prior to the upgrade, used Interior Gateway Protocol (IGP)-specific overload bits, metrics adjustments, and virtual IP (VIP) ownership changes to make the target chassis less desirable to transit traffic.

• Confirmed that traffic was indeed following an alternate path through the network.

• Executed the request system software add command to load the new operating system and rebooted the routing engines (REs) as needed.

• Did all this with minimal traffic loss during your allocated maintenance window, ...