This document provides a review of best practices for NX-OS upgrades on the Cisco MDS 9000 series switches. NX-OS release 5.2.x is used as an example throughout this document. NX-OS command syntax and DCNM-SAN GUI displays may vary slightly depending on the code. Impact on upgrade procedures may vary based on the current NX-OS release and advanced features running on the Cisco MDS SAN. Please review NX-OS release notes prior to upgrading to any code release. Verify that a backup has been completed for all Cisco MDS switch configurations prior to the activity.
This document is designed for NX-OS 5.2.x release. If your switch is running software that is earlier than Cisco NX-OS Release 5.0.x, you must upgrade to Release 5.0.x before you can upgrade to Release 5.2.x. For releases 3.3.2, 3.3.3 and 3.3.4x, upgrade to release 4.1.x or 4.2.x and then to release 5.0.x and so forth.
NX-OS Software Images
Each switch is shipped with the Cisco MDS NX-OS operating system for Cisco MDS 9000 Family switches. The Cisco MDS NX-OS software consists of two images: the kickstart image and the system image. To download new Cisco MDS 9000 Family software including Cisco NX-OS and Cisco DCNM management software, refer to the Storage Networking Software download site.
Preparing for NX-OS upgrade
Complete these steps during the week prior to the upgrade.
Step 1. Verify current Sup & Code. Use following commands
show module (verifies if new code will be compatible)
dir Bootflash://sup-active (verifies enough space on active supervisor for code)
dir bootflash://sup-standby (verifies enough space on backup supervisor for code)
Step 2. Download the code version required from Cisco website.
a) You must be logged in with your CCO account
b) Download both System and Kickstart images
c) Make sure to download code for each type of switch platform required. Make sure that Sup-1 vs Sup-2 code is downloaded from the results of the “show module” command.
d) Put code in <Server>\code\ folder on a central server
e) Rename code to short names. Examples (kick522a.bin, sys522a.bin)
f) Gather “show tech details” output from each switch.
Step 3. Clear any old code files off of supervisors (NOT current code level). Use following commands
Step 4. (T)ftp new code to each switch
a) “copy sftp://user@<IP Address>/code/***.bin bootflash:
b) Use password=”<password>”
c) dir bootflash: - make sure code is in there
d) Note: Perform this copy one switch at time, otherwise the FTP server may overload and consume more time.
e) Run install check command on each switch to verify code version works
show install all impact system bootflash:sys_code.bin kickstart bootflash:kick_code.bin
Steps before the Upgrade
Step 1. Log and Feature validation
a) Show log last 200 (to check for any dormant issues)
b) Show cfs lock (fix any current locks or clear them)
c) Show zone status (look at each line that has the word “session:” make sure it says ‘none’). If there is a lock, it must be cleared before proceeding.
Step 2. Backup syslog and ftp out to share
a) Show logging logfile >switchname.log
b) Show flogi database (write down summary total for each switch)
Hello Team We are going to implement the Cisco ACI Multi-Site solution between two sites. One of the main components of Multi-site is MSO (ACI Multi-Site orchestrator) which I found the "ACI-MSITE-VAPPL" part number for it. Based on the Cisco white p...
hello guys, We recently implemented VMM integration with AVE using vxlan as encap mode. Now we want to implement L4-L7 service graph and use it on the VMM domain. Is it possible to use L4-L7 service graph with vxlan? thanks,
Hello Team,When deploying AVE and configuring an EPG as in VXLAN mode (VM learned via Vxlan Encap), if we want to do epg extention (layer 2 extension) to a firewall, how to proceed? (we added static path to the Fw + Associate its physical dom) , but ...
When you create a VxLAN network in DCNM on the Advanced tab "L2 VNI Route-Target Both Enable" is available as a check box. At first I thought this had to do with Asymmetric vs Symmetric IRB modes, but playing around with it I noticed with both option...
I connected new two leafs 301,302 and configured vpc but when checking few commands like show vpc extended I can see consistency check not performed in one of the leaf (leaf 304) but not in leaf 303.i want to know why this error is appearing and how can i...