This document describes failure messages and general troubleshooting procedures for the Cisco Fabric Extender (FEX) power supply.
In this example, the logs reveal continuous messages for general purpose input/output (GPIO) access failure:
%SATCTRL-FEX133-2-SOHMS_DIAG_ERROR: FEX-133 Module 1: Runtime diag detected major event: GPIO access failure
%SATCTRL-FEX133-4-SOHMS_PS_GPIO: FEX-133 System PS access failure
on Power supply: 1
%SATCTRL-FEX133-4-SOHMS_PS_GPIO: FEX-133 System PS access failure
on Power supply: 2
The appropriate solution depends upon the software version on the Nexus 5000 or Nexus 7000.
This is a known cosmetic issue; see Cisco bug ID CSCtl77867 (FEX PS runtime diag detected major event: GPIO access failure). The solution is to reload the FEX or upgrade to version 5.0(3)N2(1) or later.
See Cisco bug ID CSCtz84683 (continuous GPIO access failure message seen on FEX).
See Cisco bug ID CSCtr77620 (FEX: System minor alarm on power supply 1 & Recovered).
This example shows other failure messages for the FEX power supply:
%SATCTRL-FEX104-2-SOHMS_DIAG_ERROR: FEX-104 Module 1: Runtime diag detected major event:
Voltage failure on power supply: 1
%SATCTRL-FEX104-2-SOHMS_DIAG_ERROR: FEX-104 System minor alarm on power supply 1: failed
%SATCTRL-FEX104-2-SOHMS_DIAG_ERROR: FEX-104 Recovered: System minor alarm on power
supply 1: failed
Methods to resolve these issues include:
The first step in troubleshooting is to check for hardware and power issues. If you have a software issue, error messages continue even after you swap hardware.
Review and answer these questions in order to help define the circumstances of the failure:
Gather output from these commands in order to investigate the failures:
Revision | Publish Date | Comments |
---|---|---|
1.0 |
03-May-2013 |
Initial Release |