NOTE: The troubleshooting items below are only applicable when HPE SimpliVity support is enabled, and are to be used along with VMware Troubleshooting.
|
|
NOTE: The troubleshooting items below are only applicable when HPE SimpliVity support is enabled, and are to be used along with VMware Troubleshooting. |
If the connection to your HPE SimpliVity OmniStack Virtual Controller (OVC) VMs is lost, the following log messages and exceptions may appear in the error.log:
"One or more OmniStack Virtual Controllers are offline. We cannot apply configuration for offline controllers."
"Could not connect to the Cluster over the network."
"Connection error due to invalid login credentials."
"Authentication error occurred when connecting to OmniStack Virtual Controller [OVC]. Please verify that the correct credentials have been provided."
"A connection error occurred when connecting to OmniStack Virtual Controller [OVC]. Please verify that the connection details are correct and that the cluster is accessible from the network PowerChute is installed in."
Ensure the correct credentials are provided via the PowerChute Setup wizard, or the Communication Settings screen. Additionally, check that all OVCs in your HPE SimpliVity Cluster are powered on and have the correct IP addresses assigned, and provide a sufficient Shutdown Duration value to allow the Cluster Services to start successfully,
After vCenter Server is restarted, VMware Tools installed on the VM incorrectly displays the same IP address for all OmniStack Virtual Controller VMs in the HPE SimpliVity Cluster. When this issue occurs, OmniStack Virtual Controller VMs cannot be shut down and no error message is logged to the Event Log. PowerChute may also report that it cannot communicate with the OmniStack Virtual Controller VMs as PowerChute cannot connect to the IP addresses reported by VMware Tools.
To resolve the issue, restart the OmniStack Virtual Controller VMs one at a time using the HPE vSphere plugin options:
The correct IP addresses will be displayed after the OVC VMs have restarted.
To successfully shut down HPE SimpliVity OmniStack Virtual Controller (OVC) VMs, HA Compliance must be reached and the first OVC VM must have completed its shut down process before the subsequent OVC VMs in the Cluster can be powered off.
Also ensure that you configure a sufficient duration to successfully shut down all OmniStack Virtual Controller VMs in the Cluster.
The errors below are written to the PowerChute Event Log:
"OmniStack Virtual Controller [OVC] did not shut down gracefully within the configured duration. Please find more information in the Troubleshooting section of the PowerChute User Guide."
"Insufficient time configured for OVC shutdown. Please increase OVC Shutdown Duration."
If the OmniStack Virtual Controller VMs in the Cluster cannot be started, ensure that you configure a sufficient duration to successfully start up all OmniStack Virtual Controller VMs in the Cluster.
The error below is written to the PowerChute Event Log:
"OmniStack Virtual Controller [OVC] has not started."