Cisco Bug: CSCvs64910 - Nexus NFM core due to heartbeat not being received in time
Oct 06, 2020
- Cisco Nexus 9000 Series Switches
Known Affected Releases
Symptom: A Nexus platform configured with Netflow may experience a NFM crash, accompanied by the following errors/messages: %KERN-2-SYSTEM_MSG: [28953.659055] App nfm on slot 1 vdc 1 SUP sap 306(Nfm main SAP) did not drop MTS_OPC_IM_PHY_LINK_STATE_CHANGE with msg_id 0x1a9dcef from sender sap 175(NULL) in 600 sec, contact app ownerApp nfm on slot 1 vdc 1 SUP sap 306(Nfm main SAP) did not drop MTS_OPC_IM_PHY_LINK_STATE_CHANGE with ms - kerne %SYSMGR-3-HEARTBEAT_FAILURE: Service "nfm" sent SIGABRT for not setting heartbeat for last 4 periods. Last heartbeat 1339.85 secs ago. %KERN-2-SYSTEM_MSG: [48688.211856] App nfm on slot 1 vdc 1 SUP sap 306(Nfm main SAP) did not drop MTS_OPC_IM_PHY_LINK_STATE_CHANGE with msg_id 0x2d7faef from sender sap 175(NULL) in 601 sec, contact app owner<6>[49893.074936] klm_requiem process nfm pid 31893 thread 31893 received signal 6 at 4309842349. - %SYSMGR-2-SERVICE_CRASHED: Service "nfm" (PID 31893) hasn't caught signal 6 (core will be saved). Conditions: Netflow is configured.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases