Cisco FXOS Faults and Error Messages, 1.1(3)

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 FPR Manager detects a server in a chassis slot that does not match what was previously equipped in the slot.

Recommended Action

If you see this fault, take the following actions:

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

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

Fault Details

fltFabricComputeSlotEpServerIdentificationProblem

Fault Code: F0157

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove and reinsert the server.

Step 2 Reacknowledge the server.

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

Fault Details

fltVnicEtherConfig-failed

Fault Code: F0169

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the server was successfully discovered.

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

Step 3 Confirm that the vCon assignment is correct.

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

Fault Details

fltProcessorUnitInoperable

Fault Code: F0174

Message

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

Explanation

This fault occurs in the unlikely event that processor is inoperable.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the fault occurs on a blade server processor, remove the server from the chassis and then reinsert it.

Step 2 In Cisco FPR Manager, decommission and then recommission the server.

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

Fault Details

fltProcessorUnitThermalNonCritical

Fault Code: F0175

Message

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

Explanation

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

• Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.
• Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).
• If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Step 5 Power off unused blade servers and rack servers.

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

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

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

Fault Details

fltProcessorUnitThermalThresholdCritical

Fault Code: F0176

Message

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

Explanation

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

• Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.
• Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).
• If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Step 5 Power off unused blade servers and rack servers.

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

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

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

Fault Details

fltProcessorUnitThermalThresholdNonRecoverable

Fault Code: F0177

Message

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

Explanation

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

• Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.
• Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).
• If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Step 5 Power off unused blade servers and rack servers.

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

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

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

Fault Details

fltProcessorUnitVoltageThresholdNonCritical

Fault Code: F0178

Message

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

Explanation

This fault occurs when the processor voltage is out of normal operating range, but hasn’t yet reached a critical stage. Normally the processor recovers itself from this situation

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the processor for further degradation.

Step 2 If the fault occurs on a blade server processor, remove the server from the chassis and then reinsert it.

Step 3 In Cisco FPR Manager, decommission and then recommission the server.

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

Fault Details

fltProcessorUnitVoltageThresholdCritical

Fault Code: F0179

Message

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

Explanation

This fault occurs when the processor voltage has exceeded the specified hardware voltage rating.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the fault occurs on a blade server processor, remove the server from the chassis and then reinsert it.

Step 2 In Cisco FPR Manager, decommission and then recommission the server.

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

Fault Details

fltProcessorUnitVoltageThresholdNonRecoverable

Fault Code: F0180

Message

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

Explanation

This fault occurs when the processor voltage has exceeded the specified hardware voltage rating and may cause processor hardware damage or jeopardy.

Recommended Action

If you see this fault, take the following actions:

Step 1 If the fault occurs on a blade server processor, remove the server from the chassis and then reinsert it.

Step 2 In Cisco FPR Manager, decommission and then recommission the server.

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

Fault Details

fltStorageLocalDiskInoperable

Fault Code: F0181

Message

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

Explanation

This fault occurs when the local disk has become inoperable.

Recommended Action

If you see this fault, take the following actions:

Step 1 Insert the disk in a supported slot.

Step 2 Remove and reinsert the local disk.

Step 3 Replace the disk, if an additional disk is available.

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

Fault Details

fltStorageItemCapacityExceeded

Fault Code: F0182

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Fault Details

fltStorageItemCapacityWarning

Fault Code: F0183

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Fault Details

fltMemoryUnitDegraded

Fault Code: F0184

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltMemoryUnitInoperable

Fault Code: F0185

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 If necessary, replace the DIMM.

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

Fault Details

fltMemoryUnitThermalThresholdNonCritical

Fault Code: F0186

Message

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

Explanation

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

• Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.
• Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).
• If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Step 5 Power off unused blade servers and rack servers.

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

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

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

Fault Details

fltMemoryUnitThermalThresholdCritical

Fault Code: F0187

Message

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

Explanation

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

• Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.
• Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).
• If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Step 5 Power off unused blade servers and rack servers.

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

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

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

Fault Details

fltMemoryUnitThermalThresholdNonRecoverable

Fault Code: F0188

Message

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

Explanation

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

• Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.
• Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).
• If sensors on a CPU reach 179.6F (82C), the system will take that CPU offline.

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Step 5 Power off unused blade servers and rack servers.

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

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

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

Fault Details

fltMemoryArrayVoltageThresholdNonCritical

Fault Code: F0189

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Monitor the memory array for further degradation.

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

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

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

Fault Details

fltMemoryArrayVoltageThresholdCritical

Fault Code: F0190

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Monitor the memory array for further degradation.

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

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

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

Fault Details

fltMemoryArrayVoltageThresholdNonRecoverable

Fault Code: F0191

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Monitor the memory array for further degradation.

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

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

Fault Details

fltAdaptorUnitUnidentifiable-fru

Fault Code: F0200

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that a supported adapter is installed.

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

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

Fault Details

fltAdaptorUnitMissing

Fault Code: F0203

Message

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

Explanation

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

• The endpoint reports there is no adapter in the adaptor slot.
• The endpoint cannot detect or communicate with the adapter in the adaptor slot.

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltAdaptorUnitAdaptorReachability

Fault Code: F0206

Message

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

Explanation

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

• The server does not have sufficient power.
• The I/O module is not functional.
• The adapter firmware has failed.
• The adapter is not functional

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

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

Fault Details

fltAdaptorHostIfLink-down

Fault Code: F0207

Message

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

Explanation

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

• The fabric interconnect is in End-Host mode, and all uplink ports failed.
• The server port to which the adapter is pinned failed.
• A transient error caused the link to fail.

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltAdaptorExtIfLink-down

Fault Code: F0209

Message

Adapter uplink interface [id]/[id]/[id] link state: [linkState]. Please verify connectivity to Fabric Interconnect. Acknowledging FEX might be required.Adapter uplink interface [chassisId]/[slotId]/[id]/[id] on security module [slotId] link state: [linkState]. Please check switch blade-facing port status. Resetting security module might be required.

Explanation

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

• Cisco FPR Manager cannot establish and/or validate the adapter’s connectivity to any of the fabric interconnects.
• The endpoint reports a link down or vNIC down event on the adapter link.
• The endpoint reports an errored link state or errored vNIC state event on the adapter link.

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltPortPIoLink-down

Fault Code: F0276

Message

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

Explanation

This fault occurs when a fabric interconnect port is in link-down state. This state impacts the traffic destined for the port.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the physical link is properly connected between the fabric interconnect and the peer component.

Step 2 Verify that the configuration on the peer entity is properly configured and matches the fabric interconnect port configuration.

Step 3 Unconfigure and re-configure the port.

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

Fault Details

fltPortPIoFailed

Fault Code: F0277

Message

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

Explanation

This fault is raised on fabric interconnect ports and on server-facing ports on an IOM or a FEX module when FPRM detects that the port is not up and in failed state while it is expected to be up since it has been enabled by user and there is no known hardware failure or missing SFP issue and port license is valid. Additional reason is displayed by the fault description string.

Recommended Action

If you see this fault, Corrective action maybe taken based on reason information in the fault description whenever such a reason is displayed. If the fault description displays reason as "ENM source pinning failed" then it means that the fabric interconnect is operating in End-host Node Mode and the uplink port that this server facing port is pinned to is down or does not have appropriate VLAN configured. In case of such an error for an appliance port check the VLAN configuration on uplink port. A VLAN with same id as the one on the appliance port will also need to be configured on the uplink port. After setting the configuration right if you still see the fault then create a show tech-support file for Cisco FPR Manager and the chassis or FEX module, and then contact Cisco TAC.

Fault Details

fltPortPIoHardware-failure

Fault Code: F0278

Message

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

Explanation

