Cisco Firepower 4100/9300 FXOS Faults and Error Messages, 2.10(1)

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book

Results

Updated:
February 16, 2024

Chapter: FXOS Faults

FXOS Faults

This chapter provides information about the faults that may be raised in FXOS.

FXOS Faults

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:

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

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

Fault Details 


Severity: warning
Cause: server-moved
mibFaultCode: F0156
mibFaultName: fltFabricComputeSlotEpMisplacedInChassisSlot
moClass: fabric:ComputeSlotEp
Type: equipment
autoCleared: true
Affected MO: fabric/server/chassis-[chassisId]/slot-[slotId]

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:

  1. Remove and reinsert the server.

  2. Reacknowledge the server.

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

Fault Details 


Severity: warning
Cause: server-identification-problem
mibFaultCode: F0157
mibFaultName: fltFabricComputeSlotEpServerIdentificationProblem
moClass: fabric:ComputeSlotEp
Type: equipment
autoCleared: true
Affected MO: fabric/server/chassis-[chassisId]/slot-[slotId]

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:

  1. Verify that the server was successfully discovered.

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

  3. Confirm that the vCon assignment is correct.

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

Fault Details 


Severity: minor
Cause: configuration-failed
mibFaultCode: F0169
mibFaultName: fltVnicEtherConfigFailed
moClass: vnic:Ether
Type: configuration
autoCleared: true
Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]
Affected MO: org-[name]/ls-[name]/ether-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]

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:

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

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

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

Fault Details 


Severity: major
Cause: equipment-inoperable
mibFaultCode: F0174
mibFaultName: fltProcessorUnitInoperable
moClass: processor:Unit
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]
Affected MO: sys/rack-unit-[id]/board/cpu-[id]

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:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  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.

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

Fault Details 


Severity: info
Cause: thermal-problem
mibFaultCode: F0175
mibFaultName: fltProcessorUnitThermalNonCritical
moClass: processor:Unit
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]
Affected MO: sys/rack-unit-[id]/board/cpu-[id]

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:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  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.

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

Fault Details 


Severity: major
Cause: thermal-problem
mibFaultCode: F0176
mibFaultName: fltProcessorUnitThermalThresholdCritical
moClass: processor:Unit
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]
Affected MO: sys/rack-unit-[id]/board/cpu-[id]

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:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  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.

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

Fault Details 


Severity: minor
Cause: thermal-problem
mibFaultCode: F0177
mibFaultName: fltProcessorUnitThermalThresholdNonRecoverable
moClass: processor:Unit
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]
Affected MO: sys/rack-unit-[id]/board/cpu-[id]

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:

  1. Monitor the processor for further degradation.

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

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

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

Fault Details 


Severity: minor
Cause: voltage-problem
mibFaultCode: F0178
mibFaultName: fltProcessorUnitVoltageThresholdNonCritical
moClass: processor:Unit
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]
Affected MO: sys/rack-unit-[id]/board/cpu-[id]

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:

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

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

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

Fault Details 


Severity: major
Cause: voltage-problem
mibFaultCode: F0179
mibFaultName: fltProcessorUnitVoltageThresholdCritical
moClass: processor:Unit
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]
Affected MO: sys/rack-unit-[id]/board/cpu-[id]

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:

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

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

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

Fault Details 


Severity: critical
Cause: voltage-problem
mibFaultCode: F0180
mibFaultName: fltProcessorUnitVoltageThresholdNonRecoverable
moClass: processor:Unit
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]
Affected MO: sys/rack-unit-[id]/board/cpu-[id]

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:

  1. Insert the disk in a supported slot.

  2. Remove and reinsert the local disk.

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

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

Fault Details 


Severity: major
Cause: equipment-inoperable
mibFaultCode: F0181
mibFaultName: fltStorageLocalDiskInoperable
moClass: storage:LocalDisk
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/disk-[id]
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/disk-[id]

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:

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

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

Fault Details 


Severity: minor
Cause: capacity-exceeded
mibFaultCode: F0182
mibFaultName: fltStorageItemCapacityExceeded
moClass: storage:Item
Type: environmental
autoCleared: true
Affected MO: sys/switch-[id]/stor-part-[name]

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:

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

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

Fault Details 


Severity: critical
Cause: capacity-exceeded
mibFaultCode: F0183
mibFaultName: fltStorageItemCapacityWarning
moClass: storage:Item
Type: environmental
autoCleared: true
Affected MO: sys/switch-[id]/stor-part-[name]

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:

  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.

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

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

Fault Details 


Severity: minor
Cause: equipment-degraded
mibFaultCode: F0184
mibFaultName: fltMemoryUnitDegraded
moClass: memory:Unit
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]/mem-[id]
Affected MO: sys/rack-unit-[id]/board/memarray-[id]/mem-[id]

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:

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

  2. If necessary, replace the DIMM.

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

Fault Details 


Severity: major
Cause: equipment-inoperable
mibFaultCode: F0185
mibFaultName: fltMemoryUnitInoperable
moClass: memory:Unit
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]/mem-[id]
Affected MO: sys/rack-unit-[id]/board/memarray-[id]/mem-[id]

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:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  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.

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

Fault Details 


Severity: info
Cause: thermal-problem
mibFaultCode: F0186
mibFaultName: fltMemoryUnitThermalThresholdNonCritical
moClass: memory:Unit
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]/mem-[id]
Affected MO: sys/rack-unit-[id]/board/memarray-[id]/mem-[id]

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:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  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.

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

Fault Details 


Severity: major
Cause: thermal-problem
mibFaultCode: F0187
mibFaultName: fltMemoryUnitThermalThresholdCritical
moClass: memory:Unit
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]/mem-[id]
Affected MO: sys/rack-unit-[id]/board/memarray-[id]/mem-[id]

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:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  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.

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

Fault Details 


Severity: critical
Cause: thermal-problem
mibFaultCode: F0188
mibFaultName: fltMemoryUnitThermalThresholdNonRecoverable
moClass: memory:Unit
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]/mem-[id]
Affected MO: sys/rack-unit-[id]/board/memarray-[id]/mem-[id]

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:

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

  2. Monitor the memory array for further degradation.

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

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

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

Fault Details 


Severity: minor
Cause: voltage-problem
mibFaultCode: F0189
mibFaultName: fltMemoryArrayVoltageThresholdNonCritical
moClass: memory:Array
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]
Affected MO: sys/rack-unit-[id]/board/memarray-[id]

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:

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

  2. Monitor the memory array for further degradation.

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

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

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

Fault Details 


Severity: major
Cause: voltage-problem
mibFaultCode: F0190
mibFaultName: fltMemoryArrayVoltageThresholdCritical
moClass: memory:Array
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]
Affected MO: sys/rack-unit-[id]/board/memarray-[id]

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:

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

  2. Monitor the memory array for further degradation.

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

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

Fault Details 


Severity: critical
Cause: voltage-problem
mibFaultCode: F0191
mibFaultName: fltMemoryArrayVoltageThresholdNonRecoverable
moClass: memory:Array
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]
Affected MO: sys/rack-unit-[id]/board/memarray-[id]

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:

  1. Verify that a supported adapter is installed.

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

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

Fault Details 


Severity: major
Cause: unidentifiable-fru
mibFaultCode: F0200
mibFaultName: fltAdaptorUnitUnidentifiableFru
moClass: adaptor:Unit
Type: server
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]

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:

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

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

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

Fault Details 


Severity: warning
Cause: equipment-missing
mibFaultCode: F0203
mibFaultName: fltAdaptorUnitMissing
moClass: adaptor:Unit
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]

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:

  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.

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

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

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

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

Fault Details 


Severity: info
Cause: connectivity-problem
mibFaultCode: F0206
mibFaultName: fltAdaptorUnitAdaptorReachability
moClass: adaptor:Unit
Type: connectivity
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]

fltAdaptorHostIfLink-down

Fault Code: F0207

Message: Adapter [transport] host interface [id]/[id]/[id] link state: [linkState], Associated external interface link state: [vcAdminState]Adapter [transport] host interface [chassisId]/[slotId]/[id]/[id] link state: [linkState], Associated external interface link state: [vcAdminState]

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:

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

  2. Check the associated port to ensure it is in up state.

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

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

  5. vnic link state will be down, when its associated external interface is down.The fault should not be displayed regardless if it is administratively disabled or if it is operationally not up(i.e. physical link is detected as down).

Fault Details 


Severity: major
Cause: link-down
mibFaultCode: F0207
mibFaultName: fltAdaptorHostIfLinkDown
moClass: adaptor:HostIf
Type: network
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-iscsi-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-service-eth-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-iscsi-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-service-eth-[id]

fltAdaptorExtIfLink-down

Fault Code: F0209

Message: 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:

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

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

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

Fault Details 


Severity: critical
Cause: link-down
mibFaultCode: F0209
mibFaultName: fltAdaptorExtIfLinkDown
moClass: adaptor:ExtIf
Type: network
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/ext-eth-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/ext-eth-[id]

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:

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

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

  3. Unconfigure and re-configure the port.

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

Fault Details 


Severity: major
Cause: link-down
mibFaultCode: F0276
mibFaultName: fltPortPIoLinkDown
moClass: port:PIo
Type: network
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]
Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

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 


Severity: major
Cause: port-failed
mibFaultCode: F0277
mibFaultName: fltPortPIoFailed
moClass: port:PIo
Type: network
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]
Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

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 


Severity: major
Cause: port-failed
mibFaultCode: F0278
mibFaultName: fltPortPIoHardwareFailure
moClass: port:PIo
Type: network
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]
Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

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 


Severity: info
Cause: port-failed
mibFaultCode: F0279
mibFaultName: fltPortPIoSfpNotPresent
moClass: port:PIo
Type: network
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]
Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

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:

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

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

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

Fault Details 


Severity: major
Cause: operational-state-down
mibFaultCode: F0282
mibFaultName: fltFabricExternalPcDown
moClass: fabric:ExternalPc
Type: network
autoCleared: true
Affected MO: fabric/eth-estc/[id]/net-[name]/pc-switch-[switchId]-pc-[portId]
Affected MO: fabric/eth-estc/[id]/pc-[portId]
Affected MO: fabric/eth-estc/net-[name]/pc-switch-[switchId]-pc-[portId]
Affected MO: fabric/lan/[id]/net-[name]/pc-switch-[switchId]-pc-[portId]
Affected MO: fabric/lan/[id]/net-group-[name]/pc-switch-[switchId]-pc-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]
Affected MO: fabric/lan/net-[name]/pc-switch-[switchId]-pc-[portId]
Affected MO: fabric/lan/net-group-[name]/pc-switch-[switchId]-pc-[portId]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]
Affected MO: fabric/san/[id]/net-[name]/fcoepc-switch-[switchId]-fcoepc-[portId]
Affected MO: fabric/san/[id]/net-[name]/pc-switch-[switchId]-pc-[portId]
Affected MO: fabric/san/[id]/pc-[portId]
Affected MO: fabric/san/net-[name]/fcoepc-switch-[switchId]-fcoepc-[portId]
Affected MO: fabric/san/net-[name]/pc-switch-[switchId]-pc-[portId]

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:

  1. Verify that the uplink physical interface is up.

  2. Check the associated port to ensure it is in up state.

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

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

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

Fault Details 


Severity: major
Cause: link-down
mibFaultCode: F0283
mibFaultName: fltDcxVcDown
moClass: dcx:Vc
Type: network
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/fex-[id]/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/fex-[id]/fabric-[switchId]/vc-[id]
Affected MO: sys/fex-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/fex-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/rack-unit-[id]/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/rack-unit-[id]/fabric-[switchId]/vc-[id]
Affected MO: sys/rack-unit-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/rack-unit-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/vc-[id]
Affected MO: sys/switch-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/switch-[id]/mgmt/fabric-[switchId]/vc-[id]

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:

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

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

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

Fault Details 


Severity: critical
Cause: equipment-inoperable
mibFaultCode: F0291
mibFaultName: fltNetworkElementInoperable
moClass: network:Element
Type: equipment
autoCleared: true
Affected MO: sys/switch-[id]

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:

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

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

Fault Details 


Severity: major
Cause: link-down
mibFaultCode: F0293
mibFaultName: fltMgmtEntityDegraded
moClass: mgmt:Entity
Type: network
autoCleared: true
Affected MO: sys/mgmt-entity-[id]

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:

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

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

Fault Details 


Severity: critical
Cause: link-down
mibFaultCode: F0294
mibFaultName: fltMgmtEntityDown
moClass: mgmt:Entity
Type: network
autoCleared: true
Affected MO: sys/mgmt-entity-[id]

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:

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

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

  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.

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

Fault Details 


Severity: major
Cause: insufficient-resources
mibFaultCode: F0304
mibFaultName: fltDcxNsFailed
moClass: dcx:Ns
Type: server
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/dcxns-[switchId]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/dcxns-[switchId]

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:

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

  2. Verify that an adapter and CPU are installed.

  3. Reacknowledge the server.

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

Fault Details 


Severity: minor
Cause: insufficiently-equipped
mibFaultCode: F0305
mibFaultName: fltComputePhysicalInsufficientlyEquipped
moClass: compute:Physical
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

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:

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

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

  3. Reacknowledge the server.

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

Fault Details 


Severity: minor
Cause: identity-unestablishable
mibFaultCode: F0306
mibFaultName: fltComputePhysicalIdentityUnestablishable
moClass: compute:Physical
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

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:

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

  2. If you reinstalled the server, reacknowledge it.

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

Fault Details 


Severity: major
Cause: power-problem
mibFaultCode: F0310
mibFaultName: fltComputeBoardPowerError
moClass: compute:Board
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board
Affected MO: sys/rack-unit-[id]/board

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:

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

  2. If you reinstalled the server, reacknowledge it.

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

Fault Details 


Severity: major
Cause: power-problem
mibFaultCode: F0311
mibFaultName: fltComputePhysicalPowerProblem
moClass: compute:Physical
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

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:

  1. Make sure that the server fans are working properly.

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

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

Fault Details 


Severity: minor
Cause: thermal-problem
mibFaultCode: F0312
mibFaultName: fltComputePhysicalThermalProblem
moClass: compute:Physical
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

fltComputePhysicalBiosPostTimeout

Fault Code: F0313

Message: Server [id] (service profile: [assignedToDn]) BIOS failed power-on self testBlade [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:

  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.

  2. Reacknowledge the server.

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

Fault Details 


Severity: critical
Cause: equipment-inoperable
mibFaultCode: F0313
mibFaultName: fltComputePhysicalBiosPostTimeout
moClass: compute:Physical
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

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:

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

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

  3. If the server or a server component has failed, do the following:

    1. Check the operational state of the server.

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

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

Fault Details 


Severity: major
Cause: discovery-failed
mibFaultCode: F0314
mibFaultName: fltComputePhysicalDiscoveryFailed
moClass: compute:Physical
Type: operational
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

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:

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

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

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

Fault Details 


Severity: critical
Cause: association-failed
mibFaultCode: F0315
mibFaultName: fltComputePhysicalAssociationFailed
moClass: compute:Physical
Type: configuration
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

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:

  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.

  2. Reacknowledge the server.

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

Fault Details 


Severity: major
Cause: equipment-inoperable
mibFaultCode: F0317
mibFaultName: fltComputePhysicalInoperable
moClass: compute:Physical
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

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:

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

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

  3. Reacknowledge the server.

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

Fault Details 


Severity: minor
Cause: equipment-missing
mibFaultCode: F0318
mibFaultName: fltComputePhysicalUnassignedMissing
moClass: compute:Physical
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

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:

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

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

  3. Reacknowledge the server.

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

Fault Details 


Severity: major
Cause: equipment-missing
mibFaultCode: F0319
mibFaultName: fltComputePhysicalAssignedMissing
moClass: compute:Physical
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

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:

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

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

  3. Reacknowledge the server.

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

Fault Details 


Severity: minor
Cause: identity-unestablishable
mibFaultCode: F0320
mibFaultName: fltComputePhysicalUnidentified
moClass: compute:Physical
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

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:

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

  2. If the fault does not clear after a brief time, remove the server and then reinsert it.

  3. Reacknowledge the server.

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

Fault Details 


Severity: warning
Cause: equipment-inaccessible
mibFaultCode: F0321
mibFaultName: fltComputePhysicalUnassignedInaccessible
moClass: compute:Physical
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

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:

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

  2. If the fault does not clear after a brief time, remove the server and then reinsert it.

  3. Reacknowledge the server.

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

Fault Details 


Severity: minor
Cause: equipment-inaccessible
mibFaultCode: F0322
mibFaultName: fltComputePhysicalAssignedInaccessible
moClass: compute:Physical
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

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:

  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.

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

Fault Details 


Severity: major
Cause: server-failed
mibFaultCode: F0324
mibFaultName: fltLsServerFailed
moClass: ls:Server
Type: server
autoCleared: true
Affected MO: org-[name]/ls-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]

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:

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

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

  3. If the server or a server component has failed, do the following:

    1. Check the operational state of the server.

    2. If the server is not operable, reacknowledge the server.

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

Fault Details 


Severity: major
Cause: discovery-failed
mibFaultCode: F0326
mibFaultName: fltLsServerDiscoveryFailed
moClass: ls:Server
Type: server
autoCleared: true
Affected MO: org-[name]/ls-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]

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:

  1. Check the status of the server pool associated with the service profile. If the pool is empty, add more blade servers to it.

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

  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.

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

  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.

  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 


Severity: major
Cause: configuration-failure
mibFaultCode: F0327
mibFaultName: fltLsServerConfigFailure
moClass: ls:Server
Type: server
autoCleared: true
Affected MO: org-[name]/ls-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]

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 


Severity: major
Cause: maintenance-failed
mibFaultCode: F0329
mibFaultName: fltLsServerMaintenanceFailed
moClass: ls:Server
Type: server
autoCleared: true
Affected MO: org-[name]/ls-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]

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:

  1. If the server was removed from the slot, reinsert the server in the slot.

  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.

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

Fault Details 


Severity: major
Cause: equipment-removed
mibFaultCode: F0330
mibFaultName: fltLsServerRemoved
moClass: ls:Server
Type: server
autoCleared: true
Affected MO: org-[name]/ls-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]

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:

  1. If Cisco FPR Manager shows that the CIMC is down, physically reseat the server.

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

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

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

Fault Details 


Severity: major
Cause: server-inaccessible
mibFaultCode: F0331
mibFaultName: fltLsServerInaccessible
moClass: ls:Server
Type: server
autoCleared: true
Affected MO: org-[name]/ls-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]

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:

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

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

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

Fault Details 


Severity: major
Cause: association-failed
mibFaultCode: F0332
mibFaultName: fltLsServerAssociationFailed
moClass: ls:Server
Type: server
autoCleared: true
Affected MO: org-[name]/ls-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]

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:

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

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

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

Fault Details 


Severity: warning
Cause: unassociated
mibFaultCode: F0334
mibFaultName: fltLsServerUnassociated
moClass: ls:Server
Type: server
autoCleared: true
Affected MO: org-[name]/ls-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]

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:

  1. Check the server inventory compare to the service profile qualifications.

  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.

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

Fault Details 


Severity: warning
Cause: server-failed
mibFaultCode: F0337
mibFaultName: fltLsServerServerUnfulfilled
moClass: ls:Server
Type: server
autoCleared: true
Affected MO: org-[name]/ls-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]

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:

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

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

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

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

Fault Details 


Severity: major
Cause: satellite-connection-absent
mibFaultCode: F0367
mibFaultName: fltEtherSwitchIntFIoSatelliteConnectionAbsent
moClass: ether:SwitchIntFIo
Type: connectivity
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]
Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

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:

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

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

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

Fault Details 


Severity: info
Cause: satellite-mis-connected
mibFaultCode: F0368
mibFaultName: fltEtherSwitchIntFIoSatelliteWiringProblem
moClass: ether:SwitchIntFIo
Type: connectivity
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]
Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

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:

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

  2. Verify that the power source is 220 volts.

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

  4. Remove the PSU and reinstall it.

  5. Replace the PSU.

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

Fault Details 


Severity: major
Cause: power-problem
mibFaultCode: F0369
mibFaultName: fltEquipmentPsuPowerSupplyProblem
moClass: equipment:Psu
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

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:

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

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

  3. Verify that the air flows are not obstructed.

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

  5. Power off unused blade servers and rack servers.

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

  7. Replace the faulty fan modules.

  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.

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

Fault Details 


Severity: minor
Cause: equipment-degraded
mibFaultCode: F0371
mibFaultName: fltEquipmentFanDegraded
moClass: equipment:Fan
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/fan-[id]
Affected MO: sys/fex-[id]/fan-[id]
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/fan-[id]
Affected MO: sys/switch-[id]/fan-[id]
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/fan-[id]

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:

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

  2. Replace fan module with a different fan module

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

Fault Details 


Severity: major
Cause: equipment-inoperable
mibFaultCode: F0373
mibFaultName: fltEquipmentFanInoperable
moClass: equipment:Fan
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/fan-[id]
Affected MO: sys/fex-[id]/fan-[id]
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/fan-[id]
Affected MO: sys/switch-[id]/fan-[id]
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/fan-[id]

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:

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

  2. Verify that the power source is 220 volts.

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

  4. Remove the PSU and reinstall it.

  5. Replace the PSU.

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

Fault Details 


Severity: major
Cause: equipment-inoperable
mibFaultCode: F0374
mibFaultName: fltEquipmentPsuInoperable
moClass: equipment:Psu
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

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:

  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.

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

Fault Details 


Severity: critical
Cause: equipment-removed
mibFaultCode: F0376
mibFaultName: fltEquipmentIOCardRemoved
moClass: equipment:IOCard
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]
Affected MO: sys/fex-[id]/slot-[id]

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:

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

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

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

Fault Details 


Severity: warning
Cause: equipment-missing
mibFaultCode: F0377
mibFaultName: fltEquipmentFanModuleMissing
moClass: equipment:FanModule
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]

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:

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

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

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

Fault Details 


Severity: warning
Cause: equipment-missing
mibFaultCode: F0378
mibFaultName: fltEquipmentPsuMissing
moClass: equipment:Psu
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

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:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  7. Replace faulty I/O modules.

  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.

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

Fault Details 


Severity: major
Cause: thermal-problem
mibFaultCode: F0379
mibFaultName: fltEquipmentIOCardThermalProblem
moClass: equipment:IOCard
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]
Affected MO: sys/fex-[id]/slot-[id]

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:

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

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

  3. Verify that the air flows are not obstructed.

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

  5. Power off unused blade servers and rack servers.

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

  7. Replace faulty fan modules.

  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.

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

Fault Details 


Severity: minor
Cause: thermal-problem
mibFaultCode: F0380
mibFaultName: fltEquipmentFanModuleThermalThresholdNonCritical
moClass: equipment:FanModule
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]

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:

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

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

  3. Verify that the air flows are not obstructed.

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

  5. Power off unused blade servers and rack servers.

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

  7. Replace faulty PSU modules.

  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.

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

Fault Details 


Severity: minor
Cause: thermal-problem
mibFaultCode: F0381
mibFaultName: fltEquipmentPsuThermalThresholdNonCritical
moClass: equipment:Psu
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

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:

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

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

  3. Verify that the air flows are not obstructed.

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

  5. Power off unused blade servers and rack servers.

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

  7. Replace faulty fan modules.

  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.

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

Fault Details 


Severity: major
Cause: thermal-problem
mibFaultCode: F0382
mibFaultName: fltEquipmentFanModuleThermalThresholdCritical
moClass: equipment:FanModule
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]

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:

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

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

  3. Verify that the air flows are not obstructed.

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

  5. Power off unused blade servers and rack servers.

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

  7. Replace faulty PSU modules.

  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.

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

Fault Details 


Severity: major
Cause: thermal-problem
mibFaultCode: F0383
mibFaultName: fltEquipmentPsuThermalThresholdCritical
moClass: equipment:Psu
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

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:

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

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

  3. Verify that the air flows are not obstructed.

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

  5. Power off unused blade servers and rack servers.

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

  7. Replace faulty fan modules.

  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.

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

Fault Details 


Severity: critical
Cause: thermal-problem
mibFaultCode: F0384
mibFaultName: fltEquipmentFanModuleThermalThresholdNonRecoverable
moClass: equipment:FanModule
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]

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:

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

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

  3. Verify that the air flows are not obstructed.

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

  5. Power off unused blade servers and rack servers.

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

  7. Replace faulty PSU modules.

  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.

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

Fault Details 


Severity: critical
Cause: thermal-problem
mibFaultCode: F0385
mibFaultName: fltEquipmentPsuThermalThresholdNonRecoverable
moClass: equipment:Psu
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

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:

  1. Monitor the PSU for further degradation.

  2. Remove and reseat the PSU.

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

Fault Details 


Severity: minor
Cause: voltage-problem
mibFaultCode: F0387
mibFaultName: fltEquipmentPsuVoltageThresholdNonCritical
moClass: equipment:Psu
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

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:

  1. Remove and reseat the PSU.

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

Fault Details 


Severity: major
Cause: voltage-problem
mibFaultCode: F0389
mibFaultName: fltEquipmentPsuVoltageThresholdCritical
moClass: equipment:Psu
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

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:

  1. Remove and reseat the PSU.

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

Fault Details 


Severity: critical
Cause: voltage-problem
mibFaultCode: F0391
mibFaultName: fltEquipmentPsuVoltageThresholdNonRecoverable
moClass: equipment:Psu
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

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:

  1. Monitor the PSU status.

  2. If possible, remove and reseat the PSU.

  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 


Severity: minor
Cause: performance-problem
mibFaultCode: F0392
mibFaultName: fltEquipmentPsuPerfThresholdNonCritical
moClass: equipment:Psu
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

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:

  1. Monitor the PSU status.

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

  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 


Severity: major
Cause: performance-problem
mibFaultCode: F0393
mibFaultName: fltEquipmentPsuPerfThresholdCritical
moClass: equipment:Psu
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

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 


Severity: critical
Cause: performance-problem
mibFaultCode: F0394
mibFaultName: fltEquipmentPsuPerfThresholdNonRecoverable
moClass: equipment:Psu
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

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:

  1. Monitor the fan status.

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

  3. Replace the fan module.

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

Fault Details 


Severity: info
Cause: performance-problem
mibFaultCode: F0395
mibFaultName: fltEquipmentFanPerfThresholdNonCritical
moClass: equipment:Fan
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/fan-[id]
Affected MO: sys/fex-[id]/fan-[id]
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/fan-[id]
Affected MO: sys/switch-[id]/fan-[id]
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/fan-[id]

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:

  1. Monitor the fan status.

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

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

Fault Details 


Severity: info
Cause: performance-problem
mibFaultCode: F0396
mibFaultName: fltEquipmentFanPerfThresholdCritical
moClass: equipment:Fan
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/fan-[id]
Affected MO: sys/fex-[id]/fan-[id]
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/fan-[id]
Affected MO: sys/switch-[id]/fan-[id]
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/fan-[id]

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:

  1. Replace the fan.

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

Fault Details 


Severity: info
Cause: performance-problem
mibFaultCode: F0397
mibFaultName: fltEquipmentFanPerfThresholdNonRecoverable
moClass: equipment:Fan
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/fan-[id]
Affected MO: sys/fex-[id]/fan-[id]
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/fan-[id]
Affected MO: sys/switch-[id]/fan-[id]
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/fan-[id]

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:

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

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

  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.

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

Fault Details 


Severity: major
Cause: firmware-upgrade-problem
mibFaultCode: F0398
mibFaultName: fltEquipmentIOCardFirmwareUpgrade
moClass: equipment:IOCard
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]
Affected MO: sys/fex-[id]/slot-[id]

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:

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

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

  3. Reacknowledge the chassis.

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

Fault Details 


Severity: major
Cause: unsupported-connectivity-configuration
mibFaultCode: F0399
mibFaultName: fltEquipmentChassisUnsupportedConnectivity
moClass: equipment:Chassis
Type: connectivity
autoCleared: true
Affected MO: sys/chassis-[id]

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:

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

  2. Reacknowledge the chassis.

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

Fault Details 


Severity: warning
Cause: equipment-unacknowledged
mibFaultCode: F0400
mibFaultName: fltEquipmentChassisUnacknowledged
moClass: equipment:Chassis
Type: connectivity
autoCleared: true
Affected MO: sys/chassis-[id]

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:

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

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

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

  4. Reacknowledge the chassis.

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

Fault Details 


Severity: major
Cause: unsupported-connectivity-configuration
mibFaultCode: F0401
mibFaultName: fltEquipmentIOCardUnsupportedConnectivity
moClass: equipment:IOCard
Type: connectivity
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]
Affected MO: sys/fex-[id]/slot-[id]

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:

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

  2. Reacknowledge the chassis.

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

Fault Details 


Severity: warning
Cause: equipment-unacknowledged
mibFaultCode: F0402
mibFaultName: fltEquipmentIOCardUnacknowledged
moClass: equipment:IOCard
Type: connectivity
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]
Affected MO: sys/fex-[id]/slot-[id]

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:

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

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

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

Fault Details 


Severity: warning
Cause: equipment-disconnected
mibFaultCode: F0403
mibFaultName: fltEquipmentIOCardPeerDisconnected
moClass: equipment:IOCard
Type: connectivity
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]
Affected MO: sys/fex-[id]/slot-[id]

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:

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

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

Fault Details 


Severity: critical
Cause: fru-problem
mibFaultCode: F0404
mibFaultName: fltEquipmentChassisIdentity
moClass: equipment:Chassis
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]

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:

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

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

Fault Details 


Severity: critical
Cause: fru-problem
mibFaultCode: F0405
mibFaultName: fltEquipmentIOCardIdentity
moClass: equipment:IOCard
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]
Affected MO: sys/fex-[id]/slot-[id]

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:

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

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

Fault Details 


Severity: critical
Cause: fru-problem
mibFaultCode: F0406
mibFaultName: fltEquipmentFanModuleIdentity
moClass: equipment:FanModule
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]

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:

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

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

Fault Details 


Severity: critical
Cause: fru-problem
mibFaultCode: F0407
mibFaultName: fltEquipmentPsuIdentity
moClass: equipment:Psu
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

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:

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

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

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

  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.

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

Fault Details 


Severity: major
Cause: power-problem
mibFaultCode: F0408
mibFaultName: fltEquipmentChassisPowerProblem
moClass: equipment:Chassis
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]

fltEquipmentChassisThermalThresholdCritical

Fault Code: F0409

Message: Thermal condition on chassis [id]. [thermalStateQualifier]

Explanation: This fault occurs under the following conditions:

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

  2. If the chassis controller in the supervisor 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:

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

  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.

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

  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.

  5. If the fault reports a "No connectivity between supervisor 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.

  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 


Severity: major
Cause: thermal-problem
mibFaultCode: F0409
mibFaultName: fltEquipmentChassisThermalThresholdCritical
moClass: equipment:Chassis
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]

fltEquipmentChassisThermalThresholdNonRecoverable

Fault Code: F0411

Message: Thermal condition on chassis [id]. [thermalStateQualifier]

Explanation: FPRM raises this fault under the following conditions:

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

  2. If the chassis controller in the supervisor 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:

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

  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.

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

  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.

  5. If the fault reports a "No connectivity between supervisor 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.

  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 


Severity: critical
Cause: thermal-problem
mibFaultCode: F0411
mibFaultName: fltEquipmentChassisThermalThresholdNonRecoverable
moClass: equipment:Chassis
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]

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 


Severity: major
Cause: voltage-problem
mibFaultCode: F0424
mibFaultName: fltComputeBoardCmosVoltageThresholdCritical
moClass: compute:Board
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board
Affected MO: sys/rack-unit-[id]/board

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 


Severity: major
Cause: voltage-problem
mibFaultCode: F0425
mibFaultName: fltComputeBoardCmosVoltageThresholdNonRecoverable
moClass: compute:Board
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board
Affected MO: sys/rack-unit-[id]/board

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:

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

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

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

  4. Reboot the fabric interconnects.

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

Fault Details 


Severity: critical
Cause: election-failure
mibFaultCode: F0428
mibFaultName: fltMgmtEntityElectionFailure
moClass: mgmt:Entity
Type: management
autoCleared: true
Affected MO: sys/mgmt-entity-[id]

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:

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

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

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

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

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

Fault Details 


Severity: major
Cause: ha-not-ready
mibFaultCode: F0429
mibFaultName: fltMgmtEntityHaNotReady
moClass: mgmt:Entity
Type: management
autoCleared: true
Affected MO: sys/mgmt-entity-[id]

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:

  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.

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

Fault Details 


Severity: critical
Cause: version-incompatible
mibFaultCode: F0430
mibFaultName: fltMgmtEntityVersionIncompatible
moClass: mgmt:Entity
Type: management
autoCleared: true
Affected MO: sys/mgmt-entity-[id]

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:

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

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

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

Fault Details 


Severity: warning
Cause: equipment-missing
mibFaultCode: F0434
mibFaultName: fltEquipmentFanMissing
moClass: equipment:Fan
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/fan-[id]
Affected MO: sys/fex-[id]/fan-[id]
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/fan-[id]
Affected MO: sys/switch-[id]/fan-[id]
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/fan-[id]

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:

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

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

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

Fault Details 


Severity: major
Cause: auto-firmware-upgrade
mibFaultCode: F0435
mibFaultName: fltEquipmentIOCardAutoUpgradingFirmware
moClass: equipment:IOCard
Type: connectivity
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]
Affected MO: sys/fex-[id]/slot-[id]

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:

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

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

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

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

Fault Details 


Severity: major
Cause: image-deleted
mibFaultCode: F0436
mibFaultName: fltFirmwarePackItemImageMissing
moClass: firmware:PackItem
Type: management
autoCleared: true
Affected MO: org-[name]/fw-catalog-pack-[name]/pack-image-[hwVendor]|[hwModel]|[type]
Affected MO: org-[name]/fw-host-pack-[name]/pack-image-[hwVendor]|[hwModel]|[type]
Affected MO: org-[name]/fw-infra-pack-[name]/pack-image-[hwVendor]|[hwModel]|[type]
Affected MO: org-[name]/fw-mgmt-pack-[name]/pack-image-[hwVendor]|[hwModel]|[type]
Affected MO: org-[name]/fw-platform-pack-[name]/pack-image-[hwVendor]|[hwModel]|[type]
Affected MO: org-[name]/pack-image-[hwVendor]|[hwModel]|[type]

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:

  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.

  2. Reacknowledge the chassis.

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

Fault Details 


Severity: info
Cause: unexpected-number-of-links
mibFaultCode: F0440
mibFaultName: fltEtherSwitchIntFIoSatelliteWiringNumbersUnexpected
moClass: ether:SwitchIntFIo
Type: connectivity
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]
Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

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:

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

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

  3. Reboot the fabric interconnects.

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

Fault Details 


Severity: critical
Cause: management-services-failure
mibFaultCode: F0451
mibFaultName: fltMgmtEntityManagementServicesFailure
moClass: mgmt:Entity
Type: management
autoCleared: true
Affected MO: sys/mgmt-entity-[id]

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:

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

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

  3. Reboot the fabric interconnects.

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

Fault Details 


Severity: critical
Cause: management-services-unresponsive
mibFaultCode: F0452
mibFaultName: fltMgmtEntityManagementServicesUnresponsive
moClass: mgmt:Entity
Type: management
autoCleared: true
Affected MO: sys/mgmt-entity-[id]

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:

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

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

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

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

Fault Details 


Severity: critical
Cause: equipment-inoperable
mibFaultCode: F0456
mibFaultName: fltEquipmentChassisInoperable
moClass: equipment:Chassis
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]

fltEtherServerIntFIoHardware-failure

Fault Code: F0458

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

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

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

Fault Details 


Severity: major
Cause: interface-failed
mibFaultCode: F0458
mibFaultName: fltEtherServerIntFIoHardwareFailure
moClass: ether:ServerIntFIo
Type: network
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/diag/port-[portId]
Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]
Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/rack-unit-[id]/diag/port-[portId]
Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fltDcxVcMgmt-vif-down

Fault Code: F0459

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

Explanation: This fault occurs when the transport VIF for an I/O module is down. Cisco FPR Manager raises this fault when a fabric interconnect reports the connectivity state on virtual interface as one of the following:

  • Down

  • Errored

  • Unavailable

Recommended Action: If you see this fault, take the following actions:

  1. Verify that the chassis discovery has gone through successfully. Check the states on all communicating ports from end to end.

  2. If connectivity seems correct, decommission and recommission the chassis.

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

Fault Details 


Severity: major
Cause: cmc-vif-down
mibFaultCode: F0459
mibFaultName: fltDcxVcMgmtVifDown
moClass: dcx:Vc
Type: network
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/fex-[id]/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/fex-[id]/fabric-[switchId]/vc-[id]
Affected MO: sys/fex-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/fex-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/rack-unit-[id]/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/rack-unit-[id]/fabric-[switchId]/vc-[id]
Affected MO: sys/rack-unit-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/rack-unit-[id]/mgmt/fabric-[switchId]/vc-[id]
Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/vc-[id]
Affected MO: sys/switch-[id]/mgmt/fabric-[switchId]/path-[id]/vc-[id]
Affected MO: sys/switch-[id]/mgmt/fabric-[switchId]/vc-[id]

fltSysdebugMEpLogMEpLogLog

Fault Code: F0460

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

Explanation: This fault typically occurs because Cisco FPR Manager has detected that the system event log (SEL) on the server is approaching full capacity. The available capacity in the log is low. This is an info-level fault and can be ignored if you do not want to clear the SEL at this time.

Recommended Action: If you see this fault, you can clear the SEL in Cisco FPR Manager if desired.

Fault Details 


Severity: info
Cause: log-capacity
mibFaultCode: F0460
mibFaultName: fltSysdebugMEpLogMEpLogLog
moClass: sysdebug:MEpLog
Type: operational
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/log-[type]-[id]
Affected MO: sys/fex-[id]/mgmt/log-[type]-[id]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/log-[type]-[id]
Affected MO: sys/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/mgmt/log-[type]-[id]
Affected MO: sys/switch-[id]/mgmt/log-[type]-[id]

fltSysdebugMEpLogMEpLogVeryLow

Fault Code: F0461

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

Explanation: This fault typically occurs because Cisco FPR Manager has detected that the system event log (SEL) on the server is almost full. The available capacity in the log is very low. This is an info-level fault and can be ignored if you do not want to clear the SEL at this time.

Recommended Action: If you see this fault, you can clear the SEL in Cisco FPR Manager if desired.

Fault Details 


Severity: info
Cause: log-capacity
mibFaultCode: F0461
mibFaultName: fltSysdebugMEpLogMEpLogVeryLow
moClass: sysdebug:MEpLog
Type: operational
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/log-[type]-[id]
Affected MO: sys/fex-[id]/mgmt/log-[type]-[id]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/log-[type]-[id]
Affected MO: sys/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/mgmt/log-[type]-[id]
Affected MO: sys/switch-[id]/mgmt/log-[type]-[id]

fltSysdebugMEpLogMEpLogFull

Fault Code: F0462

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

Explanation: This fault typically occurs because Cisco FPR Manager could not transfer the SEL file to the location specified in the SEL policy. This is an info-level fault and can be ignored if you do not want to clear the SEL at this time.

Recommended Action: If you see this fault, take the following actions:

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

  2. If you do want to transfer and clear the SEL and the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details 


Severity: info
Cause: log-capacity
mibFaultCode: F0462
mibFaultName: fltSysdebugMEpLogMEpLogFull
moClass: sysdebug:MEpLog
Type: operational
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/log-[type]-[id]
Affected MO: sys/fex-[id]/mgmt/log-[type]-[id]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/log-[type]-[id]
Affected MO: sys/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/mgmt/log-[type]-[id]
Affected MO: sys/switch-[id]/mgmt/log-[type]-[id]

fltComputePoolEmpty

Fault Code: F0463

Message: server pool [name] is empty

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

Recommended Action: If you see this fault, take the following actions:

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

  2. Manually associate the service profile with a server.

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

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

Fault Details 


Severity: minor
Cause: empty-pool
mibFaultCode: F0463
mibFaultName: fltComputePoolEmpty
moClass: compute:Pool
Type: server
autoCleared: true
Affected MO: org-[name]/compute-pool-[name]

fltUuidpoolPoolEmpty

Fault Code: F0464

Message: UUID suffix pool [name] is empty

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

Recommended Action: If you see this fault, take the following actions:

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

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

Fault Details 


Severity: minor
Cause: empty-pool
mibFaultCode: F0464
mibFaultName: fltUuidpoolPoolEmpty
moClass: uuidpool:Pool
Type: server
autoCleared: true
Affected MO: org-[name]/uuid-pool-[name]

fltIppoolPoolEmpty

Fault Code: F0465

Message: IP pool [name] is empty

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

Recommended Action: If you see this fault, take the following actions:

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

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

Fault Details 


Severity: minor
Cause: empty-pool
mibFaultCode: F0465
mibFaultName: fltIppoolPoolEmpty
moClass: ippool:Pool
Type: server
autoCleared: true
Affected MO: fabric/lan/network-sets/ip-pool-[name]
Affected MO: org-[name]/ip-pool-[name]

fltMacpoolPoolEmpty

Fault Code: F0466

Message: MAC pool [name] is empty

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

Recommended Action: If you see this fault, take the following actions:

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

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

Fault Details 


Severity: minor
Cause: empty-pool
mibFaultCode: F0466
mibFaultName: fltMacpoolPoolEmpty
moClass: macpool:Pool
Type: server
autoCleared: true
Affected MO: org-[name]/mac-pool-[name]

fltFirmwareUpdatableImageUnusable

Fault Code: F0470

Message: backup image is unusable. reason: [operStateQual]

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

Recommended Action: If you see this fault, take the following actions:

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

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

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

Fault Details 


Severity: major
Cause: image-unusable
mibFaultCode: F0470
mibFaultName: fltFirmwareUpdatableImageUnusable
moClass: firmware:Updatable
Type: management
autoCleared: true
Affected MO: sys/chassis-[id]/Ssd/fw-updatable
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fw-updatable
Affected MO: sys/chassis-[id]/blade-[slotId]/bios/fw-updatable
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fw-updatable
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/bios/fw-updatable
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fw-updatable
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fw-updatable
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fw-updatable
Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl/fw-updatable
Affected MO: sys/chassis-[id]/epmfpga-[slot]/fw-updatable
Affected MO: sys/chassis-[id]/fpga/fw-updatable
Affected MO: sys/chassis-[id]/rommon/fw-updatable
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fw-updatable
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fw-updatable
Affected MO: sys/fex-[id]/mgmt/fw-updatable
Affected MO: sys/fex-[id]/slot-[id]/mgmt/fw-updatable
Affected MO: sys/mgmt/fw-updatable
Affected MO: sys/os-ctrl/fw-updatable
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fw-updatable
Affected MO: sys/rack-unit-[id]/bios/fw-updatable
Affected MO: sys/rack-unit-[id]/boardController/mgmt/fw-updatable
Affected MO: sys/rack-unit-[id]/ext-board-[id]/bios/fw-updatable
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fw-updatable
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fw-updatable
Affected MO: sys/rack-unit-[id]/mgmt/fw-updatable
Affected MO: sys/rack-unit-[id]/os-ctrl/fw-updatable
Affected MO: sys/switch-[id]/mgmt/fw-updatable

fltFirmwareBootUnitCantBoot

Fault Code: F0471

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

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

Recommended Action: If you see this fault, take the following actions:

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

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

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

Fault Details 


Severity: major
Cause: image-cannot-boot
mibFaultCode: F0471
mibFaultName: fltFirmwareBootUnitCantBoot
moClass: firmware:BootUnit
Type: management
autoCleared: true
Affected MO: capabilities/ep/mgmt-ext/fw-boot-def/bootunit-[type]
Affected MO: capabilities/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/Ssd/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/bios/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/board/graphics-card-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/disk-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/bios/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/epmfpga-[slot]/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/fpga/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/rommon/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/fex-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/os-ctrl/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/bios/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/board/graphics-card-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/disk-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/bios/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/os-ctrl/fw-boot-def/bootunit-[type]
Affected MO: sys/switch-[id]/mgmt/fw-boot-def/bootunit-[type]

fltFcpoolInitiatorsEmpty

Fault Code: F0476

Message: FC pool [purpose] [name] is empty

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

Recommended Action: If you see this fault, take the following actions:

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

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

Fault Details 


Severity: minor
Cause: empty-pool
mibFaultCode: F0476
mibFaultName: fltFcpoolInitiatorsEmpty
moClass: fcpool:Initiators
Type: server
autoCleared: true
Affected MO: org-[name]/wwn-pool-[name]

fltEquipmentIOCardInaccessible

Fault Code: F0478

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

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

Recommended Action: If you see this fault, take the following actions:

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

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

Fault Details 


Severity: critical
Cause: equipment-inaccessible
mibFaultCode: F0478
mibFaultName: fltEquipmentIOCardInaccessible
moClass: equipment:IOCard
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]
Affected MO: sys/fex-[id]/slot-[id]

fltDcxVIfLinkState

Fault Code: F0479

Message: Virtual interface [id] link state is down

Explanation: This fault occurs when Cisco FPR cannot send or receive data through an uplink port.

Recommended Action: If you see this fault, take the following actions:

  1. Reenable the uplink port that failed.

  2. Check the associated port to ensure it is in up state.

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

Fault Details 


Severity: major
Cause: vif-down
mibFaultCode: F0479
mibFaultName: fltDcxVIfLinkState
moClass: dcx:VIf
Type: management
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/ext-eth-[id]/vif-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/fcoe/vif-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/vif-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]/fcoe/vif-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]/vif-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-service-eth-[id]/vif-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/ext-eth-[id]/vif-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/fcoe/vif-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/vif-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]/fcoe/vif-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]/vif-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-service-eth-[id]/vif-[id]

fltEquipmentFanModuleDegraded

Fault Code: F0480

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

Explanation: This fault occurs when a fan module is not operational.

Recommended Action: If you see this fault, take the following actions:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  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.

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

Fault Details 


Severity: minor
Cause: equipment-degraded
mibFaultCode: F0480
mibFaultName: fltEquipmentFanModuleDegraded
moClass: equipment:FanModule
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]

fltEquipmentIOCardPost-failure

Fault Code: F0481

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

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

Recommended Action: If you see this fault, take the following actions:

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

  2. If the POST results indicate FRU error, check if FPR manager has raised fault for the FRU and follow recommended action for the fault.

  3. Otherwise, reboot the I/O module.

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

Fault Details 


Severity: major
Cause: equipment-problem
mibFaultCode: F0481
mibFaultName: fltEquipmentIOCardPostFailure
moClass: equipment:IOCard
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]
Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentFanPerfThresholdLowerNonRecoverable

Fault Code: F0484

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

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

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

Fault Details 


Severity: critical
Cause: performance-problem
mibFaultCode: F0484
mibFaultName: fltEquipmentFanPerfThresholdLowerNonRecoverable
moClass: equipment:Fan
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/fan-[id]
Affected MO: sys/fex-[id]/fan-[id]
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/fan-[id]
Affected MO: sys/switch-[id]/fan-[id]
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/fan-[id]

fltComputePhysicalPost-failure

Fault Code: F0517

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

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

Recommended Action: If you see this fault, take the following actions:

  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.

  2. Reboot the server.

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

Fault Details 


Severity: major
Cause: equipment-problem
mibFaultCode: F0517
mibFaultName: fltComputePhysicalPostFailure
moClass: compute:Physical
Type: server
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

fltEquipmentPsuOffline

Fault Code: F0528

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

Explanation: This fault typically occurs when Cisco FPR Manager detects that a power supply unit in a chassis, fabric interconnect, or FEX is offline.

Recommended Action: If you see this fault, take the following actions:

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

  2. Verify that the power source is 220 volts.

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

  4. Remove the PSU and reinstall it.

  5. Replace the PSU.

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

Fault Details 


Severity: warning
Cause: equipment-offline
mibFaultCode: F0528
mibFaultName: fltEquipmentPsuOffline
moClass: equipment:Psu
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

fltStorageRaidBatteryInoperable

Fault Code: F0531

Message: RAID Battery on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]RAID Battery on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation: This fault occurs when the RAID backup unit is not operational.

Recommended Action: If you see this fault, take the following actions:

  1. If the backup unit is a battery, replace the battery.

  2. If the backup unit is a supercapacitor type and the supercapacitor is missing, verify its presence and supply if missing.

  3. If the backup unit is a supercapacitor type and the TFM is missing, verify its presence and supply if missing.

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

Fault Details 


Severity: major
Cause: equipment-inoperable
mibFaultCode: F0531
mibFaultName: fltStorageRaidBatteryInoperable
moClass: storage:RaidBattery
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/raid-battery
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/raid-battery

fltSysdebugMEpLogTransferError

Fault Code: F0532

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

Explanation: This fault occurs when the transfer of a managed endpoint log file, such as the SEL, fails.

Recommended Action: If you see this fault, take the following actions:

  1. If the fault is related to the SEL, verify the connectivity to the CIMC on the server.

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

Fault Details 


Severity: info
Cause: file-transfer-failed
mibFaultCode: F0532
mibFaultName: fltSysdebugMEpLogTransferError
moClass: sysdebug:MEpLog
Type: operational
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/log-[type]-[id]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/log-[type]-[id]
Affected MO: sys/fex-[id]/mgmt/log-[type]-[id]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/log-[type]-[id]
Affected MO: sys/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/log-[type]-[id]
Affected MO: sys/rack-unit-[id]/mgmt/log-[type]-[id]
Affected MO: sys/switch-[id]/mgmt/log-[type]-[id]

fltComputeRtcBatteryInoperable

Fault Code: F0533

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

Explanation: This fault is raised when the CMOS battery voltage is below the normal operating range. This impacts the system clock.

Recommended Action: If you see this fault, replace the CMOS battery.

Fault Details 


Severity: major
Cause: equipment-inoperable
mibFaultCode: F0533
mibFaultName: fltComputeRtcBatteryInoperable
moClass: compute:RtcBattery
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/rtc-battery
Affected MO: sys/rack-unit-[id]/board/rtc-battery

fltMemoryBufferUnitThermalThresholdNonCritical

Fault Code: F0535

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

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

  • Temperature extremes can cause Cisco 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:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  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.

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

Fault Details 


Severity: info
Cause: thermal-problem
mibFaultCode: F0535
mibFaultName: fltMemoryBufferUnitThermalThresholdNonCritical
moClass: memory:BufferUnit
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/sensor-unit-[id]
Affected MO: sys/rack-unit-[id]/board/sensor-unit-[id]

fltMemoryBufferUnitThermalThresholdCritical

Fault Code: F0536

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

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

  • Temperature extremes can cause Cisco 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:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  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.

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

Fault Details 


Severity: major
Cause: thermal-problem
mibFaultCode: F0536
mibFaultName: fltMemoryBufferUnitThermalThresholdCritical
moClass: memory:BufferUnit
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/sensor-unit-[id]
Affected MO: sys/rack-unit-[id]/board/sensor-unit-[id]

fltMemoryBufferUnitThermalThresholdNonRecoverable

Fault Code: F0537

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

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

  • Temperature extremes can cause Cisco 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:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  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.

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

Fault Details 


Severity: critical
Cause: thermal-problem
mibFaultCode: F0537
mibFaultName: fltMemoryBufferUnitThermalThresholdNonRecoverable
moClass: memory:BufferUnit
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/sensor-unit-[id]
Affected MO: sys/rack-unit-[id]/board/sensor-unit-[id]

fltComputeIOHubThermalNonCritical

Fault Code: F0538

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

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

Recommended Action: If you see this fault, monitor other environmental events related to this server and ensure the temperature ranges are within recommended ranges.

Fault Details 


Severity: minor
Cause: thermal-problem
mibFaultCode: F0538
mibFaultName: fltComputeIOHubThermalNonCritical
moClass: compute:IOHub
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/iohub
Affected MO: sys/rack-unit-[id]/board/iohub

fltComputeIOHubThermalThresholdCritical

Fault Code: F0539

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

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

Recommended Action: If you see this fault, take the following actions:

  1. Monitor other environmental events related to the server and ensure the temperature ranges are within recommended ranges.

  2. Consider turning off the server for a while if possible.

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

Fault Details 


Severity: major
Cause: thermal-problem
mibFaultCode: F0539
mibFaultName: fltComputeIOHubThermalThresholdCritical
moClass: compute:IOHub
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/iohub
Affected MO: sys/rack-unit-[id]/board/iohub

fltComputeIOHubThermalThresholdNonRecoverable

Fault Code: F0540

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

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

Recommended Action: If you see this fault, take the following actions:

  1. Shutdown the server immediately.

  2. Create a show tech-support file and contact Cisco TAC.

Fault Details 


Severity: critical
Cause: thermal-problem
mibFaultCode: F0540
mibFaultName: fltComputeIOHubThermalThresholdNonRecoverable
moClass: compute:IOHub
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/iohub
Affected MO: sys/rack-unit-[id]/board/iohub

fltEquipmentChassisIdentity-unestablishable

Fault Code: F0543

Message: Chassis [id] has an invalid FRU

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

Recommended Action: If you see this fault, take the following actions:

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

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

Fault Details 


Severity: major
Cause: identity-unestablishable
mibFaultCode: F0543
mibFaultName: fltEquipmentChassisIdentityUnestablishable
moClass: equipment:Chassis
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]

fltSwVlanPortNsResourceStatus

Fault Code: F0549

Message: Vlan-Port Resource exceeded

Explanation: This fault occurs when the total number of configured VLANs in the Cisco FPR instance has exceeded the allowed maximum number of configured VLANs on the fabric interconnect.

Recommended Action: If you see this fault, take the following actions:

  1. In the Cisco FPR Manager CLI or Cisco FPR Manager GUI, check the port VLAN count to determine by how many VLANs the system is over the maximum.

  2. Reduce the VLAN port count in one of the following ways:

    • Delete VLANs configured on the LAN cloud.

    • Delete VLANs configured on vNICs.

    • Unconfigure one or more vNICs.

    • Unconfigure one or more uplink Ethernet ports on the fabric interconnect.

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

Fault Details 


Severity: critical
Cause: limit-reached
mibFaultCode: F0549
mibFaultName: fltSwVlanPortNsResourceStatus
moClass: sw:VlanPortNs
Type: management
autoCleared: true
Affected MO: sys/switch-[id]/vlan-port-ns

fltFabricLanPinGroupEmpty

Fault Code: F0621

Message: LAN Pin Group [name] is empty

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

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

Fault Details 


Severity: minor
Cause: empty-pin-group
mibFaultCode: F0621
mibFaultName: fltFabricLanPinGroupEmpty
moClass: fabric:LanPinGroup
Type: server
autoCleared: true
Affected MO: fabric/lan/lan-pin-group-[name]

fltAdaptorExtEthIfMisConnect

Fault Code: F0625

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

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

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

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

Recommended Action: If you see this fault, take the following actions:

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

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

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

Fault Details 


Severity: warning
Cause: link-misconnected
mibFaultCode: F0625
mibFaultName: fltAdaptorExtEthIfMisConnect
moClass: adaptor:ExtEthIf
Type: network
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/ext-eth-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/ext-eth-[id]

fltAdaptorHostEthIfMisConnect

Fault Code: F0626

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

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

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

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

Recommended Action: If you see this fault, take the following actions:

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

  2. If connectivity seems correct, reacknowledge the server.

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

Fault Details 


Severity: warning
Cause: link-misconnected
mibFaultCode: F0626
mibFaultName: fltAdaptorHostEthIfMisConnect
moClass: adaptor:HostEthIf
Type: network
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]

fltPowerBudgetPowerBudgetCmcProblem

Fault Code: F0635

Message: Power cap application failed for chassis [id]

Explanation: This fault typically occurs when the server CIMC has failed to enforce the configured power cap.

Recommended Action: If you see this fault, take the following actions:

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

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

Fault Details 


Severity: major
Cause: power-cap-fail
mibFaultCode: F0635
mibFaultName: fltPowerBudgetPowerBudgetCmcProblem
moClass: power:Budget
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/budget
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/budget
Affected MO: sys/chassis-[id]/budget
Affected MO: sys/rack-unit-[id]/budget
Affected MO: sys/rack-unit-[id]/ext-board-[id]/budget

fltPowerBudgetPowerBudgetBmcProblem

Fault Code: F0637

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

Explanation: This fault typically occurs when the server CIMC or BIOS has failed to enforce the configured power cap.

Recommended Action: If you see this fault, take the following actions:

  1. Check the power consumption of the blade server. If the server is consuming significantly more power than configured in the power cap, switch to a manual per blade cap configuration. If the power consumption is still too high, consider reducing the group cap so that the power consumption of other chassis consumption can be reduced to make up for the increase.

  2. If the power consumption is still too high, the CIMC or BIOS software is likely faulty.

  3. Create a show tech-support file for Cisco FPR Manager and the chassis and then contact Cisco TAC.

Fault Details 


Severity: major
Cause: power-cap-fail
mibFaultCode: F0637
mibFaultName: fltPowerBudgetPowerBudgetBmcProblem
moClass: power:Budget
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/budget
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/budget
Affected MO: sys/chassis-[id]/budget
Affected MO: sys/rack-unit-[id]/budget
Affected MO: sys/rack-unit-[id]/ext-board-[id]/budget

fltPowerBudgetPowerBudgetDiscFail

Fault Code: F0640

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

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

Recommended Action: If you see this fault, take the following actions:

  1. Consider increasing the group cap.

  2. Reduce the number of blade servers or chassis in the Cisco FPR instance.

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

Fault Details 


Severity: major
Cause: power-cap-fail
mibFaultCode: F0640
mibFaultName: fltPowerBudgetPowerBudgetDiscFail
moClass: power:Budget
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/budget
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/budget
Affected MO: sys/chassis-[id]/budget
Affected MO: sys/rack-unit-[id]/budget
Affected MO: sys/rack-unit-[id]/ext-board-[id]/budget

fltPowerGroupPowerGroupInsufficientBudget

Fault Code: F0642

Message: insufficient budget for power group [name]

Explanation: This fault typically occurs when the group cap is insufficient to meet the minimum hardware requirements.

Recommended Action: If you see this fault, take the following actions:

  1. Consider increasing the group cap.

  2. Reduce the number of blade servers or chassis in the Cisco FPR instance.

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

Fault Details 


Severity: major
Cause: power-cap-fail
mibFaultCode: F0642
mibFaultName: fltPowerGroupPowerGroupInsufficientBudget
moClass: power:Group
Type: environmental
autoCleared: true
Affected MO: sys/power-ep/group-[name]

fltPowerGroupPowerGroupBudgetIncorrect

Fault Code: F0643

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

Explanation: This fault typically occurs when the group cap is insufficient to meet the minimum hardware requirements. Under these circumstances, Cisco FPR Manager uses the previously entered group cap for provisioning.

Recommended Action: If you see this fault, take the following actions:

  1. Consider increasing the group cap.

  2. Reduce the number of blade servers or chassis in the Cisco FPR instance.

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

Fault Details 


Severity: major
Cause: power-cap-fail
mibFaultCode: F0643
mibFaultName: fltPowerGroupPowerGroupBudgetIncorrect
moClass: power:Group
Type: environmental
autoCleared: true
Affected MO: sys/power-ep/group-[name]

fltMgmtIfMisConnect

Fault Code: F0688

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

Explanation: This fault occurs when the server and FEX connectivity changes.

Recommended Action: If you see this fault, take the following actions:

  1. Check the connectivity between the server and FEX.

  2. If the connectivity was changed by mistake, restore it to its previous configuration.

  3. If the connectivity change was intentional, reacknowledge the server.

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

Fault Details 


Severity: warning
Cause: link-misconnected
mibFaultCode: F0688
mibFaultName: fltMgmtIfMisConnect
moClass: mgmt:If
Type: operational
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]
Affected MO: sys/fex-[id]/mgmt/if-[id]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]
Affected MO: sys/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/mgmt/if-[id]
Affected MO: sys/switch-[id]/mgmt/if-[id]

fltLsComputeBindingAssignmentRequirementsNotMet

Fault Code: F0689

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

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

  • The selected server does not meet the requirements of the service profile.

  • If the service profile was configured for restricted migration, the selected server does not match the currently or previously assigned server.

Recommended Action: If you see this fault, select a different server that meets the requirements of the service profile or matches the currently or previously assigned server.

Fault Details 


Severity: minor
Cause: assignment-failed
mibFaultCode: F0689
mibFaultName: fltLsComputeBindingAssignmentRequirementsNotMet
moClass: ls:ComputeBinding
Type: server
autoCleared: true
Affected MO: org-[name]/ls-[name]/pn
Affected MO: org-[name]/ls-[name]/pn-req
Affected MO: org-[name]/tier-[name]/ls-[name]/pn
Affected MO: org-[name]/tier-[name]/ls-[name]/pn-req

fltEquipmentFexPost-failure

Fault Code: F0702

Message: fex [id] POST failure

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

Recommended Action: If you see this fault, take the following actions:

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

  2. Reboot the FEX.

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

Fault Details 


Severity: major
Cause: equipment-problem
mibFaultCode: F0702
mibFaultName: fltEquipmentFexPostFailure
moClass: equipment:Fex
Type: equipment
autoCleared: true
Affected MO: sys/fex-[id]

fltEquipmentFexIdentity

Fault Code: F0703

Message: Fex [id] has a malformed FRU

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

Recommended Action: If you see this fault, take the following actions:

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

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

Fault Details 


Severity: critical
Cause: fru-problem
mibFaultCode: F0703
mibFaultName: fltEquipmentFexIdentity
moClass: equipment:Fex
Type: equipment
autoCleared: true
Affected MO: sys/fex-[id]

fltAdaptorHostEthIfMissing

Fault Code: F0708

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

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

Recommended Action: If you see this fault, take the following actions:

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

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

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

Fault Details 


Severity: warning
Cause: link-missing
mibFaultCode: F0708
mibFaultName: fltAdaptorHostEthIfMissing
moClass: adaptor:HostEthIf
Type: network
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]

fltPortPIoInvalid-sfp

Fault Code: F0713

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

Explanation: This fault is raised against a fabric interconnect port, network-facing IOM port, or FEX module port if an unsupported transceiver type is inserted. The port cannot be used if it has an unsupported transceiver.

Recommended Action: If you see this fault, replace the transceiver with a supported SFP type. Refer to the documentation on the Cisco website for a list of supported SFPs.

Fault Details 


Severity: major
Cause: unsupported-transceiver
mibFaultCode: F0713
mibFaultName: fltPortPIoInvalidSfp
moClass: port:PIo
Type: network
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/chassis-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/chassis-[id]/sw-slot-[id]/[type]/port-[portId]
Affected MO: sys/fex-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/fex-[id]/slot-[id]/[type]/port-[portId]
Affected MO: sys/switch-[id]/slot-[id]/[type]/aggr-port-[aggrPortId]/port-[portId]
Affected MO: sys/switch-[id]/slot-[id]/[type]/port-[portId]

fltMgmtIfMissing

Fault Code: F0717

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

Explanation: This fault occurs when the connectivity between a server and FEX is removed or unconfigured.

Recommended Action: If you see this fault, take the following actions:

  1. Check the connectivity between the server and FEX.

  2. If the connectivity was changed by mistake, restore it to its previous configuration.

  3. If the connectivity change was intentional, reacknowledge the server.

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

Fault Details 


Severity: warning
Cause: link-missing
mibFaultCode: F0717
mibFaultName: fltMgmtIfMissing
moClass: mgmt:If
Type: operational
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]
Affected MO: sys/fex-[id]/mgmt/if-[id]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]
Affected MO: sys/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/mgmt/if-[id]
Affected MO: sys/switch-[id]/mgmt/if-[id]

fltFabricEthLanPcEpDown

Fault Code: F0727

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

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

Recommended Action: If you see this fault, take the following action:

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

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

Fault Details 


Severity: major
Cause: membership-down
mibFaultCode: F0727
mibFaultName: fltFabricEthLanPcEpDown
moClass: fabric:EthLanPcEp
Type: network
autoCleared: true
Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

fltEquipmentIOCardThermalThresholdNonCritical

Fault Code: F0729

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

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

  • Temperature extremes can cause Cisco 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:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  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.

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

Fault Details 


Severity: minor
Cause: thermal-problem
mibFaultCode: F0729
mibFaultName: fltEquipmentIOCardThermalThresholdNonCritical
moClass: equipment:IOCard
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]
Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentIOCardThermalThresholdCritical

Fault Code: F0730

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

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

  • Temperature extremes can cause Cisco 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:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  7. Replace the faulty I/O modules.

  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.

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

Fault Details 


Severity: major
Cause: thermal-problem
mibFaultCode: F0730
mibFaultName: fltEquipmentIOCardThermalThresholdCritical
moClass: equipment:IOCard
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]
Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentIOCardThermalThresholdNonRecoverable

Fault Code: F0731

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

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

  • Temperature extremes can cause Cisco 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:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  7. Replace the faulty I/O modules.

  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.

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

Fault Details 


Severity: critical
Cause: thermal-problem
mibFaultCode: F0731
mibFaultName: fltEquipmentIOCardThermalThresholdNonRecoverable
moClass: equipment:IOCard
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/slot-[id]
Affected MO: sys/fex-[id]/slot-[id]

fltEquipmentChassisSeeprom-inoperable

Fault Code: F0733

Message: Device [id] SEEPROM operability: [seepromOperState]

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

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

Fault Details 


Severity: critical
Cause: equipment-inoperable
mibFaultCode: F0733
mibFaultName: fltEquipmentChassisSeepromInoperable
moClass: equipment:Chassis
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]

fltExtmgmtIfMgmtifdown

Fault Code: F0736

Message: Management interface on Fabric Interconnect [id] is [operState]. Reason: [failureReason]

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

Recommended Action: If you see this fault, take the following actions:

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

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

  3. Check the default-gateway configuration for the external management interface.

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

Fault Details 


Severity: major
Cause: mgmtif-down
mibFaultCode: F0736
mibFaultName: fltExtmgmtIfMgmtifdown
moClass: extmgmt:If
Type: management
autoCleared: true
Affected MO: sys/switch-[id]/extmgmt-intf

fltPowerChassisMemberPowerGroupCapInsufficient

Fault Code: F0740

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

Explanation: This fault typically occurs when an updated group cap is insufficient to meet the minimum hardware requirements and a chassis that has just been added to the power group cannot be capped as a result.

Recommended Action: If you see this fault, take the following actions:

  1. Consider increasing the group cap.

  2. Reduce the number of blade servers or chassis in the Cisco FPR instance.

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

Fault Details 


Severity: major
Cause: group-cap-insufficient
mibFaultCode: F0740
mibFaultName: fltPowerChassisMemberPowerGroupCapInsufficient
moClass: power:ChassisMember
Type: environmental
autoCleared: true
Affected MO: sys/power-ep/group-[name]/ch-member-[id]

fltPowerChassisMemberChassisFirmwareProblem

Fault Code: F0741

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

Explanation: This fault typically occurs when the CIMC firmware on a server is an earlier release than Cisco FPR, Release 1.4.

Recommended Action: If you see this fault, consider upgrading the CIMC firmware, and the entire Cisco FPR instance if necessary, to Cisco FPR, Release 1.4 or later.

Fault Details 


Severity: major
Cause: old-chassis-component-firmware
mibFaultCode: F0741
mibFaultName: fltPowerChassisMemberChassisFirmwareProblem
moClass: power:ChassisMember
Type: environmental
autoCleared: true
Affected MO: sys/power-ep/group-[name]/ch-member-[id]

fltPowerChassisMemberChassisPsuInsufficient

Fault Code: F0742

Message: Chassis [id] cannot be capped as at least two PSU need to be powered

Explanation: This fault typically occurs when at least two PSUs are not powered on.

Recommended Action: If you see this fault, insert at least two PSUs and power them on.

Fault Details 


Severity: major
Cause: psu-insufficient
mibFaultCode: F0742
mibFaultName: fltPowerChassisMemberChassisPsuInsufficient
moClass: power:ChassisMember
Type: environmental
autoCleared: true
Affected MO: sys/power-ep/group-[name]/ch-member-[id]

fltPowerChassisMemberChassisPsuRedundanceFailure

Fault Code: F0743

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

Explanation: This fault typically occurs when chassis power redundancy has failed.

Recommended Action: If you see this fault, take the following actions:

  1. Consider adding more PSUs to the chassis.

  2. Replace any non-functional PSUs.

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

Fault Details 


Severity: major
Cause: psu-redundancy-fail
mibFaultCode: F0743
mibFaultName: fltPowerChassisMemberChassisPsuRedundanceFailure
moClass: power:ChassisMember
Type: environmental
autoCleared: true
Affected MO: sys/power-ep/group-[name]/ch-member-[id]

fltPowerBudgetPowerCapReachedCommit

Fault Code: F0744

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

Explanation: This fault typically occurs when Cisco FPR Manager is actively capping the power for a blade server.

Recommended Action: If you see this fault, no action is needed.

Fault Details 


Severity: info
Cause: power-consumption-hit-limit
mibFaultCode: F0744
mibFaultName: fltPowerBudgetPowerCapReachedCommit
moClass: power:Budget
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/budget
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/budget
Affected MO: sys/chassis-[id]/budget
Affected MO: sys/rack-unit-[id]/budget
Affected MO: sys/rack-unit-[id]/ext-board-[id]/budget

fltSysdebugAutoCoreFileExportTargetAutoCoreTransferFailure

Fault Code: F0747

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

Explanation: This fault occurs when Cisco Firepower Manager cannot transfer a core file to a remote TFTP server. This is typically the result of one of the following issues:

  • The remote TFTP server is not accessible.

  • One or more of the parameters for the TFTP server that are specified for the core export target, such as path, port, and server name, are incorrect.

Recommended Action: If you see this fault, take the following actions:

  1. Verify the connectivity to the remote server.

  2. Verify the path information of the remote server.

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

Fault Details 


Severity: warning
Cause: tftp-server-error
mibFaultCode: F0747
mibFaultName: fltSysdebugAutoCoreFileExportTargetAutoCoreTransferFailure
moClass: sysdebug:AutoCoreFileExportTarget
Type: sysdebug
autoCleared: true
Affected MO: sys/sysdebug/file-export

fltFabricMonSpanConfigFail

Fault Code: F0757

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

Explanation: This fault typically occurs when the configuration of a traffic monitoring session is incorrect.

Recommended Action: If you see this fault, correct the configuration problem provided in the fault description.

Fault Details 


Severity: major
Cause: config-error
mibFaultCode: F0757
mibFaultName: fltFabricMonSpanConfigFail
moClass: fabric:Mon
Type: network
autoCleared: true
Affected MO: fabric/lanmon/[id]/eth-mon-[name]

fltPowerBudgetChassisPsuInsufficient

Fault Code: F0764

Message: Chassis [id] cannot be capped as the available PSU power is not enough for the chassis and the blades. Please correct the problem by checking input power or replace the PSU

Explanation: This fault typically occurs when the available PSU power is not enough to deploy the power budget of chassis and blades.

Recommended Action: If you see this fault, check the PSU input power or replace the PSU.

Fault Details 


Severity: major
Cause: psu-insufficient
mibFaultCode: F0764
mibFaultName: fltPowerBudgetChassisPsuInsufficient
moClass: power:Budget
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/budget
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/budget
Affected MO: sys/chassis-[id]/budget
Affected MO: sys/rack-unit-[id]/budget
Affected MO: sys/rack-unit-[id]/ext-board-[id]/budget

fltPowerBudgetTStateTransition

Fault Code: F0765

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

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

Recommended Action: If you see this fault, take the following actions:

  1. Redeploy the power budget for the affected power group, blade server, or chassis.

  2. If the problem persists, reboot the blade server.

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

Fault Details 


Severity: critical
Cause: no-ack-from-bios
mibFaultCode: F0765
mibFaultName: fltPowerBudgetTStateTransition
moClass: power:Budget
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/budget
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/budget
Affected MO: sys/chassis-[id]/budget
Affected MO: sys/rack-unit-[id]/budget
Affected MO: sys/rack-unit-[id]/ext-board-[id]/budget

fltPowerPolicyPowerPolicyApplicationFail

Fault Code: F0766

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

Explanation: This fault occurs when a power policy cannot be applied to one or more blade servers. The affected blade servers cannot operate normally without power capping due to the limited power budget for those servers.

Recommended Action: If you see this fault, take the following actions:

  1. Increase the power budget for the blade servers in the power policy.

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

Fault Details 


Severity: minor
Cause: no-cap-fail
mibFaultCode: F0766
mibFaultName: fltPowerPolicyPowerPolicyApplicationFail
moClass: power:Policy
Type: environmental
autoCleared: true
Affected MO: org-[name]/power-policy-[name]

fltMgmtIfNew

Fault Code: F0772

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

Explanation: This fault occurs when the connectivity between a server and a FEX is added or changed.

Recommended Action: If you see this fault, take the following actions:

  1. Check the connectivity between the server and FEX.

  2. If the connectivity was changed by mistake, restore it to its previous configuration.

  3. If the connectivity change was intentional, reacknowledge the server.

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

Fault Details 


Severity: warning
Cause: new-link
mibFaultCode: F0772
mibFaultName: fltMgmtIfNew
moClass: mgmt:If
Type: operational
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/if-[id]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/if-[id]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/if-[id]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/if-[id]
Affected MO: sys/fex-[id]/mgmt/if-[id]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/if-[id]
Affected MO: sys/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/if-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/if-[id]
Affected MO: sys/rack-unit-[id]/mgmt/if-[id]
Affected MO: sys/switch-[id]/mgmt/if-[id]

fltAdaptorExtEthIfMissing

Fault Code: F0775

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

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

Recommended Action: If you see this fault, take the following actions:

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

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

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

Fault Details 


Severity: warning
Cause: link-missing
mibFaultCode: F0775
mibFaultName: fltAdaptorExtEthIfMissing
moClass: adaptor:ExtEthIf
Type: network
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/ext-eth-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/ext-eth-[id]

fltStorageLocalDiskSlotEpUnusable

Fault Code: F0776

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

Explanation: This fault occurs when the server disk drive is in a slot that is not supported by the storage controller.

Recommended Action: If you see this fault, take the following actions:

  1. Insert the server disk drive in a supported slot.

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

Fault Details 


Severity: minor
Cause: equipment-inoperable
mibFaultCode: F0776
mibFaultName: fltStorageLocalDiskSlotEpUnusable
moClass: storage:LocalDiskSlotEp
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/disk-[id]
Affected MO: sys/rack-unit-[id]/board/disk-[id]

fltFabricEthEstcPcEpDown

Fault Code: F0777

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

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

Recommended Action: If you see this fault, take the following action:

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

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

Fault Details 


Severity: major
Cause: membership-down
mibFaultCode: F0777
mibFaultName: fltFabricEthEstcPcEpDown
moClass: fabric:EthEstcPcEp
Type: network
autoCleared: true
Affected MO: fabric/eth-estc/[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

fltEquipmentFexIdentity-unestablishable

Fault Code: F0778

Message: Fex [id] has an invalid FRU

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

Recommended Action: If you see this fault, take the following actions:

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

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

Fault Details 


Severity: major
Cause: identity-unestablishable
mibFaultCode: F0778
mibFaultName: fltEquipmentFexIdentityUnestablishable
moClass: equipment:Fex
Type: equipment
autoCleared: true
Affected MO: sys/fex-[id]

fltEquipmentFanModuleInoperable

Fault Code: F0794

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

Explanation: This fault occurs if a fan module is not operational.

Recommended Action: If you see this fault, take the following actions:

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

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

Fault Details 


Severity: major
Cause: equipment-inoperable
mibFaultCode: F0794
mibFaultName: fltEquipmentFanModuleInoperable
moClass: equipment:FanModule
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]

fltLsmaintMaintPolicyUnresolvableScheduler

Fault Code: F0795

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

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

  • The schedule does not exist.

  • The schedule was deleted.

Recommended Action: If you see this fault, take the following actions:

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

  2. If the named schedule is deleted or missing, recreate it.

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

Fault Details 


Severity: warning
Cause: non-existent-scheduler
mibFaultCode: F0795
mibFaultName: fltLsmaintMaintPolicyUnresolvableScheduler
moClass: lsmaint:MaintPolicy
Type: server
autoCleared: true
Affected MO: org-[name]/maint-[name]

fltProcessorUnitIdentity-unestablishable

Fault Code: F0801

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

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

Recommended Action: If you see this fault, take the following actions:

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

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

Fault Details 


Severity: warning
Cause: identity-unestablishable
mibFaultCode: F0801
mibFaultName: fltProcessorUnitIdentityUnestablishable
moClass: processor:Unit
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]
Affected MO: sys/rack-unit-[id]/board/cpu-[id]

fltIqnpoolPoolEmpty

Fault Code: F0821

Message: iqn pool [name] is empty

Explanation: This fault typically occurs when an IQN pool does not contain any IQNs.

Recommended Action: If you see this fault, take the following actions:

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

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

Fault Details 


Severity: minor
Cause: empty-pool
mibFaultCode: F0821
mibFaultName: fltIqnpoolPoolEmpty
moClass: iqnpool:Pool
Type: server
autoCleared: true
Affected MO: org-[name]/iqn-pool-[name]

fltFabricDceSwSrvPcEpDown

Fault Code: F0831

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

Explanation: This fault typically occurs when a member port in a fabric port channel is down.

Recommended Action: If you see this fault, take the following action:

  1. Check the link connectivity between the FEX or IOM and the fabric interconnect.

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

Fault Details 


Severity: major
Cause: membership-down
mibFaultCode: F0831
mibFaultName: fltFabricDceSwSrvPcEpDown
moClass: fabric:DceSwSrvPcEp
Type: network
autoCleared: true
Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]

fltFabricEpMgrEpTransModeFail

Fault Code: F0832

Message: Port constraint violation on switch [id]: [confQual]

Explanation: This fault occurs when at least one logical interface is misconfigured. This can happen when upgrading to a different type or series of fabric interconnect or when importing a configuration. The configuration must meet the following constraints:

  • There must be at most one logical port per fabric interconnect ID/module ID/port ID.

Recommended Action: If you see this fault, take the following action:

  1. Create a list of all logical interfaces that are misconfigured and have caused an 'error-misconfigured' fault.

  2. For each logical interface, note the reason listed in the fault for the misconfiguration.

  3. Log into Cisco FPR Manager and correct each misconfigured logical interface. If you used the Cisco FPR Manager CLI, commit all changes.

  4. Review any faults or error messages that describe additional misconfigurations and correct those errors.

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

Fault Details 


Severity: critical
Cause: config-error
mibFaultCode: F0832
mibFaultName: fltFabricEpMgrEpTransModeFail
moClass: fabric:EpMgr
Type: network
autoCleared: true
Affected MO: fabric/[id]

fltFabricPIoEpErrorMisconfigured

Fault Code: F0834

Message: Interface [name] is [operState]. Reason: [operStateReason]

Explanation: This fault occurs when a logical interface is misconfigured. This can happen when upgrading to a different type or series of fabric interconnect or when importing a configuration.

Recommended Action: If you see this fault, take the following action:

  1. Create a list of all logical interfaces that are misconfigured and have caused an 'error-misconfigured' fault.

  2. For each logical interface, note the reason listed in the fault for the misconfiguration.

  3. Log into Cisco FPR Manager and correct each misconfigured logical interface. If you used the Cisco FPR Manager CLI, commit all changes.

  4. Review any faults or error messages that describe additional misconfigurations and correct those errors.

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

Fault Details 


Severity: critical
Cause: interface-misconfigured
mibFaultCode: F0834
mibFaultName: fltFabricPIoEpErrorMisconfigured
moClass: fabric:PIoEp
Type: network
autoCleared: true
Affected MO: fabric/eth-estc/[id]/net-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/pc-[portId]/eth-target-ep-[name]
Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]
Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/phys-eth-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]
Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]
Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/net-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/net-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/net-group-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/net-group-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/net-group-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]
Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]
Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]
Affected MO: fabric/lan/net-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/net-group-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/net-group-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/net-group-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/lanmon/[id]/eth-mon-[name]/dest-slot-[slotId]-port-[portId]
Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]
Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]
Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]
Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]
Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]
Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]/fcoesanpcep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/net-[name]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/net-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/phys-fcoesanep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]
Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]
Affected MO: fabric/san/net-[name]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/san/net-[name]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/san/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoe-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/san/net-[name]/sw-[switchId]-slot-[slotId]-aggr-port-[aggrPortId]/phys-switch-[switchId]-slot-[slotId]-port-[portId]
Affected MO: fabric/server/chassis-[chassisId]
Affected MO: fabric/server/chassis-[chassisId]/slot-[slotId]
Affected MO: fabric/server/chassis-ep-ven-[vendor]-mod[model]-ser-[serial]
Affected MO: fabric/server/compute-ep-ven-[vendor]-mod-[model]-ser-[serial]
Affected MO: fabric/server/sw-[id]/pc-[portId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]
Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/dest-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/ep-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/fcoesanpcep-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-eth-slot-[slotId]-port-[portId]/eth-target-ep-[name]
Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-fcoesanep-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/slot-[slotId]-port-[portId]
Affected MO: sys/switch-[id]/access-eth/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]
Affected MO: sys/switch-[id]/border-eth/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]
Affected MO: sys/switch-[id]/border-eth/pc-[portId]/eth-target-[name]
Affected MO: sys/switch-[id]/border-eth/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]
Affected MO: sys/switch-[id]/border-fc/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]
Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/pc-[portId]/eth-target-[name]
Affected MO: sys/switch-[id]/lanmon-eth/mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]
Affected MO: sys/switch-[id]/phys/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]
Affected MO: sys/switch-[id]/ssp-lanmon-eth/ssp-mon-session[name]/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]
Affected MO: sys/tbh/border-eth/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]
Affected MO: sys/tbh/border-eth/pc-[portId]/eth-target-[name]
Affected MO: sys/tbh/border-eth/slot-[slotId]-aggr-port-[aggrPortId]/ethestc-ep-slot-[slotId]port-[portId]/eth-target-[name]

fltFabricEthLanEpMissingPrimaryVlan

Fault Code: F0835

Message: Primary vlan missing from fabric: [switchId], port: [slotId]/[aggrPortId]/[portId].Primary vlan missing from fabric: [switchId], port: [slotId]/[portId].

Explanation: This fault occurs when an uplink port or port channel is configured with a primary VLAN that does not exist in the Cisco FPR instance.

Recommended Action: If you see this fault, take the following action:

  1. Update the configuration of the port or port channel to include a primary VLAN.

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

Fault Details 


Severity: major
Cause: missing-primary-vlan
mibFaultCode: F0835
mibFaultName: fltFabricEthLanEpMissingPrimaryVlan
moClass: fabric:EthLanEp
Type: management
autoCleared: true
Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

fltFabricEthLanPcMissingPrimaryVlan

Fault Code: F0836

Message: Primary vlan missing from fabric: [switchId], port-channel: [portId].

Explanation: This fault occurs when an uplink port or port channel is configured with a primary VLAN that does not exist in the Cisco FPR instance.

Recommended Action: If you see this fault, take the following action:

  1. Update the configuration of the port or port channel to include a primary VLAN.

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

Fault Details 


Severity: major
Cause: missing-primary-vlan
mibFaultCode: F0836
mibFaultName: fltFabricEthLanPcMissingPrimaryVlan
moClass: fabric:EthLanPc
Type: management
autoCleared: true
Affected MO: fabric/lan/[id]/pc-[portId]

fltVnicEtherPinningMismatch

Fault Code: F0840

Message: Hard pinning target for eth vNIC [name], service profile [name] does not have all the required vlans configured

Explanation: This fault occurs when one or more VLANs required by vNIC in a service profile are not configured on the target uplink port or port channel for a hard-pinned LAN pin group.

Recommended Action: If you see this fault, take the following actions:

  1. In the LAN Uplinks Manager of the Cisco FPR Manager GUI, configure all of the VLANs in the vNIC in the target uplink port or port channel for the LAN pin group. If you prefer to use the Cisco FPR Manager CLI, navigate to scope /eth-uplink/vlan and create the required member ports for the LAN pin group.

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

Fault Details 


Severity: warning
Cause: pinning-mismatch
mibFaultCode: F0840
mibFaultName: fltVnicEtherPinningMismatch
moClass: vnic:Ether
Type: configuration
autoCleared: true
Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]
Affected MO: org-[name]/ls-[name]/ether-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]

fltVnicEtherPinningMisconfig

Fault Code: F0841

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

Explanation: This fault occurs when one or more vNIC target uplink ports or port channels for a hard-pinned LAN pin group are either missing or misconfigured as the wrong port type.

Recommended Action: If you see this fault, take the following actions:

  1. Review the LAN pin group configuration.

  2. Correct the configuration of the port and port channels in the pin group.

  3. Ensure that all required vLANs are allowed on the target ports or port channels.

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

Fault Details 


Severity: major
Cause: pinning-misconfig
mibFaultCode: F0841
mibFaultName: fltVnicEtherPinningMisconfig
moClass: vnic:Ether
Type: configuration
autoCleared: true
Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]
Affected MO: org-[name]/ls-[name]/ether-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]

fltProcessorUnitDisabled

Fault Code: F0842

Message: Processor [id] on server [chassisId]/[slotId] operState: [operState]Processor [id] on server [id] operState: [operState]

Explanation: This fault occurs in the unlikely event that a processor is disabled.

Recommended Action: If you see this fault, take the following actions:

  1. If this fault occurs on a blade server, remove and reinsert the server into the chassis.

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

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

Fault Details 


Severity: major
Cause: equipment-disabled
mibFaultCode: F0842
mibFaultName: fltProcessorUnitDisabled
moClass: processor:Unit
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/cpu-[id]
Affected MO: sys/rack-unit-[id]/board/cpu-[id]

fltMemoryUnitDisabled

Fault Code: F0844

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

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

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

Fault Details 


Severity: major
Cause: equipment-disabled
mibFaultCode: F0844
mibFaultName: fltMemoryUnitDisabled
moClass: memory:Unit
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/memarray-[id]/mem-[id]
Affected MO: sys/rack-unit-[id]/board/memarray-[id]/mem-[id]

fltFirmwareBootUnitActivateStatusFailed

Fault Code: F0856

Message: Activation failed and Activate Status set to failed.

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

  • Firmware activation failed.

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

Recommended Action: If you see this fault, take the following actions:

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

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

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

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

Fault Details 


Severity: major
Cause: activation-failed
mibFaultCode: F0856
mibFaultName: fltFirmwareBootUnitActivateStatusFailed
moClass: firmware:BootUnit
Type: management
autoCleared: true
Affected MO: capabilities/ep/mgmt-ext/fw-boot-def/bootunit-[type]
Affected MO: capabilities/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/Ssd/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-eth-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/host-fc-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/bios/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/board/graphics-card-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/disk-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/bios/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/os-ctrl/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/epmfpga-[slot]/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/fpga/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/rommon/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/fex-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/os-ctrl/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-eth-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/host-fc-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/bios/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/board/graphics-card-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/disk-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/bios/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/mgmt/fw-boot-def/bootunit-[type]
Affected MO: sys/rack-unit-[id]/os-ctrl/fw-boot-def/bootunit-[type]
Affected MO: sys/switch-[id]/mgmt/fw-boot-def/bootunit-[type]

fltFabricInternalPcDown

Fault Code: F0858

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

Explanation: This fault occurs when the transport VIF for a server is down. Cisco FPR Manager raises this fault when a fabric interconnect reports the connectivity state on virtual interface as one of the following:

  • Down

  • Errored

  • Unavailable

Recommended Action: If you see this fault, take the following actions:

  1. Verify that the blade server discovery was successful.

  2. Check the states on all communicating ports from end to end.

  3. If connectivity seems correct, decommission and recommission the server.

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

Fault Details 


Severity: major
Cause: operational-state-down
mibFaultCode: F0858
mibFaultName: fltFabricInternalPcDown
moClass: fabric:InternalPc
Type: network
autoCleared: true
Affected MO: fabric/server/sw-[id]/pc-[portId]

fltMgmtEntityDevice-1-shared-storage-error

Fault Code: F0863

Message: device [chassis1], error accessing shared-storage

Explanation: This fault occurs in an unlikely event that the shared storage selected for writing the cluster state is not accessible. This fault is typically a transient fault. You might see this fault when one of the following occurs: (a) the Fabric Interconnect boots, (b) the IO Module is reset, (c) the rack server is reboot, or (d) system is upgraded/downgraded. If this fault is not cleared after the system returns to normal operation following the reboot/reset/upgrade/downgrade, then it may affect the full HA functionality of the Fabric Interconnect cluster.

Recommended Action: If this fault is not cleared even after the system returns to normal operation, create a show tech-support file and contact Cisco TAC.

Fault Details 


Severity: warning
Cause: device-shared-storage-error
mibFaultCode: F0863
mibFaultName: fltMgmtEntityDevice1SharedStorageError
moClass: mgmt:Entity
Type: management
autoCleared: true
Affected MO: sys/mgmt-entity-[id]

fltMgmtEntityDevice-2-shared-storage error

Fault Code: F0864

Message: device [chassis2], error accessing shared-storage

Explanation: This fault occurs in an unlikely event that the shared storage selected for writing the cluster state is not accessible. This fault is typically a transient fault. You might see this fault when one of the following occurs: (a) the Fabric Interconnect boots, (b) the IO Module is reset, (c) the rack server is reboot, or (d) system is upgraded/downgraded. If this fault is not cleared after the system returns to normal operation following the reboot/reset/upgrade/downgrade, then it may affect the full HA functionality of the Fabric Interconnect cluster.

Recommended Action: If this fault is not cleared even after the system returns to normal operation, create a show tech-support file and contact Cisco TAC.

Fault Details 


Severity: warning
Cause: device-shared-storage-error
mibFaultCode: F0864
mibFaultName: fltMgmtEntityDevice2SharedStorageError
moClass: mgmt:Entity
Type: management
autoCleared: true
Affected MO: sys/mgmt-entity-[id]

fltMgmtEntityDevice-3-shared-storage error

Fault Code: F0865

Message: device [chassis3], error accessing shared-storage

Explanation: This fault occurs in an unlikely event that the shared storage selected for writing the cluster state is not accessible. This fault is typically a transient fault. You might see this fault when one of the following occurs: (a) the Fabric Interconnect boots, (b) the IO Module is reset, (c) the rack server is reboot, or (d) system is upgraded/downgraded. If this fault is not cleared after the system returns to normal operation following the reboot/reset/upgrade/downgrade, then it may affect the full HA functionality of the Fabric Interconnect cluster.

Recommended Action: If this fault is not cleared even after the system returns to normal operation, create a show tech-support file and contact Cisco TAC.

Fault Details 


Severity: warning
Cause: device-shared-storage-error
mibFaultCode: F0865
mibFaultName: fltMgmtEntityDevice3SharedStorageError
moClass: mgmt:Entity
Type: management
autoCleared: true
Affected MO: sys/mgmt-entity-[id]

fltMgmtEntityHa-ssh-keys-mismatched

Fault Code: F0866

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

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

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

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

