Cisco Firepower 2100 Series Faults and Error Messages, Version 6.2.1

fltFabricVlanReqVlanPermitUnresolved

Fault Code: F0019

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

fltFabricVlanGroupReqVlanGroupPermitUnresolved

Fault Code: F0021

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

fltDcxNsFailed

Fault Code: F0056

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Fault Details

fltComputePhysicalInsufficientlyEquipped

Fault Code: F0057

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Verify that an adapter and CPU are installed.

Step 3 Reacknowledge the server.

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

Fault Details

fltComputePhysicalIdentityUnestablishable

Fault Code: F0058

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Reacknowledge the server.

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

Fault Details

fltComputeBoardPowerError

Fault Code: F0059

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 If you reinstalled the server, reacknowledge it.

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

Fault Details

fltComputeBoardPowerFail

Fault Code: F0060

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:

Step 1 Remove the blade server from the chassis.

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

Fault Details

fltComputeABoardThermalProblem

Fault Code: F0061

Message

Motherboard [faultQualifier] of server [chassisId]/[slotId] (service profile: [assignedToDn]) thermal: [thermal]Motherboard of server [id] (service profile: [assignedToDn]) thermal: [thermal]

Explanation

This fault typically occurs when the motherboard thermal sensors on a server detect a problem.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the server fans are working properly.

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

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

Fault Details

fltComputeABoardPowerUsageProblem

Fault Code: F0062

Message

Motherboard [faultQualifier] of server [chassisId]/[slotId] (service profile: [assignedToDn]) powerUsage: [powerUsage]Motherboard of server [id] (service profile: [assignedToDn]) powerUsage: [powerUsage]

Explanation

This fault typically occurs when the motherboard power consumption exceeds certain threshold limits. At that time the power usage sensors on a server detect a problem.

Recommended Action

If you see this fault, take the following actions:

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

Fault Details

fltComputePhysicalPowerProblem

Fault Code: F0063

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 If you reinstalled the server, reacknowledge it.

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

Fault Details

fltComputePhysicalBiosPostTimeout

Fault Code: F0065

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Reacknowledge the server.

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

Fault Details

fltComputePhysicalDiscoveryFailed

Fault Code: F0066

Message

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

Explanation

This fault typically occurs for one of the following reasons:

• The shallow discovery that occurs when the server associated with service profile failed.
• The server is down.
• The data path is not working.
• Cisco FPR Manager cannot communicate with the CIMC on the server.
• The server cannot communicate with the fabric interconnect.

Recommended Action

If you see this fault, take the following actions:

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

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

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

a. Check the operational state of the server.

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

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

Fault Details

fltComputePhysicalAssociationFailed

Fault Code: F0067

Message

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

Explanation

This fault typically occurs for one of the following reasons:

• The service profile could not be associated with the server.
• The server is down.
• The data path is not working.
• Cisco FPR Manager cannot communicate with one or more of the fabric interconnect, the server, or a component on the server.

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltComputePhysicalDisassociationFailed

Fault Code: F0068

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:

Step 1 Check the communication path to the server including fabric interconnect server ports, IOM link and the current state of the server

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

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

Fault Details

fltComputePhysicalInoperable

Fault Code: F0069

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Reacknowledge the server.

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

Fault Details

fltComputePhysicalUnassignedMissing

Fault Code: F0070

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Reacknowledge the server.

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

Fault Details

fltComputePhysicalAssignedMissing

Fault Code: F0071

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Reacknowledge the server.

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

Fault Details

fltComputePhysicalUnidentified

Fault Code: F0072

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 Reacknowledge the server.

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

Fault Details

fltComputePhysicalNetworkMisconfigured

Fault Code: F0075

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:

Step 1 Re-acknowledge the server. This will trigger Deep Discovery-Deep Association & will resolve the issue

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

Fault Details

fltComputePhysicalAdapterMismatch

Fault Code: F0076

Message

Server [id] (service profile: [assignedToDn]) has invalid adapter combinatonServer [chassisId]/[slotId] (service profile: [assignedToDn]) has invalid adapter combination

Explanation

This fault typically occurs because Cisco FPR Manager has detected that the server has an invalid combination of Cisco VICs.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the valid adapter combinations are installed configuration.

Step 2 Reacknowledge the server.

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

Fault Details

fltComputeBoardCmosVoltageThresholdCritical

Fault Code: F0077

Message

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

Explanation

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

Recommended Action

If you see this fault, replace the battery.

Fault Details

fltComputeBoardCmosVoltageThresholdNonRecoverable

Fault Code: F0078

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

fltComputeABoardMotherBoardVoltageThresholdUpperNonRecoverable

Fault Code: F0079

Message

Motherboard input voltage(12V/5V/3V) in server [id] is [voltage]Motherboard [faultQualifier] input voltage(12V/5V/3V) in server [chassisId]/[slotId] is [voltage]

Explanation

This fault is raised when one or more motherboard input voltages has become too high and is unlikely to recover.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltComputeABoardMotherBoardVoltageThresholdLowerNonRecoverable

Fault Code: F0080

Message

Motherboard input voltage(12V/5V/3V) in server [id] is [voltage]Motherboard [faultQualifier] input voltage(12V/5V/3V) in server [chassisId]/[slotId] is [voltage]

Explanation

This fault is raised when one or more motherboard input voltages has dropped too low and is unlikely to recover.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltComputeABoardMotherBoardVoltageUpperThresholdCritical

Fault Code: F0081

Message

Motherboard input voltage(12V/5V/3V) in server [id] is [voltage]Motherboard [faultQualifier] input voltage(12V/5V/3V) in server [chassisId]/[slotId] is [voltage]

Explanation

This fault is raised when one or more motherboard input voltages has crossed upper critical thresholds.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltComputeABoardMotherBoardVoltageLowerThresholdCritical

Fault Code: F0082

Message

Motherboard input voltage(12V/5V/3V) in server [id] is [voltage]Motherboard [faultQualifier] input voltage(12V/5V/3V) in server [chassisId]/[slotId] is [voltage]

Explanation

This fault is raised when one or more motherboard input voltages has crossed lower critical thresholds.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltComputePoolEmpty

Fault Code: F0083

Message

server pool [name] is empty

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Manually associate the service profile with a server.

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

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

Fault Details

fltComputePhysicalPost-failure

Fault Code: F0084

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Reboot the server.

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

Fault Details

fltComputeRtcBatteryInoperable

Fault Code: F0085

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

fltComputeIOHubThermalNonCritical

Fault Code: F0086

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

fltComputeIOHubThermalThresholdCritical

Fault Code: F0087

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:

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

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

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

Fault Details

fltComputeIOHubThermalThresholdNonRecoverable

Fault Code: F0088

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:

Step 1 Shutdown the server immediately.

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

Fault Details

fltFirmwareBootUnitPowerCycleRequired

Fault Code: F0089

Message

Board controller upgraded, manual a/c power cycle required on server [serverId]

Explanation

None set.

Recommended Action

If you see this fault, take the following actions:

Step 1 Power cycle the board controller.

Fault Details

fltCimcvmediaActualMountEntryVmediaMountFailed

Fault Code: F0090

Message

Server [chassisId]/[slotId] (service profile: [assignedToDn]) vmedia mapping [mappingName] has failed.Server [id] (service profile: [assignedToDn]) vmedia mapping [mappingName] has failed.

Explanation

None set.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the mount related details(remote server ip, port, path & file is reachable) and reack the server .

Fault Details

fltFirmwarePackItemImageMissing

Fault Code: F0095

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Fault Details

fltFirmwareUpdatableImageUnusable

Fault Code: F0096

Message

backup image is unusable. reason: [operStateQual]

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltFirmwareBootUnitCantBoot

Fault Code: F0097

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltFirmwareBootUnitActivateStatusFailed

Fault Code: F0098

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:

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

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

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

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

Fault Details

fltFirmwareStatusCimcFirmwareMismatch

Fault Code: F0099

Message

Aggregate blade CIMC firmware mismatch. Firmware: [cimcVersion]

Explanation

This fault typically occurs when the CIMC firmware image on master and slave node in an aggregate blade does not match.

Recommended Action

Update and activate master and slave CIMC to same firmware version.

Fault Details

fltFirmwareStatusPldFirmwareMismatch

Fault Code: F0100

Message

Aggregate blade board controller firmware mismatch. Firmware: [pldVersion]

Explanation

This fault typically occurs when the board controller firmware image on master and slave node in an aggregate blade does not match.

Recommended Action

Update master and slave board controller to same firmware version.

Fault Details

fltFirmwareAutoSyncPolicyDefaultHostPackageMissing

Fault Code: F0101

Message

Default host firmware package is missing or deleted.

Explanation

This fault typically occurs for the following reasons: when Auto Firmware Sync Policy is set Auto-acknowledge or User-acknowledge and default host firmware pack is not available.

• Auto Firmware Sync is not happening.
• Default host firmware package is missing or deleted.

Recommended Action

If you see this fault, take the following actions:

Step 1 Go to Servers tab and expand policies node. Select Host Firmware Packages under policies node.

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

Step 3 Create a host firmware package with name ’default’. If the problem persists, create a show tech-support file and contact Cisco TAC.

Fault Details

fltPowerChassisMemberPowerGroupCapInsufficient

Fault Code: F0149

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:

Step 1 Consider increasing the group cap.

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

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

Fault Details

fltPowerChassisMemberChassisFirmwareProblem

Fault Code: F0150

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

fltPowerBudgetFirmwareMismatch

Fault Code: F0151

Message

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

Explanation

This fault typically occurs when the CIMC or BIOS 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

fltPowerChassisMemberChassisPsuInsufficient

Fault Code: F0152

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

fltPowerBudgetChassisPsuInsufficient

Fault Code: F0153

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

fltPowerChassisMemberChassisPsuRedundanceFailure

Fault Code: F0154

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:

Step 1 Consider adding more PSUs to the chassis.

Step 2 Replace any non-functional PSUs.

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

Fault Details

fltPowerBudgetPowerBudgetCmcProblem

Fault Code: F0155

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:

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

Step 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

fltPowerBudgetPowerBudgetBmcProblem

Fault Code: F0156

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:

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

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

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

Fault Details

fltPowerBudgetPowerCapReachedCommit

Fault Code: F0157

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

fltPowerBudgetTStateTransition

Fault Code: F0158

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:

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

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

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

Fault Details

fltPowerBudgetPowerBudgetDiscFail

Fault Code: F0159

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

Step 1 Consider increasing the group cap.

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

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

Fault Details

fltPowerPolicyPowerPolicyApplicationFail

Fault Code: F0160

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:

Step 1 Increase the power budget for the blade servers in the power policy.

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

Fault Details

fltPowerGroupPowerGroupInsufficientBudget

Fault Code: F0161

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:

Step 1 Consider increasing the group cap.

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

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

Fault Details

fltPowerGroupPowerGroupBudgetIncorrect

Fault Code: F0162

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:

Step 1 Consider increasing the group cap.

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

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

Fault Details

fltPowerBudgetChassisPsuMixedMode

Fault Code: F0163

Message

Chassis [id] has a mix of high-line and low-line PSU input power sources.

Explanation

This fault occurs when there is a mix of high-line and low-line PSU input power source.

Recommended Action

If you see this fault, change all the PSU input power sources to have same mode

Fault Details

fltSmSlotSmaHeartbeat

Fault Code: F0185

Message

Slot [slotId], is not operationally up

Explanation

This fault occurs when a slot is not operationally up.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reboot the Blade associated with the Slot

Fault Details

fltSmSlotBladeNotWorking

Fault Code: F0186

Message

Slot [slotId] has a fault, either blade discovery is failed or service profile association is failed

Explanation

This fault occurs when a blade discovery is failed or service profile association is failed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reboot the blade associated with the slot

Fault Details

fltSmSlotDiskFormatFailed

Fault Code: F0187

Message

Disk format is failed on slot [slotId]

Explanation

This fault occurs when a blade disk formatting is failed.

Recommended Action

If you see this fault, take the following actions:

Step 1 Reformat disk or need disk replacement

Fault Details

fltSmSlotBladeSwap

Fault Code: F0188

Message

Blade swap detected on slot [slotId]

Explanation

This fault occurs during the blade swap.

Recommended Action

If you see this fault, take the following action:

Step 1 1. Insert the correct blade

Step 2 2. Reformat the disk

Fault Details

fltSmSecSvcSwitchConfigFail

Fault Code: F0189

Message

Switch configuration failed for Logical Device. Error: [switchErrorMsg]

Explanation

This fault occurs when switch configuration fails for a LogicalDevice.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltSmAppInstanceAppNotResponding

Fault Code: F0190

Message

App Instance [appName] on slot [slotId], is not responding

Explanation

This fault occurs when an app instance is not responding.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltSmAppInstanceAppInstallFailed

Fault Code: F0191

Message

Failed to install App Instance [appName] on slot [slotId]. Error: [errorMsg]

Explanation

This fault occurs when an app instance installation fails.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltSmAppInstanceAppStartFailed

Fault Code: F0192

Message

Failed to start App Instance [appName] on slot [slotId]. Error: [errorMsg]

Explanation

This fault occurs when an app instance start fails.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltSmAppInstanceAppUpdateFailed

Fault Code: F0193

Message

Failed to update App Instance [appName] on slot [slotId]. Error: [errorMsg]

Explanation

This fault occurs when an app instance updation fails.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltSmAppInstanceAppStopFailed

Fault Code: F0194

Message

Failed to stop App Instance [appName] on slot [slotId]. Error: [errorMsg]

Explanation

This fault occurs when an app instance stop fails.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltSmAppInstanceAppInstanceError

Fault Code: F0195

Message

Error in App Instance [appName]. [errorMsg]

Explanation

This fault occurs when an app instance is in a non-terminal error state.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltSmLogicalDeviceIncompleteConfig

Fault Code: F0196

Message

Logical Device [name] is not configured correctly. Error [errorMsg]

Explanation

This fault occurs when a logical device is not configured correctly.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltSmLogicalDeviceLogicalDeviceError

Fault Code: F0197

Message

Error in Logical Device [name]. [errorMsg]

Explanation

This fault occurs when a logical device is in a non-terminal error state.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltSmAppLicenseAgreementNotAccepted

Fault Code: F0198

Message

End User License Agreement not accepted for Application [name].[version]

Explanation

This fault occurs when an application requiring End User License Agreement(EULA) is downloaded but EULA is yet to be accepted.

Recommended Action

If you see this fault, take the following actions:

Step 1 Accept the license aggrement for this application

Fault Details

fltSmAppInstanceAppInstanceUnsupported

Fault Code: F0199

Message

App Instance [appName] on slot [slotId] is not supported in the current bundle. Error: [errorMsg]

Explanation

This fault occurs when an app instance is not supported in the current platform bundle

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltSmAppAppMetaCorrupted

Fault Code: F0200

Message

The application [appId] cannot be reloaded.

Explanation

This fault occurs when an application meta data cannot be reloaded.

Recommended Action

If you see this fault, take the following actions:

Step 1 Re-download the application from a trusted source

Fault Details

fltSwVlanPortNsVLANCompNotSupport

Fault Code: F0299

Message

VLAN Port Count Optimization is not supported

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltDcxVIfLinkState

Fault Code: F0300

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:

Step 1 Reenable the uplink port that failed.

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

Fault Details

fltVnicEtherConfig-failed

Fault Code: F0314

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that the server was successfully discovered.

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

Step 3 Confirm that the vCon assignment is correct.

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

Fault Details

fltVnicEtherPinningMismatch

Fault Code: F0315

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:

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

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

Fault Details

fltVnicEtherPinningMisconfig

Fault Code: F0316

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:

Step 1 Review the LAN pin group configuration.

Step 2 Correct the configuration of the port and port channels in the pin group.

Step 3 Ensure that all required vLANs are allowed on the target ports or port channels.

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

Fault Details

fltVnicEtherIfVlanAccessFault

Fault Code: F0317

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:

Step 1 Change the vnic’s interface name to a VLAN that you have access to.

Step 2 If you wish to use the default vlan, change the vnic’s interface name to default.

Step 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

fltVnicEtherIfVlanUnresolvable

Fault Code: F0318

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:

Step 1 Change the vnic interface name to an existing VLAN.

Step 2 Create the named vlan .

Fault Details

fltVnicEtherIfRemoteVlanUnresolvable

Fault Code: F0319

Message

The named vlan [name] for vNIC [name] cannot be resolved remotely

Explanation

None set.

Recommended Action

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.

Fault Details

fltVnicEtherIfInvalidVlan

Fault Code: F0320

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:

Step 1 an isolated vlan or a community vlan that is not associated to a valid primary vlan

Step 2 a primary vlan without any of its assoicated secondary vlans allowed on the vnic

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

Step 1 if invalid vlan is an isolated or community vlan then make sure it is mapped to a valid primary vlan.

Step 2 if invalid vlan is a primary vlan then either allow any of its secondary vlans or delete it from vnic or port profile.

Step 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

fltFabricVlanVlanConflictPermit

Fault Code: F0321

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

fltVnicProfileProfileConfigIncorrect

Fault Code: F0322

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

fltVnicIScsiConfig-failed

Fault Code: F0323

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:

Step 1 Make sure that iqn name unique per iSCSI vnic.

Step 2 Using show identity iqn check if the iSCSI vnic is registered in the universe.

Step 3 Try non disruptive actions such as changing description on the Service Profile to register the iqn in the universe.

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

Fault Details

fltVnicEtherVirtualization-conflict

Fault Code: F0324

Message

Multiple connection policies cannot be assigned to the same Eth vNIC

Explanation

