Ensure GRES and NSR are disabled
1. Log in to the primary Routing Engine’s console
2. From the configuration mode, disable nonstop active routing (NSR):
{master}[edit]
mx304# delete routing-options nonstop-routing 3. Disable nonstop-bridging if it is enabled
{master}[edit]
mx304# delete protocols layer2-control nonstop-bridging4. Disable Routing Engine redundancy if enabled
{master}[edit]
mx304# (delete | deactivate) chassis redundancy graceful-switchover5. Commit these changes to both routing engines
{master}[edit]
mx304# commit synchronize
re0:
configuration check succeeds
re1:
commit complete
re0:
commit complete1. Still from the Master RE, request a software upgrade for the Backup RE
mx304> request vmhost software add re1 /tmp/junos-vmhost-install-mx-x86-64-23.2R1.13.tgz2. Once the upgrade is complete, the system will tell you to reboot the Backup RE. (Optionally, add reboot to the request system software add to automatically reboot)
request system reboot other-routing-engine3. Once re1 is online again, check version on it to ensure it upgraded
show version invoke-on other-routing-engine1. Transfer routing control from the primary to the backup Routing Engine (the one we just upgraded)
request chassis routing-engine master switch2. Verify that the Routing Engine in slot 1 is now the primary Routing Engine
show chassis routing-engine1. Check for a previous FW version installed on the router
mx304> show version
...
JUNOS jfirmware [20240515.054255_builder_junos_234_r2]Look for a line beginning with JUNOS jfirmware. If it does exist, there is a previous fw version installed on the router.
2. Request the system delete the previous firmware version
mx304> request system software delete jfirmware
...
Package jfirmware-x86-32-23.4R2.5 is deactivate3. Verify the previous firmware has been removed by ensuring the same jfirmware line is not present when running show version