Cisco UCS Central Faults Reference, Release 1.5

fltComputeGroupMembershipGroup-Membership-State-Fault

Fault Code: F10000261

Message

UCS to Group Membership cannot be processed. [configStatusMessage]

Explanation

This fault occurs when a group membership cannot be processed.

Recommended Action

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.

Fault Details

fltComputeGroupMembershipGroup-Membership-Group-Fault

Fault Code: F10000262

Message

Group [groupDn] doesn’t exist.

Explanation

This fault occurs when a UCS domain’s group membership cannot be processed because the group dosenot exist.

Recommended Action

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.

Fault Details

fltOrgDomainGroupPolicyUCS-Grouping-Policy-Fault

Fault Code: F10000263

Message

UCS Grouping Policy cannot be processed. [configStatusMessage]

Explanation

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.

Recommended Action

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.

Fault Details

fltCommSvcEpCommSvcNotDeployed

Fault Code: F10000339

Message

Communication Service configuration can’t be deployed. Error: [configStatusMessage]

Explanation

This fault typically occurs because Cisco UCS Manager has detected an invalid communication policy confiuration.

Recommended Action

If you see this fault, take the following actions:

Step 1 Verify that ports configured across all communication services is unique.

Fault Details

fltVnicFcIfVsanUnresolvable

Fault Code: F10000388

Message

The named vsan [name] for vHBA [name] cannot be resolved

Explanation

This fault (warning) occurs when a Service Profile’s vnic interface (SAN) is unresolvable.

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

Step 2 Create the named vsan.

Fault Details

fltVnicEtherIfVlanUnresolvable

Fault Code: F10000389

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.

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

fltVnicEtherIfVlanAccessFault

Fault Code: F10000390

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.

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

fltVnicEtherIfVlanSyncFault

Fault Code: F10000391

Message

The named vlan [name] for vNIC [name] cannot be pushed to UCSM

Explanation

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.

Recommended Action

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.

Fault Details

fltVnicFcIfVsanSyncFault

Fault Code: F10000392

Message

The named vsan [name] for vHBA [name] cannot be pushed to UCSM

Explanation

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.

Recommended Action

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.

Fault Details

fltVnicEtherUnassociatedVnicIfFault

Fault Code: F10000393

Message

[name] isn’t associated with any VLAN

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

fltVnicFcUnassociatedVnicIfFault

Fault Code: F10000394

Message

[name] isn’t associated with any VSAN

Explanation

There is no vsan associated with this vhba.

Recommended Action

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.

Fault Details

fltLsSPMetaUngrouped-domain

Fault Code: F10000396

Message

Unable to resolve Vsans/vlans. Service profile deployed on [serverDn] failed due to an ungrouped domain.

Explanation

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.

Recommended Action

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

Fault Details

fltLsServerFailed

Fault Code: F10000397

Message

Service profile [name] failed

Explanation

Server has failed. This fault typically occurs if the adapter power on self-test results in major and critical errors.

Recommended Action

If you see this fault, take the following actions:

Step 1 Check the POST results for the server. In Cisco 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.

Fault Details

fltLsServerDiscoveryFailed

Fault Code: F10000398

Message

Service profile [name] discovery failed

Explanation

The shallow discovery that occurs when the server associated with service profile fails. If the server is up and the data path is working, this fault typically occurs as a result of one of the following issues:

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

a. Check the operational state of the server.

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

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

Fault Details

fltLsServerConfigFailure

Fault Code: F10000399

Message

Service profile [name] configuration failed due to [configQualifier]

Explanation

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.

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 If the server is associated or undiscovered, do one of the following:

– Discover the server.

– Disassociate the server from the current service profile.

– Select another server to associate with the service profile.

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

Step 5 If the server does not meet the requirements of the service profile, do one of the following:

– Modify the service profile to match the server.

– Select another server that does meet the requirements to associate with the service profile.

Step 6 If you can verify that the server meets the requirements of the service profile, create a show tech-support file and contact Cisco TAC.

Fault Details

fltLsServerMaintenanceFailed

Fault Code: F10000400

Message

