{"id":1038,"date":"2013-03-06T20:25:37","date_gmt":"2013-03-06T20:25:37","guid":{"rendered":"http:\/\/www.kozeniauskas.com\/itblog\/?p=1038"},"modified":"2013-04-07T21:10:15","modified_gmt":"2013-04-07T20:10:15","slug":"nexus-upgrading-cisco-nexus-5000","status":"publish","type":"post","link":"http:\/\/www.kozeniauskas.com\/itblog\/2013\/03\/06\/nexus-upgrading-cisco-nexus-5000\/","title":{"rendered":"Nexus: Upgrading Cisco Nexus 5000"},"content":{"rendered":"

So here is how to upgrade Nexus 5000 series switch. In this instance I have 2 Nexus 5010 switches in vPC configuration as they are part of the Vblock. I will be upgrading them from 5.1(3)N1(1a) to 5.2(1)N1(1)
\nFirst of all, although upgrade procedure is pretty much the same, please always check with Cisco for latest upgrade guides:
\nhttp:\/\/www.cisco.com\/en\/US\/products\/ps9670\/prod_installation_guides_list.html<\/a><\/p>\n

For the upgrade to be done as quick as possible it is important to do some work before it, like downloading the files from Cisco, uploading them to switches and running checks.<\/p>\n

    \n
  1. Download Kickstart and System files from Cisco.com<\/li>\n
  2. Verify that you have enough space on the switch
    \ndir bootflash:
    \n    \"030613_2025_NexusUpgrad1.png\"<\/a>
    \n<\/em><\/li>\n
  3. Upload both files to the switch. In this case I used TFTP server:
    \ncopy tftp:\/\/x.x.x.x\/kickstart_or_system.bin bootflash:<\/em>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<=== replace x.x.x.x with TFTP server IP, kickstart_or_system.bin with your Kickstart or System file name.
    \n<\/em>type management<\/em> when asked to Enter vrf
    \n    \"030613_2025_NexusUpgrad2.png\"<\/a>
    \nNote: In Vblock upload files to both switches. Copy operation might take some time.<\/li>\n
  4. Once both Kickstart and System files are uploaded verify that the file size of both files is correct.
    \ndir bootflash:<\/em>
    \n    \"030613_2025_NexusUpgrad3.png\"<\/a><\/li>\n
  5. Now we need to run some pre upgrade checks which will show if there any problem that should be fixed before the upgrade can be started
    \nshow compatibility system bootflash:system.bin<\/em>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<=== replace system.bin with your System file name.
    \nYou should get No incompatible configurations<\/em> message
    \n    \"030613_2025_NexusUpgrad4.png\"<\/a><\/li>\n
  6. Next we to see the impact of the upgrade:
    \nshow install all impact kickstart kickstart.bin system system.bin\u00a0\u00a0\u00a0\u00a0<\/em>\u00a0\u00a0\u00a0\u00a0<=== replace kickstart.bin and system.bin with your Kickstart and System file names.
    \nThis procedure might look like a real upgrade but it only does all the checking
    \n    \"030613_2025_NexusUpgrad5.png\"<\/a>
    \nIt will take some time to complete. It must succeed at all steps and should show that upgrade is non-disruptive
    \n    \"030613_2025_NexusUpgrad6.png\"<\/a><\/li>\n
  7. Now check spanning-tree impact. Everything should pass
    \nshow spanning-tree issu-impact
    \n    \"030613_2025_NexusUpgrad7.png\"<\/a>
    \n<\/em><\/li>\n
  8. Check lacp impact
    \nshow lacp issue-impact<\/em>
    \n    \"030613_2025_NexusUpgrad8.png\"<\/a><\/li>\n
  9. There is also show fex<\/em> to verify that all fabric extenders are reachable but in the Vblock there are no extenders connected to the switches so this can be skipped.<\/li>\n
  10. Once steps 1 \u2013 9 are completed and all are OK you can proceed to upgrade.<\/li>\n
  11. Because this is Vblock and 2 switches are in vPC config you need to identify the primary one as the upgrade should be started from primary
    \nshow vpc role<\/em>
    \n    \"030613_2025_NexusUpgrad9.png\"<\/a><\/li>\n
  12. Start upgrade
    \ninstall all kickstart kickstart.bin system system.bin\u00a0\u00a0\u00a0\u00a0<\/em>\u00a0\u00a0\u00a0\u00a0<=== replace kickstart.bin and system.bin with your Kickstart and System file names.
    \n    \"030613_2025_NexusUpgrad10.png\"<\/a><\/li>\n
  13. Once prompted verify to continue by pressing y
    \n    \"030613_2025_NexusUpgrad11.png\"<\/a>
    \n<\/em><\/li>\n
  14. The upgrade will begin.
    \nIf you connected to switch remotely over SSH, you will lose connectivity after seeing Saving supervisor runtime state
    \n<\/strong><\/em>message as the switch is rebooting. This should take about 5 minutes. Ping it to find out when it is back online.
    \n    \"030613_2025_NexusUpgrad12.png\"<\/a><\/li>\n
  15. Login to the switch and check upgrade status. If upgrade went ok you should see that it was successful.
    \nshow install all status<\/em>
    \n    \"030613_2025_NexusUpgrad13.png\"<\/a><\/li>\n
  16. Verify version
    \nshow version<\/em>
    \n    \"030613_2025_NexusUpgrad14.png\"<\/a><\/li>\n
  17. Verify that everything is working as expected.
    \nUpgrade is complete<\/li>\n
  18. In Vblock once you’ve verified that primary switch is working fine, upgrade the secondary switch.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

    So here is how to upgrade Nexus 5000 series switch. In this instance I have 2 Nexus 5010 switches in vPC configuration as they are part of the Vblock. I will be upgrading them from 5.1(3)N1(1a) to 5.2(1)N1(1) First of all, although upgrade procedure is pretty much the same, please always check with Cisco for […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[380,451,452],"tags":[453,454,497,499,455,425,500],"_links":{"self":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts\/1038"}],"collection":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/comments?post=1038"}],"version-history":[{"count":5,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts\/1038\/revisions"}],"predecessor-version":[{"id":1045,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts\/1038\/revisions\/1045"}],"wp:attachment":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/media?parent=1038"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/categories?post=1038"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/tags?post=1038"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}