Policy Manager Faults
fltFirmwareDownloadPolicyError
[type] Download Policy Configuration Error. Check scheduler Name, Username, Password and HTTP URL
This fault typically occurs when the download configuration is not correct
If you see this fault, take the following actions:
Step 1
Review the fault and the error message on the FSM tab.
Step 2 Check scheduler Name, Username, Password and HTTP URL in download configuration
Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltCommSvcEpCommSvcNotDeployed
Communication Service configuration can’t be deployed. Error: [configStatusMessage]
This fault typically occurs because Cisco UCS Manager has detected an invalid communication policy confiuration.
If you see this fault, take the following actions:
Step 1 Verify that ports configured across all communication services is unique.
fltPkiTPStatus
[name] Trustpoint’s cert-chain is invalid, reason: [certStatus].
This fault occurs when certificate status of TrustPoint has become invalid.
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.
fltPkiKeyRingStatus
[name] Keyring’s certificate is invalid, reason: [certStatus].
This fault occurs when certificate status of Keyring has become invalid.
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.
fltMgmtExportPolicyNo-scheduler-exists
scheduler [schedName] not found
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.
fltLstorageArrayAssociationFailed
Storage Array [name] association failed for [pnDn]
The storage array could not be associated with the server. This fault typically occurs because Cisco UCS Manager cannot communicate with one or more of the following:
If you see this fault, take the following actions:
Step 1 Check the FSM tab for the server and service profile to determine why the association failed.
Step 2 If the server is stuck in an inappropriate state, such as booting, power cycle the server.
Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltLstorageArrayControllerProfileCount
Storage Array [name] has only one controller profile.
The named configuration qualifier is not available. This fault typically occurs because Cisco UCS Manager cannot successfully deploy the storage array due to a lack of resources that meet the named qualifier. For example, this fault can occur if the following occurs:
If you see this fault, take the following actions:
fltLstorageProcessorConfigFailure
Storage Controller Profile [name] configuration failed
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.
fltLstorageBackstorePoolEmpty
This fault typically occurs when a volume pool does not contain any volume.
If you see this fault, take the following actions:
Step 1 If the pool is in use, add some volumes to the pool.
Step 2 If the pool is not in use, ignore the fault.
Feedback