Nexus 5672UP reboot reason [Reset triggered due to HA policy of Reset]

anas.abdullkarim · ‎12-24-2021

hello , i have Nexus 5672UP switch , i use it as L2/L3 for protocol BGP ,

sometime the switch made rebooting without any case

I get this message error.

Reason: Reset triggered due to HA policy of Reset System

version: 7.0(6)N1(1)

Service: adjmgr hap reset

# sh version 
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_home.h
tml
Copyright (c) 2002-2015, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.

Software
  BIOS:      version 2.1.2
  loader:    version N/A
  kickstart: version 7.0(6)N1(1)
  system:    version 7.0(6)N1(1)
  Power Sequencer Firmware: 
             Module 1: version v4.0
             Module 2: version v4.0
  Fabric Power Sequencer Firmware: Module 1: version v4.0
  Microcontroller Firmware:        version v0.0.0.15
  QSFP Microcontroller Firmware:   
             Module 2: v2.0.0.0
  SFP Microcontroller Firmware:   
             Module 1: v1.3.0.0
  BIOS compile time:       07/16/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 20: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 20:07:37]


Hardware
  cisco Nexus 5672UP Chassis ("Nexus 5672UP Supervisor")
  Intel(R) Xeon(R) CPU  @ 1.80 with 8243352 kB of memory.
  Processor Board ID FOC1928BXEB

  Device name: SW-IGW
  bootflash:    7692288 kB

Kernel uptime is 0 day(s), 0 hour(s), 32 minute(s), 18 second(s)

Last reset at 410372 usecs after  Sat Dec 25 00:37:54 2021

  Reason: Reset triggered due to HA policy of Reset
  System version: 7.0(6)N1(1)
  Service: adjmgr hap reset

plugin
  Core Plugin, Ethernet Plugin

Georg Pauwen · ‎12-24-2021

Hello,

the bug below might apply. Can you upgrade to an 8 or 9 code ?

Adjacency Manager crash due to excessive MTS stress
CSCvh31784
Customer Visible
Notifications
Save Bug
Open Support Case
Description
Symptom:
A Nexus 7K or Nexus 9K switch running affected code could experience a crash in the Adjacency Manager (adjmgr) process due to a heartbeat failure. The heartbeat failure occurs due to a large amount of messages in its Messaging and Transaction Service (MTS) queue and/or excessive churn.

Conditions:
What adjacency manager does is programs /32 hosts in hardware, usually these are devices that are directly connected. AM manages next-hop adjacencies learned via ARP, IGP, or statically installed. Whenever there is a change, it sends updates using the MTS buffers. MTS is an inter-process communication that sends data to different SUPs, modules, etc. If there is a or multiple hosts sending too much changes MTS buffers will be impacted adn Adjenct Manager process could crash.

Workaround:
Avoid on your network heavy ARP or IGP changes.