Guest

Preview Tool

Cisco Bug: CSCvu29498 - Multiple UCS VIC may log "hang_notify" error on no-drop VNIC after CATERR on one Server/Node

Last Modified

Oct 13, 2020

Products (1)

  • Cisco Unified Computing System

Known Affected Releases

4.0(4e)C

Description (partial)

Symptom:
Multiple UCS Virtual Interface Adapters may log "mcp.hang_notify ERROR: vnicX: hang_notify" messages and I/O will halt

Host OS such as VMWare may log errors such as the following:
nenic: enic_uplink_reset:3100: [0000:3f:00.3] Resetting
cpu5:65693)WARNING: nenic: enic_uplink_tq_stop:264: [0000:3f:00.3] Failed to stop TX queue 0. Already stopped

Conditions:
Issue has been observed to occur when
No Drop Ethernet class, such as Platinum is configured with significant server to server traffic
Hardware related error, such as a CATERR has occurred on one server in a cluster
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.