10-14-2014 11:40 AM - edited 03-01-2019 11:52 AM
I have a customer that has 3 different domains, where from time to time (months !) IOM's are crashing, creating a dump file.
Versions are 2.1.1b and 2.0.4b
No TAC case open yet; is this a known bug ?
Thanks for any clarification
Walter.
Apr 23 07:17:15 192.168.15.16 : 2014 Apr 23 07:17:15 CEST: %NOHMS-2-NOHMS_ENV_FEX_OFFLINE: FEX-3 Off-line (Serial Number FCH172570Q6)
Apr 23 07:17:15 192.168.15.16 : 2014 Apr 23 07:17:15 CEST: %PFMA-2-FEX_STATUS: Fex 3 is offline
Apr 23 07:17:37 192.168.15.16 : 2014 Apr 23 07:17:37 CEST: %UCSM-2-EQUIPMENT_INACCESSIBLE: [F0478][critical][equipment-inaccessible][sys/chassis-3/slot-1] left IOM 3/1 (A) is inaccessible
Apr 23 07:20:37 192.168.15.16 : 2014 Apr 23 07:20:37 CEST: %SATCTRL-FEX3 -2-SATCTRL: IOM-0 Module 1: Cold boot
Apr 23 07:20:44 192.168.15.16 : 2014 Apr 23 07:20:44 CEST: %PFMA-2-FEX_STATUS: Fex 3 is online
Apr 23 07:20:44 192.168.15.16 : 2014 Apr 23 07:20:44 CEST: %NOHMS-2-NOHMS_ENV_FEX_ONLINE: FEX-3 On-line
Apr 23 07:20:44 192.168.15.16 : 2014 Apr 23 07:20:44 CEST: %PFMA-2-FEX_STATUS: Fex 3 is online
Apr 23 07:20:45 192.168.15.16 : 2014 Apr 23 07:20:45 CEST: %UCSM-2-EQUIPMENT_INACCESSIBLE: [F0478][cleared][equipment-inaccessible][sys/chassis-3/slot-1] left IOM 3/1 (A) is inaccessible
Apr 23 08:21:14 192.168.15.17 : 2014 Apr 23 08:21:14 CEST: %PFMA-2-FEX_STATUS: Fex 3 is offline
Apr 23 08:21:14 192.168.15.17 : 2014 Apr 23 08:21:14 CEST: %NOHMS-2-NOHMS_ENV_FEX_OFFLINE: FEX-3 Off-line (Serial Number FCH1725J3LS)
Apr 23 08:21:38 192.168.15.16 : 2014 Apr 23 08:21:37 CEST: %UCSM-2-EQUIPMENT_INACCESSIBLE: [F0478][critical][equipment-inaccessible][sys/chassis-3/slot-2] right IOM 3/2 (B) is inaccessible
Apr 23 08:24:32 192.168.15.17 : 2014 Apr 23 08:24:32 CEST: %SATCTRL-FEX3 -2-SATCTRL: IOM-0 Module 1: Cold boot
Apr 23 08:24:40 192.168.15.17 : 2014 Apr 23 08:24:40 CEST: %PFMA-2-FEX_STATUS: Fex 3 is online
Apr 23 08:24:40 192.168.15.17 : 2014 Apr 23 08:24:40 CEST: %NOHMS-2-NOHMS_ENV_FEX_ONLINE: FEX-3 On-line
Apr 23 08:24:40 192.168.15.17 : 2014 Apr 23 08:24:40 CEST: %PFMA-2-FEX_STATUS: Fex 3 is online
Apr 23 08:25:08 192.168.15.16 : 2014 Apr 23 08:25:08 CEST: %UCSM-2-EQUIPMENT_INACCESSIBLE: [F0478][cleared][equipment-inaccessible][sys/chassis-3/slot-2] right IOM 3/2 (B) is inaccessible
Solved! Go to Solution.
10-17-2014 06:23 AM
Those two bugs are pretty much the same, did you have any question about them?
-Kenny
10-14-2014 11:49 AM
Found this
Symptom:
A Cisco 2204XP or 2208XP Fabric Extender (FEX) experiences a power-down condition while the rest of the chassis is still receiving power.
Conditions:
In very rare instances a Cisco UCSM chassis during normal system operation, regardless of the load on the blade or the system, can experience a power-down condition on one of its IO-Modules (IOM).
Workaround:
There is no work-around for this issue. Affected customers should call technical support to replace the part that failed.
10-15-2014 06:23 AM
Walter,
Have you considered this bug already ? https://tools.cisco.com/bugsearch/bug/CSCtz27298/?reffering_site=dumpcr ; <<check it despite of the UCSM version you mentioned
Gather a chassis show tech and go to the IOM in question> bmc> and look for a file called "mem_low_critical" (from the top of my mind).
Let me know if you find something similar.
-Kenny
10-17-2014 06:11 AM
10-17-2014 06:23 AM
Those two bugs are pretty much the same, did you have any question about them?
-Kenny
10-17-2014 06:33 AM
Thanks Kenny !
Customer opened a TAC case; for me it is important to know, that it is a software bug, which is fixed; therefore no hardware RMA necessary.
10-17-2014 06:35 AM
Cool.
It is the bmcd process in the IOM consuming memory that is never released.
Glad you have it figured out.
-Kenny
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide