Guest

Preview Tool

Cisco Bug: CSCvu89088 - Nexus 5K - memory leak in ipqosmgr - crashed with signal 11 segmentation fault

Last Modified

Aug 05, 2020

Products (1)

  • Cisco Nexus 5000 Series Switches

Known Affected Releases

7.3(5)N1(1)

Description (partial)

Symptom:
Memory leak in ipqosmgr caused process to crash
# sh cores
VDC  Module  Instance  Process-name     PID       Date(Year-Month-Day Time)
---  ------  --------  ---------------  --------  -------------------------
1    1       1         ipqosmgr         4664      2020-07-01 16:02:58

Decode of crash file confirms that it is a segmentation fault - signal 11 , which is a memory condition.

After crashing memory process keeps increasing.

2nd July

# show processes memory | in PID|ipqos
PID MemAlloc MemLimit MemUsed StackBase/Ptr Process
31919 576507904 1151109273 768868352 7fef8d00/7fef72a0 ipqosmgr

3rd July

# sho clock
13:27:34.316 GMT Fri Jul 03 2020
# show processes memory | in PID|ipqos
PID MemAlloc MemLimit MemUsed StackBase/Ptr Process
31919 577556480 1151109273 769916928 7fef8d00/7fef72a0 ipqosmgr

Before the crash when the memory was high, the customer couldnt make interface configuration:

2020 Jun 30 13:31:19.631 %ETHPORT-5-IF_DOWN_ADMIN_DOWN: Interface Ethernet154/1/40 is down (Administratively down)
2020 Jun 30 13:31:22.690  %ETHPORT-5-IF_ADMIN_UP: Interface Ethernet154/1/40 is admin up .
2020 Jun 30 13:31:22.774  %ETHPORT-2-IF_SEQ_ERROR: Error (not enough memory) communicating with MTS_SAP_IPQOS_MGR for opcode MTS_OPC_ETHPM_PORT_PRE_CFG (RID_PORT: Ethernet154/1/40) - Ethpm didn't receive a Link UP from the driver on time or had an internal error, check Port Client and Ethpm logs and debug i
2020 Jun 30 13:31:22.775 %ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet154/1/40 is down (Error disabled. Reason:not enough memory)

After process crashed, customer could configure the port again.

Conditions:
Customer have following setup:
Hardware
  cisco Nexus5548 Chassis
  kickstart: version 7.3(5)N1(1)
  system:    version 7.3(5)N1(1)

-> customer performed non-supported upgrade path. upgraded directly from 5.2(1)N1(1) to 7.3(5)N1(1)

-> After process crash the memory leak doesn't happen anymore.
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.