In a part 1 we have seen how easy can be done upgrade on Cisco 7600 series router. With the minimal operations (copy/configure/reboot) box will be upgraded. Today, in a part 2 we will do the same for the other vendor's box :) So, here it is, our huge and powerful JUNIPER MX960!
JUNOS Upgrade Procedures on MX960 with Redundant RE-s
Obtain the needed JUNOS image from web.
Copy new JUNOS to RE-s:
user@ MX960-re0> file copy ftp://1.1.1.1/jinstall-11.4R7.5-domestic-signed.tgz re0:/var/tmp/jinstall-11.4R7.5-domestic-signed.tgz
user@ MX960-re0> file copy ftp://1.1.1.1/jinstall-11.4R7.5-domestic-signed.tgz re1:/var/tmp/jinstall-11.4R7.5-domestic-signed.tgz
Calculate file checksum:
user@ MX960-re0> file checksum md5 re0:/var/tmp/jinstall-11.4R7.5-domestic-signed.tgz
user@ MX960-re0> file checksum md5 re1:/var/tmp/jinstall-11.4R7.5-domestic-signed.tgz
If graceful Routing Engine switchover (GRES), or nonstop
active routing (NSR) is enabled when you initiate a software installation, the
software does not install properly. Make sure you issue the CLI delete chassis redundancy command when prompted. If
GRES is enabled, it will be removed with the redundancy
command. By default, NSR is disabled. If NSR is enabled, remove the
nonstop-routing statement from the [edit routing-options] hierarchy level to
disable it.
user@ MX960-re0# delete chassis redundancy
user@ MX960-re0# commit synchronize
To minimize interruption during the upgrade process, first
new JUNOS will be installed on backup RE (RE1). Previously unconfigured
redundancy statements will help in initiation of this process.
Take the snapshots for the rollback process if needed in
future:
user@ MX960-re0> request system snapshot
user@ MX960-re0> request routing-engine login other routing-engine
user@ MX960-re1> request system snapshot
Let’s login to RE1 from the active RE0. Same time it’s
recommended to be connected to RE1 directly via console:
user@ MX960-re0> request routing-engine login other-routing-engine
Start of the new software installation:
user@ MX960-re1>request system software add validate /var/tmp/jinstall-11.4R7.5-domestic-signed.tgz
After confirmation that new image is ready to be activated
RE1 will request to reboot itself:
user@ MX960-re1> request system reboot
Reboot the system? [yes, no] (no) yes
To abort the
installation, do not reboot your device, instead, finish the installation and
then issue the request system software delete
jinstall command. This is your last chance to stop the installation.
All the software is loaded when you reboot the RE.
Installation can take about 15-20 minutes. When the reboot is complete, the RE displays the login prompt.
While the software is being upgraded, the Routing Engine on which you are
performing the installation is not routing traffic.
Login to RE1 again and check the new version and system
health:
user@ MX960-re0> request routing-engine login other-routing-engine
user@ MX960-re1>show version and haiku
Hostname: MX960-re1
Model: mx960
JUNOS Base OS boot [11.4R7.5]
JUNOS Base OS Software Suite [11.4R7.5]
JUNOS Kernel Software Suite [11.4R7.5]
JUNOS Crypto Software Suite [11.4R7.5]
JUNOS Packet Forwarding Engine Support (M/T Common) [11.4R7.5]
JUNOS Packet Forwarding Engine Support (MX Common) [11.4R7.5]
JUNOS Online Documentation [11.4R7.5]
JUNOS Voice Services Container package [11.4R7.5]
JUNOS Border Gateway Function package [11.4R7.5]
JUNOS Services AACL Container package [11.4R7.5]
JUNOS Services LL-PDF Container package [11.4R7.5]
JUNOS Services PTSP Container package [11.4R7.5]
JUNOS Services Stateful Firewall [11.4R7.5]
JUNOS Services NAT [11.4R7.5]
JUNOS Services Application Level Gateways [11.4R7.5]
JUNOS Services Captive Portal and Content Delivery Container package [11.4R7.5]
JUNOS Services RPM [11.4R7.5]
JUNOS Services HTTP Content Management package [11.4R7.5]
JUNOS AppId Services [11.4R7.5]
JUNOS IDP Services [11.4R7.5]
JUNOS Services Crypto [11.4R7.5]
JUNOS Services SSL [11.4R7.5]
JUNOS Services IPSec [11.4R7.5]
JUNOS Runtime Software Suite [11.4R7.5]
JUNOS Routing Software Suite [11.4R7.5]
... hush puppies.... good beer ...
... the sea just before sunset ...
... living like a king ...
{master}
Once everything is fine on BACKUP RE1, all the controls
could be passed to it with the hand switching:
user@ MX960-re0> request chassis routing-engine master switch
Check RE-s:
user@ MX960-re0> show chassis routing-engine
Routing Engine status:
Slot 0:
Current state Backup
Election priority Backup
Temperature 36 degrees C / 96 degrees F
CPU temperature 40 degrees C / 104 degrees F
DRAM 3584 MB
Memory utilization 17 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 5 percent
Interrupt 0 percent
Idle 100 percent
Model RE-S-2000
Routing Engine status:
Slot 1:
Current state Master
Election priority Master
Temperature 37 degrees C / 98 degrees F
CPU temperature 40 degrees C / 104 degrees F
DRAM 3584 MB
Memory utilization 15 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 0 percent
Interrupt 0 percent
Idle 94 percent
Model RE-S-2000
{master}
There will be short interruption for the control plane to be
passed from master to backup re. (60-90 seconds).
Absolutely the same upgrade process will be performed on the
“old” master RE0.
user@ MX960-re1> request routing-engine login other-routing-engine
user@ MX960-re0>request system software add validate /var/tmp/jinstall-11.4R7.5-domestic-signed.tgz
user@ MX960-re0> request system reboot
Reboot the system? [yes, no] (no) yes
Check the version, health and routing engines states after
reboot, then request switchover of the control plane from RE1 to RE0.
user@ MX960-re1> request chassis routing-engine master switch
There will be short interruption for the control plane to be
passed from RE1 to RE0. (60-90 seconds).
Upon finalizing the process redundancy should be re-added to
the configuration. This can be done with the “rollback” or with the previously
saved part of configuration:
user@ MX960-re0# rollback 1 (in some cases there can be up to 6 rollback steps needed)
user@ MX960-re0# show | compare
user@ MX960-re0# commit synchronize
Be sure with the rollback check. Finally do the system
snapshots for the new JUNOS image.
user@ MX960-re0> request system snapshot
user@ MX960-re0> request routing-engine login other routing-engine
user@ MX960-re1> request system snapshot
PS: Redundancy config based on MX960:
user@ MX960-re0# show chassis redundancy
routing-engine 0 master;
routing-engine 1 backup;
failover {
on-loss-of-keepalives;
on-disk-failure;
}
graceful-switchover;
Enjoy new JUNOS image :)
No comments:
Post a Comment