Two system version displayed on sh version on nexus 5000

[hi.sadiki]

Hi Guys,

Need your help please.

Does any one knows why do we see two system version on nexus 5000. I colored it RED.

When upgrade, which one can i Upgrade ? the first ? or the second ? or both ?

Software
  BIOS:      version 3.0.0
  loader:    version N/A
  kickstart: version 7.0(6)N1(1)
  system:    version 7.0(6)N1(1)
  Power Sequencer Firmware:
             Module 1: version v1.0
  Fabric Power Sequencer Firmware: Module 1: version v2.0
  Microcontroller Firmware:        version v0.0.0.44
  QSFP Microcontroller Firmware:   
             Module 1: v2.0.0.0
  SFP Microcontroller Firmware:   
             Module 1: v1.1.0.0
  BIOS compile time:       09/22/2014
  kickstart image file is: bootflash:///n6000-uk9-kickstart.7.0.6.N1.1.bin
  kickstart compile time:  4/7/2015 4:00:00 [04/07/2015 19:05:44]
  system image file is:    bootflash:///n6000-uk9.7.0.6.N1.1.bin
  system compile time:     4/7/2015 4:00:00 [04/07/2015 19:07:37]


Hardware
  cisco Nexus 56128P Chassis ("Nexus 56128P Supervisor")
  Intel(R) Xeon(R) CPU  @ 1.80 with 8243104 kB of memory.
  Processor Board ID FOC19224J5U
  Device name: SW
  bootflash:    8028160 kB
Kernel uptime is 440 day(s), 19 hour(s), 6 minute(s), 9 second(s)
Last reset at 105204 usecs after  Sun Jun 10 14:30:10 2001
  Reason: Reset Requested by CLI command reload
  System version: 7.1(0)N1(1a)
  Service:

plugin
  Core Plugin, Ethernet Plugin

[Mark Malone]

Looking at mine , my RED would be the last version we were on before we went to 7.1.4 back in start of Feb

upgrade both at same time using as this syntax as an example

install all kickstart bootflash: n5000-uk9-kickstart.7.1.4.N1.1 system bootflash: n5000-uk9.7.1.4.N1.1.bin

Software
  BIOS:      version 3.6.0
  Power Sequencer Firmware:
             Module 1: v7.0
             Module 1: v1.0
             Module 2: v1.0
             Module 3: v1.0
  Microcontroller Firmware:        version v1.0.0.2
  QSFP Microcontroller Firmware:
             Module not detected
  CXP Microcontroller Firmware:
             Module not detected
  kickstart: version 7.1(4)N1(1)
  system:    version 7.1(4)N1(1)
  BIOS compile time:       05/09/2012
  kickstart image file is: bootflash:///n5000-uk9-kickstart.7.1.4.N1.1.bin
  kickstart compile time:  9/2/2016 10:00:00 [09/02/2016 18:37:35]
  system image file is:    bootflash:///n5000-uk9.7.1.4.N1.1.bin
  system compile time:     9/2/2016 10:00:00 [09/02/2016 20:16:21]

Hardware
  cisco Nexus 5596 Chassis ("O2 48X10GE/Modular Supervisor")
  Intel(R) Xeon(R) CPU         with 8253848 kB of memory.
  Processor Board ID FOC18350HSS

  Device name: xir-d126sas02
  bootflash:    2007040 kB

Kernel uptime is 25 day(s), 1 hour(s), 23 minute(s), 49 second(s)

Last reset at 496331 usecs after  Sat Feb  4 12:07:19 2017

  Reason: Disruptive upgrade
  System version: 7.0(6)N1(1)
  Service:

[hi.sadiki]

Hello,

Thanks for you reply Marc, but  i am stil confisued, can you explain more please ?

Many thanks

[Mark Malone]

your system looks like it used to be running 7.1(0)N1(1a) but now its running 7.0(6)N1(1) , and the change was made from cli by a user , its the last version that was running on the system

if you check dir for flash you may still see an image in there for 7.1

[hi.sadiki]

Thanks you, I see more clearly now.

But i am confused, about the 2001. what is that mean ? that 16 years ago that nexus existed ? I don't think so, and the clock is sychronided.

Hardware
  cisco Nexus 56128P Chassis ("Nexus 56128P Supervisor")
  Intel(R) Xeon(R) CPU  @ 1.80 with 8243104 kB of memory.
  Processor Board ID FOC19224J5U
  Device name: SW
  bootflash:    8028160 kB
Kernel uptime is 440 day(s), 19 hour(s), 6 minute(s), 9 second(s)
Last reset at 105204 usecs after  Sun Jun 10 14:30:10 2001

SW# sh clock
16:10:45.163 Paris Wed Mar 01 2017

[Mark Malone · Accepted solution]

Yes but do you know if the clock was set when the last reload was done or that the it was synced with NTP and could reach it when they were testing this version  , I still have switches that tell me sometimes the log was 1993 when the clock is not set and they reload and they cant reach NTP server to update themselves and yes I did not have them back then either  :)

do you have an issue here or are you just concerned about what its reporting back to you ?

what that's reporting there will not effect any upgrade going forward with new versions

Your on a decent version there but the current recommended one is the one in my post 7.1.4 we were actually on 7.0.6 before that , we scan all our images for vulnerabilities through MVM scanner to check for issues before deployment so if your upgrading I would go with that

[hi.sadiki]

Hi Marc,

Thank you for the information; it's all clear now.

Actually, I don't have any issue, i am just curious about what was displayed