Cisco UCS Faults and Error Messages Reference, Release 2.0

Cisco UCS Faults

This chapter provides information about the faults that may be raised in a Cisco UCS instance.

This chapter contains the following sections:

•Adapter-Related Faults

•Chassis-Related Faults

•Chassis Slot-Related Faults

•Cisco UCS Manager-Related Faults

•Ethernet-Related Faults

•Fabric Extender (FEX)-Related Faults

•Fabric Interconnect-Related Faults

•Fan-Related Faults

•Fibre Channel-Related Faults

•Firmware-Related Faults

•I/O Module-Related Faults

•License-Related Faults

•Link-Related Faults

•Memory-Related Faults

•Pin Group-Related Faults

•Pool-Related Faults

•Port-Related Faults

•Port Channel-Related Faults

•Power-Related Faults

•Power Supply-Related Faults

•Processor-Related Faults

•Server-Related Faults

•Service Profile-Related Faults

•System Event Log-Related Faults

•Traffic Monitoring-related Faults

•Virtual Network Interface-Related Faults

•VLAN-Related Faults

•VSAN-Related Faults

Adapter-Related Faults

This section contains faults raised as a result of issues with the adapters in a server.

fltAdaptorExtEthIfMisConnect

Fault Code:F0625

Message

Adapter [id] eth interface [id] in server [id] mis-connected

Explanation

The link for a network-facing adapter interface is misconnected. Cisco UCS Manager raises this fault when any of the following scenarios occur:

•Cisco UCS Manager detects a new connectivity between a previously configured switch port or FEX port and the adapter's external interface.

•Cisco UCS Manager detects a misconnected link between a fabric interconnect or FEX and its non-peer adapter's interface.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check whether the adapter link is connected to a port that belongs to its peer fabric interconnect or FEX.

Step 2 If that connectivity seems correct, reacknowledge the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: link-misconnected 

CallHome: none 

mibFaultCode: 625 

mibFaultName: fltAdaptorExtEthIfMisConnect 

moClass: adaptor:ExtEthIf 

Type: network

fltAdaptorExtEthIfMissing

Fault Code:F0775

Message

Connection to Adapter [id] eth interface [id] in server [id] missing

Explanation

The link for a network-facing adapter interface is misconnected. Cisco UCS Manager raises this fault when it detects that the connectivity between a previously configured port on a fabric interconnect or FEX and its prior peer network-facing adapter interface is misconnected or missing.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check whether the adapter interface is connected to a port belonging to its peer fabric interconnect or FEX.

Step 2 If the connectivity seems correct, reacknowledge the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: link-missing 

CallHome: none 

mibFaultCode: 775 

mibFaultName: fltAdaptorExtEthIfMissing 

moClass: adaptor:ExtEthIf 

Type: network

fltAdaptorExtIfLink-down

Fault Code:F0209

Message

Adapter uplink interface [id]/[id]/[id] link state: [linkState]Adapter uplink interface [chassisId]/[slotId]/[id]/[id] link state: [linkState]

Explanation

The link for a network facing adapter interface is down. Cisco UCS Manager raises this fault when any of the following scenarios occur:

•Cisco UCS Manager cannot establish and/or validate the adapter's connectivity to any of the fabric interconnects.

•The endpoint reports a link down or vNIC down event on the adapter link.

•The endpoint reports an errored link state or errored vNIC state event on the adapter link.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the adapter is connected, configured properly, and is running the recommended firmware version.

Step 2 If the server is stuck at discovery, decommission the server and reacknowledge the server slot.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: link-down 

CallHome: none 

mibFaultCode: 209 

mibFaultName: fltAdaptorExtIfLinkDown 

moClass: adaptor:ExtIf 

Type: network

fltAdaptorHostEthIfMisConnect

Fault Code:F0626

Message

Adapter [id] eth interface [id] in server [id] mis-connected

Explanation

The link for a network-facing host interface is misconnected. Cisco UCS Manager raises this fault when any of the following scenarios occur:

•Cisco UCS Manager detects a new connectivity between a previously configured switch port and the host Ethernet interface.

•Cisco UCS Manager detects a misconnected link between the host interface and its non-peer fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check whether the host Ethernet interface is connected to a port belonging to its peer fabric interconnect.

Step 2 If connectivity seems correct, reacknowledge the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: link-misconnected 

CallHome: none 

mibFaultCode: 626 

mibFaultName: fltAdaptorHostEthIfMisConnect 

moClass: adaptor:HostEthIf 

Type: network

fltAdaptorHostEthIfMissing

Fault Code:F0708

Message

Connection to Adapter [id] eth interface [id] in server [id] missing

Explanation

The link for a network-facing host interface is missing. Cisco UCS Manager raises this fault when it detects missing connectivity between a previously configured switch port and its previous peer host interface.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check whether the adapter link is connected to a port that belongs to its non-peer fabric interconnect.

Step 2 If that connectivity seems correct, reacknowledge the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: link-missing 

CallHome: none 

mibFaultCode: 708 

mibFaultName: fltAdaptorHostEthIfMissing 

moClass: adaptor:HostEthIf 

Type: network

fltAdaptorHostIfLink-down

Fault Code:F0207

Message

Adapter [transport] host interface [id]/[id]/[id] link state: [linkState]Adapter [transport] host interface [chassisId]/[slotId]/[id]/[id] link state: [linkState]

Explanation

This fault typically occurs as a result of one of the following issues:

•The fabric interconnect is in End-Host mode, and all uplink ports failed.

•The server port to which the adapter is pinned failed.

•A transient error caused the link to fail.

Recommended Action

If you see this fault, take the following actions:

Step 1 If an associated port is disabled, enable the port.

Step 2 Reacknowledge the server with the adapter that has the failed link.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: link-down 

CallHome: none 

mibFaultCode: 207 

mibFaultName: fltAdaptorHostIfLinkDown 

moClass: adaptor:HostIf 

Type: network

fltAdaptorUnitAdaptorReachability

Fault Code:F0206

Message

Adapter [id]/[id] is unreachableAdapter [chassisId]/[slotId]/[id] is unreachable

Explanation

Cisco UCS Manager cannot access the adapter. This fault typically occurs as a result of one of the following issues:

•The server does not have sufficient power.

•The I/O module is not functional.

•The adapter firmware has failed.

•The adapter is not functional

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the POST results for the server. In Cisco UCS Manager GUI, you can access the POST results from the General tab for the server. In Cisco UCS Manager CLI, you can access the POST results through the show post command under the scope for the server.

Step 2 In Cisco UCS Manager, check the power state of the server.

Step 3 Verify that the physical server has the same power state.

Step 4 If the server is off, turn the server on.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info 

Cause: connectivity-problem 

CallHome: diagnostic 

mibFaultCode: 206 

mibFaultName: fltAdaptorUnitAdaptorReachability 

moClass: adaptor:Unit 

Type: connectivity

fltAdaptorUnitExtnMissing

Fault Code:F0901

Message

Adapter extension [id] in server [chassisId]/[slotId] presence: [presence]

Explanation

This fault typically occurs when an I/O adapter unit extension, such as a pass-through adapter, is missing. Cisco UCS Manager raises this fault when any of the following scenario occur:

•The endpoint reports there is no adapter unit extension, such as a pass-through adapter, plugged into the adapter slot.

•The endpoint cannot detect or communicate with the adapter unit extension plugged into the adapter slot.

Recommended Action

If you see this fault, take the following actions:

Step 1 Ensure the adapter unit extension is properly plugged into an adapter slot in the server.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: equipment-missing 

CallHome: none 

mibFaultCode: 901 

mibFaultName: fltAdaptorUnitExtnMissing 

moClass: adaptor:UnitExtn 

Type: equipment

fltAdaptorUnitExtnUnidentifiable-fru

Fault Code:F0900

Message

Adapter extension [id] in server [chassisId]/[slotId] has unidentified FRU

Explanation

This fault typically occurs because Cisco UCS Manager has detected an unsupported adapter unit extension, such as a pass-through adaptor. For example, the model, vendor, or revision is not recognized.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that a supported adapter unit extension is installed.

Step 2 Verify that the capability catalog in Cisco UCS Manager is up to date. If necessary, update the catalog.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: unidentifiable-fru 

CallHome: none 

mibFaultCode: 900 

mibFaultName: fltAdaptorUnitExtnUnidentifiableFru 

moClass: adaptor:UnitExtn 

Type: server

fltAdaptorUnitMissing

Fault Code:F0203

Message

Adapter [id] in server [id] presence: [presence]Adapter [id] in server [chassisId]/[slotId] presence: [presence]

Explanation

The adaptor is missing. Cisco UCS Manager raises this fault when any of the following scenarios occur:

•The endpoint reports there is no adapter in the adaptor slot.

•The endpoint cannot detect or communicate with the adapter in the adaptor slot.

Recommended Action

If you see this fault, take the following actions:

Step 1 Make sure an adapter is inserted in the adaptor slot in the server.

Step 2 Check whether the adaptor is connected and configured properly and is running the recommended firmware version.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: equipment-missing 

CallHome: none 

mibFaultCode: 203 

mibFaultName: fltAdaptorUnitMissing 

moClass: adaptor:Unit 

Type: equipment

fltAdaptorUnitUnidentifiable-fru

Fault Code:F0200

Message

Adapter [id] in server [id] has unidentified FRUAdapter [id] in server [chassisId]/[slotId] has unidentified FRU

Explanation

This fault typically occurs because Cisco UCS Manager has detected an unsupported adapter. For example, the model, vendor, or revision is not recognized.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that a supported adapter is installed.

Step 2 Verify that the capability catalog in Cisco UCS Manager is up to date. If necessary, update the catalog.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: unidentifiable-fru 

CallHome: none 

mibFaultCode: 200 

mibFaultName: fltAdaptorUnitUnidentifiableFru 

moClass: adaptor:Unit 

Type: server

Chassis-Related Faults

This section contains faults raised as a result of issues related to a chassis in the Cisco UCS instance.

fltEquipmentChassisIdentity

Fault Code:F0404

Message

Chassis [id] has a mismatch between FRU identity reported by Fabric/IOM vs. FRU identity reported by CMC

