• Chassis-Related Faults
  • Chassis Slot-Related Faults
  • Ethernet-Related Faults
  • Fabric Extended (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 Supply-Related Faults
  • Processor-Related Faults
  • Server-Related Faults
  • Service Profile-Related Faults
  • System Event Log-Related Faults
  • Traffic Monitioring-related Faults
  • Virtual Network Interface-Related Faults
  • VLAN-Related Faults
  • VSAN-Related Faults

    • 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

    •Ethernet-Related Faults

    •Fabric Extended (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 Supply-Related Faults

    •Processor-Related Faults

    •Server-Related Faults

    •Service Profile-Related Faults

    •System Event Log-Related Faults

    •Traffic Monitioring-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 network facing adaptor interface's link is misconnected.The Cisco UCS Manager raises this fault when any of the following scenario occur:

    •UCSM detects a new connectivity between previously configured switch port/fex port and reported adaptor external interface.

    •UCSM detects a misconnected link between a fabric interconnect/fex and its non-peer adaptor's interface.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Check whether the adaptor link is connected to a port belonging to its peer fabric interconnect/fabric extender.

    Step 3 If connectivity seems correct, reacknowledge the server.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: link-misconnected 

    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 network facing adaptor interface's link is missingThe Cisco UCS Manager raises this fault when any of the following scenario occur:

    •UCSM detects a missing connectivity between previously configured switch port/fex port and its previous peer adaptor external interface.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Check whether there is any adaptor link misconnected to non-peer fabric interconnect/fabric extender

    Step 3 If connectivity seems correct, reacknowledge the server

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: link-missing 

    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 network facing adaptor interface's link is down.The Cisco UCS Manager raises this fault when any of the following scenarios occur:

    •The UCSM can not establish and/or validate adaptor's connectivity to any one of the fabric interconnects.

    •Endpoint reports the link down (or vNIC down) event on the adaptor link

    •Endpoint reports the errored link state (or errored vnic state) event on the adaptor link

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

    Step 3 If the server is stuck at discovery, decommision the server and reacknowledge the server slot.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: link-down 

    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

    network facing host interface link is misconnectedCisco UCS Manager raises this fault when any of the following scenario occur:

    •UCSM detects a new connectivity between previously configured switch port and reported host ethernet interface.

    •UCSM detects a misconnected link between host interface & its non-peer fabric interconnect.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Check whether the adaptor link is connected to a port belonging to its peer fabric interconnect.

    Step 3 If connectivity seems correct, reacknowledge the server.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: link-misconnected 

    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

    network facing host interface link is missingCisco UCS Manager raises this fault when any of the following scenario occur:

    •UCSM detects a missing connectivity between previously configured switch port and its previous peer host interface

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Check whether there is any adaptor link misconnected to non-peer fabric interconnect

    Step 3 If connectivity seems correct, reacknowledge the server

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: link-missing 

    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 the End-Host mode, and all uplink ports failed.

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

    •A transient error that caused the link to fail.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

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

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: link-down 

    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

    The 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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

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

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

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

    Step 6 If the server is on, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: info 

    Cause: connectivity-problem 

    mibFaultCode: 206 

    mibFaultName: fltAdaptorUnitAdaptorReachability 

    moClass: adaptor:Unit 

    Type: connectivity

    fltAdaptorUnitMissing

    Fault Code:F0203

    Message

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

    Explanation

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

    •Endpoint reports there is no mezz card plugged into an adaptor slot

    •Endpoint can not detect/communicate to the mezz card plugged into an adaptor slot

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Make sure the mezz card is plugged into an adaptor slot in the server.

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

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: equipment-missing 

    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 the 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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Verify that a supported adapter is installed.

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

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: unidentifiable-fru 

    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 an I/O module has corrupted or has malformed FRU information.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: fru-problem 

    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 the 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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

    Step 3 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: identity-unestablishable 

    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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 In Cisco UCS Manager, acknowledge the chassis that raised the fault.

    Step 3 Physically unplug and re-plug the power cord to the chassis.

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

    Step 5 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: equipment-inoperable 

    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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

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

    Step 4 Physically unplug and re-plug the power cord to the chassis.

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

    Step 6 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: power-problem 

    mibFaultCode: 408 

    mibFaultName: fltEquipmentChassisPowerProblem 

    moClass: equipment:Chassis 

    Type: environmental

    fltEquipmentChassisSeeprom-inoperable

    Fault Code:F0733

    Message

    Device [id] SEEPROM operability: [seepromOperState]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: equipment-inoperable 

    mibFaultCode: 733 

    mibFaultName: fltEquipmentChassisSeepromInoperable 

    moClass: equipment:Chassis 

    Type: equipment

    fltEquipmentChassisThermalThresholdCritical

    Fault Code:F0409

    Message

    Temperature on chassis [id] is [thermal]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: thermal-problem 

    mibFaultCode: 409 

    mibFaultName: fltEquipmentChassisThermalThresholdCritical 

    moClass: equipment:Chassis 

    Type: environmental

    fltEquipmentChassisThermalThresholdNonCritical

    Fault Code:F0410

    Message

    Temperature on chassis [id] is [thermal]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: thermal-problem 

    mibFaultCode: 410 

    mibFaultName: fltEquipmentChassisThermalThresholdNonCritical 

    moClass: equipment:Chassis 

    Type: environmental

    fltEquipmentChassisThermalThresholdNonRecoverable

    Fault Code:F0411

    Message

    Temperature on chassis [id] is [thermal]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: thermal-problem 

    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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

    Step 3 Reacknowledge the chassis.

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: equipment-unacknowledged 

    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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

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

    Step 4 Reacknowledge the chassis.

    Step 5 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: unsupported-connectivity-configuration 

    mibFaultCode: 399 

    mibFaultName: fltEquipmentChassisUnsupportedConnectivity 

    moClass: equipment:Chassis 

    Type: connectivity

    fltFabricComputeSlotEpMisplacedInChassisSlot

    Fault Code:F0156

    Message

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

    Explanation

    This fault typically occurs when the 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 inserted, reacknowledge the server.

    Step 2 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: server-moved 

    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 the 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 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: server-identification-problem 

    mibFaultCode: 157 

    mibFaultName: fltFabricComputeSlotEpServerIdentificationProblem 

    moClass: fabric:ComputeSlotEp 

    Type: equipment

    fltMgmtEntityChassis-1-SEEPROM-error

    Fault Code:F0453

    Message

    Chassis [chassis1], error accessing SEEPROM

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: chassis-seeprom-error 

    mibFaultCode: 453 

    mibFaultName: fltMgmtEntityChassis1SEEPROMError 

    moClass: mgmt:Entity 

    Type: management

    fltMgmtEntityChassis-2-SEEPROM error

    Fault Code:F0454

    Message

    Chassis [chassis2], error accessing SEEPROM

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: chassis-seeprom-error 

    mibFaultCode: 454 

    mibFaultName: fltMgmtEntityChassis2SEEPROMError 

    moClass: mgmt:Entity 

    Type: management

    fltMgmtEntityChassis-3-SEEPROM error

    Fault Code:F0455

    Message

    Chassis [chassis3], error accessing SEEPROM

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: chassis-seeprom-error 

    mibFaultCode: 455 

    mibFaultName: fltMgmtEntityChassis3SEEPROMError 

    moClass: mgmt:Entity 

    Type: management

    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 inserted, reacknowledge the server.

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

    Fault Details 

    Severity: warning 

    Cause: server-moved 

    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, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: server-identification-problem 

    mibFaultCode: 157 

    mibFaultName: fltFabricComputeSlotEpServerIdentificationProblem 

    moClass: fabric:ComputeSlotEp 

    Type: equipment

    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

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: interface-failed 

    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 a 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.

    Fault Details 

    Severity: major 

    Cause: membership-down 

    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 a 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.

    Fault Details 

    Severity: major 

    Cause: membership-down 

    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 the 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 steps do not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: configuration-failed 

    mibFaultCode: 169 

    mibFaultName: fltVnicEtherConfigFailed 

    moClass: vnic:Ether 

    Type: configuration

    Fabric Extended (FEX)-Related Faults

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

    fltEquipmentFexIdentity

    Fault Code:F0703

    Message

    Fex [id] has a malformed FRU

    Explanation

    This fault typically occurs when an fex has corrupted or has malformed FRU information.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

    Step 3 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: fru-problem 

    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 the 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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

    Step 3 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: identity-unestablishable 

    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 the fex encounters errors during the Power On Self Test (POST). The impact of this fault varies depending on what errors were encountered during POST.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 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 through the show post command under the scope for the fex.

    Step 3 Reboot the fex.

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: equipment-problem 

    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-numbers-unexpected

    Fault Code:F0440

    Message

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

    Explanation

    Chassis discovery policy conflict with present iom uplinksCisco UCS Manager raises this fault when any of the following scenario occur:

    •UCSM detects number of present IOM uplinks are less than that defined in Chassis discovery policy link-action

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Make sure that number of present IOM uplinks are at least same as that defined in chassis discovery policy link-action. Configure corresponding sever ports.

    Step 3 Re-acknowledge the chassis to acknowledge the mismatched number of present links.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: info 

    Cause: unexpected-number-of-links 

    mibFaultCode: 440 

    mibFaultName: fltEtherSwitchIntFIoSatelliteWiringNumbersUnexpected 

    moClass: ether:SwitchIntFIo 

    Type: connectivity

    fltEtherSwitchIntFIoSatellite-wiring-problem

    Fault Code:F0368

    Message

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

    Explanation

    There is a satellite wiring problem on network facing interface of IO-moduleThe Cisco UCS Manager raises this fault when any of the following scenario occur:

    •The UCSM detects that at least one IOM uplink is misconnected to one of the (fabric interconnect) switch port

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Verify the fabric interconnect-chassis topology. Make sure each IO Module is connected to only one fabric interconnect

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

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: info 

    Cause: satellite-mis-connected 

    mibFaultCode: 368 

    mibFaultName: fltEtherSwitchIntFIoSatelliteWiringProblem 

    moClass: ether:SwitchIntFIo 

    Type: connectivity

    fltExtmgmtIfMgmtifdown

    Fault Code:F0736

    Message

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

    Explanation

    External management interface on fabric interconnect is operationally down.The Cisco UCS Manager raises this fault when any of the following scenario occur:

    •Endpoint(switch/fabric interconnect) reports that operational state of external management interface is down.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Check the state transitions of external management interface on fabric interconnect. Check the link connectivity

    Step 3 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: mgmtif-down 

    mibFaultCode: 736 

    mibFaultName: fltExtmgmtIfMgmtifdown 

    moClass: extmgmt:If 

    Type: management

    fltMgmtEntityDegraded

    Fault Code:F0293

    Message

    Fabric Interconnect [id], HA Cluster interconnect link failure

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: link-down 

    mibFaultCode: 293 

    mibFaultName: fltMgmtEntityDegraded 

    moClass: mgmt:Entity 

    Type: network

    fltMgmtEntityDown

    Fault Code:F0294

    Message

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

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: link-down 

    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

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: election-failure 

    mibFaultCode: 428 

    mibFaultName: fltMgmtEntityElectionFailure 

    moClass: mgmt:Entity 

    Type: management

    fltMgmtEntityHa-not-ready

    Fault Code:F0429

    Message

    Fabric Interconnect [id], HA functionality not ready

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: ha-not-ready 

    mibFaultCode: 429 

    mibFaultName: fltMgmtEntityHaNotReady 

    moClass: mgmt:Entity 

    Type: management

    fltMgmtEntityManagement-services-failure

    Fault Code:F0451

    Message

    Fabric Interconnect [id], management services have failed

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: management-services-failure 

    mibFaultCode: 451 

    mibFaultName: fltMgmtEntityManagementServicesFailure 

    moClass: mgmt:Entity 

    Type: management

    fltMgmtEntityManagement-services-unresponsive

    Fault Code:F0452

    Message

    Fabric Interconnect [id], management services are unresponsive

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: management-services-unresponsive 

    mibFaultCode: 452 

    mibFaultName: fltMgmtEntityManagementServicesUnresponsive 

    moClass: mgmt:Entity 

    Type: management

    fltMgmtEntityVersion-incompatible

    Fault Code:F0430

    Message

    Fabric Interconnect [id], management services, incompatible versions

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: version-incompatible 

    mibFaultCode: 430 

    mibFaultName: fltMgmtEntityVersionIncompatible 

    moClass: mgmt:Entity 

    Type: management

    fltNetworkElementInoperable

    Fault Code:F0291

    Message

    Fabric Interconnect [id] operability: [operability]

    Explanation

    The IO fabric interconnect is inoperable. The Cisco UCS Manager raises this fault when any of the following scenarios occur:

    •The switch cluster controller reports that the membership state of the fabric interconnect is down.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Make sure that both the fabric interconnects in the HA cluster are running the same switch software versions.

    Step 3 Verify that the fabric interconnect is running the switch software version compatible to the UCS Manager software version.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: equipment-inoperable 

    mibFaultCode: 291 

    mibFaultName: fltNetworkElementInoperable 

    moClass: network:Element 

    Type: equipment

    fltStorageItemCapacityExceeded

    Fault Code:F0182

    Message

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

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: capacity-exceeded 

    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

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: capacity-exceeded 

    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 [id]/[tray]-[id] operability: [operability]Fan [id] in fabric interconnect [id] operability: [operability]Fan [id] in fex [id] operability: [operability]Fan [id] in server [id] operability: [operability]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: equipment-degraded 

    mibFaultCode: 371 

    mibFaultName: fltEquipmentFanDegraded 

    moClass: equipment:Fan 

    Type: equipment

    fltEquipmentFanInoperable

    Fault Code:F0373

    Message

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

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: equipment-inoperable 

    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 server [id] presence: [presence]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: equipment-missing 

    mibFaultCode: 434 

    mibFaultName: fltEquipmentFanMissing 

    moClass: equipment:Fan 

    Type: equipment

    fltEquipmentFanModuleDegraded

    Fault Code:F0480

    Message

    Fan module [id]/[tray]-[id] operability: [operability]Fan module [id]/[tray]-[id] operability: [operability]Fan module [id]/[tray]-[id] operability: [operability]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: equipment-degraded 

    mibFaultCode: 480 

    mibFaultName: fltEquipmentFanModuleDegraded 

    moClass: equipment:FanModule 

    Type: equipment

    fltEquipmentFanModuleIdentity

    Fault Code:F0406

    Message

    Fan Module [id]/[tray]-[id] has a malformed FRUFan Module [id]/[tray]-[id] has a malformed FRU

    Explanation

    This fault typically occurs when fan module has corrupted or has malformed FRU information.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: fru-problem 

    mibFaultCode: 406 

    mibFaultName: fltEquipmentFanModuleIdentity 

    moClass: equipment:FanModule 

    Type: equipment

    fltEquipmentFanModuleInoperable

    Fault Code:F0794

    Message

    Fan [id] in server [id] operability: [operability]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: equipment-inoperable 

    mibFaultCode: 794 

    mibFaultName: fltEquipmentFanModuleInoperable 

    moClass: equipment:FanModule 

    Type: equipment

    fltEquipmentFanModuleMissing

    Fault Code:F0377

    Message

    Fan module [id]/[tray]-[id] presence: [presence]Fan module [id]/[tray]-[id] presence: [presence]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: equipment-missing 

    mibFaultCode: 377 

    mibFaultName: fltEquipmentFanModuleMissing 

    moClass: equipment:FanModule 

    Type: equipment

    fltEquipmentFanModuleThermalThresholdCritical

    Fault Code:F0382

    Message

    Fan module [id]/[tray]-[id] temperature: [thermal]Fan module [id]/[tray]-[id] temperature: [thermal]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: thermal-problem 

    mibFaultCode: 382 

    mibFaultName: fltEquipmentFanModuleThermalThresholdCritical 

    moClass: equipment:FanModule 

    Type: environmental

    fltEquipmentFanModuleThermalThresholdNonCritical

    Fault Code:F0380

    Message

    Fan module [id]/[tray]-[id] temperature: [thermal]Fan module [id]/[tray]-[id] temperature: [thermal]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: thermal-problem 

    mibFaultCode: 380 

    mibFaultName: fltEquipmentFanModuleThermalThresholdNonCritical 

    moClass: equipment:FanModule 

    Type: environmental

    fltEquipmentFanModuleThermalThresholdNonRecoverable

    Fault Code:F0384

    Message

    Fan module [id]/[tray]-[id] temperature: [thermal]Fan module [id]/[tray]-[id] temperature: [thermal]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: thermal-problem 

    mibFaultCode: 384 

    mibFaultName: fltEquipmentFanModuleThermalThresholdNonRecoverable 

    moClass: equipment:FanModule 

    Type: environmental

    fltEquipmentFanPerfThresholdCritical

    Fault Code:F0396

    Message

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

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: info 

    Cause: performance-problem 

    mibFaultCode: 396 

    mibFaultName: fltEquipmentFanPerfThresholdCritical 

    moClass: equipment:Fan 

    Type: equipment

    fltEquipmentFanPerfThresholdLowerNonRecoverable

    Fault Code:F0484

    Message

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

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: performance-problem 

    mibFaultCode: 484 

    mibFaultName: fltEquipmentFanPerfThresholdLowerNonRecoverable 

    moClass: equipment:Fan 

    Type: equipment

    fltEquipmentFanPerfThresholdNonCritical

    Fault Code:F0395

    Message

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

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: info 

    Cause: performance-problem 

    mibFaultCode: 395 

    mibFaultName: fltEquipmentFanPerfThresholdNonCritical 

    moClass: equipment:Fan 

    Type: equipment

    fltEquipmentFanPerfThresholdNonRecoverable

    Fault Code:F0397

    Message

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

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: info 

    Cause: performance-problem 

    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 vNIC.

    fltVnicFcConfig-failed

    Fault Code:F0170

    Message

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

    Explanation

    This fault typically occurs when the 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 steps do not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: configuration-failed 

    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.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If IOM version and switch version are not the same, then wait for some time for auto-upgarde to complete

    Step 2 Auto-upgarde happens when IOM version is no longer compatible with Switch version.

    Step 3 Fault will be cleared automatically when IOM upgrade is completed.

    Step 4 If you see the fault even after IOM Overall Status changes to operabale, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: auto-firmware-upgrade 

    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 Check FSM status under IOM and check if the FSM upgarde was completed successfully or failed.

    Step 2 If FSM failed, then look for the error message in the FSM.

    Step 3 If the error message is self-explanatory, eg: No connection to end point or link down etc, check the physical connectivity.

    Step 4 If the fault persists, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: firmware-upgrade-problem 

    mibFaultCode: 398 

    mibFaultName: fltEquipmentIOCardFirmwareUpgrade 

    moClass: equipment:IOCard 

    Type: equipment

    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 image is corrupted/invalid and end point cannot boot from startup image.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Go to FSM tab for the end point on which the fault is raised and check for error description.

    Step 2 If FSM failed, then look for the error message in the FSM.

    Step 3 Error message usually tells why end point was not able to boot the startup image. Eg: Something like Bad-Image or checksum failed etc.

    Step 4 If the fault persists, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: image-cannot-boot 

    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 the pack item is refering to is not present.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Go to Firmware Management-Images tab in GUI and check if the image which is reported as missing is available or not.

    Step 2 If Image is present, check for model and vendor of the image by selecting the image.

    Step 3 If the image for specified model and vendor is not present, then download that image or bundle from cisco

    Step 4 If the image is present and the fault persists, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: image-deleted 

    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 image is unusable.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Check out the reason specified for the backup image unusable.

    Step 2 If it is bad-image/corrupted-image, try downloading the image again from Cisco site..

    Step 3 If the image is present and the fault persists, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: image-unusable 

    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 an I/O module has corrupted or has malformed FRU information.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: fru-problem 

    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 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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

    Step 3 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: equipment-inaccessible 

    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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

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

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: equipment-disconnected 

    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 the I/O module encounters errors during the Power On Self Test (POST). The impact of this fault varies depending on what errors were encountered during POST.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 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 3 Reboot the I/O module.

    Step 4 If the above actions did not resolve the issue, execute the show tech-supportcommand and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: equipment-problem 

    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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Re-insert 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 3 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: equipment-removed 

    mibFaultCode: 376 

    mibFaultName: fltEquipmentIOCardRemoved 

    moClass: equipment:IOCard 

    Type: equipment

    fltEquipmentIOCardThermalProblem

    Fault Code:F0379

    Message

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

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: thermal-problem 

    mibFaultCode: 379 

    mibFaultName: fltEquipmentIOCardThermalProblem 

    moClass: equipment:IOCard 

    Type: environmental

    fltEquipmentIOCardThermalThresholdCritical

    Fault Code:F0730

    Message

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

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: thermal-problem 

    mibFaultCode: 730 

    mibFaultName: fltEquipmentIOCardThermalThresholdCritical 

    moClass: equipment:IOCard 

    Type: environmental

    fltEquipmentIOCardThermalThresholdNonCritical

    Fault Code:F0729

    Message

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

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: thermal-problem 

    mibFaultCode: 729 

    mibFaultName: fltEquipmentIOCardThermalThresholdNonCritical 

    moClass: equipment:IOCard 

    Type: environmental

    fltEquipmentIOCardThermalThresholdNonRecoverable

    Fault Code:F0731

    Message

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

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: thermal-problem 

    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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

    Step 3 Reacknowledge the chassis.

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: equipment-unacknowledged 

    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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

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

    Step 4 Reacknowledge the chassis.

    Step 5 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: unsupported-connectivity-configuration 

    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

    Installation of a license file on this fabric interconnect has failed.This fault typically occurs if license file is badly formatted or does not have a matching server host ID with fabric interconnect.

    Recommended Action

    If you see this fault, take the following actions:

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

    Step 2 Match the host-IDs with the contents in license file procured, if it matches, execute the show tech-support command and contact Cisco Technical Support.

    Step 3 If it does not match, contact Cisco Technical Support for the correct license file.

    Fault Details 

    Severity: critical 

    Cause: license-file-uninstallable 

    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

    Deletion of a license file on this 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, take the following actions:

    Step 1 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: license-file-not-deleted 

    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

    The fabric interconnect is running at least one port in the grace-period.This fault typically occurs if one or more ports on the fixed module are enabled after consuming all default licenses.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, check the number of ports enabled on Fixed module.

    Step 2 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 issuing show usage detail command under the license scope.

    Step 3 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: license-graceperiod-entered 

    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

    The fabric interconnect is running atleast one port in grace-period for more than 10 days.This fault typically occurs if one or more ports on the fixed module are enabled after consuming all default licenses and system is in this state for more than 10 days.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, check the number of ports enabled on Fixed module.

    Step 2 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 issuing show usage detail command under the license scope.

    Step 3 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: license-graceperiod-10days 

    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

    The fabric interconnect is running at least one port in grace-period for more than 30 days.This fault typically occurs if one or more ports on the fixed module are enabled after consuming all default licenses and system is in this state for more than 30 days.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, check the number of ports enabled on Fixed module.

    Step 2 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 issuing show usage detail command under the license scope.

    Step 3 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: license-graceperiod-30days 

    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

    The fabric interconnect is running at least one port in grace-period for more than 60 days.This fault typically occurs if one or more ports on the fixed module are enabled after consuming all default licenses and system is in this state for more than 60 days.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, check the number of ports enabled on Fixed module.

    Step 2 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 issuing show usage detail command under the license scope.

    Step 3 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: license-graceperiod-60days 

    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

    The fabric interconnect is running at least one port in grace-period for more than 90 days.This fault typically occurs if one or more ports on the fixed module are enabled after consuming all default licenses and system is in this state for more than 90 days.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, check the number of ports enabled on Fixed module.

    Step 2 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 issuing show usage detail command under the license scope.

    Step 3 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: license-graceperiod-90days 

    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

    The fabric interconnect is running at least one port in grace-period for more than 119 days.This fault typically occurs if one or more ports on the fixed module are enabled after consuming all default licenses and system is in this state for more than 119 days.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, check the number of ports enabled on Fixed module.

    Step 2 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 issuing show usage detail command under the license scope.

    Step 3 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: license-graceperiod-119days 

    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

    The fabric interconnect is running atleast one port in grace-period for more than 120 days.This fault typically occurs if one or more ports on the fixed module are enabled after consuming all default licenses and system is in this state for more than 120 days. This puts the system licensing state as expired.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, check the number of ports enabled on Fixed module.

    Step 2 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 issuing show usage detail command under the license scope.

    Step 3 Execute the show tech-support command and contact Cisco Technical Support immediately to procure more licenses.

    Step 4 Disable any additional ports to bring the number of enabled ports down to the number of total licenses.

    Fault Details 

    Severity: critical 

    Cause: license-graceperiod-expired 

    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

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: satellite-connection-absent 

    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

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: voltage-problem 

    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

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: voltage-problem 

    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

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: voltage-problem 

    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

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: thermal-problem 

    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

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: thermal-problem 

    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

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: thermal-problem 

    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

    The DIMM is in a degraded operability stateThe Cisco UCS Manager raises this fault when any of the following scenarios occur:

    •The UCSM marks a memory unit (DIMM) as degraded operability when an excessive number of correctable ECC errors are reported by BIOS.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Monitor the error statistics on the degraded DIMM through the GUI tab. If the high number of errors persists, there is a high possibilty of the DIMM becoming inoperable.

    Step 3 The fault indicates that the DIMM is operating in a degraded state. If the DIMM becomes inoperable, replace the DIMM.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: equipment-degraded 

    mibFaultCode: 184 

    mibFaultName: fltMemoryUnitDegraded 

    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 the 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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

    Step 3 If the above actions did not resolve the issue, you may have unsupported DIMMs or DIMM configuration in the server. Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: identity-unestablishable 

    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 occurred on a DIMM. The DIMM may be inoperable.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

    Step 3 If necessary, replace the DIMM.

    Step 4 If the above actions do not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: equipment-inoperable 

    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

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: thermal-problem 

    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

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: thermal-problem 

    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

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: thermal-problem 

    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, take the following action:

    Step 1 Add a target to the LAN Pin Group.

    Fault Details 

    Severity: minor 

    Cause: empty-pin-group 

    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, take the following action:

    Step 1 Add a target to the SAN Pin Group.

    Fault Details 

    Severity: minor 

    Cause: empty-pin-group 

    mibFaultCode: 622 

    mibFaultName: fltFabricSanPinGroupEmpty 

    moClass: fabric:SanPinGroup 

    Type: server

    Pool-Related Faults

    This section contains faults raised as a result of issues related to a server pool, UUID suffix pool, or other pool in the Cisco UCS instance.

    fltComputePoolEmpty

    Fault Code:F0463

    Message

    server pool [name] is empty

    Explanation

    This fault typically occurs when the selected server pool does not contain any servers.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Verify the qualifier settings in the server pool policy qualifications. If the policy was modified after the server was discovered, reacknowledge the server.

    Step 2 Manually associate the service profile with a server.

    Step 3 If the server pool is not used, ignore the fault.

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: empty-pool 

    mibFaultCode: 463 

    mibFaultName: fltComputePoolEmpty 

    moClass: compute:Pool 

    Type: server

    fltFcpoolInitiatorsEmpty

    Fault Code:F0476

    Message

    FC pool [purpose] [name] is empty

    Explanation

    This fault typically occurs when a WWN pool does not contain any WWNs.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the pool is in use, add a block of WWNs to the pool.

    Step 2 If the pool is not in use, ignore the fault.

    Fault Details 

    Severity: minor 

    Cause: empty-pool 

    mibFaultCode: 476 

    mibFaultName: fltFcpoolInitiatorsEmpty 

    moClass: fcpool:Initiators 

    Type: server

    fltIppoolPoolEmpty

    Fault Code:F0465

    Message

    IP pool [name] is empty

    Explanation

    This fault typically occurs when an IP address pool does not contain any IP addresses.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the pool is in use, add a block of IP addresses to the pool.

    Step 2 If the pool is not in use, ignore the fault.

    Fault Details 

    Severity: minor 

    Cause: empty-pool 

    mibFaultCode: 465 

    mibFaultName: fltIppoolPoolEmpty 

    moClass: ippool:Pool 

    Type: server

    fltMacpoolPoolEmpty

    Fault Code:F0466

    Message

    MAC pool [name] is empty

    Explanation

    This fault typically occurs when a MAC address pool does not contain any MAC addresses.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the pool is in use, add a block of MAC addresses to the pool.

    Step 2 If the pool is not in use, ignore the fault.

    Fault Details 

    Severity: minor 

    Cause: empty-pool 

    mibFaultCode: 466 

    mibFaultName: fltMacpoolPoolEmpty 

    moClass: macpool:Pool 

    Type: server

    fltUuidpoolPoolEmpty

    Fault Code:F0464

    Message

    UUID suffix pool [name] is empty

    Explanation

    This fault typically occurs when a UUID suffix pool does not contain any UUID suffixes.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the pool is in use, add a block of UUID suffixes to the pool.

    Step 2 If the pool is not in use, ignore the fault.

    Fault Details 

    Severity: minor 

    Cause: empty-pool 

    mibFaultCode: 464 

    mibFaultName: fltUuidpoolPoolEmpty 

    moClass: uuidpool:Pool 

    Type: server

    Port-Related Faults

    This section contains faults raised as a result of issues with one or more ports in a Cisco UCS instance.

    fltPortPIoFailed

    Fault Code:F0277

    Message

    [transport] port [portId] on chassis [id] oper state: [operState], reason: [stateQual][transport] port [portId] on fabric interconnect [id] oper state: [operState], reason: [stateQual]

    Explanation

    This fault is raised on the fabric interconnect port, the server facing ports on the IOM or the FEX module when the system detects an indeterminate fault.

    Recommended Action

    If you see this fault, take the following actions:Execute the show tech-support command for UCSM and the chassis or FEX module on which fault is reported and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: port-failed 

    mibFaultCode: 277 

    mibFaultName: fltPortPIoFailed 

    moClass: port:PIo 

    Type: network

    fltPortPIoHardware-failure

    Fault Code:F0278

    Message

    [transport] port [portId] on chassis [id] oper state: [operState], reason: hardware-failure[transport] port [portId] on fabric interconnect [id] oper state: [operState], reason: hardware-failure

    Explanation

    This fault is raised on the fabric interconnect port, ports on the IOM or the FEX module when the system detects a hardware failure.

    Recommended Action

    If you see this fault, take the following actions: Execute the show tech-support detail command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: port-failed 

    mibFaultCode: 278 

    mibFaultName: fltPortPIoHardwareFailure 

    moClass: port:PIo 

    Type: network

    fltPortPIoInvalid-sfp

    Fault Code:F0713

    Message

    [transport] port [portId] on chassis [id] role : [ifRole] transceiver type:[xcvrType][transport] port [portId] on fabric interconnect [id] role : [ifRole] transceiver type:[xcvrType]

    Explanation

    This fault is raised against a Fabric Interconnect port,network facing IOM port or a FEX module port if an unsupported transceiver type is inserted in it.The port cannot be used when it has an unsupported transceiver.

    Recommended Action

    If you see this fault, take the following actions:Replace with a supported SFP type.Refer to the CCO documentation for a list of supported SFPs.

    Fault Details 

    Severity: major 

    Cause: unsupported-transceiver 

    mibFaultCode: 713 

    mibFaultName: fltPortPIoInvalidSfp 

    moClass: port:PIo 

    Type: network

    fltPortPIoLink-down

    Fault Code:F0276

    Message

    [transport] port [portId] on chassis [id] oper state: [operState], reason: [stateQual][transport] port [portId] on fabric interconnect [id] oper state: [operState], reason: [stateQual]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: link-down 

    mibFaultCode: 276 

    mibFaultName: fltPortPIoLinkDown 

    moClass: port:PIo 

    Type: network

    fltPortPIoSfp-not-present

    Fault Code:F0279

    Message

    [transport] port [portId] on chassis [id] oper state: [operState][transport] port [portId] on fabric interconnect [id] oper state: [operState]

    Explanation

    When a fabric interconnect port is not in an unconfigured state, an SFP is required for its operation. This fault is raised to indicate that the SFP is missing.

    Recommended Action

    If you see this fault, take the following actions:Insert an appropriate SFP. The list of supported SFPs can be found in Cisco's external website.

    Fault Details 

    Severity: info 

    Cause: port-failed 

    mibFaultCode: 279 

    mibFaultName: fltPortPIoSfpNotPresent 

    moClass: port:PIo 

    Type: network

    Port Channel-Related Faults

    This section contains faults raised as a result of issues with one or more port channels in a Cisco UCS instance.

    fltFabricFcSanPcEpIncompatibleSpeed

    Fault Code:F0734

    Message

    Member [slotId]/[portId] cannot be added to SAN Port-Channel [portId] on fabric interconnect [id], reason: [membership]

    Explanation

    This fault typically occurs when the maximum supported FC speed of the port in the FC port-channel is incompatible with the FC port-channel admin speed.

    Recommended Action

    If you see this fault, take the following action:

    Step 1 Change the admin speed of the port-channel.

    or

    Step 2 Replace the GEM with a one which suits the admin-speed of the port-channel.

    Fault Details 

    Severity: major 

    Cause: incompatible-speed 

    mibFaultCode: 734 

    mibFaultName: fltFabricFcSanPcEpIncompatibleSpeed 

    moClass: fabric:FcSanPcEp 

    Type: network

    fltFabricFcSanPcIncompatibleSpeed

    Fault Code:F0735

    Message

    Cannot set admin speed to the requested value, Speed incompatible with member ports in the port-channel

    Explanation

    This fault typically occurs when the maximum supported FC speed of the port in the FC port-channel is incompatible with the FC port-channel admin speed.

    Recommended Action

    If you see this fault, take the following action:

    Step 1 Change the admin speed of the port-channel.

    or

    Step 2 Replace the GEM with a one which suits the admin-speed of the port-channel.

    Fault Details 

    Severity: major 

    Cause: incompatible-speed 

    mibFaultCode: 735 

    mibFaultName: fltFabricFcSanPcIncompatibleSpeed 

    moClass: fabric:FcSanPc 

    Type: network

    Power Supply-Related Faults

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

    fltEquipmentPsuIdentity

    Fault Code:F0407

    Message

    Power supply [id] on chassis [id] has a malformed FRUPower supply [id] on server [id] has a malformed FRU

    Explanation

    This fault typically occurs when a power supply unit has corrupted or has malformed FRU information.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: fru-problem 

    mibFaultCode: 407 

    mibFaultName: fltEquipmentPsuIdentity 

    moClass: equipment:Psu 

    Type: equipment

    fltEquipmentPsuInoperable

    Fault Code:F0374

    Message

    Power supply [id] in chassis [id] operability: [operability]Power supply [id] in fabric interconnect [id] operability: [operability]Power supply [id] in fex [id] operability: [operability]Power supply [id] in server [id] operability: [operability]

    Explanation

    This fault typically occurs when the Cisco UCS Manager detects a problem with a power supply unit in a chassis, fabric interconnect or a fex. For example, the PSU is not functional.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Verify that the power cord is properly connected to the PSU and the power source.

    Step 2 Verify that the power source is 220 volts.

    Step 3 Verify that the PSU is properly installed in the chassis or fabric interconnect.

    Step 4 Remove the PSU and reinstall it.

    Step 5 Replace the PSU.

    Step 6 If the above actions did not resolve the issue, note down the type of PSU, execute the show tech-support command, and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: equipment-inoperable 

    mibFaultCode: 374 

    mibFaultName: fltEquipmentPsuInoperable 

    moClass: equipment:Psu 

    Type: equipment

    fltEquipmentPsuMissing

    Fault Code:F0378

    Message

    Power supply [id] in chassis [id] presence: [presence]Power supply [id] in fabric interconnect [id] presence: [presence]Power supply [id] in fex [id] presence: [presence]Power supply [id] in server [id] presence: [presence]

    Explanation

    This fault typically occurs when the Cisco UCS Manager detects a problem with a power supply unit in a chassis, fabric interconnect or a fex. For example, the PSU is missing.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 If the power supply unit is physically present in the slot, remove and then reinsert it.

    Step 3 If the power supply unit is not physically present in the slot, reinsert it.

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: equipment-missing 

    mibFaultCode: 378 

    mibFaultName: fltEquipmentPsuMissing 

    moClass: equipment:Psu 

    Type: equipment

    fltEquipmentPsuOffline

    Fault Code:F0528

    Message

    Power supply [id] in chassis [id] power: [power]Power supply [id] in fabric interconnect [id] power: [power]Power supply [id] in fex [id] power: [power]Power supply [id] in server [id] power: [power]

    Explanation

    This fault typically occurs when Cisco UCS Manager detects that a power supply unit in a chassis, fabric interconnect or a fex is offline.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Verify that the power cord is properly connected to the PSU and the power source.

    Step 2 Verify that the power source is 220 volts.

    Step 3 Verify that the PSU is properly installed in the chassis or fabric interconnect.

    Step 4 Remove the PSU and reinstall it.

    Step 5 Replace the PSU.

    Step 6 If the above actions did not resolve the issue, note down the type of PSU, execute the show tech-support command, and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: equipment-offline 

    mibFaultCode: 528 

    mibFaultName: fltEquipmentPsuOffline 

    moClass: equipment:Psu 

    Type: environmental

    fltEquipmentPsuPerfThresholdCritical

    Fault Code:F0393

    Message

    Power supply [id] in chassis [id] output power: [perf]Power supply [id] in fabric interconnect [id] output power: [perf]Power supply [id] in server [id] output power: [perf]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: performance-problem 

    mibFaultCode: 393 

    mibFaultName: fltEquipmentPsuPerfThresholdCritical 

    moClass: equipment:Psu 

    Type: equipment

    fltEquipmentPsuPerfThresholdNonCritical

    Fault Code:F0392

    Message

    Power supply [id] in chassis [id] output power: [perf]Power supply [id] in fabric interconnect [id] output power: [perf]Power supply [id] in server [id] output power: [perf]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: performance-problem 

    mibFaultCode: 392 

    mibFaultName: fltEquipmentPsuPerfThresholdNonCritical 

    moClass: equipment:Psu 

    Type: equipment

    fltEquipmentPsuPerfThresholdNonRecoverable

    Fault Code:F0394

    Message

    Power supply [id] in chassis [id] output power: [perf]Power supply [id] in fabric interconnect [id] output power: [perf]Power supply [id] in server [id] output power: [perf]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: performance-problem 

    mibFaultCode: 394 

    mibFaultName: fltEquipmentPsuPerfThresholdNonRecoverable 

    moClass: equipment:Psu 

    Type: equipment

    fltEquipmentPsuPowerSupplyProblem

    Fault Code:F0369

    Message

    Power supply [id] in chassis [id] power: [power]Power supply [id] in fabric interconnect [id] power: [power]Power supply [id] in fex [id] power: [power]Power supply [id] in server [id] power: [power]

    Explanation

    This fault typically occurs when the Cisco UCS Manager detects a problem with a power supply unit in a chassis, fabric interconnect or a fex. For example, the PSU is not functional.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Verify that the power cord is properly connected to the PSU and the power source.

    Step 2 Verify that the power source is 220 volts.

    Step 3 Verify that the PSU is properly installed in the chassis or fabric interconnect.

    Step 4 Remove the PSU and reinstall it.

    Step 5 Replace the PSU.

    Step 6 If the above actions did not resolve the issue, note down the type of PSU, execute the show tech-support command, and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: power-problem 

    mibFaultCode: 369 

    mibFaultName: fltEquipmentPsuPowerSupplyProblem 

    moClass: equipment:Psu 

    Type: environmental

    fltEquipmentPsuThermalThresholdCritical

    Fault Code:F0383

    Message

    Power supply [id] in chassis [id] temperature: [thermal]Power supply [id] in fabric interconnect [id] temperature: [thermal]Power supply [id] in server [id] temperature: [thermal]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: thermal-problem 

    mibFaultCode: 383 

    mibFaultName: fltEquipmentPsuThermalThresholdCritical 

    moClass: equipment:Psu 

    Type: environmental

    fltEquipmentPsuThermalThresholdNonCritical

    Fault Code:F0381

    Message

    Power supply [id] in chassis [id] temperature: [thermal]Power supply [id] in fabric interconnect [id] temperature: [thermal]Power supply [id] in server [id] temperature: [thermal]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: thermal-problem 

    mibFaultCode: 381 

    mibFaultName: fltEquipmentPsuThermalThresholdNonCritical 

    moClass: equipment:Psu 

    Type: environmental

    fltEquipmentPsuThermalThresholdNonRecoverable

    Fault Code:F0385

    Message

    Power supply [id] in chassis [id] temperature: [thermal]Power supply [id] in fabric interconnect [id] temperature: [thermal]Power supply [id] in server [id] temperature: [thermal]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: thermal-problem 

    mibFaultCode: 385 

    mibFaultName: fltEquipmentPsuThermalThresholdNonRecoverable 

    moClass: equipment:Psu 

    Type: environmental

    fltEquipmentPsuVoltageThresholdCritical

    Fault Code:F0389

    Message

    Power supply [id] in chassis [id] voltage: [voltage]Power supply [id] in fabric interconnect [id] voltage: [voltage]Power supply [id] in fex [id] voltage: [voltage]Power supply [id] in server [id] voltage: [voltage]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: voltage-problem 

    mibFaultCode: 389 

    mibFaultName: fltEquipmentPsuVoltageThresholdCritical 

    moClass: equipment:Psu 

    Type: environmental

    fltEquipmentPsuVoltageThresholdNonCritical

    Fault Code:F0387

    Message

    Power supply [id] in chassis [id] voltage: [voltage]Power supply [id] in fabric interconnect [id] voltage: [voltage]Power supply [id] in fex [id] voltage: [voltage]Power supply [id] in server [id] voltage: [voltage]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: voltage-problem 

    mibFaultCode: 387 

    mibFaultName: fltEquipmentPsuVoltageThresholdNonCritical 

    moClass: equipment:Psu 

    Type: environmental

    fltEquipmentPsuVoltageThresholdNonRecoverable

    Fault Code:F0391

    Message

    Power supply [id] in chassis [id] voltage: [voltage]Power supply [id] in fabric interconnect [id] voltage: [voltage]Power supply [id] in fex [id] voltage: [voltage]Power supply [id] in server [id] voltage: [voltage]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: voltage-problem 

    mibFaultCode: 391 

    mibFaultName: fltEquipmentPsuVoltageThresholdNonRecoverable 

    moClass: equipment:Psu 

    Type: environmental

    fltFabricExternalPcDown

    Fault Code:F0282

    Message

    [type] port-channel [portId] on fabric interconnect [id] oper state: [operState], reason: [stateQual][type] port-channel [portId] on fabric interconnect [id] oper state: [operState], reason: [stateQual]

    Explanation

    The fabric port-channel operationally down.The Cisco UCS Manager raises this fault when any of the following scenarios occur:

    •Endpoint(switch/fabric interconnect) reports that the fabric port channel operational state is down.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Verify that the member ports in the fabric port channel are admin up and operational. Check the link connectivity.

    Step 3 If connectivity seems correct, check the operational states on the peer switch ports of the port channels members.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: operational-state-down 

    mibFaultCode: 282 

    mibFaultName: fltFabricExternalPcDown 

    moClass: fabric:ExternalPc 

    Type: network

    fltFabricFcSanPcEpDown

    Fault Code:F0728

    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 a FC port-channel is down .

    Recommended Action

    If you see this fault, take the following action:

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

    Fault Details 

    Severity: major 

    Cause: membership-down 

    mibFaultCode: 728 

    mibFaultName: fltFabricFcSanPcEpDown 

    moClass: fabric:FcSanPcEp 

    Type: network

    Processor-Related Faults

    This section contains faults raised as a result of issues with a server processor.

    fltProcessorUnitIdentity-unestablishable

    Fault Code:F0801

    Message

    Processor [id] on server [chassisId]/[slotId] has an invalid FRUProcessor [id] on server [id] has an invalid FRU

    Explanation

    This fault typically occurs because the Cisco UCS Manager has detected unsupported CPU 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 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

    Step 3 If the above actions did not resolve the issue, you may have unsupported CPU configuration in the server. Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: identity-unestablishable 

    mibFaultCode: 801 

    mibFaultName: fltProcessorUnitIdentityUnestablishable 

    moClass: processor:Unit 

    Type: equipment

    fltProcessorUnitInoperable

    Fault Code:F0174

    Message

    Processor [id] on server [chassisId]/[slotId] operability: [operability]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: equipment-inoperable 

    mibFaultCode: 174 

    mibFaultName: fltProcessorUnitInoperable 

    moClass: processor:Unit 

    Type: equipment

    fltProcessorUnitThermalNonCritical

    Fault Code:F0175

    Message

    Processor [id] on server [chassisId]/[slotId] temperature: [thermal]Processor [id] on server [id] temperature: [thermal]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: thermal-problem 

    mibFaultCode: 175 

    mibFaultName: fltProcessorUnitThermalNonCritical 

    moClass: processor:Unit 

    Type: environmental

    fltProcessorUnitThermalThresholdCritical

    Fault Code:F0176

    Message

    Processor [id] on server [chassisId]/[slotId] temperature: [thermal]Processor [id] on server [id] temperature: [thermal]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: thermal-problem 

    mibFaultCode: 176 

    mibFaultName: fltProcessorUnitThermalThresholdCritical 

    moClass: processor:Unit 

    Type: environmental

    fltProcessorUnitThermalThresholdNonRecoverable

    Fault Code:F0177

    Message

    Processor [id] on server [chassisId]/[slotId] temperature: [thermal]Processor [id] on server [id] temperature: [thermal]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: thermal-problem 

    mibFaultCode: 177 

    mibFaultName: fltProcessorUnitThermalThresholdNonRecoverable 

    moClass: processor:Unit 

    Type: environmental

    fltProcessorUnitVoltageThresholdCritical

    Fault Code:F0179

    Message

    Processor [id] on server [chassisId]/[slotId] voltage: [voltage]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: voltage-problem 

    mibFaultCode: 179 

    mibFaultName: fltProcessorUnitVoltageThresholdCritical 

    moClass: processor:Unit 

    Type: environmental

    fltProcessorUnitVoltageThresholdNonCritical

    Fault Code:F0178

    Message

    Processor [id] on server [chassisId]/[slotId] voltage: [voltage]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: voltage-problem 

    mibFaultCode: 178 

    mibFaultName: fltProcessorUnitVoltageThresholdNonCritical 

    moClass: processor:Unit 

    Type: environmental

    fltProcessorUnitVoltageThresholdNonRecoverable

    Fault Code:F0180

    Message

    Processor [id] on server [chassisId]/[slotId] voltage: [voltage]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: voltage-problem 

    mibFaultCode: 180 

    mibFaultName: fltProcessorUnitVoltageThresholdNonRecoverable 

    moClass: processor:Unit 

    Type: environmental

    Server-Related Faults

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

    fltComputeBoardCmosVoltageThresholdCritical

    Fault Code:F0424

    Message

    Possible loss of CMOS settings: CMOS battery voltage on server [chassisId]/[slotId] is [cmosVoltage]Possible loss of CMOS settings: CMOS battery voltage on server [id] is [cmosVoltage]

    Explanation

    This fault is raised when CMOS battery voltage has gone lower than normal operating range. This could impact clock and other CMOS settings.

    Recommended Action

    If you see this fault, take the following actions:Replace the battery.

    Fault Details 

    Severity: minor 

    Cause: voltage-problem 

    mibFaultCode: 424 

    mibFaultName: fltComputeBoardCmosVoltageThresholdCritical 

    moClass: compute:Board 

    Type: environmental

    fltComputeBoardCmosVoltageThresholdNonRecoverable

    Fault Code:F0425

    Message

    Possible loss of CMOS settings: CMOS battery voltage on server [chassisId]/[slotId] is [cmosVoltage]Possible loss of CMOS settings: CMOS battery voltage on server [id] is [cmosVoltage]

    Explanation

    This fault is raised when CMOS battery voltage has gone quite low and is unlikely to recover. This will impact clock and other CMOS settings.

    Recommended Action

    If you see this fault, take the following actions:Replace the battery.

    Fault Details 

    Severity: major 

    Cause: voltage-problem 

    mibFaultCode: 425 

    mibFaultName: fltComputeBoardCmosVoltageThresholdNonRecoverable 

    moClass: compute:Board 

    Type: environmental

    fltComputeBoardPowerError

    Fault Code:F0310

    Message

    Motherboard of server [chassisId]/[slotId] (service profile: [assignedToDn]) power: [operPower]Motherboard of server [id] (service profile: [assignedToDn]) power: [operPower]

    Explanation

    This fault typically occurs when the server power sensors have detected a problem.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Make sure that the server is correctly installed in the chassis and that all cables are secure.

    Step 3 If you reinstalled the server, reacknowledge it.

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: power-problem 

    mibFaultCode: 310 

    mibFaultName: fltComputeBoardPowerError 

    moClass: compute:Board 

    Type: environmental

    fltComputeIOHubThermalNonCritical

    Fault Code:F0538

    Message

    IO Hub on server [chassisId]/[slotId] temperature: [thermal]

    Explanation

    This fault is raised when the IO controller temperature is outside the upper or lower non-critical threshold.

    Recommended Action

    If you see this fault, take the following actions:Monitor other environmental events related to this server and ensure the temperature ranges are within recommended ranges.

    Fault Details 

    Severity: minor 

    Cause: thermal-problem 

    mibFaultCode: 538 

    mibFaultName: fltComputeIOHubThermalNonCritical 

    moClass: compute:IOHub 

    Type: environmental

    fltComputeIOHubThermalThresholdCritical

    Fault Code:F0539

    Message

    IO Hub on server [chassisId]/[slotId] temperature: [thermal]

    Explanation

    This fault is raised when the IO controller temperature is outside the upper or lower critical threshold.

    Recommended Action

    If you see this fault, take the following actions:Monitor other environmental events related to this server and ensure the temperature ranges are within recommended ranges. Consider turning off the server for a while if possible.

    Fault Details 

    Severity: major 

    Cause: thermal-problem 

    mibFaultCode: 539 

    mibFaultName: fltComputeIOHubThermalThresholdCritical 

    moClass: compute:IOHub 

    Type: environmental

    fltComputeIOHubThermalThresholdNonRecoverable

    Fault Code:F0540

    Message

    IO Hub on server [chassisId]/[slotId] temperature: [thermal]

    Explanation

    This fault is raised when the IO controller temperature is outside the recoverable range of operation.

    Recommended Action

    If you see this fault, take the following actions:Shutdown server immediately. Contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: thermal-problem 

    mibFaultCode: 540 

    mibFaultName: fltComputeIOHubThermalThresholdNonRecoverable 

    moClass: compute:IOHub 

    Type: environmental

    fltComputePhysicalAssignedInaccessible

    Fault Code:F0322

    Message

    Server [id] (service profile: [assignedToDn]) inaccessibleServer [chassisId]/[slotId] (service profile: [assignedToDn]) inaccessible

    Explanation

    This fault typically occurs when the server, which is associated with a service profile, has lost connection to the fabric interconnects. This fault occurs if there are communication issues between CIMC and the fabric interconnects.

    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 brief time, remove the server and then reinsert it.

    Step 3 Reacknowledge the server.

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: equipment-inaccessible 

    mibFaultCode: 322 

    mibFaultName: fltComputePhysicalAssignedInaccessible 

    moClass: compute:Physical 

    Type: equipment

    fltComputePhysicalAssignedMissing

    Fault Code:F0319

    Message

    Server [id] (service profile: [assignedToDn]) missingServer [chassisId]/[slotId] (service profile: [assignedToDn]) missing

    Explanation

    This fault typically occurs when the server, which is associated with a service profile, was previously physically inserted in the slot, but cannot be detected by the Cisco UCS Manager.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 If the server is physically present in the slot, remove and then reinsert it.

    Step 3 If the server is not physically present in the slot, reinsert it.

    Step 4 Reacknowledge the server.

    Step 5 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: equipment-missing 

    mibFaultCode: 319 

    mibFaultName: fltComputePhysicalAssignedMissing 

    moClass: compute:Physical 

    Type: equipment

    fltComputePhysicalAssociationFailed

    Fault Code:F0315

    Message

    Service profile [assignedToDn] failed to associate with server [id]Service profile [assignedToDn] failed to associate with server [chassisId]/[slotId]

    Explanation

    This fault typically occurs for one of the following reasons:

    •The service profile could not be associated with the server.

    •The server is down.

    •The data path is not working.

    •The Cisco UCS Manager cannot communicate with one or more of the fabric interconnect, the server, or a component on the server.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Check the FSM tab and the current state of the server and any FSM operations.

    Step 3 If the server is stuck in an inappropriate state, such as booting, power-cycle the server.

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: association-failed 

    mibFaultCode: 315 

    mibFaultName: fltComputePhysicalAssociationFailed 

    moClass: compute:Physical 

    Type: configuration

    fltComputePhysicalBiosPostTimeout

    Fault Code:F0313

    Message

    Server [id] (service profile: [assignedToDn]) BIOS failed power-on self testServer [chassisId]/[slotId] (service profile: [assignedToDn]) BIOS failed power-on self test

    Explanation

    This fault typically occurs when the server has encountered a diagnostic failure.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

    Step 3 Reacknowledge the server.

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: equipment-inoperable 

    mibFaultCode: 313 

    mibFaultName: fltComputePhysicalBiosPostTimeout 

    moClass: compute:Physical 

    Type: equipment

    fltComputePhysicalDiscoveryFailed

    Fault Code:F0314

    Message

    Server [id] (service profile: [assignedToDn]) discovery: [discovery]Server [chassisId]/[slotId] (service profile: [assignedToDn]) discovery: [discovery]

    Explanation

    This fault typically occurs for one of the following reasons:

    •The shallow discovery that occurs when the server associated with the service profile failed.

    •The server is down.

    •The data path is not working.

    •Cisco UCS Manager cannot communicate with the BMC on the server.

    •The server cannot communicate with the fabric interconnect.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Check the FSM tab and the current state of the server and any FSM operations.

    Step 3 Check the error descriptions and see if any server components indicate a failure.

    Step 4 If the server or a server component has failed, do the following:

    a. Check the operational state of the server.

    b. If the server is not operable, re-acknowledge the server.

    Step 5 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: discovery-failed 

    mibFaultCode: 314 

    mibFaultName: fltComputePhysicalDiscoveryFailed 

    moClass: compute:Physical 

    Type: operational

    fltComputePhysicalIdentityUnestablishable

    Fault Code:F0306

    Message

    Server [id] (service profile: [assignedToDn]) has an invalid FRUServer [chassisId]/[slotId] (service profile: [assignedToDn]) has an invalid FRU

    Explanation

    This fault typically occurs because the Cisco UCS Manager has detected an unsupported server or CPU.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Verify that a supported server and/or CPU is installed.

    Step 3 Verify that the Cisco UCS Manager capability catalog is up-to-date.

    Step 4 Reacknowledge the server.

    Step 5 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: identity-unestablishable 

    mibFaultCode: 306 

    mibFaultName: fltComputePhysicalIdentityUnestablishable 

    moClass: compute:Physical 

    Type: equipment

    fltComputePhysicalInoperable

    Fault Code:F0317

    Message

    Server [id] (service profile: [assignedToDn]) health: [operability]Server [chassisId]/[slotId] (service profile: [assignedToDn]) health: [operability]

    Explanation

    This fault typically occurs when the server has encountered a diagnostic failure.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 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 3 Reacknowledge the server.

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: equipment-inoperable 

    mibFaultCode: 317 

    mibFaultName: fltComputePhysicalInoperable 

    moClass: compute:Physical 

    Type: equipment

    fltComputePhysicalInsufficientlyEquipped

    Fault Code:F0305

    Message

    Server [id] (service profile: [assignedToDn]) has insufficient number of DIMMs, CPUs and/or adaptersServer [chassisId]/[slotId] (service profile: [assignedToDn]) has insufficient number of DIMMs, CPUs and/or adapters

    Explanation

    This fault typically occurs because the Cisco UCS Manager has detected that the server has an insufficient number of DIMMs, CPUs and/or adapter.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Verify that the DIMMs are installed in a supported configuration.

    Step 3 Verify that an adapter and CPU are installed.

    Step 4 Reacknowledge the server.

    Step 5 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: insufficiently-equipped 

    mibFaultCode: 305 

    mibFaultName: fltComputePhysicalInsufficientlyEquipped 

    moClass: compute:Physical 

    Type: equipment

    fltComputePhysicalPost-failure

    Fault Code:F0517

    Message

    Server [id] POST or diagnostic failureServer [chassisId]/[slotId] POST or diagnostic failure

    Explanation

    This fault typically occurs when the server has encountered a diagnostic failure or an error during POST.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 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 3 Reboot the server.

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: equipment-problem 

    mibFaultCode: 517 

    mibFaultName: fltComputePhysicalPostFailure 

    moClass: compute:Physical 

    Type: server

    fltComputePhysicalPowerProblem

    Fault Code:F0311

    Message

    Server [id] (service profile: [assignedToDn]) oper state: [operState]Server [chassisId]/[slotId] (service profile: [assignedToDn]) oper state: [operState]

    Explanation

    This fault typically occurs when the server power sensors have detected a problem.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Make sure that the server is correctly installed in the chassis and that all cables are secure.

    Step 3 If you reinstalled the server, reacknowledge it.

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: power-problem 

    mibFaultCode: 311 

    mibFaultName: fltComputePhysicalPowerProblem 

    moClass: compute:Physical 

    Type: environmental

    fltComputePhysicalThermalProblem

    Fault Code:F0312

    Message

    Server [id] (service profile: [assignedToDn]) oper state: [operState]Server [chassisId]/[slotId] (service profile: [assignedToDn]) oper state: [operState]

    Explanation

    This fault typically occurs when the server thermal sensors have detected a problem.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Make sure that the server fans are working properly.

    Step 3 Wait for 24 hours to see if the problem resolves itself.

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: thermal-problem 

    mibFaultCode: 312 

    mibFaultName: fltComputePhysicalThermalProblem 

    moClass: compute:Physical 

    Type: environmental

    fltComputePhysicalUnassignedInaccessible

    Fault Code:F0321

    Message

    Server [id] (no profile) inaccessibleServer [chassisId]/[slotId] (no profile) inaccessible

    Explanation

    This fault typically occurs when the server, which is not associated with a service profile, has lost connection to the fabric interconnects. This fault occurs if there are communication issues between CIMC and the fabric interconnects.

    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 brief time, remove the server and then reinsert it.

    Step 3 Reacknowledge the server.

    Step 4 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: equipment-inaccessible 

    mibFaultCode: 321 

    mibFaultName: fltComputePhysicalUnassignedInaccessible 

    moClass: compute:Physical 

    Type: equipment

    fltComputePhysicalUnassignedMissing

    Fault Code:F0318

    Message

    Server [id] (no profile) missingServer [chassisId]/[slotId] (no profile) missing

    Explanation

    This fault typically occurs when the server, which is not associated with a service profile, was previously physically inserted in the slot, but cannot be detected by the Cisco UCS Manager.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 If the server is physically present in the slot, remove and then reinsert it.

    Step 3 If the server is not physically present in the slot, reinsert it.

    Step 4 Reacknowledge the server.

    Step 5 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: equipment-missing 

    mibFaultCode: 318 

    mibFaultName: fltComputePhysicalUnassignedMissing 

    moClass: compute:Physical 

    Type: equipment

    fltComputePhysicalUnidentified

    Fault Code:F0320

    Message

    Server [id] (service profile: [assignedToDn]) has an invalid FRU: [presence]Server [chassisId]/[slotId] (service profile: [assignedToDn]) has an invalid FRU: [presence]

    Explanation

    This fault typically occurs because the Cisco UCS Manager has detected an unsupported server or CPU.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Verify that a supported server and/or CPU is installed.

    Step 3 Verify that the Cisco UCS Manager capability catalog is up-to-date.

    Step 4 Reacknowledge the server.

    Step 5 If the above actions did not resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: identity-unestablishable 

    mibFaultCode: 320 

    mibFaultName: fltComputePhysicalUnidentified 

    moClass: compute:Physical 

    Type: equipment

    fltComputeRtcBatteryInoperable

    Fault Code:F0533

    Message

    RTC Battery on server [chassisId]/[slotId] operability: [operability]

    Explanation

    This fault is raised when CMOS battery voltage is below normal operating range. This will impact system clock.

    Recommended Action

    If you see this fault, take the following actions:Replace the CMOS battery.

    Fault Details 

    Severity: major 

    Cause: equipment-inoperable 

    mibFaultCode: 533 

    mibFaultName: fltComputeRtcBatteryInoperable 

    moClass: compute:RtcBattery 

    Type: equipment

    fltMgmtIfMisConnect

    Fault Code:F0688

    Message

    Management Port [id] in server [id] is mis connected

    Explanation

    This fault occurs on server and fex connectivity change.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Check the connectivity between server and fex and if changed by mistake then make it same as before.

    Step 2 If intended, then reacknowledge the server.

    Step 3 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: link-misconnected 

    mibFaultCode: 688 

    mibFaultName: fltMgmtIfMisConnect 

    moClass: mgmt:If 

    Type: operational

    fltMgmtIfMissing

    Fault Code:F0717

    Message

    Connection to Management Port [id] in server [id] is missing

    Explanation

    This fault occurs when connectivity betwwen server and fex connectivity is removed.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Check the connectivity between server and fex and if changed by mistake then make it the same as before.

    Step 2 If intended, then reacknowledge the server.

    Step 3 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: link-missing 

    mibFaultCode: 717 

    mibFaultName: fltMgmtIfMissing 

    moClass: mgmt:If 

    Type: operational

    fltMgmtIfNew

    Fault Code:F0772

    Message

    New connection discovered on Management Port [id] in server [id]

    Explanation

    This fault occurs when new connectivity is added betwwen server and fex.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Check the connectivity between server and fex and if changed by mistake then make it same as before.

    Step 2 If intended, then reacknowledge the server.

    Step 3 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: new-link 

    mibFaultCode: 772 

    mibFaultName: fltMgmtIfNew 

    moClass: mgmt:If 

    Type: operational

    fltPowerBudgetChassisPsuInsufficient

    Fault Code:F0764

    Message

    Chassis [id] has had PSU failures. Please correct the problem by checking input power or replace the PSU

    Explanation

    This fault typically occurs when atleast 2 PSU are not powered on.

    Recommended Action

    If you see this fault, take the following actions:Consider adding and powering 2 PSU.

    Fault Details 

    Severity: major 

    Cause: psu-failure 

    mibFaultCode: 764 

    mibFaultName: fltPowerBudgetChassisPsuInsufficient 

    moClass: power:Budget 

    Type: environmental

    fltPowerBudgetFirmwareMismatch

    Fault Code:F0798

    Message

    Firmware on blade [chassisId]/[slotId] does not allow chassis level power capping. Please consider upgrading to atleast 1.4 version

    Explanation

    This fault typically occurs when CIMC or BIOS firmware is older than 1.4.

    Recommended Action

    If you see this fault, take the following actions:Consider upgrading to 1.4 or higher version.

    Fault Details 

    Severity: major 

    Cause: old-firmware 

    mibFaultCode: 798 

    mibFaultName: fltPowerBudgetFirmwareMismatch 

    moClass: power:Budget 

    Type: environmental

    fltPowerBudgetPowerBudgetBmcProblem

    Fault Code:F0637

    Message

    Power cap application failed for server [chassisId]/[slotId]Power cap application failed for server [id]

    Explanation

    This fault typically occurs when CIMC or BIOS has failed to enforce powercap.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Check the power consumption of blade. If consumption is significantlygreater than power cap, switch to manual per blade cap. If consumption isstill high, it indicates faulty cimc or bios software.

    Step 2 Execute show tech-support command for UCSM and chassis and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: power-cap-fail 

    mibFaultCode: 637 

    mibFaultName: fltPowerBudgetPowerBudgetBmcProblem 

    moClass: power:Budget 

    Type: environmental

    fltPowerBudgetPowerBudgetCmcProblem

    Fault Code:F0635

    Message

    Power cap application failed for chassis [id]

    Explanation

    This fault typically occurs when CMC has failed to enforce power cap.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Check the power consumption of chassis. If consumption is significantly greater than power cap, consider reducing the group cap so that other chassis consumption can be reduced to make up for the increase.

    Step 2 Execute show tech-support command for UCSM and chassis and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: power-cap-fail 

    mibFaultCode: 635 

    mibFaultName: fltPowerBudgetPowerBudgetCmcProblem 

    moClass: power:Budget 

    Type: environmental

    fltPowerBudgetPowerBudgetDiscFail

    Fault Code:F0640

    Message

    Insufficient power available to discover server [chassisId]/[slotId]Insufficient power available to discover server [id]

    Explanation

    This fault typically occurs when discovery fails due to unavailable power in the group.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Consider increasing the group cap.

    Step 2 Another option is to reduce the blades or chassis in the system.

    Fault Details 

    Severity: major 

    Cause: power-cap-fail 

    mibFaultCode: 640 

    mibFaultName: fltPowerBudgetPowerBudgetDiscFail 

    moClass: power:Budget 

    Type: environmental

    fltPowerBudgetPowerCapReachedCommit

    Fault Code:F0744

    Message

    P-State lowered as consumption hit power cap for server [chassisId]/[slotId]P-State lowered as consumption hit power cap for server [id]

    Explanation

    This fault typically occurs when bladed is being actively capped.

    Recommended Action

    If you see this fault, take the following actions:No action is needed.

    Fault Details 

    Severity: info 

    Cause: power-consumption-hit-limit 

    mibFaultCode: 744 

    mibFaultName: fltPowerBudgetPowerCapReachedCommit 

    moClass: power:Budget 

    Type: environmental

    fltPowerBudgetTStateTransition

    Fault Code:F0765

    Message

    Blade [chassisId]/[slotId] has been severely throttled. CIMC can recover if budget is redeployed to the blade or by rebooting the blade. If problem persists, please ensure that OS is ACPI compliantRack server [id] has been severely throttled. CIMC can recover if budget is redeployed to the blade or by rebooting the blade. If problem persists, please ensure that OS is ACPI compliant

    Explanation

    This fault typically occurs when processor T-state are used to severely throttle the CPU.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Redeploy budget for the particular group/blade/chassis.

    Step 2 If problem persists, reboot the blade.

    Fault Details 

    Severity: critical 

    Cause: no-ack-from-bios 

    mibFaultCode: 765 

    mibFaultName: fltPowerBudgetTStateTransition 

    moClass: power:Budget 

    Type: environmental

    fltPowerChassisMemberChassisFirmwareProblem

    Fault Code:F0741

    Message

    Chassis [id] cannot be capped as atleast one of the CMC or CIMC firmware version is less than 1.4. Please upgrade the firmware for cap to be applied.

    Explanation

    This fault typically occurs when CMC firmware is older than 1.4.

    Recommended Action

    If you see this fault, take the following actions:Consider upgrading to 1.4 or higher version.

    Fault Details 

    Severity: major 

    Cause: old-chassis-component-firmware 

    mibFaultCode: 741 

    mibFaultName: fltPowerChassisMemberChassisFirmwareProblem 

    moClass: power:ChassisMember 

    Type: environmental

    fltPowerChassisMemberChassisPsuInsufficient

    Fault Code:F0742

    Message

    Chassis [id] cannot be capped as atleast two PSU need to be powered

    Explanation

    This fault typically occurs when atleast 2 PSU are not powered on.

    Recommended Action

    If you see this fault, take the following actions:Consider adding and powering 2 PSU.

    Fault Details 

    Severity: major 

    Cause: psu-insufficient 

    mibFaultCode: 742 

    mibFaultName: fltPowerChassisMemberChassisPsuInsufficient 

    moClass: power:ChassisMember 

    Type: environmental

    fltPowerChassisMemberChassisPsuRedundanceFailure

    Fault Code:F0743

    Message

    Chassis [id] was configured for redundancy, but running in a non-redundant configuration.

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: psu-redundancy-fail 

    mibFaultCode: 743 

    mibFaultName: fltPowerChassisMemberChassisPsuRedundanceFailure 

    moClass: power:ChassisMember 

    Type: environmental

    fltPowerChassisMemberPowerGroupCapInsufficient

    Fault Code:F0740

    Message

    Chassis [id] cannot be capped as group cap is low. Please consider raising the cap.

    Explanation

    This fault typically occurs when updated group cap is insufficient for minimum hardware requirements.The newly added chassis to the group will not be capped as a result.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Consider increasing the group cap.

    Step 2 Another option is to reduce the blades or chassis in the system.

    Fault Details 

    Severity: major 

    Cause: group-cap-insufficient 

    mibFaultCode: 740 

    mibFaultName: fltPowerChassisMemberPowerGroupCapInsufficient 

    moClass: power:ChassisMember 

    Type: environmental

    fltPowerGroupPowerGroupBudgetIncorrect

    Fault Code:F0643

    Message

    admin committed insufficient for power group [name], using previous value [operCommitted]

    Explanation

    This fault typically occurs when updated group cap is insufficient for minimum hardware requirements.The previously entered cap will be used for provisioning.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Consider increasing the group cap.

    Step 2 Another option is to reduce the blades or chassis in the system.

    Fault Details 

    Severity: major 

    Cause: power-cap-fail 

    mibFaultCode: 643 

    mibFaultName: fltPowerGroupPowerGroupBudgetIncorrect 

    moClass: power:Group 

    Type: environmental

    fltPowerGroupPowerGroupInsufficientBudget

    Fault Code:F0642

    Message

    insufficient budget for power group [name]

    Explanation

    This fault typically occurs when group cap is insufficient for minimum hardware requirements.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Consider increasing the group cap.

    Step 2 Another option is to reduce the blades or chassis in the system.

    Fault Details 

    Severity: major 

    Cause: power-cap-fail 

    mibFaultCode: 642 

    mibFaultName: fltPowerGroupPowerGroupInsufficientBudget 

    moClass: power:Group 

    Type: environmental

    fltPowerPolicyPowerPolicyApplicationFail

    Fault Code:F0766

    Message

    Insufficient budget to apply no-cap priority through policy [name]. Blades will continue to be capped.

    Explanation

    Power Policy application on blades failed Cisco UCS Manager raises this fault when any of the following scenario occur:

    •Blades will not be able to operate normally without power capping due to the limited power budget on the blades.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Increase the power budget for the blades.

    Step 3 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: no-cap-fail 

    mibFaultCode: 766 

    mibFaultName: fltPowerPolicyPowerPolicyApplicationFail 

    moClass: power:Policy 

    Type: environmental

    fltStorageLocalDiskInoperable

    Fault Code:F0181

    Message

    Local disk [id] on server [chassisId]/[slotId] operability: [operability]Local disk [id] on server [id] operability: [operability]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: equipment-inoperable 

    mibFaultCode: 181 

    mibFaultName: fltStorageLocalDiskInoperable 

    moClass: storage:LocalDisk 

    Type: equipment

    fltStorageLocalDiskSlotEpUnusable

    Fault Code:F0776

    Message

    Local disk [id] on server [serverId] is not usable by the operating system

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: equipment-inoperable 

    mibFaultCode: 776 

    mibFaultName: fltStorageLocalDiskSlotEpUnusable 

    moClass: storage:LocalDiskSlotEp 

    Type: equipment

    fltStorageRaidBatteryInoperable

    Fault Code:F0531

    Message

    RAID Battery on server [chassisId]/[slotId] operability: [operability]RAID Battery on server [id] operability: [operability]

    Explanation

    None set.

    Recommended Action

    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: equipment-inoperable 

    mibFaultCode: 531 

    mibFaultName: fltStorageRaidBatteryInoperable 

    moClass: storage:RaidBattery 

    Type: equipment

    Service Profile-Related Faults

    This section contains faults raised as a result of issues related to the service profile associated with a server.

    fltLsComputeBindingAssignmentRequirementsNotMet

    Fault Code:F0689

    Message

    Assignment of service profile [name] to server [pnDn] failed

    Explanation

    The server could not be assigned to the service profile.This fault typically occurs as a result of one of the following issues:

    •The selected server doesn't meet the requirements of the service profile.

    •In case restricted migration was chosen, the selected server doesn't match the currently or previously assigned server.

    Recommended Action

    If you see this fault, take the following action:

    Step 1 Select a different server that meets the requirements of the service profile or matches the currently or previously assigned server

    Fault Details 

    Severity: minor 

    Cause: assignment-failed 

    mibFaultCode: 689 

    mibFaultName: fltLsComputeBindingAssignmentRequirementsNotMet 

    moClass: ls:ComputeBinding 

    Type: server

    fltLsServerAssociationFailed

    Fault Code:F0332

    Message

    Service profile [name] association failed for [pnDn]

    Explanation

    The service profile could not be associated with the server.This fault typically occurs because the Cisco UCS Manager cannot communicate with one or more of the following:

    •Fabric interconnect

    •BMC on the server

    •SAS controller driver

    •Server

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Check the FSM tab for the server and service profile to determine why the association failed.

    Step 3 If the server is stuck in an inappropriate state, such as booting, power cycle the server.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: association-failed 

    mibFaultCode: 332 

    mibFaultName: fltLsServerAssociationFailed 

    moClass: ls:Server 

    Type: server

    fltLsServerConfigFailure

    Fault Code:F0327

    Message

    Service profile [name] configuration failed due to [configQualifier]

    Explanation

    The named configuration qualifier is not available.This fault typically occurs because the Cisco UCS Manager cannot successfully deploy the service profile due to a lack of resources that meet the named qualifier. For example, this fault can occur if:

    •The service profile is configured for a server adapter with vHBAs, and the adapter on the server does not support vHBAs.

    •The local disk configuration policy in the service profile specifies the No Local Storage mode, but the server contains local disks.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Check the state of the server and ensure that it is in either the discovered or unassociated state.

    Step 3 If the server is associated or undiscovered, do one of the following:

    –Discover the server.

    –Disassociate the server from the current service profile.

    –Select another server to associate with the service profile.

    Step 4 Review each policy in the service profile and verify that the selected server meets the requirements in the policy.

    Step 5 If the server does not meet the requirements of the service profile, do one of the following:

    –Modify the service profile to match the server.

    –Select another server that does meet the requirements to associate with the service profile.

    Step 6 If you can verify that the server meets the requirements of the service profile, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: configuration-failure 

    mibFaultCode: 327 

    mibFaultName: fltLsServerConfigFailure 

    moClass: ls:Server 

    Type: server

    fltLsServerDiscoveryFailed

    Fault Code:F0326

    Message

    Service profile [name] discovery failed

    Explanation

    The shallow discovery that occurs when the server associated with service profile fails.If the server is up and the data path is working, this fault typically occurs as a result of one of the following issues:

    •The Cisco UCS Manager cannot communicate with the BMC on the server.

    •The server cannot communicate with the fabric interconnect.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Check the FSM tab and view the current state of the server and any FSM operations.

    Step 3 Check the error descriptions and see if any server components indicate a failure.

    Step 4 If the server or a server component has failed, do the following:

    a. Check the operational state of the server.

    b. If the server is not operable, re-acknowledge the server.

    Step 5 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: discovery-failed 

    mibFaultCode: 326 

    mibFaultName: fltLsServerDiscoveryFailed 

    moClass: ls:Server 

    Type: server

    fltLsServerFailed

    Fault Code:F0324

    Message

    Service profile [name] failed

    Explanation

    The server has failed.This fault typically occurs if the adapter power on self-test results in major and critical errors.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

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

    Step 3 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: server-failed 

    mibFaultCode: 324 

    mibFaultName: fltLsServerFailed 

    moClass: ls:Server 

    Type: server

    fltLsServerInaccessible

    Fault Code:F0331

    Message

    Service profile [name] cannot be accessed

    Explanation

    The Cisco UCS Manager cannot communicate with the BMC on the server.This fault typically occurs as a result of one of the following issues:

    •The server port or ports have failed.

    •The I/O module is offline.

    •The BMC has failed.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 If Cisco UCS Manager shows that the BMC is down, physically reseat the server.

    Step 3 If the Cisco UCS Manager shows that the server ports have failed, attempt to enable them.

    Step 4 If the I/O module is offline, check for faults on that component.

    Step 5 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: server-inaccessible 

    mibFaultCode: 331 

    mibFaultName: fltLsServerInaccessible 

    moClass: ls:Server 

    Type: server

    fltLsServerMaintenanceFailed

    Fault Code:F0329

    Message

    Service profile [name] maintenance failed

    Explanation

    The Cisco UCS Manager currently does not use this fault.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: maintenance-failed 

    mibFaultCode: 329 

    mibFaultName: fltLsServerMaintenanceFailed 

    moClass: ls:Server 

    Type: server

    fltLsServerRemoved

    Fault Code:F0330

    Message

    Service profile [name] underlying resource removed

    Explanation

    The Cisco UCS Manager cannot access the server associated with the service profile.This fault typically occurs as a result of one of the following issues:

    •The server has been physically removed from the slot.

    •The server is not available.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 If the server was removed from the slot, reinsert the server in the slot.

    Step 3 If the server was not removed, remove and reinsert the server.NOTE:If the server is operable, this action can be disruptive to current operations.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: equipment-removed 

    mibFaultCode: 330 

    mibFaultName: fltLsServerRemoved 

    moClass: ls:Server 

    Type: server

    fltLsServerServer-unfulfilled

    Fault Code:F0337

    Message

    Server [pnDn] does not fulfill Service profile [name] due to [configQualifier]

    Explanation

    The server no longer meets the qualification requirements of the service profile.This fault typically occurs as a result of one of the following issues:

    •The server has been physically changed.

    •A required component of the server has failed.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Check the server inventory compare to the service profile qualifications.

    Step 3 If the server inventory does not match the service profile qualifications, do one of the following:

    –Associate the server with a different service profile.

    –Ensure the server has sufficient resources to qualify for the current service profile.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: server-failed 

    mibFaultCode: 337 

    mibFaultName: fltLsServerServerUnfulfilled 

    moClass: ls:Server 

    Type: server

    fltLsServerUnassociated

    Fault Code:F0334

    Message

    Service profile [name] is not associated

    Explanation

    The service profile has not yet been associated with a server or a server pool.This fault typically occurs as a result of one of the following issues:

    •There is no acceptable server in the server pool.

    •The association failed.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 If you did not intend to associate the service profile, ignore the fault.

    Step 3 If you did intend to associate the service profile, check the association failure fault.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: unassociated 

    mibFaultCode: 334 

    mibFaultName: fltLsServerUnassociated 

    moClass: ls:Server 

    Type: server

    fltLsmaintMaintPolicyUnresolvableScheduler

    Fault Code:F0795

    Message

    Schedule [schedName] referenced by maintenance policy [name] does not exist

    Explanation

    The schedule that is referenced by the maintenance policy does not exist. This fault typically occurs as a result of one of the following issues:

    •The schedule does not exist.

    •The schedule was deleted.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Check if the named schedule exists. If it is deleted or missing, try to create it.

    Step 3 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: non-existent-scheduler 

    mibFaultCode: 795 

    mibFaultName: fltLsmaintMaintPolicyUnresolvableScheduler 

    moClass: lsmaint:MaintPolicy 

    Type: server

    System Event Log-Related Faults

    This section contains faults raised as a result of issues related to the system event log (SEL) in the Cisco UCS instance.

    fltSysdebugAutoCoreFileExportTargetAutoCoreTransferFailure

    Fault Code:F0747

    Message

    Auto core transfer failure at remote server [hostname]:[path] [exportFailureReason]

    Explanation

    Cisco UCS Manager cannot transfer core file to remote tftp server. This fault typically occurs as a result of one of the following issues:

    •The remote server is not accessible.

    •The parameters as specified in the core-export-target, such as path,port andserver-name, are incorrect.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Verify the connectivity to the remote server.

    Step 3 Verify the path information of the remote server.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: warning 

    Cause: tftp-server-error 

    mibFaultCode: 747 

    mibFaultName: fltSysdebugAutoCoreFileExportTargetAutoCoreTransferFailure 

    moClass: sysdebug:AutoCoreFileExportTarget 

    Type: sysdebug

    fltSysdebugMEpLogMEpLogFull

    Fault Code:F0462

    Message

    Log capacity on [side] IOM [chassisId]/[id] is [capacity]Log capacity on Management Controller on server [chassisId]/[slotId] is [capacity]Log capacity on Management Controller on server [id] is [capacity]

    Explanation

    This fault typically occurs because the Cisco UCS Manager could not transfer the SEL file to the location specified in the SEL policy.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Verify the configuration of the SEL policy to ensure that the location, user, and password provided are correct.

    Step 2 This is an info level fault and can be ignored if you do not want to clear the SEL at this time.

    Step 3 If this does not resolve the problem, execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: info 

    Cause: log-capacity 

    mibFaultCode: 462 

    mibFaultName: fltSysdebugMEpLogMEpLogFull 

    moClass: sysdebug:MEpLog 

    Type: operational

    fltSysdebugMEpLogMEpLogLog

    Fault Code:F0460

    Message

    Log capacity on [side] IOM [chassisId]/[id] is [capacity]Log capacity on Management Controller on server [chassisId]/[slotId] is [capacity]Log capacity on Management Controller on server [id] is [capacity]

    Explanation

    This fault typically occurs because the Cisco UCS Manager has detected that the system event log (SEL) on the server is approaching full capacity. The available capacity in the log is low.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If desired, clear the SEL in the Cisco UCS Manager.

    Step 2 This is an info level fault and can be ignored if you do not want to clear the SEL at this time.

    Fault Details 

    Severity: info 

    Cause: log-capacity 

    mibFaultCode: 460 

    mibFaultName: fltSysdebugMEpLogMEpLogLog 

    moClass: sysdebug:MEpLog 

    Type: operational

    fltSysdebugMEpLogMEpLogVeryLow

    Fault Code:F0461

    Message

    Log capacity on [side] IOM [chassisId]/[id] is [capacity]Log capacity on Management Controller on server [chassisId]/[slotId] is [capacity]Log capacity on Management Controller on server [id] is [capacity]

    Explanation

    This fault typically occurs because the Cisco UCS Manager has detected that the system event log (SEL) on the server is almost full. The available capacity in the log is very low.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If desired, clear the SEL in the Cisco UCS Manager.

    Step 2 This is an info level fault and can be ignored if you do not want to clear the SEL at this time.

    Fault Details 

    Severity: info 

    Cause: log-capacity 

    mibFaultCode: 461 

    mibFaultName: fltSysdebugMEpLogMEpLogVeryLow 

    moClass: sysdebug:MEpLog 

    Type: operational

    fltSysdebugMEpLogTransferError

    Fault Code:F0532

    Message

    Server [chassisId]/[slotId] [type] transfer failed: [operState]Server [id] [type] transfer failed: [operState]

    Explanation

    This fault occurs when transfer of the mananged end point log filessuch as SEL, fails.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If its a SEL related error, check the connectivity to the CIMC.

    Step 2 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 3 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: info 

    Cause: file-transfer-failed 

    mibFaultCode: 532 

    mibFaultName: fltSysdebugMEpLogTransferError 

    moClass: sysdebug:MEpLog 

    Type: operational

    Traffic Monitioring-related Faults

    This section contains faults caused by issues related to traffic monitoring.

    fltFabricMonSpanConfigFail

    Fault Code:F0757

    Message

    Configuration for traffic monitor [name] failed, reason: [configFailReason]

    Explanation

    This fault typically occurs when the configurtaion put under traffic monitoring session is not correct.

    Recommended Action

    If you see this fault, take the following action:

    Step 1 Correct the problem provided in the description of the raised fault.

    Fault Details 

    Severity: major 

    Cause: config-error 

    mibFaultCode: 757 

    mibFaultName: fltFabricMonSpanConfigFail 

    moClass: fabric:Mon 

    Type: network

    Virtual Network Interface-Related Faults

    This section contains faults caused by issues related to a virtual network interface allocation in a service profile.

    fltDcxNsFailed

    Fault Code:F0304

    Message

    Server [chassisId]/[slotId] (service profile: [assignedToDn]) virtual network interface allocation failed.Server [id] (service profile: [assignedToDn]) virtual network interface allocation failed.

    Explanation

    The adaptor unit's vif-namespace activation failed due to insufficient resources.The Cisco UCS Manager raises this fault when any of the following scenarios occur:

    •The number of deployed vif resources exceeds the max vif resources available on the adaptor unit corresponding to the fabric interconnect

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Check the Ns "size" and "used" resources to get the exceeded number.

    Step 3 Unconfigure/delete the exceeded number of vNICs on the adaptor unit.

    Step 4 Add additional fabric uplinks from IOM to the corresponding fabric interconnect and reacknowledge the chassis. That will increase the "NS size" on the adaptor

    Step 5 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: insufficient-resources 

    mibFaultCode: 304 

    mibFaultName: fltDcxNsFailed 

    moClass: dcx:Ns 

    Type: server

    fltDcxVIfLinkState

    Fault Code:F0479

    Message

    Virtual interface [id] link state is down

    Explanation

    This fault occurs when Cisco UCS cannot send or receive data through an uplink port.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Re-enable the uplink port that has failed.

    Step 3 If the above action did not resolve the issue, execute the show-tech-support command.

    Step 4 Contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: vif-down 

    mibFaultCode: 479 

    mibFaultName: fltDcxVIfLinkState 

    moClass: dcx:VIf 

    Type: management

    fltDcxVcDown

    Fault Code:F0283

    Message

    [transport] VIF [chassisId] / [slotId] [switchId]-[id] down, reason: [stateQual][transport] VIF [chassisId] / [id] [switchId]-[id] down, reason: [stateQual]

    Explanation

    The transport VIF for server is down.The Cisco UCS Manager raises this fault when any of the following scenario occur:

    •Endpoint(switch/fabric interconnect) reports the connectivity state on virtual interface as one of: a.down, b.errored, c.unavailable.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Verify that the blade discovery was completed successfully. Check the states on all of the communicating ports in an end to end manner.

    Step 3 If connectivity seems correct, recommision the server.

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: link-down 

    mibFaultCode: 283 

    mibFaultName: fltDcxVcDown 

    moClass: dcx:Vc 

    Type: network

    fltDcxVcMgmt-vif-down

    Fault Code:F0459

    Message

    IOM [chassisId] / [slotId] ([switchId]) management VIF [id] down, reason [stateQual]

    Explanation

    transport VIF for IO-Module is downCisco UCS Manager raises this fault when any of the following scenario occur:

    •Endpoint(switch/fabric interconnect) reports the connectivity state on virtual interface as one of: a.down b.errored c.unavailable

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Verify that the chassis discovery has gone through successfully. Check the states on all communicating ports in end to end manner

    Step 3 If connectivity seems correct, recommision the chassis

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: major 

    Cause: cmc-vif-down 

    mibFaultCode: 459 

    mibFaultName: fltDcxVcMgmtVifDown 

    moClass: dcx:Vc 

    Type: network

    VLAN-Related Faults

    This section contains faults caused by issues related to a VLAN fault.

    fltFabricVlanPrimaryVlanMissingIsolated

    Fault Code:F0620

    Message

    Primary Vlan can not be resolved for isolated vlan [name]

    Explanation

    This fault typically occurs when Cisco UCS Manager encountered a problem resolvingthe primary vlan Id corresponding to a particular isolated vlan.

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 Assocate the isolated vlan with a valid primary vlan.

    Step 2 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: minor 

    Cause: primary-vlan-missing-isolated 

    mibFaultCode: 620 

    mibFaultName: fltFabricVlanPrimaryVlanMissingIsolated 

    moClass: fabric:Vlan 

    Type: network

    fltSwVlanPortNsResourceStatus

    Fault Code:F0549

    Message

    Vlan-Port Resource exceeded

    Explanation

    port vlan count has exceeded the allowed max limit on the switchCisco UCS Manager raises this fault when any of the following scenario occur:

    •The total number of user deployed vlan port instances(access domain + border domain) in the system exceeds the max allowed limit

    Recommended Action

    If you see this fault, take the following actions:

    Step 1 If the fault occurs in the Cisco UCS Manager GUI, capture one or more screenshots of the fault message and other related areas.

    Step 2 Check the exceeded count on fabric interconnect through GUI & CLI

    Step 3 The vlan port count can be reduced in one of the following ways:

    –Delete some vlans from LAN cloud

    –Remove some vlans under vnics

    –Unconfigure some vnics

    –Unconfigure some uplink ethernet ports on the switch

    Step 4 Execute the show tech-support command and contact Cisco Technical Support.

    Fault Details 

    Severity: critical 

    Cause: limit-reached 

    mibFaultCode: 549 

    mibFaultName: fltSwVlanPortNsResourceStatus 

    moClass: sw:VlanPortNs 

    Type: management

    VSAN-Related Faults

    This section contains faults caused by issues related to a VSAN fault.

    fltFabricVsanEpErrorDisabled

    Fault Code:F0797

    Message

    [type] Port [slotId]/[portId] on fabric interconnect [switchId] has VSAN [id] in error disabled statePort channel [portId] on fabric interconnect [switchId] has VSAN [id] in error disabled state

    Explanation

    This fault typically occurs when a port is assigned to a VSAN that exists in the restricted range (3840-4078) or VSAN 4079 which is reserved .

    Recommended Action

    If you see this fault, take the following action:

    Step 1 If VSAN is in the restricted range (3840-4078).

    Step 2 Delete the port channels on the fabric-interconnect.

    Step 3 Disable uplink trunking on the fabric-interconnect.

    Step 4 Switch to FC switch mode.

    Step 5 If VSAN is reserved (4079), move the port to non reserved VSAN.

    Fault Details 

    Severity: major 

    Cause: vsan-misconfigured 

    mibFaultCode: 797 

    mibFaultName: fltFabricVsanEpErrorDisabled 

    moClass: fabric:VsanEp 

    Type: network

    fltFabricVsanErrorDisabled

    Fault Code:F0796

    Message

    VSAN [name] is [operState]

    Explanation

    This fault typically occurs when VSAN exists in the range (3840-4078) and FC end host mode is enabled.

    Recommended Action

    If you see this fault, take the following action:

    Step 1 Delete the port channels on the fabric-interconnect.

    Step 2 Disable uplink trunking on the fabric-interconnect.

    Step 3 Switch to FC switch mode.

    Fault Details 

    Severity: major 

    Cause: vsan-misconfigured 

    mibFaultCode: 796 

    mibFaultName: fltFabricVsanErrorDisabled 

    moClass: fabric:Vsan 

    Type: network