Guest

Preview Tool

Cisco Bug: CSCuj33719 - Nexus 6004 Pacifica asic 2 group 20: Fatal fi_bip_errors asserted

Last Modified

Feb 13, 2018

Products (7)

  • Cisco Nexus 6000 Series Switches
  • Cisco Nexus 5596UP Switch
  • Cisco Nexus 5548P Switch
  • Cisco Nexus 6004 Switch
  • Cisco Nexus 6001 Switch
  • Cisco Nexus 5548UP Switch
  • Cisco Nexus 5596T Switch

Known Affected Releases

6.0(2)N2(1)

Description (partial)

Symptom:
Pacifica asic 2 group 20: Fatal fi_bip_errors interrupt asserted 0x1818  - pacifica
2013 Sep  9 15:23:51 mdc-ds-g %USER-2-SYSTEM_MSG: BIP_ERRORS: lane 0: timestamp 0; current_time 188970; Register 0x0  - pacifica
2013 Sep  9 15:23:51 mdc-ds-g %USER-2-SYSTEM_MSG: BIP_ERRORS: lane 1: timestamp 188950; current_time 188970; Register 0x1818  - pacifica
2013 Sep  9 15:23:51 mdc-ds-g %USER-2-SYSTEM_MSG: BIP_ERRORS: lane 2: timestamp 0; current_time 188970; Register 0x0  - pacifica
2013 Sep  9 15:23:51 mdc-ds-g %USER-2-SYSTEM_MSG: BIP_ERRORS: lane 3: timestamp 0; current_time 188970; Register 0x0  - pacifica
2013 Sep  9 15:23:51 mdc-ds-g %USER-2-SYSTEM_MSG: INT_FI_RX_PCS: Reg 0x0 current_time 188970; alignment_int time 0;   - pacifica

***NOTE
It is not known if this is will impact traffic flow. This customer's box was pre-production and doesnt have any real traffic on it. I have also Isolated this host by shutting down the VPC, allowing all traffic flow in the customers network to go through the Peer n6k, which is not having this issue.

Conditions:
These errors occur upon bootup of the switch,and last 5-7 days before disappearing
There have been a few previous cases, where the box was RMA'd. The DE's were willing to look at this and found a way to edit the asic registers in the diag shell to prevent this from happening. 

They suggested I file this DDTS to track the issue, and are discussing internally how to resolve this.
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.