This fault occurs when multiple connection policies are assigned to the same vNIC.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check on the vNIC if different types of connection policies (dynamic/VMQ) are assigned. Keep only one type.

Step 2 Check on the vNIC through CLI if more than one connection policy of the same type is assigned. Keep only one connection policy.

Fault Details

fltVnicEtherVirtualization-netflow-conflict

Fault Code: F0325

Message

Netflow and VMQ/SRIOV-USNIC policies cannot be assigned to the same Eth vNIC

Explanation

This fault typically occurs when a netflow src vnic is made a USNIC or VMQ vnic

Recommended Action

If you see this fault, take the following actions:

Step 1 Remove the vnic from a netflow session or remove the usnic/vmq policy

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

Fault Details

fltLsIssuesIscsi-config-failed

Fault Code: F0326

Message

Service Profile [name] configuration failed due to iSCSI issue [iscsiConfigIssues]

Explanation

This fault typically occurs when Cisco FPR Manager Service Profile configuration failed due to iSCSI Config Issues.

Recommended Action

If you see this fault, take the following actions:

Step 1 Correct the Service Profile iSCSI Configuration as per the issue reported.

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

Fault Details

fltMacpoolPoolEmpty

Fault Code: F0332

Message

MAC pool [name] is empty

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Fault Details

fltCallhomeEpNoSnmpPolicyForCallhome

Fault Code: F0335

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

fltAdaptorUnitUnidentifiable-fru

Fault Code: F0349

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that a supported adapter is installed.

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

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

Fault Details

fltAdaptorUnitExtnUnidentifiable-fru

Fault Code: F0350

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:

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

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

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

Fault Details

fltAdaptorUnitMissing

Fault Code: F0351

Message

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

Explanation

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

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltAdaptorUnitExtnMissing

Fault Code: F0352

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:

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

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

Fault Details

fltAdaptorUnitAdaptorReachability

Fault Code: F0353

Message

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

Explanation

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

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

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

Fault Details

fltAdaptorHostIfLink-down

Fault Code: F0354

Message

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

Explanation

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

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltAdaptorExtIfLink-down

Fault Code: F0355

Message

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

Explanation

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

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltAdaptorHostEthIfMisConnect

Fault Code: F0356

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:

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

Step 2 If connectivity seems correct, reacknowledge the server.

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

Fault Details

fltAdaptorHostEthIfMissing

Fault Code: F0357

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:

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

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

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

Fault Details

fltAdaptorExtEthIfMisConnect

Fault Code: F0358

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:

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

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

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

Fault Details

fltAdaptorExtEthIfMissing

Fault Code: F0359

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:

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

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

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

Fault Details

fltMemoryUnitDegraded

Fault Code: F0369

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltMemoryUnitIdentity-unestablishable

Fault Code: F0370

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

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

Fault Details

fltMemoryUnitInoperable

Fault Code: F0371

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 If necessary, replace the DIMM.

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

Fault Details

fltMemoryUnitDisabled

Fault Code: F0372

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

fltMemoryUnitThermalThresholdNonCritical

Fault Code: F0373

Message

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

Explanation

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

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Step 5 Power off unused blade servers and rack servers.

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

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

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

Fault Details

fltMemoryBufferUnitThermalThresholdNonCritical

Fault Code: F0374

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:

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

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

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

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

Step 5 Power off unused blade servers and rack servers.

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

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

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

Fault Details

fltMemoryUnitThermalThresholdCritical

Fault Code: F0375

Message

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

Explanation

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

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Step 5 Power off unused blade servers and rack servers.

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

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

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

Fault Details

fltMemoryBufferUnitThermalThresholdCritical

Fault Code: F0376

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:

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

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

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

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

Step 5 Power off unused blade servers and rack servers.

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

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

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

Fault Details

fltMemoryUnitThermalThresholdNonRecoverable

Fault Code: F0377

Message

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

Explanation

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

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

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

Step 5 Power off unused blade servers and rack servers.

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

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

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

Fault Details

fltMemoryBufferUnitThermalThresholdNonRecoverable

Fault Code: F0378

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:

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

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

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

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

Step 5 Power off unused blade servers and rack servers.

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

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

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

Fault Details

fltMemoryArrayVoltageThresholdNonCritical

Fault Code: F0379

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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

Step 2 Monitor the memory array for further degradation.

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

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

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

Fault Details

fltMemoryArrayVoltageThresholdCritical

Fault Code: F0380

Message

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

Explanation

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

Recommended Action

If you see this fault, take the following actions:

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