07-12-2012 01:27 PM
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?
07-13-2012 11:18 AM
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
07-13-2012 11:52 AM
Yes. They all crashed from the statsclient hap reset.
07-16-2012 06:28 AM
please open a TAC Case on this. We need to analyze the core files to investigate this issue further.
Vinayak
07-14-2016 07:30 AM
We are seeing the same issue. Nexus 4001i and it just rebooted with this error.
Does anyone know if this is a bug, do we need to upgrade IOS, any idea?
----- reset reason for Supervisor-module 1 (from Supervisor in slot 1) ---
1) At 561957 usecs after Thu Jul 14 12:40:07 2016
Reason: Reset triggered due to HA policy of Reset
Service: statsclient hap reset
Version: 4.1(2)E1(1h)
Thanks
08-08-2012 10:20 PM
Keep us in the loop, do you have case number yet?
Sent from Cisco Technical Support iPhone App
08-09-2012 07:07 AM
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.
02-08-2013 12:01 AM
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 1.1.1.1 (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
03-19-2013 01:56 AM
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 ?
Thanks
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: