Connection to HX Connect lost after pre-upgrade step from HX 3.5(2g) to HX 4.0(2a). During the upgrade, if there is an expired certificate in the upgrade source version, the browser will log user out after pre-upgrade step. This is accepted secure behavior since the certificate of the server has changed after pre-upgrade.

Refresh the browser and login again.

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:

sysmtool --ns cluster --cmd accesspolicy --accesspolicy=lenient

Re-log back in again. This will generate CSRF tokens to validate all future requests between the client and server.

Option to upgrade UCS does not appear in HX Connect.

Verify that all backend services are up and running:

1. Verify that stNodeMgr is running on Hyper-V clusters.

2. Verify that stUpgradeSvc is running on Hyper-V clusters.

3. If any of the services are stopped, start them by running start <service-name>, where <service-name> is stNodeMgr or stMgr or stUpgradeSvc.

During UCS Server Firmware Upgrade, when the node that is not part of the Fail Over Cluster (FOC) being used, then upgrade fails with Pause HyperV Host: Suspend-ClusterNode -Drain. An error occurred pausing node 'node not in FOC'.

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:

Run

1) /bin/hxdpservices stop

2) /bin/hxdpservices start

Wait for 5 minutes

Start UCS Server Firmware upgrade again