Cisco Bug: CSCuw41121 - VIC 1240 -- Assert Failed
Nov 29, 2018
- Cisco Unified Computing System
Known Affected Releases
Symptom: ESXi host looses connectivity loss to FC SAN. Network connectivity especially ICMP was working. All VMs are unresponsive due to storage loss. There is a segmentation fault causing assert fail and CPU panic. As core is generated and uploaded to the UCSM. We can see the following events in mezz logs before the crash: 150902-17:51:25.487744 ecpumgr.main ERROR: ecpu 2 panic: ASSERT FAILED (Exception 11 triggered!) @ mips/ecpu_panic.c:138 150902-17:51:25.487942 ecpumgr.main Generating core /tmp/tmpcore_palo_dfw2.65536... 150902-17:51:30.556785 memmon.memmon Free system memory 23708 kB, decreasing by 1004 kB 150902-17:51:32.244991 ecpumgr.main Core /tmp/tmpcore_palo_dfw2.65536 completed (32510584 bytes written) 150902-17:51:43.768646 root: movecore: transfer of 1441173092_BC03_MEZZ0601_palo_dfw2_log.65536.tar.gz to sam1 completed 150902-17:51:43.797634 mcp.notify_svc received crash msg: Crash occurred; details are in 1441173092_BC03_MEZZ0601_palo_dfw2_log.65536.tar.gz 150902-17:51:50.701702 memmon.memmon Free system memory 20736 kB, decreasing by 2972 kB 150902-17:51:57.468753 mcp.vnic_dev vnic27 vnic_dev_addr_del 0e:fc:00:4f:00:49 STARTING FIRMWARE VERSION 4.0(1f) Conditions: Blade using VIC 1240.
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