Explanation

This fault typically occurs when the FRU information for an I/O module is corrupted or malformed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco UCS Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: fru-problem 

CallHome: diagnostic 

mibFaultCode: 404 

mibFaultName: fltEquipmentChassisIdentity 

moClass: equipment:Chassis 

Type: equipment

fltEquipmentChassisIdentity-unestablishable

Fault Code:F0543

Message

Chassis [id] has an invalid FRU

Explanation

This fault typically occurs because Cisco UCS Manager has detected an unsupported chassis. For example, the model, vendor, or revision is not recognized.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco UCS Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, execute the show tech-support command and contact Cisco technical support.

Fault Details

Severity: major 

Cause: identity-unestablishable 

CallHome: none 

mibFaultCode: 543 

mibFaultName: fltEquipmentChassisIdentityUnestablishable 

moClass: equipment:Chassis 

Type: equipment

fltEquipmentChassisInoperable

Fault Code:F0456

Message

Chassis [id] operability: [operability]

Explanation

This fault typically occurs for one of the following reasons:

•The fabric interconnect cannot communicate with a chassis. For a cluster configuration, this fault means that neither fabric interconnect can communicate with the chassis.

•The chassis has an invalid FRU.

Recommended Action

If you see this fault, take the following actions:

Step 1 In Cisco UCS Manager, reacknowledge the chassis that raised the fault.

Step 2 Physically unplug and replug the power cord into the chassis.

Step 3 Verify that the I/O modules are functional.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: equipment-inoperable 

CallHome: diagnostic 

mibFaultCode: 456 

mibFaultName: fltEquipmentChassisInoperable 

moClass: equipment:Chassis 

Type: equipment

fltEquipmentChassisPowerProblem

Fault Code:F0408

Message

Power state on chassis [id] is [power]

Explanation

This fault typically occurs when the chassis fails to meet the minimal power requirements defined in the power policy or when one or more power supplies have failed.

Recommended Action

If you see this fault, take the following actions:

Step 1 In Cisco UCS Manager, verify that all PSUs for the chassis are functional.

Step 2 Verify that all PSUs are seated properly within the chassis and are powered on.

Step 3 Physically unplug and replug the power cord into the chassis.

Step 4 If all PSUs are operating at maximum capacity, either add more PSUs to the chassis or redefine the power policy in Cisco UCS Manager.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: power-problem 

CallHome: environmental 

mibFaultCode: 408 

mibFaultName: fltEquipmentChassisPowerProblem 

moClass: equipment:Chassis 

Type: environmental

fltEquipmentChassisSeeprom-inoperable

Fault Code:F0733

Message

Device [id] SEEPROM operability: [seepromOperState]

Explanation

This fault occurs in the unlikely event that the Chassis shared storage (SEEPROM) is not operational.

Recommended Action

If you see this fault, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: equipment-inoperable 

CallHome: diagnostic 

mibFaultCode: 733 

mibFaultName: fltEquipmentChassisSeepromInoperable 

moClass: equipment:Chassis 

Type: equipment

fltEquipmentChassisThermalThresholdCritical

Fault Code:F0409

Message

Thermal condition on chassis [id] cause: [thermalStateQualifier]

Explanation

This fault occurs under the following conditions:

•If a component within a chassis is operating outside the safe thermal operating range.

•If the chassis controller in the IOM is unable to determine the thermal condition of a blade server, the show tech-support file for the chassis provides a more detailed report of the most severe thermal conditions currently applicable for that chassis.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the temperature readings for the blade servers and IOM and ensure they are within the recommended thermal safe operating range.

Step 2 If the fault reports a "Thermal Sensor threshold crossing in blade" error for one or more blade servers, check if DIMM or processor temperature related faults have been raised against that blade.

Step 3 If the fault reports a "Thermal Sensor threshold crossing in IOM" error for one or both the IOMs, check if thermal faults have been raised against that IOM. Those faults include details of the thermal condition.

Step 4 If the fault reports a "Missing or Faulty Fan" error, check on the status of that fan. If it needs replacement, create a show tech-support file for the chassis and contact Cisco TAC.

Step 5 If the fault reports a "No connectivity between IOM and blade" or "Thermal Sensor readings unavailable from blade" error, check if that blade server is operational and whether any faults have been raised against that blade server. In this situation, the chassis controller may go into a fail-safe operating mode and the fan speeds may increase as a precautionary measure.

Step 6 If the above actions did not resolve the issue and the condition persists, create a show tech-support file for Cisco UCS Manager and the chassis and contact Cisco TAC.

Fault Details

Severity: major 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 409 

mibFaultName: fltEquipmentChassisThermalThresholdCritical 

moClass: equipment:Chassis 

Type: environmental

fltEquipmentChassisThermalThresholdNonCritical

Fault Code:F0410

Message

Thermal condition on chassis [id] cause: [thermalStateQualifier]

Explanation

UCSM raises this fault under the following conditions:

•If a component within a chassis is operating outside the safe thermal operating range.

•If the chassis controller in the IOM is unable to determine the thermal condition of a blade server, the show tech-support file for the chassis provides a more detailed report of the most severe thermal conditions currently applicable for that chassis.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the temperature readings for the blade servers and IOM and ensure they are within the recommended thermal safe operating range.

Step 2 If the fault reports a "Thermal Sensor threshold crossing in blade" error for one or more blade servers, check if DIMM or processor temperature related faults have been raised against that blade.

Step 3 If the fault reports a "Thermal Sensor threshold crossing in IOM" error for one or both the IOMs, check if thermal faults have been raised against that IOM. Those faults include details of the thermal condition.

Step 4 If the fault reports a "Missing or Faulty Fan" error, check on the status of that fan. If it needs replacement, create a show tech-support file for the chassis and contact Cisco TAC.

Step 5 If the fault reports a "No connectivity between IOM and blade" or "Thermal Sensor readings unavailable from blade" error, check if that blade server is operational and whether any faults have been raised against that blade server. In this situation, the chassis controller may go into a fail-safe operating mode and the fan speeds may increase as a precautionary measure.

Step 6 If the above actions did not resolve the issue and the condition persists, create a show tech-support file for Cisco UCS Manager and the chassis and contact Cisco TAC.

Fault Details

Severity: minor 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 410 

mibFaultName: fltEquipmentChassisThermalThresholdNonCritical 

moClass: equipment:Chassis 

Type: environmental

fltEquipmentChassisThermalThresholdNonRecoverable

Fault Code:F0411

Message

Thermal condition on chassis [id] cause:[thermalStateQualifier]

Explanation

UCSM raises this fault under the following conditions:

Step 1 If a component within a chassis is operating outside the safe thermal operating range.

Step 2 If the chassis controller in the IOM is unable to determine the thermal condition of a blade server, the show tech-support file for the chassis provides a more detailed report of the most severe thermal conditions currently applicable for that chassis.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the temperature readings for the blade servers and IOM and ensure they are within the recommended thermal safe operating range.

Step 2 If the fault reports a "Thermal Sensor threshold crossing in blade" error for one or more blade servers, check if DIMM or processor temperature related faults have been raised against that blade.

Step 3 If the fault reports a "Thermal Sensor threshold crossing in IOM" error for one or both the IOMs, check if thermal faults have been raised against that IOM. Those faults include details of the thermal condition.

Step 4 If the fault reports a "Missing or Faulty Fan" error, check on the status of that fan. If it needs replacement, create a show tech-support file for the chassis and contact Cisco TAC.

Step 5 If the fault reports a "No connectivity between IOM and blade" or "Thermal Sensor readings unavailable from blade" error, check if that blade server is operational and whether any faults have been raised against that blade server. In this situation, the chassis controller may go into a fail-safe operating mode and the fan speeds may increase as a precautionary measure.

Step 6 If the above actions did not resolve the issue and the condition persists, create a show tech-support file for Cisco UCS Manager and the chassis and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 411 

mibFaultName: fltEquipmentChassisThermalThresholdNonRecoverable 

moClass: equipment:Chassis 

Type: environmental

fltEquipmentChassisUnacknowledged

Fault Code:F0400

Message

Chassis [id] connectivity configuration: [configState]

Explanation

This fault typically occurs when or more of the I/O module links from the chassis are unacknowledged.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the state of the I/O module links.

Step 2 Reacknowledge the chassis.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: equipment-unacknowledged 

CallHome: none 

mibFaultCode: 400 

mibFaultName: fltEquipmentChassisUnacknowledged 

moClass: equipment:Chassis 

Type: connectivity

fltEquipmentChassisUnsupportedConnectivity

Fault Code:F0399

Message

Current connectivity for chassis [id] does not match discovery policy: [configState]

Explanation

This fault typically occurs when the current connectivity for a chassis does not match the configuration in the chassis discovery policy.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the correct number of links are configured in the chassis discovery policy.

Step 2 Check the state of the I/O module links.

Step 3 Reacknowledge the chassis.

Step 4 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: unsupported-connectivity-configuration 

CallHome: none 

mibFaultCode: 399 

mibFaultName: fltEquipmentChassisUnsupportedConnectivity 

moClass: equipment:Chassis 

Type: connectivity

Chassis Slot-Related Faults

This section contains faults raised as a result of issues with a server slot in a chassis.

fltFabricComputeSlotEpMisplacedInChassisSlot

Fault Code:F0156

Message

Server, vendor([vendor]), model([model]), serial([serial]) in slot [chassisId]/[slotId] presence: [presence]

Explanation

This fault typically occurs when Cisco UCS Manager detects a server in a chassis slot that does not match what was previously equipped in the slot.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the previous server was intentionally removed and a new one was inserted, reacknowledge the server.

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: server-moved 

CallHome: none 

mibFaultCode: 156 

mibFaultName: fltFabricComputeSlotEpMisplacedInChassisSlot 

moClass: fabric:ComputeSlotEp 

Type: equipment

fltFabricComputeSlotEpServerIdentificationProblem

Fault Code:F0157

Message

Problem identifying server in slot [chassisId]/[slotId]

Explanation

This fault typically occurs when Cisco UCS Manager encountered a problem identifying the server in a chassis slot.

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove and reinsert the server.

Step 2 Reacknowledge the server.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: server-identification-problem 

CallHome: none 

mibFaultCode: 157 

mibFaultName: fltFabricComputeSlotEpServerIdentificationProblem 

moClass: fabric:ComputeSlotEp 

Type: equipment

Cisco UCS Manager-Related Faults

This section contains faults raised as a result of issues with Cisco UCS Manager.

fltMgmtPmonEntryUCSM process failure

Fault Code:F0867

Message

UCSM process [name] failed on FI [switchId]

Explanation

This fault occurs in an unlikely event of a Cisco UCS Manager process crash. Typically, the failed process restarts and recovers from the problem. Any pending operations are restarted after the process successfully restarts.

Recommended Action

If you see this fault and the process does not restart successfully, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: ucsm-process-failure 

CallHome: none 

mibFaultCode: 867 

mibFaultName: fltMgmtPmonEntryUCSMProcessFailure 

moClass: mgmt:PmonEntry 

Type: management

Ethernet-Related Faults

This section contains faults raised as a result of issues with the Ethernet configuration for a vNIC.

fltEtherServerIntFIoHardware-failure

Fault Code:F0458

Message

IOM [transport] interface [portId] on chassis [id] oper state: [operState], reason: [stateQual]Fabric Interconnect [transport] interface [portId] on fabric interconnect [id] oper state: [operState], reason: [stateQual]IOM [transport] interface [portId] on fex [id] oper state: [operState], reason: [stateQual]

Explanation

This fault is raised on the IOM/FEX backplane ports when Cisco UCS Manager detects a hardware failure.

Recommended Action

If you see this fault, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: interface-failed 

CallHome: none 

mibFaultCode: 458 

mibFaultName: fltEtherServerIntFIoHardwareFailure 

moClass: ether:ServerIntFIo 

Type: network

fltFabricEthEstcPcEpDown

Fault Code:F0777

Message

[type] Member [slotId]/[portId] of Port-Channel [portId] on fabric interconnect [id] is down, membership: [membership]

Explanation

This fault typically occurs when a member port in an Ethernet port channel is down.

Recommended Action

If you see this fault, take the following action:

Step 1 Check the link connectivity on the upstream Ethernet switch.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: membership-down 

CallHome: none 

mibFaultCode: 777 

mibFaultName: fltFabricEthEstcPcEpDown 

moClass: fabric:EthEstcPcEp 

Type: network

fltFabricEthLanPcEpDown

Fault Code:F0727

Message

[type] Member [slotId]/[portId] of Port-Channel [portId] on fabric interconnect [id] is down, membership: [membership]

Explanation

This fault typically occurs when a member port in an Ethernet port channel is down.

Recommended Action

If you see this fault, take the following action:

Step 1 Check the link connectivity on the upstream Ethernet switch.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: membership-down 

CallHome: none 

mibFaultCode: 727 

mibFaultName: fltFabricEthLanPcEpDown 

moClass: fabric:EthLanPcEp 

Type: network

fltVnicEtherConfig-failed

Fault Code:F0169

Message

Eth vNIC [name], service profile [name] failed to apply configuration

Explanation

This fault typically occurs when Cisco UCS Manager could not place the vNIC on the vCon.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the server was successfully discovered.

Step 2 Verify that the correct type of adapters are installed on the server.

Step 3 Confirm that the vCon assignment is correct.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor 

Cause: configuration-failed 

CallHome: none 

mibFaultCode: 169 

mibFaultName: fltVnicEtherConfigFailed 

moClass: vnic:Ether 

Type: configuration

Fabric Extender (FEX)-Related Faults

This section contains faults raised as a result of issues related to a fabric extender module in the Cisco UCS instance.

fltEquipmentFexFex-unsupported

Fault Code:F0905

Message

Fex [id] with model [model] is unsupported

Explanation

This fault typically occurs because Cisco UCS Manager has detected an unsupported FEX. For example, the model, vendor, or revision is not recognized.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that a supported FEX is installed.

Step 2 Verify that the capability catalog in Cisco UCS Manager is up to date. If necessary, update the catalog.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: fex-unsupported 

CallHome: none 

mibFaultCode: 905 

mibFaultName: fltEquipmentFexFexUnsupported 

moClass: equipment:Fex 

Type: equipment

fltEquipmentFexIdentity

Fault Code:F0703

Message

Fex [id] has a malformed FRU

Explanation

This fault typically occurs when the FRU information for a FEX is corrupted or malformed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco UCS Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: fru-problem 

CallHome: diagnostic 

mibFaultCode: 703 

mibFaultName: fltEquipmentFexIdentity 

moClass: equipment:Fex 

Type: equipment

fltEquipmentFexIdentity-unestablishable

Fault Code:F0778

Message

Fex [id] has an invalid FRU

Explanation

This fault typically occurs because Cisco UCS Manager detected an unsupported chassis. For example, the model, vendor, or revision is not recognized.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco UCS Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: identity-unestablishable 

CallHome: none 

mibFaultCode: 778 

mibFaultName: fltEquipmentFexIdentityUnestablishable 

moClass: equipment:Fex 

Type: equipment

fltEquipmentFexPost-failure

Fault Code:F0702

Message

fex [id] POST failure

Explanation

This fault typically occurs when a FEX encounters errors during the Power On Self Test (POST). The impact of this fault varies depending on which errors were encountered during POST.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the POST results for the FEX. In the Cisco UCS Manager GUI, you can access the POST results from the General tab for the FEX. In the Cisco UCS Manager CLI, you can access the POST results by entering the show post command under the scope for the FEX.

Step 2 Reboot the FEX.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: equipment-problem 

CallHome: diagnostic 

mibFaultCode: 702 

mibFaultName: fltEquipmentFexPostFailure 

moClass: equipment:Fex 

Type: equipment

Fabric Interconnect-Related Faults

This section contains faults raised as a result of issues with a fabric interconnect.

fltEtherSwitchIntFIoSatellite-wiring-problem

Fault Code:F0368

Message

Invalid connection between IOM port [chassisId]/[slotId]/[portId] and fabric interconnect [switchId]:[peerSlotId]/[peerPortId]

Explanation

This fault typically occurs as a result of a satellite wiring problem on the network-facing interface of an I/O module and Cisco UCS Manager detects that at least one IOM uplink is misconnected to one of the fabric interconnect ports.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify the fabric interconnect-chassis topology. Make sure each I/O module is connected to only one fabric interconnect.

Step 2 Ensure that the links are plugged in properly and re-acknowledge the chassis.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info 

Cause: satellite-mis-connected 

CallHome: none 

mibFaultCode: 368 

mibFaultName: fltEtherSwitchIntFIoSatelliteWiringProblem 

moClass: ether:SwitchIntFIo 

Type: connectivity

fltEtherSwitchIntFIoSatellite-wiring-numbers-unexpected

Fault Code:F0440

Message

Chassis discovery policy conflict: Link IOM [chassisId]/[slotId]/[portId] to fabric interconnect [switchId]:[peerSlotId]/[peerPortId] not configured

Explanation

The configuration of the chassis discovery policy conflicts with the physical IOM uplinks. Cisco UCS Manager raises this fault when the chassis discovery policy is configured for more links than are physically cabled between the IOM uplinks on the chassis and the fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

Step 1 Ensure that you cable at least the same number of IOM uplinks as are configured in the chassis discovery policy, and that you configure the corresponding server ports on the fabric interconnect.

Step 2 Reacknowledge the chassis.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info 

Cause: unexpected-number-of-links 

CallHome: none 

mibFaultCode: 440 

mibFaultName: fltEtherSwitchIntFIoSatelliteWiringNumbersUnexpected 

moClass: ether:SwitchIntFIo 

Type: connectivity

fltEquipmentSwitchCardPowerOff

Fault Code:F0884

Message

Switch card is powered down.

Explanation

This fault occurs when the switch card is powered down.

Recommended Action

If you see this fault, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: power-down 

CallHome: none 

mibFaultCode: 884 

mibFaultName: fltEquipmentSwitchCardPowerOff 

moClass: equipment:SwitchCard 

Type: equipment

fltExtmgmtIfMgmtifdown

Fault Code:F0736

Message

Management interface on Fabric Interconnect [id] is [operState]

Explanation

This fault occurs when a fabric interconnect reports that the operational state of an external management interface is down.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the state transitions of the external management interface on the fabric interconnect.

Step 2 Check the link connectivity for the external management interface.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: mgmtif-down 

CallHome: diagnostic 

mibFaultCode: 736 

mibFaultName: fltExtmgmtIfMgmtifdown 

moClass: extmgmt:If 

Type: management

fltMgmtEntityDegraded

Fault Code:F0293

Message

Fabric Interconnect [id], HA Cluster interconnect link failure

Explanation

This fault occurs when one of the cluster links (either L1 or L2) of a fabric interconnect is not operationally up. This issue impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that both L1 and L2 links are properly connected between the fabric interconnects.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: link-down 

CallHome: diagnostic 

mibFaultCode: 293 

mibFaultName: fltMgmtEntityDegraded 

moClass: mgmt:Entity 

Type: network

fltMgmtEntityDevice-1-shared-storage-error

Fault Code:F0863

Message

device [chassis1], error accessing shared-storage

Explanation

This fault occurs in an unlikely event that the shared storage selected for writing the cluster state is not accessible. This impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, create a show tech-support file and contact Cisco TAC.lt;br/

Fault Details

Severity: warning 

Cause: device-shared-storage-error 

CallHome: none 

mibFaultCode: 863 

mibFaultName: fltMgmtEntityDevice1SharedStorageError 

moClass: mgmt:Entity 

Type: management

fltMgmtEntityDevice-2-shared-storage error

Fault Code:F0864

Message

device [chassis2], error accessing shared-storage

Explanation

This fault occurs in an unlikely event that the shared storage selected for writing the cluster state is not accessible. This impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, create a show tech-support file and contact Cisco TAC.lt;br/

Fault Details

Severity: warning 

Cause: device-shared-storage-error 

CallHome: none 

mibFaultCode: 864 

mibFaultName: fltMgmtEntityDevice2SharedStorageError 

moClass: mgmt:Entity 

Type: management

fltMgmtEntityDevice-3-shared-storage error

