Nexus 5k and N2k fabric extender
Current Version: 6.1(2)
Target Version: 6.2(14)
Multihomed vs Singlehomed upgrade
- Connect to physical device via console cable.
- Pre-installation test
- Follow MOP of Dimension Data.
- Once all the requirement, image etc. are ready you can proceed to upgrade.
###DELETE & UPLOAD IMAGE ON NEXUS5K
S1(A)#copy tftp: bootflash:
S1(A)#Name: (Kickstart / System filename.bin)
S1(A)#dir | Include .bin (Select the unused file.)
Dir | include .bin
SAVE: copy running start
###VERIFYING UPLOAD ED KICKSTART AND SYSYEM
S1(A)#show file bootflash:\\kickstart.bin md5sum
Compare the output command on your md5 document. If there’s a different with the output and the document we need to repeat the upload process.
Dir | I .bin
Show vpc role
###KICKSTART & SYSTEM INSTALLATION (on privilege mode)
S1(A)#install all kickstart bootflash:name system bootflash:name
S1(A)#do you want to continue y/n: Y
After N5k up-gradation process all it’s Fex will be transferred to standby N5k because all fex’s are using the old version.
Also VPC peer link will be in down state because of version mismatch.
On N5k upgrade process the parent send the updated version to all Fex’s.
### Activating FEX new installed version
Now we only have 2 fex # 1 and 2
! We need to reload all fex one at a time
N5k(S)#reload fex 1
N5k(S)#reload fex 2
We reload the dex so we can activate the newer version.
After reload all fex will transfer to the active and the updated one.
On N5k Standby lets change the boot and kickstart version on global config
N5k-S(conf)#boot system bootflash:name
N5k-S(conf)#boot kickstart bootflash:name
Save: Copy run start
Verify N5K Active fex if all online.
#show vpc role
Now if FEX on active N5k is all online we can now reload the N5k Standby.
After the boot process verify the ff.
#show vpc role
Now all N5k and its fex has been upgraded. VPC Link also established.
- Installed different version or path on N5k.
A: All current configuration will be affected and worse case will be erase. So that why we need to backup the existing images and configuration so that we can do rollback in-cased we encountered this issue.