Recommended Action: If you see this fault, take the following actions:

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

  2. Enter connect local-mgmt

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

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

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

Fault Details 


Severity: major
Cause: ha-ssh-keys-mismatched
mibFaultCode: F0866
mibFaultName: fltMgmtEntityHaSshKeysMismatched
moClass: mgmt:Entity
Type: management
autoCleared: true
Affected MO: sys/mgmt-entity-[id]

fltComputeBoardPowerFail

Fault Code: F0868

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

Explanation: This fault typically occurs when the power sensors on a blade server detect a problem.

Recommended Action: If you see this fault, take the following actions:

  1. Remove the blade server from the chassis.

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

Fault Details 


Severity: critical
Cause: power-problem
mibFaultCode: F0868
mibFaultName: fltComputeBoardPowerFail
moClass: compute:Board
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board
Affected MO: sys/rack-unit-[id]/board

fltVmVifLinkState

Fault Code: F0876

Message: Virtual interface [vifId] link is down; reason [stateQual]

Explanation: This fault occurs when Cisco FPR cannot send or receive data through an uplink port.

Recommended Action: If you see this fault, take the following actions:

  1. Enable the failed uplink port.

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

Fault Details 


Severity: minor
Cause: vif-down
mibFaultCode: F0876
mibFaultName: fltVmVifLinkState
moClass: vm:Vif
Type: management
autoCleared: true
Affected MO: vmm/computeEp-[uuid]/nic-[name]/sw-[phSwitchId]vif-[vifId]
Affected MO: vmm/hv-[uuid]/nic-[name]/sw-[phSwitchId]vif-[vifId]
Affected MO: vmm/vm-[uuid]/nic-[name]/sw-[phSwitchId]vif-[vifId]

fltEquipmentPsuPowerSupplyShutdown

Fault Code: F0881

Message: Power supply [id] in chassis [id] shutdown reason:[powerStateQualifier]

Explanation: This fault typically occurs when a power supply unit in a chassis, fabric interconnect, or a FEX is shut down, either due to higher than expected power current, higher than expected temperatures, or the failure of a fan.

Recommended Action: If you see this fault, take the following actions:

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

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

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

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

  5. Power off unused blade servers and rack servers.

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

  7. Verify that the power source is 220 volts.

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

  9. Remove the PSU and reinstall it.

  10. Replace the PSU.

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

Fault Details 


Severity: major
Cause: equipment-offline
mibFaultCode: F0881
mibFaultName: fltEquipmentPsuPowerSupplyShutdown
moClass: equipment:Psu
Type: environmental
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentPsuPowerThreshold

Fault Code: F0882

Message: Power supply [id] on chassis [id] has exceeded its power thresholdPower supply [id] on server [id] has exceeded its power threshold

Explanation: This fault occurs when a power supply unit is drawing too much current.

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

Fault Details 


Severity: critical
Cause: power-problem
mibFaultCode: F0882
mibFaultName: fltEquipmentPsuPowerThreshold
moClass: equipment:Psu
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

fltEquipmentPsuInputError

Fault Code: F0883

Message: Power supply [id] on chassis [id] has disconnected cable or bad input voltagePower supply [id] on server [id] has disconnected cable or bad input voltage

Explanation: This fault occurs when a power cable is disconnected or input voltage is incorrect.

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

Fault Details 


Severity: critical
Cause: power-problem
mibFaultCode: F0883
mibFaultName: fltEquipmentPsuInputError
moClass: equipment:Psu
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/psu-[id]
Affected MO: sys/fex-[id]/psu-[id]
Affected MO: sys/rack-unit-[id]/psu-[id]
Affected MO: sys/switch-[id]/psu-[id]

fltNetworkElementInventoryFailed

Fault Code: F0885

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

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

Recommended Action: If you see this fault, take the following actions:

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

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

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

Fault Details 


Severity: major
Cause: inventory-failed
mibFaultCode: F0885
mibFaultName: fltNetworkElementInventoryFailed
moClass: network:Element
Type: equipment
autoCleared: true
Affected MO: sys/switch-[id]

fltAdaptorUnitExtnUnidentifiable-fru

Fault Code: F0900

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

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

Recommended Action: If you see this fault, take the following actions:

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

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

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

Fault Details 


Severity: major
Cause: unidentifiable-fru
mibFaultCode: F0900
mibFaultName: fltAdaptorUnitExtnUnidentifiableFru
moClass: adaptor:UnitExtn
Type: server
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/adaptor-extn-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/adaptor-extn-[id]

fltAdaptorUnitExtnMissing

Fault Code: F0901

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

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

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

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

Recommended Action: If you see this fault, take the following actions:

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

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

Fault Details 


Severity: warning
Cause: equipment-missing
mibFaultCode: F0901
mibFaultName: fltAdaptorUnitExtnMissing
moClass: adaptor:UnitExtn
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/adaptor-extn-[id]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/adaptor-extn-[id]

fltEquipmentFexFex-unsupported

Fault Code: F0902

Message: Fex [id] with model [model] is unsupported

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

Recommended Action: If you see this fault, take the following actions:

  1. Verify that a supported FEX is installed.

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

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

Fault Details 


Severity: major
Cause: fex-unsupported
mibFaultCode: F0902
mibFaultName: fltEquipmentFexFexUnsupported
moClass: equipment:Fex
Type: equipment
autoCleared: true
Affected MO: sys/fex-[id]

fltVnicIScsiConfig-failed

Fault Code: F0903

Message: iSCSI vNIC [name], service profile [name] has duplicate iqn name [initiatorName]

Explanation: This fault typically occurs when IScsi Vnics refer the same iqn name.

Recommended Action: If you see this fault, take the following actions:

  1. Make sure that iqn name unique per iSCSI vnic.

  2. Using show identity iqn check if the iSCSI vnic is registered in the universe.

  3. Try non disruptive actions such as changing description on the Service Profile to register the iqn in the universe.

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

Fault Details 


Severity: major
Cause: configuration-failed
mibFaultCode: F0903
mibFaultName: fltVnicIScsiConfigFailed
moClass: vnic:IScsi
Type: configuration
autoCleared: true
Affected MO: org-[name]/ls-[name]/iscsi-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]/iscsi-[name]

fltPkiKeyRingStatus

Fault Code: F0909

Message: [name] Keyring's certificate is invalid, reason: [certStatus].

Explanation: This fault occurs when certificate status of Keyring has become invalid.

Recommended Action: None set.

Fault Details 


Severity: major
Cause: invalid-keyring-certificate
mibFaultCode: F0909
mibFaultName: fltPkiKeyRingStatus
moClass: pki:KeyRing
Type: security
autoCleared: true
Affected MO: sys/pki-ext/keyring-[name]

fltPkiTPStatus

Fault Code: F0910

Message: [name] Trustpoint's cert-chain is invalid, reason: [certStatus].

Explanation: This fault occurs when certificate status of TrustPoint has become invalid.

Recommended Action: None set.

Fault Details 


Severity: major
Cause: invalid-trustpoint-cert-chain
mibFaultCode: F0910
mibFaultName: fltPkiTPStatus
moClass: pki:TP
Type: security
autoCleared: true
Affected MO: sys/pki-ext/tp-[name]

fltComputePhysicalDisassociationFailed

Fault Code: F0915

Message: Failed to disassociate server [id]Failed to disassociate server [chassisId]/[slotId]

Explanation: This fault typically occurs for one of the following reasons:

  • 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:

  1. Check the communication path to the server including fabric interconnect server ports, IOM link and the current state of the server

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

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

Fault Details 


Severity: major
Cause: disassociation-failed
mibFaultCode: F0915
mibFaultName: fltComputePhysicalDisassociationFailed
moClass: compute:Physical
Type: configuration
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

fltComputePhysicalNetworkMisconfigured

Fault Code: F0916

Message: Server [id] (service profile: [assignedToDn]) has mis-configured network vif resourcesServer [chassisId]/[slotId] (service profile: [assignedToDn]) has mis-configured network vif resources

Explanation: This fault would occur when FPRM VIF-id Map is not the same as the VIF-id map deployed on the adaptor upon Full Backup->Restore etc.

Recommended Action: If you see this fault, take the following actions:

  1. Re-acknowledge the server. This will trigger Deep Discovery->Deep Association & will resolve the issue

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

Fault Details 


Severity: minor
Cause: vif-ids-mismatch
mibFaultCode: F0916
mibFaultName: fltComputePhysicalNetworkMisconfigured
moClass: compute:Physical
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]
Affected MO: sys/rack-unit-[id]

fltVnicProfileProfileConfigIncorrect

Fault Code: F0917

Message: The Port Profile [name] has an invalid configuration.

Explanation: This fault occurs there is an invalid entry for a port profile configuration.

Recommended Action: Check documentation and correct the offending entry in the port profile configuration.

Fault Details 


Severity: warning
Cause: profile-config-incorrect
mibFaultCode: F0917
mibFaultName: fltVnicProfileProfileConfigIncorrect
moClass: vnic:Profile
Type: configuration
autoCleared: true
Affected MO: fabric/lan/profiles/vnic-[name]

fltVnicEtherIfVlanAccessFault

Fault Code: F0932

Message: The named vlan [name] for vNIC [name] cannot be accessed from org [name]

Explanation: This fault typically occurs when a Service Profile's vnic interface (LAN) is resolvable but the service profile does not have access to the vlan. In this case, the default vlan will be used.

Recommended Action: This fault will be removed if you perform one of the following actions:

  1. Change the vnic's interface name to a VLAN that you have access to.

  2. If you wish to use the default vlan, change the vnic's interface name to default.

  3. Configure access to the named vlan by creating a vlan permit or vlan group permit in the service profile's org (or a parent org).

Fault Details 


Severity: major
Cause: inaccessible-vlan-referenced
mibFaultCode: F0932
mibFaultName: fltVnicEtherIfVlanAccessFault
moClass: vnic:EtherIf
Type: configuration
autoCleared: true
Affected MO: fabric/lan/network-sets/fabric-network-[name]/fabric-network-def-[name]/vm-network-def-[name]/if-[name]
Affected MO: fabric/lan/profiles/vnic-[name]/if-[name]
Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]/if-[name]
Affected MO: org-[name]/lan-conn-templ-[name]/if-[name]
Affected MO: org-[name]/ls-[name]/ether-[name]/if-[name]
Affected MO: org-[name]/ls-[name]/if-[name]
Affected MO: org-[name]/ls-[name]/ipc-[name]/if-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]/if-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]/if-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]/ipc-[name]/if-[name]

fltVnicEtherIfVlanUnresolvable

Fault Code: F0933

Message: The named vlan [name] for vNIC [name] cannot be resolved

Explanation: This fault (warning) occurs when a Service Profile's vnic interface (LAN) is unresolvable. In this case, the default vlan will be used as the operational vlan.

Recommended Action: This fault will be removed if you perform one of the following actions:

  1. Change the vnic interface name to an existing VLAN.

  2. Create the named vlan .

Fault Details 


Severity: warning
Cause: referenced-vlan-unresolvable
mibFaultCode: F0933
mibFaultName: fltVnicEtherIfVlanUnresolvable
moClass: vnic:EtherIf
Type: configuration
autoCleared: true
Affected MO: fabric/lan/network-sets/fabric-network-[name]/fabric-network-def-[name]/vm-network-def-[name]/if-[name]
Affected MO: fabric/lan/profiles/vnic-[name]/if-[name]
Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]/if-[name]
Affected MO: org-[name]/lan-conn-templ-[name]/if-[name]
Affected MO: org-[name]/ls-[name]/ether-[name]/if-[name]
Affected MO: org-[name]/ls-[name]/if-[name]
Affected MO: org-[name]/ls-[name]/ipc-[name]/if-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]/if-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]/if-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]/ipc-[name]/if-[name]

fltVnicEtherIfInvalidVlan

Fault Code: F0934

Message: Invalid Vlan in the allowed vlan list

Explanation: This fault typically occurs when a vnic of a service profile or a port profile contains an invalid vlan. an invalid vlan can be any one of the following:

  1. an isolated vlan or a community vlan that is not associated to a valid primary vlan

  2. a primary vlan without any of its assoicated secondary vlans allowed on the vnic

  3. a vlan which has sharing-type or primary vlan name not matching to that of vlan in lan-side/appliance-side

Recommended Action: This fault will be removed if you perform one of the following actions:

  1. if invalid vlan is an isolated or community vlan then make sure it is mapped to a valid primary vlan.

  2. if invalid vlan is a primary vlan then either allow any of its secondary vlans or delete it from vnic or port profile.

  3. if invalid vlan is a vlan that does not match the sharing properties with the vlan of same vlan id in the lan-side/appliance-side, change the properties of this vlan to be the same as the other.

Fault Details 


Severity: major
Cause: invalid-vlan-in-the-allowed-vlan-list
mibFaultCode: F0934
mibFaultName: fltVnicEtherIfInvalidVlan
moClass: vnic:EtherIf
Type: configuration
autoCleared: true
Affected MO: fabric/lan/network-sets/fabric-network-[name]/fabric-network-def-[name]/vm-network-def-[name]/if-[name]
Affected MO: fabric/lan/profiles/vnic-[name]/if-[name]
Affected MO: org-[name]/lan-conn-pol-[name]/ether-[name]/if-[name]
Affected MO: org-[name]/lan-conn-templ-[name]/if-[name]
Affected MO: org-[name]/ls-[name]/ether-[name]/if-[name]
Affected MO: org-[name]/ls-[name]/if-[name]
Affected MO: org-[name]/ls-[name]/ipc-[name]/if-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]/ether-[name]/if-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]/if-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]/ipc-[name]/if-[name]

fltFabricVlanVlanConflictPermit

Fault Code: F0935

Message: There are multiple vlans with id [id] have different accessability configured.

Explanation: This fault occurs when multipl global vlans with the same id have different access configurations.

Recommended Action: Change the access configuration by configuring VLAN/VLAN Group Permits.

Fault Details 


Severity: warning
Cause: vlan-conflict-permit
mibFaultCode: F0935
mibFaultName: fltFabricVlanVlanConflictPermit
moClass: fabric:Vlan
Type: configuration
autoCleared: true
Affected MO: fabric/eth-estc/[id]/net-[name]
Affected MO: fabric/eth-estc/net-[name]
Affected MO: fabric/lan/[id]/net-[name]
Affected MO: fabric/lan/net-[name]

fltFabricVlanReqVlanPermitUnresolved

Fault Code: F0936

Message: The VLAN permit does not reference any existing vlans.

Explanation: This fault occurs when a VLAN permit exists but there are no vnics by the name.

Recommended Action: Delete the VLAN permit, create the referenced VLAN (or ignore).

Fault Details 


Severity: warning
Cause: vlan-permit-unresolved
mibFaultCode: F0936
mibFaultName: fltFabricVlanReqVlanPermitUnresolved
moClass: fabric:VlanReq
Type: configuration
autoCleared: true
Affected MO: org-[name]/vlan-req-[name]

fltFabricVlanGroupReqVlanGroupPermitUnresolved

Fault Code: F0937

Message: The VLAN permit does not reference any existing net groups.

Explanation: This fault occurs when a VLAN group permit exists but there are no referenced network groups.

Recommended Action: Delete the VLAN permit, create the referenced VLAN (or ignore).

Fault Details 


Severity: warning
Cause: group-permit-unresolved
mibFaultCode: F0937
mibFaultName: fltFabricVlanGroupReqVlanGroupPermitUnresolved
moClass: fabric:VlanGroupReq
Type: configuration
autoCleared: true
Affected MO: org-[name]/vlan-group-req-[name]

fltExtpolClientClientLostConnectivity

Fault Code: F0988

Message: FPRM has lost connectivity with Firepower Central

Explanation: None set.

Recommended Action: None set.

Fault Details 


Severity: major
Cause: client-lost-connectivity
mibFaultCode: F0988
mibFaultName: fltExtpolClientClientLostConnectivity
moClass: extpol:Client
Type: network
autoCleared: true
Affected MO: extpol/reg/clients/client-[id]

fltStorageLocalDiskDegraded

Fault Code: F0996

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 degraded. The fault description will contain the physical drive state, which indicates the reason for the degradation.

Recommended Action: If you see this fault, take the following actions:

  1. If the drive state is "rebuild" or "copyback", wait for the rebuild or copyback operation to complete.

  2. If the drive state is "predictive-failure", replace the disk.

Fault Details 


Severity: warning
Cause: equipment-degraded
mibFaultCode: F0996
mibFaultName: fltStorageLocalDiskDegraded
moClass: storage:LocalDisk
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/disk-[id]
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/disk-[id]

fltStorageRaidBatteryDegraded

Fault Code: F0997

Message: RAID Battery on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]RAID Battery on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation: This fault occurs when the RAID backup unit is degraded.

Recommended Action: If you see this fault, take the following actions:

  1. If the fault reason indicates the backup unit is in a relearning cycle, wait for relearning to complete.

  2. If the fault reason indicates the backup unit is about to fail, replace the backup unit.

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

Fault Details 


Severity: minor
Cause: equipment-degraded
mibFaultCode: F0997
mibFaultName: fltStorageRaidBatteryDegraded
moClass: storage:RaidBattery
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/raid-battery
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/raid-battery

fltStorageRaidBatteryRelearnAborted

Fault Code: F0998

Message: RAID Battery on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]RAID Battery on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation: NOTE: This fault is not currently implemented by Firepower ManagerThis fault is present only as a placeholder, possibly for another release,such as stand-alone rack servers.--- This fault occurs when the backup unit's relearning cycle was aborted.

Recommended Action: If you see this fault, take the following actions:

  1. Retry the learn cycle.

  2. Replace the backup unit.

Fault Details 


Severity: minor
Cause: equipment-degraded
mibFaultCode: F0998
mibFaultName: fltStorageRaidBatteryRelearnAborted
moClass: storage:RaidBattery
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/raid-battery
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/raid-battery

fltStorageRaidBatteryRelearnFailed

Fault Code: F0999

Message: RAID Battery on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]RAID Battery on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation: NOTE: This fault is not currently implemented by Firepower ManagerThis fault is present only as a placeholder, possibly for another release,such as stand-alone rack servers.--- This fault occurs when the backup unit's relearning cycle has failed.

Recommended Action: If you see this fault, take the following actions:

  1. Retry the learn cycle.

  2. Replace the backup unit.

Fault Details 


Severity: major
Cause: equipment-degraded
mibFaultCode: F0999
mibFaultName: fltStorageRaidBatteryRelearnFailed
moClass: storage:RaidBattery
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/raid-battery
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/raid-battery

fltStorageInitiatorConfiguration-error

Fault Code: F1001

Message: Initiator [name] either cannot be resolved or does not match with one of the storage targets. No zones are deployed for this initiator and the target.

Explanation: Initiator either cannot be resolved or does not match with one of the targets.

Recommended Action: If you see this fault, take the following action:

  1. Check if vhba interface referenced by this Initiator exsits.

  2. Check if switch id or vsan name of the vhba interface referenced by this Initiator matches one of the targets.

Fault Details 


Severity: warning
Cause: configuration-error
mibFaultCode: F1001
mibFaultName: fltStorageInitiatorConfigurationError
moClass: storage:Initiator
Type: equipment
autoCleared: true
Affected MO: org-[name]/ls-[name]/grp-[name]/ini-[name]
Affected MO: org-[name]/san-conn-pol-[name]/grp-[name]/ini-[name]
Affected MO: org-[name]/tier-[name]/ls-[name]/grp-[name]/ini-[name]

fltStorageControllerPatrolReadFailed

Fault Code: F1003

Message: Controller [id] on server [chassisId]/[slotId] had a patrol read failure. Reason: [operQualifierReason]Controller [id] on server [id] had a patrol read failure. Reason: [operQualifierReason]

Explanation: NOTE: This fault is not currently implemented by Firepower ManagerThis fault is present only as a placeholder, possibly for another release,such as stand-alone rack servers.--- This fault occurs when a Patrol Read operation has failed.

Recommended Action: Re-run the patrol read operation.

Fault Details 


Severity: warning
Cause: operation-failed
mibFaultCode: F1003
mibFaultName: fltStorageControllerPatrolReadFailed
moClass: storage:Controller
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]

fltStorageControllerInoperable

Fault Code: F1004

Message: Controller [id] on server [chassisId]/[slotId] is inoperable. Reason: [operQualifierReason]Controller [id] on server [id] is inoperable. Reason: [operQualifierReason]

Explanation: This fault occurs when the storage controller is inaccessible.

Recommended Action: For PCI and mezz-based storage controllers, check the seating of the storage controller. If the problem persists, replace the controller.

Fault Details 


Severity: critical
Cause: equipment-inoperable
mibFaultCode: F1004
mibFaultName: fltStorageControllerInoperable
moClass: storage:Controller
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]

fltStorageLocalDiskRebuildFailed

Fault Code: F1005

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

Explanation: NOTE: This fault is not currently implemented by Firepower ManagerThis fault is present only as a placeholder, possibly for another release,such as stand-alone rack servers.--- This fault occurs when a rebuild operation has failed. This may cause a degradation in performance.

Recommended Action: If you see this fault, take the following action:

  1. Retry the rebuild operation.

  2. Replace the disk.

Fault Details 


Severity: major
Cause: equipment-offline
mibFaultCode: F1005
mibFaultName: fltStorageLocalDiskRebuildFailed
moClass: storage:LocalDisk
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/disk-[id]
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/disk-[id]

fltStorageLocalDiskCopybackFailed

Fault Code: F1006

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

Explanation: NOTE: This fault is not currently implemented by Firepower ManagerThis fault is present only as a placeholder, possibly for another release,such as stand-alone rack servers.--- This fault occurs when a copyback operation has failed. This may cause a degradation in performance.

Recommended Action: If you see this fault, take the following action:

  1. Retry the copyback operation.

  2. Replace the disk.

Fault Details 


Severity: major
Cause: equipment-offline
mibFaultCode: F1006
mibFaultName: fltStorageLocalDiskCopybackFailed
moClass: storage:LocalDisk
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/disk-[id]
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/disk-[id]

fltStorageVirtualDriveInoperable

Fault Code: F1007

Message: Virtual drive [id] on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]Virtual drive [id] on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation: This fault occurs when the virtual drive has become inoperable.

Recommended Action: If you see this fault, take the following actions:

  1. Verify the presence and health of disks that are used by the virtual drive.

  2. If applicable, reseat or replace used disks.

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

Fault Details 


Severity: critical
Cause: equipment-inoperable
mibFaultCode: F1007
mibFaultName: fltStorageVirtualDriveInoperable
moClass: storage:VirtualDrive
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/vd-[id]
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/vd-[id]

fltStorageVirtualDriveDegraded

Fault Code: F1008

Message: Virtual drive [id] on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]Virtual drive [id] on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation: This fault occurs when the virtual drive has become degraded. The fault description will contain the physical drive state, which indicates the reason for the degradation.

Recommended Action: If you see this fault, take the following actions:

  1. If the drive is performing a consistency check operation, wait for the operation to complete.

  2. Verify the presence and health of disks that are used by the virtual drive.

  3. If applicable, reseat or replace used disks.

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

Fault Details 


Severity: major
Cause: equipment-degraded
mibFaultCode: F1008
mibFaultName: fltStorageVirtualDriveDegraded
moClass: storage:VirtualDrive
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/vd-[id]
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/vd-[id]

fltStorageVirtualDriveReconstructionFailed

Fault Code: F1009

Message: Virtual drive [id] on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]Virtual drive [id] on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation: NOTE: This fault is not currently implemented by Firepower ManagerThis fault is present only as a placeholder, possibly for another release,such as stand-alone rack servers.--- This fault occurs when a drive reconstruction operation has failed. This may cause a degradation in performance.

Recommended Action: If you see this fault, take the following action:

  1. Retry the reconstruction operation.

  2. Delete and recreate the virtual drive.

Fault Details 


Severity: major
Cause: equipment-degraded
mibFaultCode: F1009
mibFaultName: fltStorageVirtualDriveReconstructionFailed
moClass: storage:VirtualDrive
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/vd-[id]
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/vd-[id]

fltStorageVirtualDriveConsistencyCheckFailed

Fault Code: F1010

Message: Virtual drive [id] on server [chassisId]/[slotId] operability: [operability]. Reason: [operQualifierReason]Virtual drive [id] on server [id] operability: [operability]. Reason: [operQualifierReason]

Explanation: NOTE: This fault is not currently implemented by Firepower ManagerThis fault is present only as a placeholder, possibly for another release,such as stand-alone rack servers.--- This fault occurs when a drive consistency check operation has failed. This may cause a degradation in performance.

Recommended Action: If you see this fault, take the following action:

  1. Retry the consistency check operation.

  2. Delete and recreate the virtual drive.

Fault Details 


Severity: major
Cause: equipment-degraded
mibFaultCode: F1010
mibFaultName: fltStorageVirtualDriveConsistencyCheckFailed
moClass: storage:VirtualDrive
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/board/storage-[type]-[id]/vd-[id]
Affected MO: sys/rack-unit-[id]/board/storage-[type]-[id]/vd-[id]

fltAaaProviderGroupProvidergroup

Fault Code: F1026

Message: For [dn]: Server Group with name [name] already exist, You need to specify a unique name for this object.

Explanation: This fault typically occurs because Cisco FPR Manager has detected multiple provider-groups with same name.

Recommended Action: If you see this fault, take the following actions:

  1. Need to delete the duplicate provider group configured causing this problem.

Fault Details 


Severity: major
Cause: provider-group-already-exists
mibFaultCode: F1026
mibFaultName: fltAaaProviderGroupProvidergroup
moClass: aaa:ProviderGroup
Type: security
autoCleared: true
Affected MO: sys/ldap-ext/providergroup-[name]
Affected MO: sys/radius-ext/providergroup-[name]
Affected MO: sys/tacacs-ext/providergroup-[name]

fltAaaConfigServergroup

Fault Code: F1027

Message: For [dn]: [realm] Server Group with name [providerGroup] doesn't exist or is not deployed.

Explanation: This fault typically occurs because Cisco FPR Manager has detected an unsupported authentication method.

Recommended Action: If you see this fault, take the following actions:

  1. Verify that server group configured for authentication is present.

  2. If the server group is not configured, create the server group to use for authentication.

Fault Details 


Severity: critical
Cause: invalid-server-group
mibFaultCode: F1027
mibFaultName: fltAaaConfigServergroup
moClass: aaa:Config
Type: security
autoCleared: true
Affected MO: sys/auth-realm/console-auth
Affected MO: sys/auth-realm/default-auth
Affected MO: sys/auth-realm/domain-[name]/domain-auth

fltAaaRoleRoleNotDeployed

Fault Code: F1028

Message: Role [name] can't be deployed. Error: [configStatusMessage]

Explanation: This fault typically occurs because Cisco FPR Manager has detected an unsupported role.

Recommended Action: If you see this fault, take the following actions:

  1. Verify that total number of roles is less than maximum supported roles.

  2. Verify that sum of privileges across all roles is less than maximum privileges sum.

Fault Details 


Severity: critical
Cause: role-config-error
mibFaultCode: F1028
mibFaultName: fltAaaRoleRoleNotDeployed
moClass: aaa:Role
Type: security
autoCleared: true
Affected MO: sys/user-ext/role-[name]

fltAaaLocaleLocaleNotDeployed

Fault Code: F1029

Message: Locale [name] can't be deployed. Error: [configStatusMessage]

Explanation: This fault typically occurs because Cisco FPR Manager has detected an unsupported locale.

Recommended Action: If you see this fault, take the following actions:

  1. Verify that total number of locale is less than maximum supported roles.

Fault Details 


Severity: critical
Cause: locale-config-error
mibFaultCode: F1029
mibFaultName: fltAaaLocaleLocaleNotDeployed
moClass: aaa:Locale
Type: security
autoCleared: true
Affected MO: sys/user-ext/locale-[name]

fltAaaUserRoleUserRoleNotDeployed

Fault Code: F1030

Message: For user: [name] role [name] can't be assigned. Error: [configStatusMessage].For Ldap Group: [name] role [name] can't be assigned. Error: [configStatusMessage].

Explanation: This fault typically occurs because Cisco FPR Manager has detected an unsupported user role for ldap groups or local users.

Recommended Action: If you see this fault, take the following actions:

  1. Verify that the role is present .

  2. Verify that the role is applied .

  3. Verify that the role is compatible with locales assigned to ldap group or local user .

Fault Details 


Severity: critical
Cause: user-role-config-error
mibFaultCode: F1030
mibFaultName: fltAaaUserRoleUserRoleNotDeployed
moClass: aaa:UserRole
Type: security
autoCleared: true
Affected MO: sys/ldap-ext/ldapgroup-[name]/role-[name]
Affected MO: sys/user-ext/remoteuser-[name]/role-[name]
Affected MO: sys/user-ext/user-[name]/role-[name]

fltAaaUserLocaleUserLocaleNotDeployed

Fault Code: F1031

Message: For user: [name] locale [name] can't be assigned. Error: [configStatusMessage].For Ldap Group: [name] locale [name] can't be assigned. Error: [configStatusMessage].

Explanation: This fault typically occurs because Cisco FPR Manager has detected an unsupported user locale for ldap groups or local users.

Recommended Action: If you see this fault, take the following actions:

  1. Verify that the locale is present .

  2. Verify that the locale is applied .

  3. Verify that the locale is compatible with roles assigned to ldap group or local user .

Fault Details 


Severity: critical
Cause: user-locale-config-error
mibFaultCode: F1031
mibFaultName: fltAaaUserLocaleUserLocaleNotDeployed
moClass: aaa:UserLocale
Type: security
autoCleared: true
Affected MO: sys/ldap-ext/ldapgroup-[name]/locale-[name]
Affected MO: sys/user-ext/remoteuser-[name]/locale-[name]
Affected MO: sys/user-ext/user-[name]/locale-[name]

fltPkiKeyRingKeyRingNotDeployed

Fault Code: F1032

Message: Keyring [name] can't be deployed. Error: [configStatusMessage]

Explanation: This fault typically occurs because Cisco FPR Manager has detected an invalid Keyring.

Recommended Action: If you see this fault, take the following actions:

  1. Verify that the trust point configured for this keyring is present .

  2. Verify that the trust point found above is applied .

Fault Details 


Severity: critical
Cause: keyring-config-error
mibFaultCode: F1032
mibFaultName: fltPkiKeyRingKeyRingNotDeployed
moClass: pki:KeyRing
Type: security
autoCleared: true
Affected MO: sys/pki-ext/keyring-[name]

fltCommSnmpSyscontactEmpty

Fault Code: F1033

Message: FPR Manager cannot deploy an empty value of SNMP Syscontact when Callhome is enabled. The previous value [sysContact] for SNMP Syscontact has been retained.

Explanation: This fault typically occurs when FPR Manager receives an invalid configuration from FPR Central wherein SNMP Syscontact is set to empty when Callhome is enabled.

Recommended Action: If you see this fault, please ensure that the SNMP Syscontact field on FPR Central is configured correctly for the domain group corresponding to this FPRM.

Fault Details 


Severity: warning
Cause: snmp-config-error
mibFaultCode: F1033
mibFaultName: fltCommSnmpSyscontactEmpty
moClass: comm:Snmp
Type: configuration
autoCleared: true
Affected MO: sys/svc-ext/snmp-svc

fltCommDateTimeCommTimeZoneInvalid

Fault Code: F1034

Message: Timezone:[timezone] is invalid

Explanation: This fault typically occurs because Cisco FPR Manager has detected an unsupported role.

Recommended Action: If you see this fault, take the following actions:

  1. Verify that total number of roles is less than maximum supported roles.

  2. Verify that sum of privileges across all roles is less than maximum privileges sum.

Fault Details 


Severity: minor
Cause: timezone-file-not-exists
mibFaultCode: F1034
mibFaultName: fltCommDateTimeCommTimeZoneInvalid
moClass: comm:DateTime
Type: configuration
autoCleared: true
Affected MO: sys/svc-ext/datetime-svc

fltAaaUserLocalUserNotDeployed

Fault Code: F1035

Message: Local User [name] can't be deployed. Error: [configStatusMessage]

Explanation: This fault typically occurs because Cisco FPR Manager has detected an invalid system user.

Recommended Action: If you see this fault, take the following actions:

  1. Verify that local user name is not used by snmp users.

Fault Details 


Severity: major
Cause: user-config-error
mibFaultCode: F1035
mibFaultName: fltAaaUserLocalUserNotDeployed
moClass: aaa:User
Type: security
autoCleared: true
Affected MO: sys/user-ext/user-[name]

fltCommSnmpUserSnmpUserNotDeployed

Fault Code: F1036

Message: SNMP User [name] can't be deployed. Error: [configStatusMessage]

Explanation: This fault typically occurs because Cisco FPR Manager has detected an invalid snmp user.

Recommended Action: If you see this fault, take the following actions:

  1. Verify that snmp user name is not used by system users.

Fault Details 


Severity: major
Cause: snmp-user-config-error
mibFaultCode: F1036
mibFaultName: fltCommSnmpUserSnmpUserNotDeployed
moClass: comm:SnmpUser
Type: configuration
autoCleared: true
Affected MO: sys/svc-ext/snmp-svc/snmpv3-user-[name]

fltCommSvcEpCommSvcNotDeployed

Fault Code: F1037

Message: Communication Service configuration can't be deployed. Error: [configStatusMessage]

Explanation: This fault typically occurs because Cisco FPR Manager has detected an invalid communication policy confiuration.

Recommended Action: If you see this fault, take the following actions:

  1. Verify that ports configured across all communication services is unique.

Fault Details 


Severity: major
Cause: comm-svc-config-error
mibFaultCode: F1037
mibFaultName: fltCommSvcEpCommSvcNotDeployed
moClass: comm:SvcEp
Type: configuration
autoCleared: true
Affected MO: sys/svc-ext

fltSwVlanPortNsVLANCompNotSupport

Fault Code: F1056

Message: VLAN Port Count Optimization is not supported

Explanation: None set.

Recommended Action: None set.

Fault Details 


Severity: critical
Cause: no-vlan-optimization
mibFaultCode: F1056
mibFaultName: fltSwVlanPortNsVLANCompNotSupport
moClass: sw:VlanPortNs
Type: network
autoCleared: true
Affected MO: sys/switch-[id]/vlan-port-ns

fltPolicyControlEpSuspendModeActive

Fault Code: F1057

Message: FPRM is suspended from receiving updates from FPR Central.

Explanation: This fault occurs when FPRM enters into suspend state from receiving updates from FPR Central that it is registered with.

Recommended Action: If you see this fault, take the following actions:

  1. Please check if FPR Central is restored to a previous version or a policy roll-back has occured. You may have brought FPR in to manual suspension mode by using set suspendstate on command under the system->control-ep policy scope.

  2. Please confirm the suspend state by using show control-ep policy detail under system scope. If you still want to receive the updates from FPR Central, you need to restore it back to a version compatible with FPRM or set the suspend state to off by acknowledging it by using set ackstate acked under policy-control scope.

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

Fault Details 


Severity: warning
Cause: suspend-mode-entered
mibFaultCode: F1057
mibFaultName: fltPolicyControlEpSuspendModeActive
moClass: policy:ControlEp
Type: management
autoCleared: true
Affected MO: sys/control-ep-[type]

fltNetworkElementThermalThresholdCritical

Fault Code: F1080

Message: Fabric Interconnect [id] temperature: [thermal]

Explanation: This fault occurs when the temperature of a Fabric Interconnect 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.

  • 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:

  1. Review the product specifications to determine the temperature operating range of the Fabric Interconnect.

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

  3. Verify that the air flows are not obstructed.

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

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

  6. Replace faulty Fabric Interconnects.

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

Fault Details 


Severity: major
Cause: thermal-problem
mibFaultCode: F1080
mibFaultName: fltNetworkElementThermalThresholdCritical
moClass: network:Element
Type: environmental
autoCleared: true
Affected MO: sys/switch-[id]

fltFabricPinTargetDown

Fault Code: F1088

Message: Pin target is a non-existent interface

Explanation: This fault typically occurs when a PinGroup has an unresolvable target.

Recommended Action: If you see this fault, take the following action:

  1. Check whether the PinGroup target is correctly provisioned.

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

Fault Details 


Severity: warning
Cause: invalid-target
mibFaultCode: F1088
mibFaultName: fltFabricPinTargetDown
moClass: fabric:PinTarget
Type: network
autoCleared: true
Affected MO: fabric/lan/lan-pin-group-[name]/target-[fabricId]
Affected MO: fabric/san/san-pin-group-[name]/target-[fabricId]