This fault is raised on fabric interconnect ports and server-facing ports on an IOM or a FEX module when the system detects a hardware failure.

Recommended Action

If you see this fault, create a show tech-support file for Cisco FPR Manager and the chassis or FEX module, and then contact Cisco TAC.

Fault Details

fltPortPIoSfp-not-present

Fault Code: F0279

Message

[transport] port [portId] on chassis [id] oper state: [operState][transport] port [slotId]/[aggrPortId]/[portId] on fabric interconnect [id] oper state: [operState][transport] port [slotId]/[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 from a configured port.

Recommended Action

If you see this fault, insert a supported SFP into the port on the fabric interconnect. A list of supported SFPs can be found on www.Cisco.com.

Fault Details

fltFabricExternalPcDown

Fault Code: F0282

Message

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

Explanation

This fault typically occurs when a fabric interconnect reports that a fabric port channel is operationally down.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the member ports in the fabric port channel are administratively up and operational. Check the link connectivity for each port.

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

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

Fault Details

fltDcxVcDown

Fault Code: F0283

Message

[transport] VIF [id] on server [chassisId] / [slotId] of switch [switchId] down, reason: [stateQual][transport] VIF [id] on server [id] of switch [switchId] down, reason: [stateQual]

Explanation

This fault typically occurs when a fabric interconnect reports one of the following connectivity states for a virtual interface:

• Down
• Errored
• Unavailable

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the uplink physical interface is up.

Step 2 If the vNIC/vHBA is configured for a pin group, verify that the pin group targets are configured correctly.

Step 3 In the Network Control Policy for the vNIC, verify that the ’Action on Uplink Fail’ field is set to ’warning’.

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

Fault Details

fltNetworkElementInoperable

Fault Code: F0291

Message

Fabric Interconnect [id] operability: [operability]

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltMgmtEntityDegraded

Fault Code: F0293

Message

Fabric Interconnect [id], HA Cluster interconnect link failure

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Fault Details

fltMgmtEntityDown

Fault Code: F0294

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Fault Details

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 adapter’s vif-namespace activation failed due to insufficient resources. Cisco FPR Manager raises this fault when the number of deployed VIF resources exceeds the maximum VIF resources available on the adapter connected to the fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the NS "size" and "used" resources to determine by how many vNICs the adapter exceeded the maximum.

Step 2 Unconfigure or delete all vNICs on the adapter above the maximum number.

Step 3 Add additional fabric uplinks from the IOM to the corresponding fabric interconnect and reacknowledge the chassis. This increases the "NS size" on the adapter.

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

Fault Details

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 Cisco FPR Manager has detected that the server has an insufficient number of DIMMs, CPUs, and/or adapters.

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Verify that an adapter and CPU are installed.

Step 3 Reacknowledge the server.

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

Fault Details

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 Cisco FPR Manager has detected an unsupported server or CPU.

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Verify that the Cisco FPR Manager capability catalog is up to date.

Step 3 Reacknowledge the server.

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

Fault Details

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 Make sure that the server is correctly installed in the chassis and that all cables are secure.

Step 2 If you reinstalled the server, reacknowledge it.

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

Fault Details

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 Make sure that the server is correctly installed in the chassis and that all cables are secure.

Step 2 If you reinstalled the server, reacknowledge it.

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

Fault Details

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 Make sure that the server fans are working properly.

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

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

Fault Details

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 Check the POST results for the server. In Cisco FPR Manager GUI, you can access the POST results from the General tab for the server. In Cisco FPR Manager CLI, you can access the POST results through the show post command under the scope for the server.

Step 2 Reacknowledge the server.

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

Fault Details

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 service profile failed.
• The server is down.
• The data path is not working.
• Cisco FPR Manager cannot communicate with the CIMC on the server.
• The server cannot communicate with the fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 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 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

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.
• Cisco FPR 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 Check the FSM tab and the current state of the server and any FSM operations.

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

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

Fault Details

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 Check the POST results for the server.In Cisco FPR Manager GUI, you can access the POST results from the General tab for the server. In Cisco FPR Manager CLI, you can access the POST results through the show post command under the scope for the server.

Step 2 Reacknowledge the server.

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

Fault Details

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 Cisco FPR Manager.

Recommended Action

If you see this fault, take the following actions:

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

Step 2 If the server is not physically present in the slot, insert it.

Step 3 Reacknowledge the server.

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

Fault Details

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 Cisco FPR Manager.

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Reacknowledge the server.

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

Fault Details

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 Cisco FPR Manager has detected an unsupported server or CPU.

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Verify that the Cisco FPR Manager capability catalog is up to date.

Step 3 Reacknowledge the server.

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

Fault Details

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 the server 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, create a show tech-support file and contact Cisco TAC.

Fault Details

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 the server 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, create a show tech-support file and contact Cisco TAC.

Fault Details

fltLsServerFailed

Fault Code: F0324

Message

Service profile [name] failed

Explanation

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 Check the POST results for the server. In Cisco FPR Manager GUI, you can access the POST results from the General tab for the server. In Cisco FPR Manager CLI, you can access the POST results through the show post command under the scope for the server.

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

Fault Details

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:

• Cisco FPR Manager cannot communicate with the CIMC on the server.
• The server cannot communicate with the fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Fault Details

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 Cisco FPR 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 following occurs:

• The service profile is configured for a server adapter with vHBAs, and the adapter on the server does not support vHBAs.
• The service profile is created from a template which includes a server pool, and the server pool is empty.
• 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 Check the status of the server pool associated with the service profile. If the pool is empty, add more blade servers to it.

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, create a show tech-support file and contact Cisco TAC.

Fault Details

fltLsServerMaintenanceFailed

Fault Code: F0329

Message

Service profile [name] maintenance failed

Explanation

Cisco FPR Manager currently does not use this fault.

Recommended Action

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

Fault Details

fltLsServerRemoved

Fault Code: F0330

Message

Service profile [name] underlying resource removed

Explanation

Cisco FPR 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 server was removed from the slot, reinsert the server in the slot.

Step 2 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 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

fltLsServerInaccessible

Fault Code: F0331

Message

Service profile [name] cannot be accessed

Explanation

Cisco FPR Manager cannot communicate with the CIMC 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 Cisco FPR Manager shows that the CIMC is down, physically reseat the server.

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

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

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

Fault Details

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 Cisco FPR Manager cannot communicate with one or more of the following:

• Fabric interconnect
• CIMC on the server
• SAS controller driver
• Server

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

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 you did not intend to associate the service profile, ignore the fault.

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

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

Fault Details

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 Check the server inventory compare to the service profile qualifications.

Step 2 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 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

fltEtherSwitchIntFIoSatellite-connection-absent

Fault Code: F0367

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Fault Details

fltEtherSwitchIntFIoSatellite-wiring-problem

Fault Code: F0368

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

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 Cisco FPR 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, create a show tech-support file and contact Cisco TAC.

Fault Details

fltEquipmentFanDegraded

Fault Code: F0371

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Verify that the air flows are not obstructed.

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

Step 5 Power off unused blade servers and rack servers.

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

Step 7 Replace the faulty fan modules.

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

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

Fault Details

fltEquipmentFanInoperable

Fault Code: F0373

Message

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

Explanation

This fault occurs if a fan is not operational.

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Replace fan module with a different fan module

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

Fault Details

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 Cisco FPR 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, create a show tech-support file and contact Cisco TAC.

Fault Details

fltEquipmentIOCardRemoved

Fault Code: F0376

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Fault Details

fltEquipmentFanModuleMissing

Fault Code: F0377

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

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 Cisco FPR 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 PSU is physically present in the slot, remove and then reinsert it.

Step 2 If the PSU is not physically present in the slot, insert a new PSU.

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

Fault Details

fltEquipmentIOCardThermalProblem

Fault Code: F0379

Message

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

Explanation

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

• Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.
• Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Step 5 Power off unused blade servers and rack servers.

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

Step 7 Replace faulty I/O modules.

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

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

Fault Details

fltEquipmentFanModuleThermalThresholdNonCritical

Fault Code: F0380

Message

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

Explanation

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

• Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.
• Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Verify that the air flows are not obstructed.

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

Step 5 Power off unused blade servers and rack servers.

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

Step 7 Replace faulty fan modules.

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

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

Fault Details

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

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

• Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.
• Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Verify that the air flows are not obstructed.

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

Step 5 Power off unused blade servers and rack servers.

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

Step 7 Replace faulty PSU modules.

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

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

Fault Details

fltEquipmentFanModuleThermalThresholdCritical

Fault Code: F0382

Message

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

Explanation

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

• Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.
• Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Verify that the air flows are not obstructed.

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

Step 5 Power off unused blade servers and rack servers.

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

Step 7 Replace faulty fan modules.

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

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

Fault Details

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

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

• Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.
• Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Verify that the air flows are not obstructed.

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

Step 5 Power off unused blade servers and rack servers.

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

Step 7 Replace faulty PSU modules.

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

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

Fault Details

fltEquipmentFanModuleThermalThresholdNonRecoverable

Fault Code: F0384

Message

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

Explanation

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

• Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.
• Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Verify that the air flows are not obstructed.

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

Step 5 Power off unused blade servers and rack servers.

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

Step 7 Replace faulty fan modules.

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

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

Fault Details

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

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

• Temperature extremes can cause Cisco FPR equipment to operate at reduced efficiency and cause a variety of problems, including early degradation, failure of chips, and failure of equipment. In addition, extreme temperature fluctuations can cause CPUs to become loose in their sockets.
• Cisco FPR equipment should operate in an environment that provides an inlet air temperature not colder than 50F (10C) nor hotter than 95F (35C).

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Verify that the air flows are not obstructed.

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

Step 5 Power off unused blade servers and rack servers.

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

Step 7 Replace faulty PSU modules.

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

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

Fault Details

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

This fault occurs when the PSU voltage is out of normal operating range, but hasn’t reached to a critical stage yet. Normally the PSU will recover itself from this situation.

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the PSU for further degradation.

Step 2 Remove and reseat the PSU.

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

Fault Details

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

This fault occurs when the PSU voltage has exceeded the specified hardware voltage rating.

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove and reseat the PSU.

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

Fault Details

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

This fault occurs when the PSU voltage has exceeded the specified hardware voltage rating and PSU hardware may have been damaged as a result or may be at risk of being damaged.

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove and reseat the PSU.

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

Fault Details

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

This fault is raised as a warning if the current output of the PSU in a chassis, fabric interconnect, or rack server does not match the desired output value.

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the PSU status.

Step 2 If possible, remove and reseat the PSU.

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

Fault Details

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

This fault occurs if the current output of the PSU in a chassis, fabric interconnect, or rack server is far below or above the desired output value.

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the PSU status.

Step 2 Plan to replace the PSU as soon as possible.

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

Fault Details

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

This fault occurs if the current output of the PSU in a chassis, fabric interconnect, or rack server is far above or below the non-recoverable threshold value.

Recommended Action

If you see this fault, plan to replace the PSU as soon as possible.

Fault Details

fltEquipmentFanPerfThresholdNonCritical

Fault Code: F0395

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the fan status.

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

Step 3 Replace the fan module.

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

Fault Details

fltEquipmentFanPerfThresholdCritical

Fault Code: F0396

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

Step 1 Monitor the fan status.

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

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

Fault Details

fltEquipmentFanPerfThresholdNonRecoverable

Fault Code: F0397

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

Step 1 Replace the fan.

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

Fault Details

fltEquipmentIOCardFirmwareUpgrade

Fault Code: F0398

Message

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

Explanation

This fault typically occurs when an IOM upgrade fails.

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Fault Details

fltEquipmentChassisUnsupportedConnectivity

Fault Code: F0399

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Reacknowledge the chassis.

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

Fault Details

fltEquipmentChassisUnacknowledged

Fault Code: F0400

Message

Chassis [id] connectivity configuration: [configState]

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Reacknowledge the chassis.

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

Fault Details

fltEquipmentIOCardUnsupportedConnectivity

Fault Code: F0401

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Note that atleast 2 links are required to be connected between FEX and 61xx Fabric Interconnect

Step 4 Reacknowledge the chassis.

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

Fault Details

fltEquipmentIOCardUnacknowledged

Fault Code: F0402

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Reacknowledge the chassis.

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

Fault Details

fltEquipmentIOCardPeerDisconnected

Fault Code: F0403

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltEquipmentChassisIdentity

Fault Code: F0404

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Fault Details

fltEquipmentIOCardIdentity

Fault Code: F0405

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Fault Details

fltEquipmentFanModuleIdentity

Fault Code: F0406

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Fault Details

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 the FRU information for a power supply unit is corrupted or malformed.

Recommended Action

If you see this fault, take the following actions:

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

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

Fault Details

fltEquipmentChassisPowerProblem

Fault Code: F0408

Message

Power state on chassis [id] is [power]

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

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

Fault Details

fltEquipmentChassisThermalThresholdCritical

Fault Code: F0409

Message

Thermal condition on chassis [id]. [thermalStateQualifier]

Explanation

This fault occurs under the following conditions:

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

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

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

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

Fault Details

fltEquipmentChassisThermalThresholdNonCritical

Fault Code: F0410

Message

Thermal condition on chassis [id]. [thermalStateQualifier]

Explanation

FPRM raises this fault under the following conditions:

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

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

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

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

Fault Details

fltEquipmentChassisThermalThresholdNonRecoverable

Fault Code: F0411

Message

Thermal condition on chassis [id]. [thermalStateQualifier]

Explanation

FPRM raises this fault under the following conditions:

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

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

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

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

Fault Details

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 the CMOS battery voltage has dropped to lower than the normal operating range. This could impact the clock and other CMOS settings.

Recommended Action

If you see this fault, replace the battery.

Fault Details

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 the CMOS battery voltage has dropped quite low and is unlikely to recover. This impacts the clock and other CMOS settings.

Recommended Action

If you see this fault, replace the battery.

Fault Details

fltMgmtEntityElection-failure

Fault Code: F0428

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Step 4 Reboot the fabric interconnects.

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

Fault Details

fltMgmtEntityHa-not-ready

Fault Code: F0429

Message

Fabric Interconnect [id], HA functionality not ready

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

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

Fault Details

fltMgmtEntityVersion-incompatible

Fault Code: F0430

Message

Fabric Interconnect [id], management services, incompatible versions

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Fault Details

fltEquipmentFanMissing

Fault Code: F0434

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltEquipmentIOCardAutoUpgradingFirmware

Fault Code: F0435

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltFirmwarePackItemImageMissing

Fault Code: F0436

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Fault Details

fltEtherSwitchIntFIoSatellite-wiring-numbers-unexpected

Fault Code: F0440

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Reacknowledge the chassis.

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

Fault Details

fltMgmtEntityManagement-services-failure

Fault Code: F0451

Message

Fabric Interconnect [id], management services have failed

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Reboot the fabric interconnects.

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

Fault Details

fltMgmtEntityManagement-services-unresponsive

Fault Code: F0452

Message

Fabric Interconnect [id], management services are unresponsive

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Reboot the fabric interconnects.

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

Fault Details

fltEquipmentChassisInoperable

Fault Code: F0456

Message

Chassis [id] operability: [operability]

Explanation

This fault typically occurs for one of the following reasons:

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Fault Details