Cisco Nexus 5596T model

[AndrewHow]

I have query about the version 6.0.2.N1.2.bin? Can I straight upgrade the version from 6.0.2.N1.2.bin to 7.1.5.N1.1.bin? Any command important command that I can run to check the VSAN and SAN setting on the customer nexus switches? I worry about after running the updated version and some command is deprecated from previous 6.0.2.N1.2.bin. Basically everyone know the show run and show tech is the way but the customer is confidential about their configuration file. Thanks guys!

Below is the current version running.

Software

  BIOS:      version 3.6.0

  loader:    version N/A

  kickstart: version 6.0(2)N1(2)

  system:    version 6.0(2)N1(2)

  Power Sequencer Firmware:

             Module 1: version v2.0

             Module 2: version v1.0

  Microcontroller Firmware:        version v1.0.0.2

  SFP uC:    Module 1: v1.1.0.0

  QSFP uC:   Module not detected

  BIOS compile time:       05/09/2012

  kickstart image file is: bootflash:///n5000-uk9-kickstart.6.0.2.N1.2.bin

  kickstart compile time:  3/14/2013 1:00:00 [03/14/2013 16:53:55]

  system image file is:    bootflash:///n5000-uk9.6.0.2.N1.2.bin

  system compile time:     3/14/2013 1:00:00 [03/14/2013 19:28:50]

Hardware

  cisco Nexus 5596 Chassis ("O2 32X10GBase-T + 16X10GE/Modular Supervisor")

  Intel(R) Xeon(R) CPU         with 8262944 kB of memory.

  Processor Board ID FOC1734071N

  Device name: BSC-N5K_1

  bootflash:    2007040 kB

Kernel uptime is 828 day(s), 15 hour(s), 12 minute(s), 8 second(s)

Last reset

  Reason: Unknown

  System version: 6.0(2)N1(2)

  Service

[Andrea Testino]

Hi Andrew,

If you read the 7.1(5)N1(1) Release Note's , you will notice that 6.0(2)N1(2) is not listed under the "current release" column that you can upgrade directly to 7.1(5) from. 

The proper upgrade path from 6.0(2)N1(2) would be the following (there are others):

6.0(2)N1(1) > 6.0(2)N2(7) > 7.0(8)N1(1) > 7.1(5)N1(1). 

This is derived from the Release Notes for the 6.x and 7.x release and looking at the "supported upgrade" tables. I'd read the caveats under the upgrade section very carefully to understand whether something is applicable to the environment or not.

Unsupported Upgrades on Nexus 5k/6k series tend to cause configuration loss - Cisco TAC may request a reload due to an unsupported upgrade on occasion if the switch's functionality is degraded due to an unsupported path being followed.

Hope that helps.

- Andrea 

[AndrewHow]

Thanks! andrea for information. Do you know what is the common command that is helpful to check all the SAN status and brief information. Appreciate for the reply and helps!

[Rick1776]

It depends on what you trying to look at for the SAN information.

You can do the following....

show interface brief (will show you the fc or vfc interfaces on the box)
show flogi database
show npv status (if npv is enabled)
show license (will show you the current license you have installed)
show fabric-mode
show running-config

[AndrewHow]

Thanks rick. 

[Rick1776]

Not a problem. Have a great day.

[AndrewHow]

Hi Andrea,

I have successfully upgrade from 6.0.1 to 7.1.5 version. But need some clarification, The VSAN FC port need to reboot again for FC port to be able to detect? I thought when upgraded the version it should be went smoothly, never thought of the VSAN FC port not detect on first boot only the second time then will only worked again.

[Rick1776]

Yes I’ve run into that before in the past when going for 6 to 7.