Fault Code:F0865

Message

device [chassis3], error accessing shared-storage

Explanation

This fault occurs in an unlikely event that the shared storage selected for writing the cluster state is not accessible. This impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, create a show tech-support file and contact Cisco TAC.lt;br/

Fault Details

Severity: warning 

Cause: device-shared-storage-error 

CallHome: none 

mibFaultCode: 865 

mibFaultName: fltMgmtEntityDevice3SharedStorageError 

moClass: mgmt:Entity 

Type: management

fltMgmtEntityDown

Fault Code:F0294

Message

Fabric Interconnect [id], HA Cluster interconnect total link failure

Explanation

This fault occurs when both cluster links (L1 and L2) of the fabric interconnects are in a link-down state. This issue impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that both L1 and L2 links are properly connected between the fabric interconnects.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: link-down 

CallHome: diagnostic 

mibFaultCode: 294 

mibFaultName: fltMgmtEntityDown 

moClass: mgmt:Entity 

Type: network

fltMgmtEntityElection-failure

Fault Code:F0428

Message

Fabric Interconnect [id], election of primary managemt instance has failed

Explanation

This fault occurs in an unlikely event that the fabric interconnects in a cluster configuration could not reach an agreement for selecting the primary fabric interconnect. This impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the initial setup configuration is correct on both fabric interconnects.

Step 2 Verify that the L1 and L2 links are properly connected between the fabric interconnects.

Step 3 In the Cisco UCS Manager CLI, run the cluster force primary local-mgmt command on one fabric interconnect.

Step 4 Reboot the fabric interconnects.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: election-failure 

CallHome: diagnostic 

mibFaultCode: 428 

mibFaultName: fltMgmtEntityElectionFailure 

moClass: mgmt:Entity 

Type: management

fltMgmtEntityHa-not-ready

Fault Code:F0429

Message

Fabric Interconnect [id], HA functionality not ready

Explanation

This fault occurs if Cisco UCS Manager cannot discover or communicate with one or more chassis or rack servers to write the HA Cluster state. This impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the initial setup configuration is correct on both fabric interconnects.

Step 2 Verify that the L1 and L2 links are properly connected between the fabric interconnects.

Step 3 Verify that the IOMs and/or FEXes are reachable and the server ports are enabled and operationally up.

Step 4 Verify that the chassis and/or rack servers are powered up and reachable

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: ha-not-ready 

CallHome: none 

mibFaultCode: 429 

mibFaultName: fltMgmtEntityHaNotReady 

moClass: mgmt:Entity 

Type: management

fltMgmtEntityHa-ssh-keys-mismatched

Fault Code:F0866

Message

Fabric Interconnect [id], management services, mismatched SSH keys

Explanation

This fault indicates that one of the following scenarios has occurred:

•The internal SSH keys used for HA in the cluster configuration are mismatched. This causes certain operations to fail.

•Another fabric interconnect is connected to the primary fabric interconnect in the cluster without first erasing the existing configuration in the primary.

Recommended Action

If you see this fault, take the following actions:

Step 1 Log into the Cisco UCS Manager CLI on the subordinate fabric interconnect.

Step 2 Enter connect local-mgmt

Step 3 Enter erase configuration to erase the configuration on the subordinate fabric interconnect and reboot it.

Step 4 When the secondary fabric interconnect has rebooted, reconfigure it for the cluster.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: ha-ssh-keys-mismatched 

CallHome: none 

mibFaultCode: 866 

mibFaultName: fltMgmtEntityHaSshKeysMismatched 

moClass: mgmt:Entity 

Type: management

fltMgmtEntityManagement-services-failure

Fault Code:F0451

Message

Fabric Interconnect [id], management services have failed

Explanation

This fault occurs in an unlikely event that management services fail on a fabric interconnect. This impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the initial setup configuration is correct on both fabric interconnects.

Step 2 Verify that the L1 and L2 links are properly connected between the fabric interconnects.

Step 3 Reboot the fabric interconnects.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: management-services-failure 

CallHome: diagnostic 

mibFaultCode: 451 

mibFaultName: fltMgmtEntityManagementServicesFailure 

moClass: mgmt:Entity 

Type: management

fltMgmtEntityManagement-services-unresponsive

Fault Code:F0452

Message

Fabric Interconnect [id], management services are unresponsive

Explanation

This fault occurs when management services on a fabric interconnect are unresponsive. This impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the initial setup configuration is correct on both fabric interconnects.

Step 2 Verify that the L1 and L2 links are properly connected between the fabric interconnects.

Step 3 Reboot the fabric interconnects.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: management-services-unresponsive 

CallHome: diagnostic 

mibFaultCode: 452 

mibFaultName: fltMgmtEntityManagementServicesUnresponsive 

moClass: mgmt:Entity 

Type: management

fltMgmtEntityVersion-incompatible

Fault Code:F0430

Message

Fabric Interconnect [id], management services, incompatible versions

Explanation

This fault occurs if the Cisco UCS Manager software on the subordinate fabric interconnect is not the same release as that of the primary fabric interconnect. This impacts the full HA functionality of the fabric interconnect cluster.

Recommended Action

If you see this fault, take the following actions:

Step 1 Upgrade the Cisco UCS Manager software on the subordinate fabric interconnect to the same release as the primary fabric interconnect and verify that both fabric interconnects are running the same release of Cisco UCS Manager.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: version-incompatible 

CallHome: diagnostic 

mibFaultCode: 430 

mibFaultName: fltMgmtEntityVersionIncompatible 

moClass: mgmt:Entity 

Type: management

fltNetworkElementInoperable

Fault Code:F0291

Message

Fabric Interconnect [id] operability: [operability]

Explanation

This fault typically occurs when the fabric interconnect cluster controller reports that the membership state of the fabric interconnect is down, indicating that the fabric interconnect is inoperable.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that both fabric interconnects in the cluster are running the same Kernel and System software versions.

Step 2 Verify that the fabric interconnects software version and the Cisco UCS Manager software versions are the same.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: equipment-inoperable 

CallHome: diagnostic 

mibFaultCode: 291 

mibFaultName: fltNetworkElementInoperable 

moClass: network:Element 

Type: equipment

fltNetworkElementInventoryFailed

Fault Code:F0885

Message

Fabric Interconnect [id] inventory is not complete: [inventoryStatus]

Explanation

Cisco UCS Manager raises this fault when the management subsystem is unable to perform an inventory of the physical components, such as I/O cards or physical ports.

Recommended Action

If you see this fault, take the following actions:

Step 1 Ensure that both fabric interconnects in an HA cluster are running the same software versions.

Step 2 Ensure that the fabric interconnect software is a version that is compatible with the Cisco UCS Manager software.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: inventory-failed 

CallHome: diagnostic 

mibFaultCode: 885 

mibFaultName: fltNetworkElementInventoryFailed 

moClass: network:Element 

Type: equipment

fltStorageItemCapacityExceeded

Fault Code:F0182

Message

Disk usage for partition [name] on fabric interconnect [id] exceeded 70%

Explanation

This fault occurs when the partition disk usage exceeds 70% but is less than 90%.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reduce the partition disk usage to less than 70% by deleting unused and unnecessary files.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor 

Cause: capacity-exceeded 

CallHome: none 

mibFaultCode: 182 

mibFaultName: fltStorageItemCapacityExceeded 

moClass: storage:Item 

Type: environmental

fltStorageItemCapacityWarning

Fault Code:F0183

Message

Disk usage for partition [name] on fabric interconnect [id] exceeded 90%

Explanation

This fault occurs when the partition disk usage exceeds 90%.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reduce the partition disk usage to less than 90% by deleting unused and unnecessary files.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: capacity-exceeded 

CallHome: none 

mibFaultCode: 183 

mibFaultName: fltStorageItemCapacityWarning 

moClass: storage:Item 

Type: environmental

Fan-Related Faults

This section contains faults raised as a result of issues related to a fan or fan module in the Cisco UCS instance.

fltEquipmentFanDegraded

Fault Code:F0371

Message

Fan [id] in Fan Module [tray]-[id] under chassis [id] operability: [operability]Fan [id] in fabric interconnect [id] operability: [operability]Fan [id] in fex [id] operability: [operability]Fan [id] in Fan Module [tray]-[id] under server [id] operability: [operability]

Explanation

This fault occurs when one or more fans in a fan module are not operational, but at least one fan is operational.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the fan module.

Step 2 Review the Cisco UCS Site Preparation Guide and ensure the fan module has adequate airflow, including front and back clearance.

Step 3 Verify that the air flows are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace the faulty fan modules.

Step 8 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor 

Cause: equipment-degraded 

CallHome: none 

mibFaultCode: 371 

mibFaultName: fltEquipmentFanDegraded 

moClass: equipment:Fan 

Type: equipment

fltEquipmentFanInoperable

Fault Code:F0373

Message

Fan [id] in Fan Module [tray]-[id] under chassis [id] operability: [operability]Fan [id] in fabric interconnect [id] operability: [operability]Fan [id] in fex [id] operability: [operability]Fan [id] in Fan Module [tray]-[id] under server [id] operability: [operability]

Explanation

This fault occurs if a fan is not operational.

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove fan module and re-install the fan module again. Remove only one fan module at a time.

Step 2 Replace fan module with a different fan module

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: equipment-inoperable 

CallHome: environmental 

mibFaultCode: 373 

mibFaultName: fltEquipmentFanInoperable 

moClass: equipment:Fan 

Type: equipment

fltEquipmentFanMissing

Fault Code:F0434

Message

Fan [id] in fabric interconnect [id] presence: [presence]Fan [id] in fex [id] presence: [presence]Fan [id] in Fan Module [tray]-[id] under server [id] presence: [presence]

Explanation

This fault occurs in the unlikely event that a fan in a fan module cannot be detected.

Recommended Action

If you see this fault, take the following actions:

Step 1 Insert/reinsert the fan module in the slot that is reporting the issue.

Step 2 Replace the fan module with a different fan module, if available.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: equipment-missing 

CallHome: none 

mibFaultCode: 434 

mibFaultName: fltEquipmentFanMissing 

moClass: equipment:Fan 

Type: equipment

fltEquipmentFanModuleDegraded

Fault Code:F0480

Message

Fan module [tray]-[id] in chassis [id] operability: [operability]Fan module [tray]-[id] in server [id] operability: [operability]Fan module [tray]-[id] in fabric interconnect [id] operability: [operability]

Explanation

This fault occurs when a fan module is not operational.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the fan module.

Step 2 Review the Cisco UCS Site Preparation Guide to ensure the fan module has adequate airflow, including front and back clearance.

Step 3 Verify that the air flows for the fan module are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor 

Cause: equipment-degraded 

CallHome: none 

mibFaultCode: 480 

mibFaultName: fltEquipmentFanModuleDegraded 

moClass: equipment:FanModule 

Type: equipment

fltEquipmentFanModuleIdentity

Fault Code:F0406

Message

Fan Module [tray]-[id] in chassis [id] has a malformed FRUFan Module [tray]-[id] in server [id] has a malformed FRUFan Module [tray]-[id] in fabric interconnect [id] has a malformed FRU

Explanation

This fault typically occurs when the FRU information for a fan module is corrupted or malformed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco UCS Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: fru-problem 

CallHome: diagnostic 

mibFaultCode: 406 

mibFaultName: fltEquipmentFanModuleIdentity 

moClass: equipment:FanModule 

Type: equipment

fltEquipmentFanModuleInoperable

Fault Code:F0794

Message

Fan module [tray]-[id] in chassis [id] operability: [operability]Fan module [tray]-[id] in server [id] operability: [operability]Fan module [tray]-[id] in fabric interconnect [id] operability: [operability]

Explanation

This fault occurs if a fan module is not operational.

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove and reinstall the fan module. If multiple fans are affected by this fault, remove and reinstall one fan module at a time.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: equipment-inoperable 

CallHome: environmental 

mibFaultCode: 794 

mibFaultName: fltEquipmentFanModuleInoperable 

moClass: equipment:FanModule 

Type: equipment

fltEquipmentFanModuleMissing

Fault Code:F0377

Message

Fan module [tray]-[id] in chassis [id] presence: [presence]Fan module [tray]-[id] in server [id] presence: [presence]Fan module [tray]-[id] in fabric interconnect [id] presence: [presence]

Explanation

This fault occurs if a fan Module slot is not equipped or removed from its slot

Recommended Action

If you see this fault, take the following actions:

Step 1 If the reported slot is empty, insert a fan module into the slot.

Step 2 If the reported slot contains a fan module, remove and reinsert the fan module.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: equipment-missing 

CallHome: none 

mibFaultCode: 377 

mibFaultName: fltEquipmentFanModuleMissing 

moClass: equipment:FanModule 

Type: equipment

fltEquipmentFanModuleThermalThresholdCritical

Fault Code:F0382

Message

