nexus5596UP: Reset triggered due to HA policy of Reset

[Universidade Aveiro]

Hi,

This weekend both of my nexus 5596UP they had a reload. With show version

Reason: Reset triggered due to HA policy of Reset

System version: 7.1(4)N1(1)

Service: arp hap reset

I saw that is a core dump saved and I have de file on my PC.

nx5k5-sw02#sh cores

VDC  Module Instance  Process-name     PID Date(Year-Month-Day Time)

---  ------ --------  ---------------  -------- -------------------------

1    1 1         arp              3534      2017-04-13 18:57:40

Now how can I see what really happened?

Thanks in advanced,

António

[Vitor Mazali]

It seems to be something as this bug CSCuo85450, even your NX-OS version is not listed as affected release.

Have you raised up a TAC case?

Link: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuo85450/?referring_site=bugquickviewredir

Conditions:

Gratuitious ARP storms are suspected as the trigger for this issue.

Workaround:

Identify source of ARP storm and stop it.

Further Problem Description:

This bug has absolutely nothing to do with Proxy ARP or DHCP or MAC address or limitation of ARP table entries.

This is a code defect. The trigger is easily seen during ARP storm. The crash can happen without evident of ARP storm in less frequency.

[Universidade Aveiro]

Thank you Vitor Mazali,

Unfortunately, I do not have Cisco support. However, can you tell me if it is possible to see what was the root of cause that occurs the reload of nexus, with the core dump file?

Once again thank you,

Best regards,

Antonio

[Vitor Mazali]

I see, Antonio, unfortunately, I can't tell you the root cause from dump file, this should be uploaded to the TAC team.

Have you tried the "show processes log details"? This could provide you more information on the reset.

Anyway, I'd try an upgrade to one of the versions which have that bug fixed.

Kind regards,

Vitor Mazali.

[Universidade Aveiro]

Hi Vitor Mazali,

The nexus 5596UP don't have available the command "show processes log details".

As you can see the version it's one of the bug fixes.

Software

  BIOS:      version 3.6.0

  Power Sequencer Firmware:

            Module 1: v7.0

            Module 1: 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 19: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 21:16:21]

Hardware

  cisco Nexus 5596 Chassis ("O2 48X10GE/Modular Supervisor")

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

Thank you.

António

[Vitor Mazali]

Antonio,

as you can see in the link below, the command is one of those listed in the troubleshooting guide:

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/troubleshooting/guide/N5K_Troubleshooting_Guide/n5K_ts_oview.html

Also, your current release isn't one of the listed as known fixed releases. There's the 7.0(4)N1(1), but, there's no 7.1(4)N1(1), which is yours.

Kind regards,

Vitor Mazali.

[Universidade Aveiro]

Thank you for your support, however the NX-OS version on my nexus it is Cisco Suggested, as you can see.

From all fixes release list, the only version that is available, for my 5596UP it is 7.0(4)N1(1), but my nexus has the version 7.1.XXX.

And despite of troubleshooting guide said that the command is available, in this version 7.1(4)N1(1), isn’t!

Once again, thank you for your support,

António