fltFabricEthLanEpOverlapping-vlan

Fault Code: F1090

Message: On Fabric: [switchId], Port: [slotId]/[aggrPortId]/[portId] following overlapping VLANs detected: [overlappingVlans]On Fabric: [switchId], Port: [slotId]/[portId] following overlapping VLANs detected: [overlappingVlans]

Explanation: This fault occurs when Overlapping Vlans occur due to mis configuration.

Recommended Action: Ports configured on Vlans belonging to a group should not intersect with other ports of different network group belonging to Vlans which overlap .

Fault Details 


Severity: info
Cause: configuration-error
mibFaultCode: F1090
mibFaultName: fltFabricEthLanEpOverlappingVlan
moClass: fabric:EthLanEp
Type: network
autoCleared: true
Affected MO: fabric/eth-estc/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/eth-estc/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/lan/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/lanmon/[id]/eth-mon-[name]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/fcoesanpc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/san/[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/pc-[portId]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]
Affected MO: fabric/server/sw-[id]/slot-[slotId]-aggr-port-[aggrPortId]/phys-slot-[slotId]-port-[portId]

fltFabricEthLanPcOverlapping-vlan

Fault Code: F1091

Message: Overlapping VLANs detected on Fabric: [switchId], Port: [portId] in configured VLANs: [overlappingVlans]

Explanation: This fault occurs when Overlapping Vlans occur due to mis configuration.

Recommended Action: Ports configured on Vlans belonging to a group should not intersect with other ports of different network group belonging to Vlans which overlap .

Fault Details 


Severity: info
Cause: configuration-error
mibFaultCode: F1091
mibFaultName: fltFabricEthLanPcOverlappingVlan
moClass: fabric:EthLanPc
Type: network
autoCleared: true
Affected MO: fabric/lan/[id]/pc-[portId]

fltFabricVlanMisconfigured-mcast-policy

Fault Code: F1095

Message: VLAN [name] multicast policy [mcastPolicyName] is non-default.

Explanation: This fault is raised when VLAN belonging to a Springfield fabric has a non-default multicast policy assigned to it.

Recommended Action: If you see this fault, take the following action:

  1. Un-assign multicast policy for the this vlan or change the multicast policy to default.

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

Fault Details 


Severity: major
Cause: vlan-mcast-policy-misconfigured
mibFaultCode: F1095
mibFaultName: fltFabricVlanMisconfiguredMcastPolicy
moClass: fabric:Vlan
Type: network
autoCleared: true
Affected MO: fabric/eth-estc/[id]/net-[name]
Affected MO: fabric/eth-estc/net-[name]
Affected MO: fabric/lan/[id]/net-[name]
Affected MO: fabric/lan/net-[name]

fltMgmtConnectionDisabled

Fault Code: F1097

Message: Management Connection [type] in server [id] is not operational

Explanation: This fault occurs when multiple management connections are acknowledegd.

Recommended Action: If you see this fault, take the following actions:

  1. Disable the management connection which is unused.

  2. If new management connection needs to be used, decommission and recommission server.

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

Fault Details 


Severity: warning
Cause: another-connection-already-enabled
mibFaultCode: F1097
mibFaultName: fltMgmtConnectionDisabled
moClass: mgmt:Connection
Type: operational
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/fex-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/switch-[id]/mgmt/mgmt-connection-[type]

fltMgmtConnectionUnused

Fault Code: F1098

Message: Management Connection [type] in server [id] is unused

Explanation: This fault occurs when a management connection is not enabel

Recommended Action: If you see this fault, you can enable the connection if none of the management connections are enabled. Else this can be ignored

Fault Details 


Severity: info
Cause: connection-unused
mibFaultCode: F1098
mibFaultName: fltMgmtConnectionUnused
moClass: mgmt:Connection
Type: operational
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/fex-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/switch-[id]/mgmt/mgmt-connection-[type]

fltMgmtConnectionUnsupportedConnectivity

Fault Code: F1099

Message: Unsupported connectivity for management connection [type] in server [id]

Explanation: This fault typically occurs because Cisco FPR Manager has detected that the physical connectivity of the management port of the server is unsupported.

Recommended Action: If you see this fault, take the following actions:

  1. Connect the management port/s of the rack mount server to the Fabric Extender/s

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

Fault Details 


Severity: minor
Cause: unsupported-connectivity
mibFaultCode: F1099
mibFaultName: fltMgmtConnectionUnsupportedConnectivity
moClass: mgmt:Connection
Type: operational
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/adaptor-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/boardController/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/boardController/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/blade-[slotId]/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/slot-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/chassis-[id]/sw-slot-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/fex-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/fex-[id]/slot-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/adaptor-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/boardController/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/boardController/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/ext-board-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/rack-unit-[id]/mgmt/mgmt-connection-[type]
Affected MO: sys/switch-[id]/mgmt/mgmt-connection-[type]

fltCallhomeEpNoSnmpPolicyForCallhome

Fault Code: F1102

Message: FPR Manager cannot apply Callhome policy if SNMP Policy is not configured or if SNMP Syscontact has an empty value. The Callhome policy from FPR Central has not been applied.

Explanation: This fault typically occurs when FPR Manager receives an invalid configuration from FPR Central wherein Callhome is configured on FPR Central but there is no SNMP Syscontact defined locally.

Recommended Action: If you see this fault, please ensure that the SNMP Policy is configured on FPRM Manager, either locally or via FPR Central.

Fault Details 


Severity: minor
Cause: callhome-config-error
mibFaultCode: F1102
mibFaultName: fltCallhomeEpNoSnmpPolicyForCallhome
moClass: callhome:Ep
Type: configuration
autoCleared: true
Affected MO: call-home

fltCapabilityCatalogueLoadErrors

Fault Code: F1103

Message: Load errors: File parse errors: [fileParseFailures], provider load failures: [providerLoadFailures], XML element load errors: [loadErrors].

Explanation: The capability catalog failed to load fully. This may be caused by either a faulty FPRM image or a faulty catalog image.

Recommended Action: If you see this fault, take the following actions:

  1. Check the version of the capability catalog.

  2. Contact Cisco TAC to see if there are known issues with the catalog and if there is a catalog image that will fix the known issues.

Fault Details 


Severity: major
Cause: load-catalog-failed
mibFaultCode: F1103
mibFaultName: fltCapabilityCatalogueLoadErrors
moClass: capability:Catalogue
Type: management
autoCleared: true
Affected MO: capabilities

fltExtmgmtArpTargetsArpTargetsNotValid

Fault Code: F1114

Message: Invalid ARP Targets configured for Management Interface Polling. Error: [configStatusMessage]

Explanation: This fault typically occurs because Cisco FPR Manager has detected an invalid ArpTargets Configuration.

Recommended Action: If you see this fault, take the following actions:

  1. Verify that Arp target ip address and external management ip address are in the same subnet.

  2. Verify that Arp target ip address is not the same as ip address of this system's fabric-interconnects.

  3. Verify that Arp target ip address is not the same as virtual IP Address.

Fault Details 


Severity: major
Cause: arp-targets-config-error
mibFaultCode: F1114
mibFaultName: fltExtmgmtArpTargetsArpTargetsNotValid
moClass: extmgmt:ArpTargets
Type: management
autoCleared: true
Affected MO: sys/extmgmt-intf-monitor-policy/arp-target-policy

fltExtpolClientGracePeriodWarning

Fault Code: F1211

Message: FPR domain [name] registered with FPR Central has entered into the grace period.

Explanation: A FPR domain is registered with FPR Central without having a license. This fault typically occurs if this FPR domain is registered with FPR Central after all default (and procured) licenses are assigned to other FPR domains.

Recommended Action: If you see this fault, take the following actions:

  1. Check the number of licenses installed and consumed on FPR Central. In the Cisco FPR Central GUI, you can access the licensing information from the Operations Management tab for the FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under license scope from service-reg session.

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

Fault Details 


Severity: warning
Cause: license-graceperiod-entered
mibFaultCode: F1211
mibFaultName: fltExtpolClientGracePeriodWarning
moClass: extpol:Client
Type: management
autoCleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning2

Fault Code: F1212

Message: FPR Domain [name] registered with FPR Central is running in the grace period for more than 10 days

Explanation: This FPR domain is registered with FPR Central without having a license. This fault typically occurs if this FPR domain is registered with FPR Central after all default (and procured) licenses are assigned to other FPR domains.

Recommended Action: If you see this fault, take the following actions:

  1. Check the number of licenses installed and consumed on FPR Central. In the Cisco FPR Central GUI, you can access the licensing information from the Operations Management tab for the FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

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

Fault Details 


Severity: warning
Cause: license-graceperiod-10days
mibFaultCode: F1212
mibFaultName: fltExtpolClientGracePeriodWarning2
moClass: extpol:Client
Type: management
autoCleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning3

Fault Code: F1213

Message: FPR Domain [name] registered with FPR Central is running in the grace period for more than 30 days

Explanation: This FPR Domain registered with FPR Central has been running in the grace period for more than 30 days. This fault typically occurs if this FPR domain is registered with FPR Central after all default (and procured) licenses are assigned to other FPR domains and the unlicensed FPR Domains have been running for more than 120 days.

Recommended Action: If you see this fault, take the following actions:

  1. Check the number of licenses installed and consumed on FPR Central. In the Cisco FPR Manager GUI, you can access the licensing information from the Operations Management tab for the FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

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

Fault Details 


Severity: warning
Cause: license-graceperiod-30days
mibFaultCode: F1213
mibFaultName: fltExtpolClientGracePeriodWarning3
moClass: extpol:Client
Type: management
autoCleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning4

Fault Code: F1214

Message: FPR Domain [name] registered with FPR Central is running in the grace period for more than 60 days

Explanation: This FPR Domain registered with FPR Central has been running in the grace period for more than 60 days. This fault typically occurs if this FPR domain is registered with FPR Central after all default (and procured) licenses are assigned to other FPR domains and the unlicensed FPR Domains have been running for more than 60 days.

Recommended Action: If you see this fault, take the following actions:

  1. Check the number of licenses installed and consumed on FPR Central. In the Cisco FPR Central GUI, you can access the licensing information from the Operations Management tab for the FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

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

Fault Details 


Severity: warning
Cause: license-graceperiod-60days
mibFaultCode: F1214
mibFaultName: fltExtpolClientGracePeriodWarning4
moClass: extpol:Client
Type: management
autoCleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning5

Fault Code: F1215

Message: FPR Domain [name] registered with FPR Central is running in the grace period for more than 90 days

Explanation: This FPR Domain registered with FPR Central has been running in the grace period for more than 90 days. This fault typically occurs if this FPR domains is registered with FPR Central after all default (and procured) licenses are assigned to other FPR domains and the unlicensed FPR Domains have been running for more than 90 days.

Recommended Action: If you see this fault, take the following actions:

  1. Check the number of licenses installed and consumed by FPR Central. In the Cisco FPR Central GUI, you can access the licensing information from the Operations Management tab for the FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

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

Fault Details 


Severity: major
Cause: license-graceperiod-90days
mibFaultCode: F1215
mibFaultName: fltExtpolClientGracePeriodWarning5
moClass: extpol:Client
Type: management
autoCleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning6

Fault Code: F1216

Message: FPR Domain [name] registered with FPR Central is running in the grace period for more than 119 days

Explanation: This FPR Domain registered with FPR Central has been running in the grace period for more than 119 days. This fault typically occurs if this FPR domain is registered with FPR Central after all default (and procured) licenses are assigned to other FPR domains and the unlicensed FPR Domains have been running for more than 119 days.

Recommended Action: If you see this fault, take the following actions:

  1. Check the number of licenses installed and consumed on FPR Central. In the Cisco FPR Central GUI, you can access the licensing information from the Operations Management tab for FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

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

Fault Details 


Severity: critical
Cause: license-graceperiod-119days
mibFaultCode: F1216
mibFaultName: fltExtpolClientGracePeriodWarning6
moClass: extpol:Client
Type: management
autoCleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning7

Fault Code: F1217

Message: Grace period for FPR Domain [name] registered with FPR Central has expired. Please acquire a license for the same.

Explanation: This FPR Domain registered with FPR Central has been running in the grace period for more than 120 days. FPR domains are registered with FPR Central after all default (and procured) licenses are assigned to other FPR domains and the unlicensed FPR Domains have been running for more than 120 days. At this stage, the system licensing state is set to expired.

Recommended Action: If you see this fault, take the following actions:

  1. Check the number of licenses installed and consumed on FPR Central. In the Cisco FPR Central GUI, you can access the licensing information from the Operations Management tab for FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

  2. Disable the unlicensed FPR Domains to bring the number of enabled Domains down to the number of total licenses.

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

Fault Details 


Severity: critical
Cause: license-graceperiod-expired
mibFaultCode: F1217
mibFaultName: fltExtpolClientGracePeriodWarning7
moClass: extpol:Client
Type: management
autoCleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning1

Fault Code: F1218

Message: FPR Domain [name] is registered with FPR Central without a valid license.

Explanation: This FPR domain is registered with FPR Central without having a license. This fault typically occurs if this FPR domain is registered with FPR Central without the initial activation license and after all default licenses are assigned to other FPR domains.

Recommended Action: If you see this fault, take the following actions:

  1. Check if the initial activation license is installed on FPR Central. In the Cisco FPR Central GUI, you can access the licensing information from the Operations Management tab for FPR Central. In the Cisco FPR Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

  2. Disable the unlicensed FPR Domains to bring the number of enabled Domains down to the number of total licenses.

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

Fault Details 


Severity: critical
Cause: license-insufficient
mibFaultCode: F1218
mibFaultName: fltExtpolClientGracePeriodWarning1
moClass: extpol:Client
Type: management
autoCleared: true
Affected MO: extpol/reg/clients/client-[id]

fltStorageItemFilesystemIssues

Fault Code: F1219

Message: Partition [name] on fabric interconnect [id] has file system errors

Explanation: This fault occurs when the partition develops faults

Recommended Action: If you see this fault, take the following actions:

  1. Create a show tech-support file and contact Cisco TAC.

Fault Details 


Severity: major
Cause: equipment-degraded
mibFaultCode: F1219
mibFaultName: fltStorageItemFilesystemIssues
moClass: storage:Item
Type: equipment
autoCleared: true
Affected MO: sys/switch-[id]/stor-part-[name]

fltPkiKeyRingModulus

Fault Code: F1222

Message: [name] Keyring's RSA modulus is invalid.

Explanation: This fault occurs when RSA keyring is created without modulus set.

Recommended Action: None set.

Fault Details 


Severity: major
Cause: invalid-keyring-modulus
mibFaultCode: F1222
mibFaultName: fltPkiKeyRingModulus
moClass: pki:KeyRing
Type: security
autoCleared: true
Affected MO: sys/pki-ext/keyring-[name]

fltAaaOrgLocaleOrgNotPresent

Fault Code: F1223

Message: Locale Org [name] can't be deployed. Error: [configStatusMessage]

Explanation: This fault typically occurs because Cisco FPR Manager has detected an unidentified org reference.

Recommended Action: If you see this fault, take the following actions:

  1. Verify that the org dn referenced in this Org is exists, if not create the same.

Fault Details 


Severity: warning
Cause: locale-org-config-error
mibFaultCode: F1223
mibFaultName: fltAaaOrgLocaleOrgNotPresent
moClass: aaa:Org
Type: security
autoCleared: true
Affected MO: sys/user-ext/locale-[name]/org-[name]

fltNetworkOperLevelExtraprimaryvlans

Fault Code: F1229

Message: Fabric Interconnect [id]: Number of primary vlans exceeds the max limit on the FI: Number of Primary Vlans: [primaryVlanCount] and Max primary vlans allowed: [maxPrimaryVlanCount]

Explanation: This fault occurs when the fabric interconnect has more number of primary vlans than what is supported.

Recommended Action: If you see this fault, take the following actions:

  1. It is recommended that operator should delete the extra primary vlans than are there in the FI. System may appear to be normally functioning even with these extra primary vlans in place. However there may be performance issues observed as the system is operating above the recommended scale limits..

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

Fault Details 


Severity: major
Cause: extra-primary-vlans
mibFaultCode: F1229
mibFaultName: fltNetworkOperLevelExtraprimaryvlans
moClass: network:OperLevel
Type: equipment
autoCleared: true
Affected MO: sys/switch-[id]/oper-level

fltEquipmentHealthLedCriticalError

Fault Code: F1236

Message: Health LED of server [chassisId]/[slotId] shows error. Reason: [healthLedStateQualifier]Health LED of server [id] shows error. Reason: [healthLedStateQualifier]

Explanation: This fault is raised Blade LED changes to amber blinking

Recommended Action: If you see this fault, take the following actions:

  1. Read fault summary and determine course of action.

Fault Details 


Severity: critical
Cause: health-led-amber-blinking
mibFaultCode: F1236
mibFaultName: fltEquipmentHealthLedCriticalError
moClass: equipment:HealthLed
Type: equipment
autoCleared: true
Affected MO: sys/chassis-[id]/blade-[slotId]/ext-board-[id]/health-led
Affected MO: sys/chassis-[id]/blade-[slotId]/health-led
Affected MO: sys/chassis-[id]/fan-module-[tray]-[id]/health-led
Affected MO: sys/chassis-[id]/health-led
Affected MO: sys/chassis-[id]/psu-[id]/health-led
Affected MO: sys/chassis-[id]/slot-[id]/health-led
Affected MO: sys/fex-[id]/health-led
Affected MO: sys/fex-[id]/psu-[id]/health-led
Affected MO: sys/fex-[id]/slot-[id]/health-led
Affected MO: sys/rack-unit-[id]/ext-board-[id]/health-led
Affected MO: sys/rack-unit-[id]/fan-module-[tray]-[id]/health-led
Affected MO: sys/rack-unit-[id]/health-led
Affected MO: sys/rack-unit-[id]/psu-[id]/health-led
Affected MO: sys/switch-[id]/fan-module-[tray]-[id]/health-led
Affected MO: sys/switch-[id]/psu-[id]/health-led

fltEquipmentHealthLedMinorError

Fault Code: F1237

Message: Health LED of server [chassisId]/[slotId] shows error. Reason: [healthLedStateQualifier]Health LED of server [id] shows error. Reason: [healthLedStateQualifier]

Explanation: This fault is raised Blade LED changes to amber

Recommended Action: If you see this fault, take the following actions:

  1. Read fault summary and determine course of action.