Fan module [tray]-[id] in chassis [id] temperature: [thermal]Fan module [tray]-[id] in server [id] temperature: [thermal]Fan module [tray]-[id] in fabric interconnect [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a fan module has exceeded a critical threshold value. Be aware of the following possible contributing factors:

•Temperature extremes can cause Cisco UCS equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

•Cisco UCS equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the fan module.

Step 2 Review the Cisco UCS Site Preparation Guide to ensure the fan modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace faulty fan modules.

Step 8 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major f

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 382 

mibFaultName: fltEquipmentFanModuleThermalThresholdCritical 

moClass: equipment:FanModule 

Type: environmental

fltEquipmentFanModuleThermalThresholdNonCritical

Fault Code:F0380

Message

Fan module [tray]-[id] in chassis [id] temperature: [thermal]Fan module [tray]-[id] in server [id] temperature: [thermal]Fan module [tray]-[id] in fabric interconnect [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a fan module has exceeded a non-critical threshold value, but is still below the critical threshold. Be aware of the following possible contributing factors:

•Temperature extremes can cause Cisco UCS equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

•Cisco UCS equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the fan module.

Step 2 Review the Cisco UCS Site Preparation Guide to ensure the fan modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace faulty fan modules.

Step 8 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 380 

mibFaultName: fltEquipmentFanModuleThermalThresholdNonCritical 

moClass: equipment:FanModule 

Type: environmental

fltEquipmentFanModuleThermalThresholdNonRecoverable

Fault Code:F0384

Message

Fan module [tray]-[id] in chassis [id] temperature: [thermal]Fan module [tray]-[id] in server [id] temperature: [thermal]Fan module [tray]-[id] in fabric interconnect [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a fan module has been out of operating range, and the issue is not recoverable. Be aware of the following possible contributing factors:

•Temperature extremes can cause Cisco UCS equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

•Cisco UCS equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the fan module.

Step 2 Review the Cisco UCS Site Preparation Guide to ensure the fan modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace faulty fan modules.

Step 8 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 384 

mibFaultName: fltEquipmentFanModuleThermalThresholdNonRecoverable 

moClass: equipment:FanModule 

Type: environmental

fltEquipmentFanPerfThresholdCritical

Fault Code:F0396

Message

Fan [id] in Fan Module [tray]-[id] under chassis [id] speed: [perf]Fan [id] in fabric interconnect [id] speed: [perf]Fan [id] in Fan Module [tray]-[id] under server [id] speed: [perf]

Explanation

This fault occurs when the fan speed read from the fan controller does not match the desired fan speed and has exceeded the critical threshold and is in risk of failure. This can indicate a problem with a fan or with the reading from the fan controller.

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the fan status.

Step 2 If the problem persists for a long period of time or if other fans do not show the same problem, reseat the fan.

Step 3 If the above actions did not resolve the issue, create a show tech-support file for the chassis and contact Cisco TAC.

Fault Details

Severity: info 

Cause: performance-problem 

CallHome: diagnostic 

mibFaultCode: 396 

mibFaultName: fltEquipmentFanPerfThresholdCritical 

moClass: equipment:Fan 

Type: equipment

fltEquipmentFanPerfThresholdLowerNonRecoverable

Fault Code:F0484

Message

Fan [id] in Fan Module [tray]-[id] under chassis [id] speed: [perf]Fan [id] in fabric interconnect [id] speed: [perf]Fan [id] in Fan Module [tray]-[id] under server [id] speed: [perf]

Explanation

This fault occurs when the fan speed reading from the fan controller is far below the desired fan speed, and the fan has likely failed.

Recommended Action

If you see this fault, create a detailed show tech-support file for the chassis and replace the fan module. If necessary, contact Cisco TAC.

Fault Details

Severity: critical 

Cause: performance-problem 

CallHome: diagnostic 

mibFaultCode: 484 

mibFaultName: fltEquipmentFanPerfThresholdLowerNonRecoverable 

moClass: equipment:Fan 

Type: equipment

fltEquipmentFanPerfThresholdNonCritical

Fault Code:F0395

Message

Fan [id] in Fan Module [tray]-[id] under chassis [id] speed: [perf]Fan [id] in fabric interconnect [id] speed: [perf]Fan [id] in Fan Module [tray]-[id] under server [id] speed: [perf]

Explanation

This fault occurs when the fan speed reading from the fan controller does not match the desired fan speed and is outside of the normal operating range. This can indicate a problem with a fan or with the reading from the fan controller.

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the fan status.

Step 2 If the problem persists for a long period of time or if other fans do not show the same problem, reseat the fan.

Step 3 Replace the fan module.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info 

Cause: performance-problem 

CallHome: diagnostic 

mibFaultCode: 395 

mibFaultName: fltEquipmentFanPerfThresholdNonCritical 

moClass: equipment:Fan 

Type: equipment

fltEquipmentFanPerfThresholdNonRecoverable

Fault Code:F0397

Message

Fan [id] in Fan Module [tray]-[id] under chassis [id] speed: [perf]Fan [id] in fabric interconnect [id] speed: [perf]Fan [id] in Fan Module [tray]-[id] under server [id] speed: [perf]

Explanation

This fault occurs when the fan speed read from the fan controller has far exceeded the desired fan speed. It frequently indicates that the fan has failed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Replace the fan.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: info 

Cause: performance-problem 

CallHome: diagnostic 

mibFaultCode: 397 

mibFaultName: fltEquipmentFanPerfThresholdNonRecoverable 

moClass: equipment:Fan 

Type: equipment

Fibre Channel-Related Faults

This section contains the following faults raised as a result of issues with the Fibre Channel configuration for a vHBA.

fltVnicFcConfig-failed

Fault Code:F0170

Message

FC vHBA [name], service profile [name] failed to apply configuration

Explanation

This fault typically occurs when Cisco UCS Manager could not place the vHBA on the vCon.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the server was successfully discovered.

Step 2 Verify that the correct type of adapters are installed on the server.

Step 3 Confirm that the vCon assignment is correct.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor 

Cause: configuration-failed 

CallHome: none 

mibFaultCode: 170 

mibFaultName: fltVnicFcConfigFailed 

moClass: vnic:Fc 

Type: configuration

Firmware-Related Faults

This section contains faults raised as a result of issues related to a firmware upgrade or to running firmware on a component in the Cisco UCS instance.

fltEquipmentIOCardAutoUpgradingFirmware

Fault Code:F0435

Message

IOM [chassisId]/[id] ([switchId]) is auto upgrading firmware

Explanation

This fault typically occurs when an I/O module is auto upgrading. Auto-upgrade occurs when the firmware version on the IOM is incompatible with the firmware version on the fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the IOM and fabric interconnects are not running the same firmware version, wait for the auto-upgrade to complete.

Step 2 When the IOM upgrade is completed, verify that Cisco UCS Manager has cleared this fault.

Step 3 If you see this fault after the IOM overall status changes to operable, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: auto-firmware-upgrade 

CallHome: none 

mibFaultCode: 435 

mibFaultName: fltEquipmentIOCardAutoUpgradingFirmware 

moClass: equipment:IOCard 

Type: connectivity

fltEquipmentIOCardFirmwareUpgrade

Fault Code:F0398

Message

Chassis controller in IOM [chassisId]/[id] ([switchId]) firmware upgrade problem: [upgradeStatus]

Explanation

This fault typically occurs when an IOM upgrade fails.

Recommended Action

If you see this fault, take the following actions:

Step 1 On the FSM tab for the IOM, verify whether FSM for the upgrade completed successfully or failed.

Step 2 If the FSM failed, review the error message in the FSM.

Step 3 If the error message is self explanatory, verify the physical connectivity. For example, an error message could be No Connection to Endpoint or Link Down.

Step 4 If the above action did not resolve the issue and the fault persists, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: firmware-upgrade-problem 

CallHome: none 

mibFaultCode: 398 

mibFaultName: fltEquipmentIOCardFirmwareUpgrade 

moClass: equipment:IOCard 

Type: equipment

fltFirmwareBootUnitActivateStatusFailed

Fault Code:F0856

Message

Activation failed and Activate Status set to failed.

Explanation

This fault typically occurs for the following reasons: when firmware activation fails, or if the after activation running image is not the corresponding startup image.

•Firmware activation failed.

•The version of firmware running on the server after activation is not the version listed in Cisco UCS Manager as the startup image.

Recommended Action

If you see this fault, take the following actions:

Step 1 Go to FSM tab for the endpoint on which the fault is raised and review the error description for the reason that the activation failed.

Step 2 If the FSM failed, review the error message in the FSM.

Step 3 If possible, correct the problem described in the error message.

Step 4 If the problem persists, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: activation-failed 

CallHome: none 

mibFaultCode: 856 

mibFaultName: fltFirmwareBootUnitActivateStatusFailed 

moClass: firmware:BootUnit 

Type: management

fltFirmwareBootUnitCantBoot

Fault Code:F0471

Message

unable to boot the startup image. End point booted with backup image

Explanation

This fault typically occurs when the startup firmware image on an endpoint is corrupted or invalid, and the endpoint cannot boot from that image.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the fault and the error message on the FSM tab for the endpoint to determine why the firmware image is unusable. The error message usually includes an explanation for why the endpoint could not boot from the startup image, such as Bad-Image or Checksum Failed.

Step 2 If the firmware image is bad or corrupted, download another copy from the Cisco website and update the startup version on the endpoint with the new image.

Step 3 If the fault persists, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: image-cannot-boot 

CallHome: none 

mibFaultCode: 471 

mibFaultName: fltFirmwareBootUnitCantBoot 

moClass: firmware:BootUnit 

Type: management

fltFirmwarePackItemImageMissing

Fault Code:F0436

Message

[type] image with vendor [hwVendor], model [hwModel] and version [version] is deleted

Explanation

This fault typically occurs when the image to which a firmware package item refers is missing.

Recommended Action

If you see this fault, take the following actions:

Step 1 In Cisco UCS Manager GUI, navigate to the Firmware Management Images tab and determine whether the missing image is available or not.

Step 2 If the image is present, click on it to verify the model and vendor.

Step 3 If the image for the required model and vendor is not present, download that image or bundle from the Cisco.com website.

Step 4 If the image is present and the fault persists, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: image-deleted 

CallHome: none 

mibFaultCode: 436 

mibFaultName: fltFirmwarePackItemImageMissing 

moClass: firmware:PackItem 

Type: management

fltFirmwareUpdatableImageUnusable

Fault Code:F0470

Message

backup image is unusable. reason: [operStateQual]

Explanation

This fault typically occurs when the backup firmware image on an endpoint is unusable.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the fault and the error message on the FSM tab for the endpoint to determine why the firmware image is unusable.

Step 2 If the firmware image is bad or corrupted, download another copy from the Cisco website and update the backup version on the endpoint with the new image.

Step 3 If the image is present and the fault persists, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: image-unusable 

CallHome: none 

mibFaultCode: 470 

mibFaultName: fltFirmwareUpdatableImageUnusable 

moClass: firmware:Updatable 

Type: management

I/O Module-Related Faults

This section contains faults raised as a result of issues related to an I/O module in the Cisco UCS instance.

fltEquipmentIOCardIdentity

Fault Code:F0405

Message

[side] IOM [chassisId]/[id] ([switchId]) has a malformed FRU

Explanation

This fault typically occurs when the FRU information for an I/O module is corrupted or malformed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco UCS Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: fru-problem 

CallHome: diagnostic 

mibFaultCode: 405 

mibFaultName: fltEquipmentIOCardIdentity 

moClass: equipment:IOCard 

Type: equipment

fltEquipmentIOCardInaccessible

Fault Code:F0478

Message

[side] IOM [chassisId]/[id] ([switchId]) is inaccessible

Explanation

This fault typically occurs because an I/O module has lost its connection to the fabric interconnects. In a cluster configuration, the chassis fails over to the other I/O module. For a standalone configuration, the chassis associated with the I/O module loses network connectivity. This is a critical fault because it can result in the loss of network connectivity and disrupt data traffic through the I/O module.

Recommended Action

If you see this fault, take the following actions:

Step 1 Wait a few minutes to see if the fault clears. This is typically a temporary issue, and can occur after a firmware upgrade.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: equipment-inaccessible 

CallHome: diagnostic 

mibFaultCode: 478 

mibFaultName: fltEquipmentIOCardInaccessible 

moClass: equipment:IOCard 

Type: equipment

fltEquipmentIOCardPeerDisconnected

Fault Code:F0403

Message

IOM [chassisId]/[id] ([switchId]) peer connectivity: [peerCommStatus]

Explanation

This fault typically occurs when an I/O module is unable to communicate with its peer I/O module.

Recommended Action

If you see this fault, take the following actions:

Step 1 Wait a few minutes to see if the fault clears. This is typically a temporary issue, and can occur after a firmware upgrade.

Step 2 If the fault does not clear after a few minutes, remove and reinsert the I/O module.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: equipment-disconnected 

CallHome: none 

mibFaultCode: 403 

mibFaultName: fltEquipmentIOCardPeerDisconnected 

moClass: equipment:IOCard 

Type: connectivity

fltEquipmentIOCardPost-failure

Fault Code:F0481

Message

[side] IOM [chassisId]/[id] ([switchId]) POST failure

Explanation

This fault typically occurs when an I/O module encounters errors during the Power On Self Test (POST). The impact of this fault varies according to the errors that were encountered during POST.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the POST results for the I/O module. In Cisco UCS Manager GUI, you can access the POST results from the General tab for the I/O module. In Cisco UCS Manager CLI, you can access the POST results through the show post command under the scope for the I/O module.

Step 2 Reboot the I/O module.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: equipment-problem 

CallHome: diagnostic 

mibFaultCode: 481 

mibFaultName: fltEquipmentIOCardPostFailure 

moClass: equipment:IOCard 

Type: equipment

fltEquipmentIOCardRemoved

Fault Code:F0376

Message

[side] IOM [chassisId]/[id] ([switchId]) is removed

Explanation

This fault typically occurs because an I/O module is removed from the chassis. In a cluster configuration, the chassis fails over to the other I/O module. For a standalone configuration, the chassis associated with the I/O module loses network connectivity. This is a critical fault because it can result in the loss of network connectivity and disrupt data traffic through the I/O module.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reinsert the I/O module and configure the fabric-interconnect ports connected to it as server ports and wait a few minutes to see if the fault clears.

Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: equipment-removed 

CallHome: none 

mibFaultCode: 376 

mibFaultName: fltEquipmentIOCardRemoved 

moClass: equipment:IOCard 

Type: equipment

fltEquipmentIOCardThermalProblem

Fault Code:F0379

Message

[side] IOM [chassisId]/[id] ([switchId]) operState: [operState]

Explanation

This fault occurs when there is a thermal problem on an I/O module. Be aware of the following possible contributing factors:

•Temperature extremes can cause Cisco UCS equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

•Cisco UCS equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the I/O module.

Step 2 Review the Cisco UCS Site Preparation Guide to ensure the I/O modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco UCS chassis are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace faulty I/O modules.

Step 8 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 379 

mibFaultName: fltEquipmentIOCardThermalProblem 

moClass: equipment:IOCard 

Type: environmental

fltEquipmentIOCardThermalThresholdCritical

Fault Code:F0730

Message

[side] IOM [chassisId]/[id] ([switchId]) temperature: [thermal]

Explanation

This fault occurs when the temperature of an I/O module has exceeded a critical threshold value. Be aware of the following possible contributing factors:

•Temperature extremes can cause Cisco UCS equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

•Cisco UCS equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

•If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the I/O module.

Step 2 Review the Cisco UCS Site Preparation Guide to ensure the chassis and I/O modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco UCS chassis and I/O module are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace the faulty I/O modules.

Step 8 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 730 

mibFaultName: fltEquipmentIOCardThermalThresholdCritical 

moClass: equipment:IOCard 

Type: environmental

fltEquipmentIOCardThermalThresholdNonCritical

Fault Code:F0729

Message

[side] IOM [chassisId]/[id] ([switchId]) temperature: [thermal]

Explanation

This fault occurs when the temperature of an I/O module has exceeded a non-critical threshold value, but is still below the critical threshold. Be aware of the following possible contributing factors:

•Temperature extremes can cause Cisco UCS equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

•Cisco UCS equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

•If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the I/O module.

Step 2 Review the Cisco UCS Site Preparation Guide to ensure the chassis and I/O modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco UCS chassis and I/O module are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 729 

mibFaultName: fltEquipmentIOCardThermalThresholdNonCritical 

moClass: equipment:IOCard 

Type: environmental

fltEquipmentIOCardThermalThresholdNonRecoverable

Fault Code:F0731

Message

[side] IOM [chassisId]/[id] ([switchId]) temperature: [thermal]

Explanation

This fault occurs when the temperature of an I/O module has been out of the operating range, and the issue is not recoverable. Be aware of the following possible contributing factors:

•Temperature extremes can cause Cisco UCS equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

•Cisco UCS equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

•If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the I/O module.

Step 2 Review the Cisco UCS Site Preparation Guide to ensure the chassis and I/O modules have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco UCS chassis and I/O module are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Replace the faulty I/O modules.

Step 8 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 9 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 731 

mibFaultName: fltEquipmentIOCardThermalThresholdNonRecoverable 

moClass: equipment:IOCard 

Type: environmental

fltEquipmentIOCardUnacknowledged

Fault Code:F0402

Message

IOM [chassisId]/[id] ([switchId]) connectivity configuration: [configState]

Explanation

This fault typically occurs when an I/O module is unacknowledged.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the state of the I/O module links.

Step 2 Reacknowledge the chassis.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: equipment-unacknowledged 

CallHome: none 

mibFaultCode: 402 

mibFaultName: fltEquipmentIOCardUnacknowledged 

moClass: equipment:IOCard 

Type: connectivity

fltEquipmentIOCardUnsupportedConnectivity

Fault Code:F0401

Message

IOM [chassisId]/[id] ([switchId]) current connectivity does not match discovery policy: [configState]

Explanation

This fault typically occurs when the current connectivity for an I/O module does not match the configuration in the chassis discovery policy.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the correct number of links are configured in the chassis discovery policy.

Step 2 Check the state of the I/O module links.

Step 3 Reacknowledge the chassis.

Step 4 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: unsupported-connectivity-configuration 

CallHome: none 

mibFaultCode: 401 

mibFaultName: fltEquipmentIOCardUnsupportedConnectivity 

moClass: equipment:IOCard 

Type: connectivity

License-Related Faults

This section contains faults raised as a result of issues related to licensing.

fltLicenseFileBadLicenseFile

Fault Code:F0677

Message

license file [name] on fabric-interconnect [scope] can not be installed

Explanation

The installation of a license file on the fabric interconnect failed. This fault typically occurs if the license file is badly formatted or its host ID does not match that of the fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

Step 1 In the Cisco UCS Manager CLI, check the host IDs for both fabric interconnects. You can access the host ID information by entering the show server-host-id detail command under the license scope.

Step 2 Match the host IDs with the contents of the license file. If the host ID matches that of one of the fabric interconnects, create a show tech-support file and contact Cisco TAC. If it does not match, contact Cisco TAC to obtain the correct license File.

Fault Details

Severity: critical 

Cause: license-file-uninstallable 

CallHome: none 

mibFaultCode: 677 

mibFaultName: fltLicenseFileBadLicenseFile 

moClass: license:File 

Type: management

fltLicenseFileFileNotDeleted

Fault Code:F0678

Message

license file [name] from fabric-interconnect [scope] could not be deleted

Explanation

The deletion of a license file on the fabric interconnect has failed. This fault typically occurs if license framework is not able to delete a file.

Recommended Action

If you see this fault, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: license-file-not-deleted 

CallHome: none 

mibFaultCode: 678 

mibFaultName: fltLicenseFileFileNotDeleted 

moClass: license:File 

Type: management

fltLicenseInstanceGracePeriodWarning1

Fault Code:F0670

Message

license for [feature] on fabric-interconnect [scope] has entered into the grace period.

Explanation

At least one port on the fabric interconnect is running in the grace period. This fault typically occurs if one or more ports on the fixed module are enabled after all default licenses have been assigned to a port.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the number of licenses installed and being used on each fabric interconnect. In the Cisco UCS Manager GUI, you can access the licensing information from the Admin tab for the fabric interconnect. In the Cisco UCS Manager CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: license-graceperiod-entered 

CallHome: none 

mibFaultCode: 670 

mibFaultName: fltLicenseInstanceGracePeriodWarning1 

moClass: license:Instance 

Type: management

fltLicenseInstanceGracePeriodWarning2

Fault Code:F0671

Message

license for [feature] on fabric-interconnect [scope] is running in the grace period for more than 10 days

Explanation

At least one port on the fabric interconnect has been running in the grace period for more than 10 days. This fault typically occurs if one or more ports on the fixed module are enabled after all default licenses have been assigned to ports and the unlicensed ports have been running for more than 10 days.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the number of licenses installed and consumed on each fabric interconnect. In the Cisco UCS Manager GUI, you can access the licensing information from the Admin tab for the fabric interconnect. In the Cisco UCS Manager CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: license-graceperiod-10days 

CallHome: none 

mibFaultCode: 671 

mibFaultName: fltLicenseInstanceGracePeriodWarning2 

moClass: license:Instance 

Type: management

fltLicenseInstanceGracePeriodWarning3

Fault Code:F0672

Message

license for [feature] on fabric-interconnect [scope] is running in the grace period for more than 30 days

Explanation

At least one port on the fabric interconnect has been running in the grace period for more than 30 days. This fault typically occurs if one or more ports on the fixed module are enabled after all default licenses have been assigned to ports and the unlicensed ports have been running for more than 30 days.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the number of licenses installed and consumed on each fabric interconnect. In the Cisco UCS Manager GUI, you can access the licensing information from the Admin tab for the fabric interconnect. In the Cisco UCS Manager CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: license-graceperiod-30days 

CallHome: none 

mibFaultCode: 672 

mibFaultName: fltLicenseInstanceGracePeriodWarning3 

moClass: license:Instance 

Type: management

fltLicenseInstanceGracePeriodWarning4

Fault Code:F0673

Message

license for [feature] on fabric-interconnect [scope] is running in the grace period for more than 60 days

Explanation

At least one port on the fabric interconnect has been running in the grace period for more than 60 days. This fault typically occurs if one or more ports on the fixed module are enabled after all default licenses have been assigned to ports and the unlicensed ports have been running for more than 60 days.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the number of licenses installed and consumed on each fabric interconnect. In the Cisco UCS Manager GUI, you can access the licensing information from the Admin tab for the fabric interconnect. In the Cisco UCS Manager CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: license-graceperiod-60days 

CallHome: none 

mibFaultCode: 673 

mibFaultName: fltLicenseInstanceGracePeriodWarning4 

moClass: license:Instance 

Type: management

fltLicenseInstanceGracePeriodWarning5

Fault Code:F0674

Message

license for [feature] on fabric-interconnect [scope] is running in the grace period for more than 90 days

Explanation

At least one port on the fabric interconnect has been running in the grace period for more than 90 days. This fault typically occurs if one or more ports on the fixed module are enabled after all default licenses have been assigned to ports and the unlicensed ports have been running for more than 90 days.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the number of licenses installed and consumed on each fabric interconnect. In the Cisco UCS Manager GUI, you can access the licensing information from the Admin tab for the fabric interconnect. In the Cisco UCS Manager CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: license-graceperiod-90days 

CallHome: none 

mibFaultCode: 674 

mibFaultName: fltLicenseInstanceGracePeriodWarning5 

moClass: license:Instance 

Type: management

fltLicenseInstanceGracePeriodWarning6

Fault Code:F0675

Message

license for [feature] on fabric-interconnect [scope] is running in the grace period for more than 119 days

Explanation

At least one port on the fabric interconnect has been running in the grace period for more than 119 days. This fault typically occurs if one or more ports on the fixed module are enabled after all default licenses have been assigned to ports and the unlicensed ports have been running for more than 119 days.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the number of licenses installed and consumed on each fabric interconnect. In the Cisco UCS Manager GUI, you can access the licensing information from the Admin tab for the fabric interconnect. In the Cisco UCS Manager CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: license-graceperiod-119days 

CallHome: none 

mibFaultCode: 675 

mibFaultName: fltLicenseInstanceGracePeriodWarning6 

moClass: license:Instance 

Type: management

fltLicenseInstanceGracePeriodWarning7

Fault Code:F0676

Message

Grace period for [feature] on fabric-interconnect [scope] is expired. Please acquire a license for the same.

Explanation

At least one port on the fabric interconnect has been running in the grace period for more than 120 days. This fault typically occurs if one or more ports on the fixed module are enabled after all default licenses have been assigned to ports and the unlicensed ports have been running for more than 120 days. At this stage, the system licensing state is set to expired.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the number of licenses installed and consumed on each fabric interconnect. In the Cisco UCS Manager GUI, you can access the licensing information from the Admin tab for the fabric interconnect. In the Cisco UCS Manager CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 Disable the unlicensed ports to bring the number of enabled ports down to the number of total licenses.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC immediately to procure more licenses.

Fault Details

Severity: critical 

Cause: license-graceperiod-expired 

CallHome: environmental 

mibFaultCode: 676 

mibFaultName: fltLicenseInstanceGracePeriodWarning7 

moClass: license:Instance 

Type: management

Link-Related Faults

This section contains faults raised as a result of issues related to the links between a chassis or I/O module and a fabric interconnect.

fltEtherSwitchIntFIoSatellite-connection-absent

Fault Code:F0367

Message

No link between IOM port [chassisId]/[slotId]/[portId] and fabric interconnect [switchId]:[peerSlotId]/[peerPortId]

Explanation

This fault is raised when an I/O module fabric port, which links the I/O module port and the fabric interconnect, is not functional

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify the fabric interconnect-chassis topology. Make sure each I/O module is connected to only one fabric interconnect.

Step 2 Ensure that the fabric interconnect server port is configured and enabled.

Step 3 Ensure that the links are plugged in properly and reacknowledge the chassis.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: satellite-connection-absent 

CallHome: none 

mibFaultCode: 367 

mibFaultName: fltEtherSwitchIntFIoSatelliteConnectionAbsent 

moClass: ether:SwitchIntFIo 

Type: connectivity

Memory-Related Faults

This section contains faults raised as issues with memory units or DIMMs in a server.

fltMemoryArrayVoltageThresholdCritical

Fault Code:F0190

Message

Memory array [id] on server [chassisId]/[slotId] voltage: [voltage]Memory array [id] on server [id] voltage: [voltage]

Explanation

This fault occurs when the memory array voltage exceeds the specified hardware voltage rating

Recommended Action

If you see this fault, take the following actions:

Step 1 If the SEL is enabled, look at the SEL statistics on the DIMM to determine which threshold was crossed.

Step 2 Monitor the memory array for further degradation.

Step 3 If the fault occurs on a blade server memory array, remove the blade and re-insert into the chassis.

Step 4 In Cisco UCS Manager, decommission and recommission the server.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: voltage-problem 

CallHome: environmental 

mibFaultCode: 190 

mibFaultName: fltMemoryArrayVoltageThresholdCritical 

moClass: memory:Array 

Type: environmental

fltMemoryArrayVoltageThresholdNonCritical

Fault Code:F0189

Message

Memory array [id] on server [chassisId]/[slotId] voltage: [voltage]Memory array [id] on server [id] voltage: [voltage]

Explanation

This fault occurs when the memory array voltage is out of normal operating range, but hasn't yet reached a critical stage. Typically the memory array recovers itself from this situation.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the SEL is enabled, look at the SEL statistics on the DIMM to determine which threshold was crossed.

Step 2 Monitor the memory array for further degradation.

Step 3 If the fault occurs on a blade server memory array, remove the blade and re-insert into the chassis.

Step 4 In Cisco UCS Manager, decommission and recommission the server.

Step 5 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor 

Cause: voltage-problem 

CallHome: environmental 

mibFaultCode: 189 

mibFaultName: fltMemoryArrayVoltageThresholdNonCritical 

moClass: memory:Array 

Type: environmental

fltMemoryArrayVoltageThresholdNonRecoverable

Fault Code:F0191

Message

Memory array [id] on server [chassisId]/[slotId] voltage: [voltage]Memory array [id] on server [id] voltage: [voltage]

Explanation

This fault occurs when the memory array voltage exceeded the specified hardware voltage rating and potentially memory hardware may be in damage or jeopardy

Recommended Action

If you see this fault, take the following actions:

Step 1 If the SEL is enabled, review the SEL statistics on the DIMM to determine which threshold was crossed.

Step 2 Monitor the memory array for further degradation.

Step 3 If the fault occurs on a blade server memory array, remove the server from the chassis and re-insert it.

Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: voltage-problem 

CallHome: environmental 

mibFaultCode: 191 

mibFaultName: fltMemoryArrayVoltageThresholdNonRecoverable 

moClass: memory:Array 

Type: environmental

fltMemoryBufferUnitThermalThresholdCritical

Fault Code:F0536

Message

Buffer Unit [id] on server [chassisId]/[slotId] temperature: [thermal]Buffer Unit [id] on server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a memory buffer unit on a blade or rack server exceeds a critical threshold value. Be aware of the following possible contributing factors:

•Temperature extremes can cause Cisco UCS equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

•Cisco UCS equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

•If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco UCS Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco UCS chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 536 

mibFaultName: fltMemoryBufferUnitThermalThresholdCritical 

moClass: memory:BufferUnit 

Type: environmental

fltMemoryBufferUnitThermalThresholdNonCritical

Fault Code:F0535

Message

Buffer Unit [id] on server [chassisId]/[slotId] temperature: [thermal]Buffer Unit [id] on server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a memory buffer unit on a blade or rack server exceeds a non-critical threshold value, but is still below the critical threshold. Be aware of the following possible contributing factors:

•Temperature extremes can cause Cisco UCS equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

•Cisco UCS equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

•If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco UCS Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco UCS chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 535 

mibFaultName: fltMemoryBufferUnitThermalThresholdNonCritical 

moClass: memory:BufferUnit 

Type: environmental

fltMemoryBufferUnitThermalThresholdNonRecoverable

Fault Code:F0537

Message

Buffer Unit [id] on server [chassisId]/[slotId] temperature: [thermal]Buffer Unit [id] on server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a memory buffer unit on a blade or rack server has been out of the operating range, and the issue is not recoverable. Be aware of the following possible contributing factors:

•Temperature extremes can cause Cisco UCS equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

•Cisco UCS equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

•If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco UCS Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco UCS chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 537 

mibFaultName: fltMemoryBufferUnitThermalThresholdNonRecoverable 

moClass: memory:BufferUnit 

Type: environmental

fltMemoryUnitDegraded

Fault Code:F0184

Message

DIMM [location] on server [chassisId]/[slotId] operability: [operability]DIMM [location] on server [id] operability: [operability]

Explanation

This fault occurs when a DIMM is in a degraded operability state. This state typically occurs when an excessive number of correctable ECC errors are reported on the DIMM by the server BIOS.

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the error statistics on the degraded DIMM through Cisco UCS Manager. If the high number of errors persists, there is a high possibility of the DIMM becoming inoperable.

Step 2 If the DIMM becomes inoperable, replace the DIMM.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor 

Cause: equipment-degraded 

CallHome: none 

mibFaultCode: 184 

mibFaultName: fltMemoryUnitDegraded 

moClass: memory:Unit 

Type: equipment

fltMemoryUnitDisabled

Fault Code:F0844

Message

DIMM [location] on server [chassisId]/[slotId] operState: [operState]DIMM [location] on server [id] operaState: [operState]

Explanation

This fault is raised when the server BIOS disables a DIMM. The BIOS could disable a DIMM for several reasons, including incorrect location of the DIMM or incompatible speed.

Recommended Action

If you see this fault, refer to the Cisco UCS B-Series Troubleshooting Guide for information on how to resolve the DIMM issues.

Fault Details

Severity: major 

Cause: equipment-disabled 

CallHome: diagnostic 

mibFaultCode: 844 

mibFaultName: fltMemoryUnitDisabled 

moClass: memory:Unit 

Type: equipment

fltMemoryUnitIdentity-unestablishable

Fault Code:F0502

Message

DIMM [location] on server [chassisId]/[slotId] has an invalid FRUDIMM [location] on server [id] has an invalid FRU

Explanation

This fault typically occurs because Cisco UCS Manager has detected unsupported DIMM in the server. For example, the model, vendor, or revision is not recognized.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the capability catalog in Cisco UCS Manager is up to date. If necessary, update the catalog.

Step 2 If the above action did not resolve the issue, you may have unsupported DIMMs or DIMM configuration in the server. Create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning 

Cause: identity-unestablishable 

CallHome: none 

mibFaultCode: 502 

mibFaultName: fltMemoryUnitIdentityUnestablishable 

moClass: memory:Unit 

Type: equipment

fltMemoryUnitInoperable

Fault Code:F0185

Message

DIMM [location] on server [chassisId]/[slotId] operability: [operability]DIMM [location] on server [id] operability: [operability]

Explanation

This fault typically occurs because an above threshold number of correctable or uncorrectable errors has occurred on a DIMM. The DIMM may be inoperable.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the SEL is enabled, review the SEL statistics on the DIMM to determine which threshold was crossed.

Step 2 If necessary, replace the DIMM.

Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: equipment-inoperable 

CallHome: diagnostic 

mibFaultCode: 185 

mibFaultName: fltMemoryUnitInoperable 

moClass: memory:Unit 

Type: equipment

fltMemoryUnitThermalThresholdCritical

Fault Code:F0187

Message

DIMM [location] on server [chassisId]/[slotId] temperature: [thermal]DIMM [location] on server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a memory unit on a blade or rack server exceeds a critical threshold value. Be aware of the following possible contributing factors:

•Temperature extremes can cause Cisco UCS equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

•Cisco UCS equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

•If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco UCS Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco UCS chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 187 

mibFaultName: fltMemoryUnitThermalThresholdCritical 

moClass: memory:Unit 

Type: environmental

fltMemoryUnitThermalThresholdNonCritical

Fault Code:F0186

Message

DIMM [location] on server [chassisId]/[slotId] temperature: [thermal]DIMM [location] on server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a memory unit on a blade or rack server exceeds a non-critical threshold value, but is still below the critical threshold. Be aware of the following possible contributing factors:

•Temperature extremes can cause Cisco UCS equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

•Cisco UCS equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

•If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco UCS Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco UCS chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: minor 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 186 

mibFaultName: fltMemoryUnitThermalThresholdNonCritical 

moClass: memory:Unit 

Type: environmental

fltMemoryUnitThermalThresholdNonRecoverable

Fault Code:F0188

Message

DIMM [location] on server [chassisId]/[slotId] temperature: [thermal]DIMM [location] on server [id] temperature: [thermal]

Explanation

This fault occurs when the temperature of a memory unit on a blade or rack server has been out of the operating range, and the issue is not recoverable.Be aware of the following possible contributing factors:

•Temperature extremes can cause Cisco UCS equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.

•Cisco UCS equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

•If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

Step 1 Review the product specifications to determine the temperature operating range of the server.

Step 2 Review the Cisco UCS Site Preparation Guide to ensure the servers have adequate airflow, including front and back clearance.

Step 3 Verify that the air flows on the Cisco UCS chassis or rack server are not obstructed.

Step 4 Verify that the site cooling system is operating properly.

Step 5 Power off unused blade servers and rack servers.

Step 6 Clean the installation site at regular intervals to avoid buildup of dust and debris, which can cause a system to overheat.

Step 7 Use the Cisco UCS power capping capability to limit power usage. Power capping can limit the power consumption of the system, including blade and rack servers, to a threshold that is less than or equal to the system's maximum rated power. Power-capping can have an impact on heat dissipation and help to lower the installation site temperature.

Step 8 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical 

Cause: thermal-problem 

CallHome: environmental 

mibFaultCode: 188 

mibFaultName: fltMemoryUnitThermalThresholdNonRecoverable 

moClass: memory:Unit 

Type: environmental

Pin Group-Related Faults

This section contains faults raised as a result of issues related to a pin groups in the Cisco UCS instance.

fltFabricLanPinGroupEmpty

Fault Code:F0621

Message

LAN Pin Group [name] is empty

Explanation

This fault typically occurs when a LAN pin group does not contain any targets.

Recommended Action

If you see this fault, add a target to the LAN pin group.

Fault Details

Severity: minor 

Cause: empty-pin-group 

CallHome: none 

mibFaultCode: 621 

mibFaultName: fltFabricLanPinGroupEmpty 

moClass: fabric:LanPinGroup 

Type: server

fltFabricSanPinGroupEmpty

Fault Code:F0622

Message

SAN Pin Group [name] is empty

Explanation

This fault typically occurs when a SAN pin group does not contain any targets.

Recommended Action

If you see this fault, add a target to the SAN pin group.

Fault Details

Severity: minor 

Cause: empty-pin-group 

CallHome: none 

mibFaultCode: 622 

mibFaultName: fltFabricSanPinGroupEmpty 

moClass: fabric:SanPinGroup 

Type: server

fltVnicEtherPinningMisconfig

Fault Code:F0841

Message

Hard pinning target for eth vNIC [name], service profile [name] is missing or misconfigured

Explanation