- fltStorageItemCapacityExceeded
- fltStorageItemCapacityWarning
- fltComputeGroupMembershipGroup-Membership-State-Fault
- fltComputeGroupMembershipGroup-Membership-Group-Fault
- fltOrgDomainGroupPolicyUCS-Grouping-Policy-Fault
- fltCommSvcEpCommSvcNotDeployed
- fltVnicFcIfVsanUnresolvable
- fltVnicEtherIfVlanUnresolvable
- fltVnicEtherIfVlanAccessFault
- fltVnicEtherIfVlanSyncFault
- fltVnicFcIfVsanSyncFault
- fltVnicEtherUnassociatedVnicIfFault
- fltVnicFcUnassociatedVnicIfFault
- fltLsSPMetaUngrouped-domain
- fltLsServerFailed
- fltLsServerDiscoveryFailed
- fltLsServerConfigFailure
- fltLsServerMaintenanceFailed
- fltLsServerRemoved
- fltLsServerInaccessible
- fltLsServerAssociationFailed
- fltLsComputeBindingAssignmentRequirementsNotMet
- fltLsServerUnassociated
- fltLsServerServer-unfulfilled
- fltLsmaintMaintPolicyUnresolvableScheduler
- fltComputePoolEmpty
- fltComputeAOperationRemote-operation-fail
- fltLsIssuesConfigFailure
- fltVnicFaultVlanSyncFault
- fltVnicMgmtIfVlanUnresolvable
- fltVnicMgmtIfVlanAccessFault
- fltVnicMgmtIfVlanSyncFault
- fltVnicMgmtUnassociatedVnicIfFault
- fltPkiTPStatus
- fltPkiKeyRingStatus
- fltQueryUsageContextTimeout
- fltQueryUsageContextFailed
- fltQueryDependencyContextTimeout
- fltQueryDependencyContextFailed
- fltQueryImportContextTimeout
- fltQueryImportContextFailed
- fltComputeRemoteOpStatusRemote-op-failed
Resource Manager Faults
First Published: July 23, 2014
Last Updated: July 23, 2014
fltStorageItemCapacityExceeded
Disk usage for partition [systemName] [name] exceeded 70%
This fault occurs when the partition disk usage exceeds 70% but is less than 90%.
If you see this fault, take the following actions:
Step 1
Reduce the partition disk usage to less than 70% by deleting unused and unnecessary files.
Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltStorageItemCapacityWarning
Disk usage for partition [systemName] [name] exceeded 90%
This fault occurs when the partition disk usage exceeds 90%.
If you see this fault, take the following actions:
Step 1 Reduce the partition disk usage to less than 90% by deleting unused and unnecessary files.
Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltComputeGroupMembershipGroup-Membership-State-Fault
UCS to Group Membership cannot be processed. [configStatusMessage]
This fault occurs when a group membership cannot be processed.
If you see this fault, take the following actions:
Step 1 Please check the fault description for additional information.
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltComputeGroupMembershipGroup-Membership-Group-Fault
Group [groupDn] doesn’t exist.
This fault occurs when a UCS domain’s group membership cannot be processed because the group dosenot exist.
If you see this fault, take the following actions:
Step 1 Please provide a existing domain group.
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltOrgDomainGroupPolicyUCS-Grouping-Policy-Fault
UCS Grouping Policy cannot be processed. [configStatusMessage]
The domain group policy can not be applied. This fault typically occurs when there is no domain group or registration policy set for the domain group policy. Please check the fault message for details.
If you see this fault, take the following actions:
Step 1 1. Check that a valid domain group and registration policy are associated with this domain group policy.
Step 2 If the above action 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.
fltVnicFcIfVsanUnresolvable
The named vsan [name] for vNIC [name] cannot be resolved
This fault (warning) occurs when a Service Profile’s vnic interface (SAN) is unresolvable.
This fault will be removed if you perform one of the following actions:
Step 1 Change the vnic interface name to an existing VSAN.
Step 2 Create the named vsan .
fltVnicEtherIfVlanUnresolvable
The named vlan [name] for vNIC [name] cannot be resolved
This fault (warning) occurs when a Service Profile’s vnic interface (LAN) is unresolvable.
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 .
fltVnicEtherIfVlanAccessFault
The named vlan [name] for vNIC [name] cannot be accessed from org [name]
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.
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 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).
fltVnicEtherIfVlanSyncFault
The named vlan [name] for vNIC [name] cannot be pushed to UCSM
The vlan was unable to be pushed down to UCSM. This fault typically occurs if a vlan with the same name already exists on the UCSM do main or the vlan id cannot be set because it is already taken.
If you see this fault, take the following actions:
Step 1 If the vlan already exists on the UCSM domain, delete the local vlan.
Step 2 If the vlan id is already taken, change the vlan id.
Step 3 If the vlan does not exist, delete the vnic reference.
Step 4 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltVnicFcIfVsanSyncFault
The named vsan [name] for vHBA [name] cannot be pushed to UCSM
The vsan was unable to be pushed down to UCSM. This fault typically occurs if a vsan with the same name already exists on the UCSM domain or the vsan id cannot be set because it is already taken.
If you see this fault, take the following actions:
Step 1 If the vsan already exists on the UCSM domain, delete the local vsan.
Step 2 If the vsan id is already taken, change the vsan id.
Step 3 If the vsan does not exist, delete the vhba reference.
Step 4 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltVnicEtherUnassociatedVnicIfFault
[name] isn’t associated with any VLAN
fltVnicFcUnassociatedVnicIfFault
[name] isn’t associated with any VSAN
There is no vsan associated with this vhba.
If you see this fault, take the following actions:
Step 1 Associate a vsan with this vhba.
Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltLsSPMetaUngrouped-domain
Unable to resolve Vsans/vlans. Service profile deployed on [serverDn] failed due to an ungrouped domain.
Server deployment failed . This fault typically occurs if the service profile uses a Vlan or a Vsan, but it is deployed on a physical blade/server that belongs to an ungrouped domain .
If you see this fault, take the following actions:
Step 1 add the UCS of the physical server to a domain
Step 2 Remove the interface name from the Vnic: remove the usage of the Vlan or Vsan from the service profile
fltLsServerFailed
Server has failed. This fault typically occurs if the adapter power on self-test results in major and critical errors.
If you see this fault, take the following actions:
Step 1 Check the POST results for the server. In Cisco UCS Manager GUI, you can access the POST results from the General tab for the server. In Cisco UCS Manager CLI, you can access the POST results through the show post command under the scope for the server.
Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltLsServerDiscoveryFailed
Service profile [name] discovery failed
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 UCS Manager cannot communicate with the CIMC on the server.
- The server cannot communicate with the fabric interconnect.
If you see this fault, take the following actions:
Step 1 Check the FSM tab and view the current state of the server and any FSM operations.
Step 2 Check the error descriptions and see if any server components indicate a failure.
Step 3 If the server or a server component has failed, do the following:
Step 4 Check the operational state of the server.
Step 5 If the server is not operable, reacknowledge the server.
Step 6 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltLsServerConfigFailure
Service profile [name] configuration failed due to [configQualifier]
The named configuration qualifier is not available. This fault typically occurs because Cisco UCS Manager cannot successfully deploy the service profile due to a lack of resources that meet the named qualifier. For example, this fault can occur if the 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.
If you see this fault, take the following actions:
Step 1 Check the status of the server pool associated with the service profile. If the pool is empty, add more blade servers to it.
Step 2 Check the state of the server and ensure that it is in either the discovered or unassociated state.
Step 3 If the server is associated or undiscovered, do one of the following:
– Disassociate the server from the current service profile.
– Select another server to associate with the service profile.
Step 4 Review each policy in the service profile and verify that the selected server meets the requirements in the policy.
Step 5 If the server does not meet the requirements of the service profile, do one of the following:
– Modify the service profile to match the server.
– Select another server that does meet the requirements to associate with the service profile.
Step 6 If you can verify that the server meets the requirements of the service profile, create a show tech-support file and contact Cisco TAC.
fltLsServerMaintenanceFailed
Service profile [name] maintenance failed
Cisco UCS Manager currently does not use this fault.
If you see this fault, create a show tech-support file and contact Cisco TAC.
fltLsServerRemoved
Service profile [name] underlying resource removed
Cisco UCS Manager cannot access the server associated with the service profile. This fault typically occurs as a result of one of the following issues:
If you see this fault, take the following actions:
Step 1 If the server was removed from the slot, reinsert the server in the slot.
Step 2 If the server was not removed, remove and reinsert the server.NOTE: If the server is operable, this action can be disruptive to current operations.
Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltLsServerInaccessible
Service profile [name] cannot be accessed
Cisco UCS Manager cannot communicate with the CIMC on the server. This fault typically occurs as a result of one of the following issues:
If you see this fault, take the following actions:
Step 1 If Cisco UCS Manager shows that the CIMC is down, physically reseat the server.
Step 2 If Cisco UCS Manager shows that the server ports have failed, attempt to enable them.
Step 3 If the I/O module is offline, check for faults on that component.
Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltLsServerAssociationFailed
Service profile [name] association failed for [pnDn]
The service profile 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.
fltLsComputeBindingAssignmentRequirementsNotMet
Assignment of service profile [name] to server [pnDn] failed
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.
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.
fltLsServerUnassociated
Service profile [name] is not associated
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:
If you see this fault, take the following actions:
Step 1 If you did not intend to associate the service profile, ignore the fault.
Step 2 If you did intend to associate the service profile, check the association failure fault.
Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltLsServerServer-unfulfilled
Server [pnDn] does not fulfill Service profile [name] due to [configQualifier]
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:
If you see this fault, take the following actions:
Step 1 Check the server inventory compare to the service profile qualifications.
Step 2 If the server inventory does not match the service profile qualifications, do one of the following:
– Associate the server with a different service profile.
– Ensure the server has sufficient resources to qualify for the current service profile.
Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltLsmaintMaintPolicyUnresolvableScheduler
Schedule [schedName] referenced by maintenance policy [name] does not exist
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:
If you see this fault, take the following actions:
Step 1 Check if the named schedule exists. If it is deleted or missing, try to create it.
Step 2 If the named schedule is deleted or missing, recreate it.
Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltComputePoolEmpty
This fault typically occurs when the selected server pool does not contain any servers.
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.
fltComputeAOperationRemote-operation-fail
Remote opearation failed in UCSM. Error Code: [[remoteErrorCode]]. [remoteErrorDescr]
This fault typically occurs when a remote physical operation performed on UCS Central encounters an error condition.
If you see this fault, take the following actions:
Step 1 Verify the UCSM Client is in registered operation status
Step 2 Verify the UCSM Client is in connected connection status
Step 3 If the UCSM Client has not responded wait for 30 seconds before retrying the operation on the same object
Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltLsIssuesConfigFailure
Service profile [name] configuration failed due to [iscsiConfigIssues] [networkConfigIssues] [serverConfigIssues] [storageConfigIssues] [vnicConfigIssues]
The named configuration qualifier is not available. This fault typically occurs because Cisco UCS Manager cannot successfully deploy the service profile due to a lack of resources that meet the named qualifier. For example, this fault can occur if the 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.
If you see this fault, take the following actions:
Step 1 Check the status of the server pool associated with the service profile. If the pool is empty, add more blade servers to it.
Step 2 Check the state of the server and ensure that it is in either the discovered or unassociated state.
Step 3 If the server is associated or undiscovered, do one of the following:
– Disassociate the server from the current service profile.
– Select another server to associate with the service profile.
Step 4 Review each policy in the service profile and verify that the selected server meets the requirements in the policy.
Step 5 If the server does not meet the requirements of the service profile, do one of the following:
– Modify the service profile to match the server.
– Select another server that does meet the requirements to associate with the service profile.
Step 6 If you can verify that the server meets the requirements of the service profile, create a show tech-support file and contact Cisco TAC.
fltVnicFaultVlanSyncFault
The named vXan [name] cannot be pushed to UCSM. UCSM Message - [descr]
The vlan/vsan was unable to be pushed down to UCSM. This fault typically occurs if a vlan/vsan with the same name already exists on the UCSM domain or the vlan/vsan id cannot be set because it is already taken. Please check the fault message for details.
If you see this fault, take the following actions:
Step 1 If the vlan/vsan already exists on the UCSM domain, delete the local vlan/vsan.
Step 2 If the vlan/vsan id is already taken, change the vlan/vsan id.
Step 3 If the vlan/vsan does not exist, delete the vnic/vhba reference.
Step 4 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltVnicMgmtIfVlanUnresolvable
The named vlan [name] for vNIC [name] cannot be resolved
This fault (warning) occurs when a Service Profile’s vnic interface (LAN) is unresolvable.
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 .
fltVnicMgmtIfVlanAccessFault
The named vlan [name] for vNIC [name] cannot be accessed from org [name]
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.
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 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).
fltVnicMgmtIfVlanSyncFault
The named vlan [name] for vNIC [name] cannot be pushed to UCSM
The vlan was unable to be pushed down to UCSM. This fault typically occurs if a vlan with the same name already exists on the UCSM domain or the vlan id cannot be set because it is already taken.
If you see this fault, take the following actions:
Step 1 If the vlan already exists on the UCSM domain, delete the local vlan.
Step 2 If the vlan id is already taken, change the vlan id.
Step 3 If the vlan does not exist, delete the vnic reference.
Step 4 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltVnicMgmtUnassociatedVnicIfFault
[name] isn’t associated with any VLAN
There is no vlan associated with this vnic.
If you see this fault, take the following actions:
Step 1 Associate a vlan with this vnic.
Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltPkiTPStatus
[name] Trustpoint’s cert-chain is invalid, reason: [certStatus].
This fault occurs when certificate status of TrustPoint has become invalid.
fltPkiKeyRingStatus
[name] Keyring’s certificate is invalid, reason: [certStatus].
This fault occurs when certificate status of Keyring has become invalid.
fltQueryUsageContextTimeout
Getting usage for [targetDn] times out
This fault occurs when UCS Central fails to get usage from UCSM within the timeout period.
If you see this fault, take the following actions:
Step 1 Please check the fault description, which will have details of UCSM connection time out and other additional information.
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltQueryUsageContextFailed
Getting usage for [targetDn] fails, since [statusDescription]
This fault occurs when UCS Central fails to get usage from UCSM.
If you see this fault, take the following actions:
Step 1 Please check the fault description, which will have details of UCSM connection failure and other additional information.
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltQueryDependencyContextTimeout
Getting Dependency for [targetDn] times out
This fault occurs when UCS Central fails to get policy dependencies from UCSM within the timeout period.
If you see this fault, take the following actions:
Step 1 Please check the fault description, which will have details of UCSM connection time out and other additional information.
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltQueryDependencyContextFailed
Getting Dependency for [targetDn] fails, since [statusDescription]
This fault occurs when UCS Central fails to get policy dependencies from UCSM.
If you see this fault, take the following actions:
Step 1 Please check the fault description, which will have details of UCSM connection failure and other additional information.
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltQueryImportContextTimeout
Importing for [targetDn] times out
This fault occurs when UCS Central fails to import policies from UCSM within the timeout period.
If you see this fault, take the following actions:
Step 1 Please check the fault description, which will have details of UCSM connection time out and other additional information.
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltQueryImportContextFailed
Importing for [targetDn] fails, since [statusDescription]
This fault occurs when UCS Central fails to import policies from UCSM.
If you see this fault, take the following actions:
Step 1 Please check the fault description, which will have details of UCSM connection failure and other additional information.
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
fltComputeRemoteOpStatusRemote-op-failed
Remote operation of type [opType] on [name] failed. Reason: [descr]
This fault occurs when a remote operation on a UCS domain failed.
If you see this fault, take the following actions:
Step 1 Please check the fault description, which gives what type of operation failed and also provides additional information.
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
Feedback