Service profile [name] maintenance failed

Explanation

Cisco UCS Manager currently does not use this fault.

Recommended Action

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

Fault Details

fltLsServerRemoved

Fault Code: F10000401

Message

Service profile [name] underlying resource removed

Explanation

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:

• The server has been physically removed from the slot.
• The server is not available.

Recommended Action

If you see this fault, take the following actions:

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

Step 2 If the server was not removed, remove and reinsert the server.NOTE: If the server is operable, this action can be disruptive to current operations.

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

Fault Details

fltLsServerInaccessible

Fault Code: F10000402

Message

Service profile [name] cannot be accessed

Explanation

Cisco UCS Manager cannot communicate with the CIMC on the server. This fault typically occurs as a result of one of the following issues:

• The server port or ports have failed.
• The I/O module is offline.
• The BMC has failed.

Recommended Action

If you see this fault, take the following actions:

Step 1 If Cisco 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.

Fault Details

fltLsServerAssociationFailed

Fault Code: F10000403

Message

Service profile [name] association failed for [pnDn]

Explanation

The service profile could not be associated with the server. This fault typically occurs because Cisco UCS Manager cannot communicate with one or more of the following:

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

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltLsComputeBindingAssignmentRequirementsNotMet

Fault Code: F10000404

Message

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

Explanation

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

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

Recommended Action

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

Fault Details

fltLsServerUnassociated

Fault Code: F10000405

Message

Service profile [name] is not associated

Explanation

The service profile has not yet been associated with a server or a server pool. This fault typically occurs as a result of one of the following issues:

• There is no acceptable server in the server pool.
• The association failed.

Recommended Action

If you see this fault, take the following actions:

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

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

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

Fault Details

fltLsServerServer-unfulfilled

Fault Code: F10000406

Message

Server [pnDn] does not fulfill Service profile [name] due to [configQualifier]

Explanation

The server no longer meets the qualification requirements of the service profile. This fault typically occurs as a result of one of the following issues:

• The server has been physically changed.
• A required component of the server has failed.

Recommended Action

If you see this fault, take the following actions:

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

Step 2 If the server inventory does not match the service profile qualifications, do one of the following:

– Associate the server with a different service profile.

– Ensure the server has sufficient resources to qualify for the current service profile.

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

Fault Details

fltLsmaintMaintPolicyUnresolvableScheduler

Fault Code: F10000407

Message

Schedule [schedName] referenced by maintenance policy [name] does not exist

Explanation

The schedule that is referenced by the maintenance policy does not exist. This fault typically occurs as a result of one of the following issues:

• The schedule does not exist.
• The schedule was deleted.

Recommended Action

If you see this fault, take the following actions:

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.

Fault Details

fltComputePoolEmpty

Fault Code: F10000557

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

fltComputeAOperationRemote-operation-fail

Fault Code: F10000558

Message

Remote opearation failed in UCSM. Error Code: [[remoteErrorCode]]. [remoteErrorDescr]

Explanation

This fault typically occurs when a remote physical operation performed on UCS Central encounters an error condition.

Recommended Action

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.

Fault Details

fltLsIssuesConfigFailure

Fault Code: F10000571

Message

Service profile [name] configuration failed due to [iscsiConfigIssues] [networkConfigIssues] [serverConfigIssues] [storageConfigIssues] [vnicConfigIssues]

Explanation

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.

Recommended Action

If you see this fault, take the following actions:

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

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

Step 3 If the server is associated or undiscovered, do one of the following:

– Discover the server.

– Disassociate the server from the current service profile.

– Select another server to associate with the service profile.

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

Step 5 If the server does not meet the requirements of the service profile, do one of the following:

– Modify the service profile to match the server.

– Select another server that does meet the requirements to associate with the service profile.

Step 6 If you can verify that the server meets the requirements of the service profile, create a show tech-support file and contact Cisco TAC.

Fault Details

fltVnicFaultVlanSyncFault

Fault Code: F10000572

Message

The named vXan [name] cannot be pushed to UCSM. UCSM Message - [descr]

Explanation

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.

Recommended Action

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.

Fault Details