The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Symptom |
Resolution |
---|---|
Validation fails when the non-clustered VMs are running on the Hyper-V host that is being placed in HX Maintenance Mode. |
Power off the non-clustered VMs or manually migrate them to another node. |
VM Live migration can fail while pausing the Failover cluster node. |
This can be due to several underlying issues related to resources on the Windows host or networking failure between the nodes within the failover cluster. Check the Failover cluster event log to debug the issue. Retry placing the node in HX Maintenance Mode after resolving these issues. |
When the cluster is configured with rf=2 + strict access policy, the cluster resiliency state remains in warning state and the online upgrade fails due to the resiliency state. |
Change strict mode to lenient mode temporarily before upgrading and then change back after the upgrade is complete:
|
Option to upgrade UCS does not appear in HX Connect. |
Verify that all backend services are up and running:
|
During UCS Server Firmware Upgrade, when the node that is not part of the Fail Over Cluster (FOC) being used, then upgrade
fails with |
Remove one of the FOCs from the node which shows as failed WFC and make sure that the working FOC has all the nodes of the cluster. Perform the following on all stCtlVms of every node:
|