Nexus 4001i + New DCNM = Crash

Unanswered Question
Jul 12th, 2012

I have a customer with a bunch of N4001i blade switches. They are all running either 4.1(2)E1(1h) or (1g). They upgraded to DCNM 6.1.1a. Within a few minutes all of the N4Ks crashed.

This is what was gleaned from a sh ver:

Reason: Reset triggered due to HA policy of Reset

  System version: 4.1(2)E1(1g)

  Service: statsclient hap reset

The statsclient appears to be the problem. Has anyone else seen this?

I have this problem too.
2 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
vdsudame Fri, 07/13/2012 - 11:18

Can you please check all the switches and confirm if we have the same reset reason on all of them ? ie 'statsclient hap reset' ? Or is it something different, like 'cdp hap reset' ?

Thanks, Vinayak

vdsudame Mon, 07/16/2012 - 06:28

please open a TAC Case on this. We need to analyze the core files to investigate this issue further.


andlevin Wed, 08/08/2012 - 22:20

Keep us in the loop, do you have case number yet?

Sent from Cisco Technical Support iPhone App

z08mjk2374 Thu, 08/09/2012 - 07:07

Unfortunately when I tried to open the TAC case we found out that the hardware is covered under a different contract that isn't associated with my company. I do interact with this customer on a fairly regular basis. I will ask what happened the next time I hear from them.

ARUNPRABHU A Fri, 02/08/2013 - 00:01

Dear Team,

     I too facing the Same kind of Issue that is reboot of N4K, the Combination is same i.e. is N4K and DCNM.

Reason: Reset triggered due to HA policy of Reset
System version: 4.1(2)E1(1g)
Service: pfma hap reset <= fault symptom

The following logs from TACAS

dcnm Cisco Data Center Network Manager Architect sync-snmp-password ******** dcnm (FAILURE) 0 none 0 WANRT05

I could able to see from the logs that DCNM accessing the Snmp sync and created the reboot. Expecting revert if some one had faced this issue and any field notes from cisco...

Thanks ... Arun

supportcramra Tue, 03/19/2013 - 01:56

Dear Team,

Same issue for me, using NX4K and dcnm-installer-linux.6.1.1b.

Did the support find a solution because this bug does't seem to be in the Cisco Bug Tool Kit...

Have you try the lastest DCNM release ?



This Discussion

Related Content