Field Notice: FN - 63560 - Nexus 5000 System Restart after 130 days of uptime - Workaround Provided

Available Languages

Updated:September 6, 2012
Document ID:FN63560

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Notice

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.

Revision History

Revision Publish Date Comments
1.0
10-Sep-12
Initial Release
10.0
11-Oct-17
Migration to new field notice system

Products Affected

Affected OS Type Affected Release Affected Release Number Comments
NON-IOS
5
5.1(3)N1(1a),5.1(3)N2(1),5.1(3)N2(1a),5.1(3)N1(1)

Defect Information

Defect ID Headline
CSCub31212 System restart with reason "ipfib hap reset".

Problem Description

Due to a memory leak, Nexus 5000 systems with LAN_BASE_SERVICES_PKG license installed that are running 5.1(3) prior to 5.1(3)N2(1b) may reboot due to memory exhaustion.

Background

Nexus 55xx switches with the LAN_BASE_SERVICES_PKG license installed can potentially restart due to "ipfib hap reset". It is not required that the L3 module be installed. The following can be observed in the output of show system reset-reason


Reason: Reset triggered due to HA policy of Reset

Service: ipfib hap reset

The issue is due to Memory Leak in "ipfib" processes .

The leak is around 1.8-2MB per day. The system will restart when 250 MB is leaked. This results in a system reboot after almost 130 days.

To identify the current memory allocation for ipfib process, use the following command and check for "MemAlloc". If you observe the MemAlloc is close to 250000000(250MB) the system may be at risk of an unexpected reboot. 


switch# sh processes mem



PID    MemAlloc StkSize   RSSMem   LibMem    StackBase/Ptr      Process

----   -------  -------  -------   -------   -------------     ---------

    1    159744    86016   618496  1716224 bffc4e50/bffc4940  init


   
    

 3272  261722112    86016 284368896 37801984 bfc95ec0/bfc94b5c  ipfib

Problem Symptom

The Nexus 5000 system with LAN_BASE_SERVICES_PKG license installed that are running 5.1(3) prior to 5.1(3)N2(1b) may restart due to memory depletion and report a restart reason of "ipfib hap reset".

Workaround/Solution

Nexus 55xx systems should be restarted before the ipfib process reaches 250MB of memory use or be upgraded to 5.1(3)N2(1b) or any 5.2(1)N1(1) or later Nexus 5000 software release. If the switch hardware and software configurations permit, customers may also downgrade to 5.0(3) releases of the Nexus 5000 software.

The issue is present in all 5.1(3) releases and the fix in the 5.1(3) train is present in 5.1.(3)N2(1b).

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Cisco Notification Service—Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco