Looks good, right lets go with the upgrade.
Jloader first. The ftp load command uses the syntax 'request system software add ftp://10.10.15.23/jloader-ex-3242-11.3I20110326_0802_hmerge-signed.tgz'. This is basically saying we're using FTP to get the image and that the image is located on server with IP address 10.10.15.23. Without stating a username and password int he form ftp://username:password@ the JunOS parser will use the default username of 'anonymous' with no password. Some FTP servers come with built in anonymous support...FileZilla needs you to create a user called 'anonymous' with the password checkbox unchecked. HEre is the process:
Each node in the cluster will be upgraded in turn until it finishes and returns you back tot he prompt:
The FileZilla management console shows you the whole process as the file is pulled back to the cluster master node. Here is a brief screen shot of the download:
Right, thats the jloader upgrade bit applied (but not yet active until we reboot. To save time we're now going to upgrade the firmware so that we only do one reboot. Here is the process and remember, this is a 4 node cluster as shown by the fpc0,1,2,3. If you have a larger node number then your output will be different.
So, just like the man said 'A reboot is required to install the software'. Let us oblige...
It took about 5 minutes to come around again, I logged in and checked the firmware versions and loader.
Thats OK now I checked the state of the partitions
Looks like I have two partitions there active/backup....all looking pretty sweet. Lets get some more information on the state of those partitions...detail?...nah thats what they would expect you to do lets look at the snapshot...
We're upgraded, we've got two healthy partitions...just need to wait for a failure now to see it automatically fix itself...but I won't wish for that. I think one question we're all asking is how do I find out if there has been a partition failure if it fixes itself?
Well you've got console logs, syslog and SNMP...take your pick. From the management port you will see
WARNING: THIS DEVICE HAS BOOTED FROM THE BACKUP JUNOS IMAGE
You can of course always look at the chassis alarms.
user@switch> show chassis alarms
1 alarms currently active
Alarm time Class Description
2011-02-17 05:48:49 PST Minor Host 0 Boot from backup root
Thank you for reading and may all of your upgrades be as sweet.
First things first, lets kill off the VCP ports to disable the VC traffic.
Now go into config mode by typing ‘configure’. and then we’ll load the factory default settings.
Before we can commit the blank configuration we need to set the root password...it won’t save without it...give it a go if you want.
OK so now commit the blank configuration
Back into EXEC mode we’ll take a look at the new cluster status. Note we can’t see the other node because the VCP ports are disabled.
Lets run through the same process on the other node and commit. Now back in EXEC mode we turn the VCP ports back on. By NOT putting the keyword ‘disable’ on the end they are enabled...I know thats a bit poor but there you go.
> request virtual-chassis vc-port set interface vcp-0
> request virtual-chassis vc-port set interface vcp-1
So now we check the status of the node...all good. We have a Master and Backup in a two node cluster with FPC 0 and FPC1. The mastership priorities are both the default of 128.