Categories

CUC (6) CUCM (28) Jabber (6) Python (2) Routing (3) Solarwinds Orion NPM (4) switching (1) Video (6) voice (3)

Tuesday, 29 November 2011

IOS upgrade on a Catalyst switch stack

I thought this would be worth a post, as a mucked around with this a bit before I got it right. First time I tried upgrading a 3 member 2960 stack,
I ended up with a stack not being a stack as the different members ran both the upgraded version as well as some stack memebers running the "old" IOS version.

Step 1: load the new IOS into flash

I personally prefer using Cerberus FTP server (use no ip ftp passive).

hostname#copy ftp://anonymous:cisco@10.2.2.100/c2960s-universalk9-mz.122-58.SE1.bin flash:/
Destination filename [c2960s-universalk9-mz.122-58.SE1.bin]?
Accessing ftp://anonymous:cisco@10.1.2.100/c2960s-universalk9-mz.122-58.SE1.bin...
Loading c2960s-universalk9-mz.122-58.SE1.bin !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 13245186/4096 bytes]


the destination is flash:/ which is the flash of the stack master.


Step 2: Copy IOS to all other stack members' flash

Rember that when a stack member boots up it has no knowledge of the stack and can therefore not refer to a master, as it assumes itself to be the stack master,
until proper election takes place. This means that each individual stack member must have the new IOS in its physical flash. (in this case c2960s-universalk9-mz.122-58.SE1.bin).



Hostname#copy flash:/c2960s-universalk9-mz.122-58.SE1.bin flash2:/c2960s-universalk9-mz.122-58.SE1.bin
Destination filename [c2960s-universalk9-mz.122-58.SE1.bin]?
Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
13245186 bytes copied in 128.335 secs (103208 bytes/sec)


By issueing this, the previously copied IOS image is copied to stack member 2 's flash. Do the same for all the other stack members.

Step 3: change the boot statement on each member

I had a 3 switch stack and issued:


hostname#boot system switch 1 flash:/c2960s-universalk9-mz.122-58.SE1.bin
hostname#boot system switch 2 flash:/c2960s-universalk9-mz.122-58.SE1.bin
hostname#boot system switch 3 flash:/c2960s-universalk9-mz.122-58.SE1.bin


Step 4: verify boot statement (show boot)

As one can see below all stack members point to the same IOS image and all switches have the image in their flash.

hostname#sh boot
BOOT path-list : flash:/c2960s-universalk9-mz.122-58.SE1.bin
Config file : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break : no
Manual Boot : no
HELPER path-list :
Auto upgrade : yes
Auto upgrade path :
NVRAM/Config file
buffer size: 524288
Timeout for Config
Download: 0 seconds
Config Download
via DHCP: disabled (next boot: disabled)
-------------------
Switch 2
-------------------
BOOT path-list : flash:/c2960s-universalk9-mz.122-58.SE1.bin
Config file : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break : no
Manual Boot : no
HELPER path-list :

Auto upgrade : no
Auto upgrade path :
-------------------
Switch 3
-------------------
BOOT path-list : flash:/c2960s-universalk9-mz.122-58.SE1.bin
Config file : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break : no
Manual Boot : no
HELPER path-list :
Auto upgrade : no
Auto upgrade path :


All that remains is a reboot and a sh ver

2 comments:

  1. This is brilliant, a great detailed account o fwhat to do, thank you. xx

    ReplyDelete
  2. Thank you! Although this is an old post, it still helped me today. I appreciate it!

    ReplyDelete