JUNOS upgrade on MX960 platform.
Recently I have been participating in project where we had to upgade few big boxes in the network. I have been upgrading Alcatel SR7750 TiMOS, Juniper MX960 JunOS and few Cisco boxes.
Recently I have been participating in project where we had to upgade few big boxes in the network. I have been upgrading Alcatel SR7750 TiMOS, Juniper MX960 JunOS and few Cisco boxes.
1.
First step is to upload new version of OS onto the
primary RE0 and backup RE1.
2.
Check that you have enough space at compact flash.
Needs to have more than 1GB
root> show system storageFilesystem Size Used Avail Capacity Mounted on/dev/ad0s1a 3.5G 484M 2.8G 14% /devfs 1.0K 1.0K 0B 100% /dev/dev/md0 76M 76M 0B 100% /packages/mnt/jbase/dev/md1 27M 27M 0B 100% /packages/mnt/jkernel-14.1R1.10/dev/md2 127M 127M 0B 100% /packages/mnt/jpfe-M320-14.1R1.10
2.1
Ensure that new candidate of Junos is loaded on both
RE
file copy ftp://username:root@ftp/JUNOS/NEW_JunOS /var/tmp/NEW_JunOS
file copy /var/tmp/NEW_JunOS re0:/var/tmp/NEW_JunOS
file copy /var/tmp/NEW_JunOS re1:/var/tmp/NEW_JunOS
file list detail /var/tmp/
file list detail re0:/var/tmp
file list detail re1:/var/tmp
file checksum md5 /var/tmp/NEW_JunOS
file checksum md5 re0:/var/tmp/NEW_JunOS
file checksum md5 re1:/var/tmp/NEW_JunOS
2.2
Generate MD5
checksum against the file downloaded. Compare this to the MD5 checksum file
found on the Juniper website and ensure that they are the identical.
root> file checksum md5 /var/tmp/NEW_JunOS
MD5 (/var/tmp/NEW_JunOS) = 983542e9ffd83a4c88c35c7504f8ef974
2.3
Login to the backup
RE and copy new JunOS file :
root> request routing-engine login re1
or
root> request routing-engine login other routing-engine
2.4
Generate again MD5
on RE1 and compare checksum with the one originated on RE0
root> file checksum md5 /var/tmp/NEW_JunOS
MD5 (/var/tmp/NEW_JunOS) = 983542e9ffd83a4c88c35c7504f8ef974
2.5
Do backup of your
current system just to make sure that if something go wrong you will be able to
recover stable system:
MASTER
root> request system snapshot
BACKUP
root> request routing-engine login other routing-engine
root> request system snapshot
3. Perform JunOS upgrade on RE1 (backup Routing Engine)
Currently our
box is running system from RE0. We can perform JunOS upgrade on RE1 without
service affecting. To install new system on RE1 we need to be sure that we are
connected to correct RE.
To check that
you need to type :
root> show chassis routing-engineRouting Engine status:Slot 0:Current state MasterElection priority MasterTemperature 30 degrees C / 86 degrees FCPU temperature 29 degrees C / 84 degrees FDRAM 8159 MB (8192 MB installed)Memory utilization 16 percentCPU utilization:User 1 percentBackground 0 percentKernel 1 percentInterrupt 1 percentIdle 97 percentModel RE-S-1800x2Serial ID 9009100646Start time 2014-09-19 01:04:46 BSTUptime 732 days, 11 hours, 54 minutes, 35 secondsLast reboot reason Router rebooted after a normal shutdown.Load averages: 1 minute 5 minute 15 minute0.00 0.00 0.00Routing Engine status:Slot 1:Current state BackupElection priority BackupTemperature 29 degrees C / 84 degrees FCPU temperature 30 degrees C / 86 degrees FDRAM 8159 MB (8192 MB installed)Memory utilization 29 percentCPU utilization:User 17 percentBackground 0 percentKernel 16 percentInterrupt 3 percentIdle 64 percentModel RE-S-1800x2Serial ID 9009100620Start time 2014-09-19 00:45:58 BSTUptime 732 days, 12 hours, 13 minutes, 36 secondsLast reboot reason Router rebooted after a normal shutdown.Load averages: 1 minute 5 minute 15 minute0.47 0.51 0.48{master}root>
If not please
login to BACKUP RE using :
root> request routing-engine login other routing-engine
Perform
upgrade on Backup RE1 and reboot RE1:
root> request system software add /var/tmp/NEW_JunOSroot> request system reboot
4. Perform JunOS upgrade on RE0 (MASTER Routing Engine)
First login
to the MASTER :
root> request chassis routing-engine master switch
Perform
upgrade on Master RE0 and reboot RE0:
root> request system software add /var/tmp/NEW_JunOSroot> request system reboot
5. Check version
After reboot
of the master RE0 you should have the same version on both Routing Engine.
root> show chassis routing-engine
Routing Engine status:
Slot 0:
Current state Backup
Election priority Master (default)
Routing Engine status:
Slot 1:
Current state Master
Election priority Backup (default)
In one of my case output was like this :
root> show chassis routing-engine
Routing Engine status:
Slot 0:
Current state Backup
Election priority Master (default)
Routing Engine status:
Slot 1:
Current state Master
Election priority Backup (default)
root> show version invoke-on all-routing-engines
re0:
-------------------------------------------------------------------
Hostname: root_lab
Model: mx960
JUNOS Base OS boot [12.3R4-S4]
JUNOS Base OS Software Suite [12.3R4-S4]
JUNOS 64-bit Kernel Software Suite [12.3R4-S4]
JUNOS Crypto Software Suite [12.3R4-S4]
JUNOS Packet Forwarding Engine Support (M/T/EX Common) [12.3R4-S4]
JUNOS Packet Forwarding Engine Support (MX Common) [12.3R4-S4]
JUNOS Online Documentation [12.3R4-S4]
JUNOS Services AACL Container package [12.3R4-S4]
JUNOS Services Application Level Gateways [12.3R4-S4]
JUNOS AppId Services [12.3R4-S4]
JUNOS Border Gateway Function package [12.3R4-S4]
JUNOS Services Captive Portal and Content Delivery Container
package [12.3R4-S4]
JUNOS Services HTTP Content Management package [12.3R4-S4]
JUNOS IDP Services [12.3R4-S4]
JUNOS Services LL-PDF Container package [12.3R4-S4]
JUNOS Services NAT [12.3R4-S4]
JUNOS Services PTSP Container package [12.3R4-S4]
JUNOS Services RPM [12.3R4-S4]
JUNOS Services Stateful Firewall [12.3R4-S4]
JUNOS Voice Services Container package [12.3R4-S4]
JUNOS Services Example Container package [12.3R4-S4]
JUNOS Services SSL [12.3R4-S4]
JUNOS Services Crypto [12.3R4-S4]
JUNOS Services IPSec [12.3R4-S4]
JUNOS Runtime Software Suite [12.3R4-S4]
JUNOS platform Software Suite [12.3R4-S4]
JUNOS Routing Software Suite [12.3R4-S4]
JUNOS AIS Script Suite [4.0R2.1]
re1:
-------------------------------------------------------------------
Hostname: root_lab
Model: mx960
JUNOS Base OS boot [12.3R4-S4]
JUNOS Base OS Software Suite [12.3R4-S4]
JUNOS 64-bit Kernel Software Suite [12.3R4-S4]
JUNOS Crypto Software Suite [12.3R4-S4]
JUNOS Packet Forwarding Engine Support (M/T/EX Common) [12.3R4-S4]
JUNOS Packet Forwarding Engine Support (MX Common) [12.3R4-S4]
JUNOS Online Documentation [12.3R4-S4]
JUNOS Services AACL Container package [12.3R4-S4]
JUNOS Services Application Level Gateways [12.3R4-S4]
JUNOS AppId Services [12.3R4-S4]
JUNOS Border Gateway Function package [12.3R4-S4]
JUNOS Services Captive Portal and Content Delivery Container package [12.3R4-S4]
JUNOS Services HTTP Content Management package [12.3R4-S4]
JUNOS IDP Services [12.3R4-S4]
JUNOS Services LL-PDF Container package [12.3R4-S4]
JUNOS Services NAT [12.3R4-S4]
JUNOS Services PTSP Container package [12.3R4-S4]
JUNOS Services RPM [12.3R4-S4]
JUNOS Services Stateful Firewall [12.3R4-S4]
JUNOS Voice Services Container package [12.3R4-S4]
JUNOS Services Example Container package [12.3R4-S4]
JUNOS Services SSL [12.3R4-S4]
JUNOS Services Crypto [12.3R4-S4]
JUNOS Services IPSec [12.3R4-S4]
JUNOS Runtime Software Suite [12.3R4-S4]
JUNOS platform Software Suite [12.3R4-S4]
JUNOS Routing Software Suite [12.3R4-S4]
{master}
Root>
Post a Comment