fltAdaptorUnitAdaptorReachability

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.

fltEquipmentChassisIdentity-unestablishable

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.

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.

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.

fltEquipmentFexIdentity-unestablishable

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.

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

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.

fltStorageItemCapacityExceeded

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

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.

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.

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.

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.

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.

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

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

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

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

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.

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.

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.

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.

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.

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.

fltEquipmentIOCardUnsupportedConnectivity

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.

fltLicenseInstanceGracePeriodWarning1

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.

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.

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.

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.

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.

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.

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

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

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

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

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

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

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.

fltMemoryUnitThermalThresholdCritical

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

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

fltProcessorUnitInoperable

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

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

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

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.

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

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.

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.

fltComputePhysicalInoperable

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.

fltComputePhysicalPost-failure

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.

fltComputePhysicalUnassignedInaccessible

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.

fltPowerBudgetPowerBudgetBmcProblem

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

fltPowerBudgetPowerBudgetDiscFail

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.

fltStorageLocalDiskInoperable

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

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.

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:

fltLsServerFailed

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.