PowerStore: PowerStoreX-SSH disabled may lead to node failure
Summary: On a PowerStoreX cluster, if SSH is either stopped or disabled during the PowerStoreX boot process, a node failure may occur.
Symptoms
Cause
-
PowerStoreX requires SSH connectivity with its hypervisor and peer hypervisor for proper functionality.
-
Stopping SSH while the cluster is running leads to no major impact to the system except for the following alert:
Alert Code: 0x0030ba02 Description: Polling Failed for internal M.2 module in slot <undefined>
-
If SSH is stopped or disabled during the boot process of the PowerStoreX VM, this may lead the PowerStoreX VM to enter service mode and raise the following alerts:
Alert Code: 0x00400107 Description: Node <A/B> entered Service Mode
Alert Code: 0x00304203 Description: Node has stopped
Alert Code: 0x00304404 Description: The node was deactivated (disabled) by user request
Alert Code: 0x0030ba02 Description: Polling Failed for internal M.2 module in slot <undefined> -
If there is an unplanned ESX reboot on the ESX that runs System Manager, and SSH is disabled during boot, system alerts stop functioning on appliance.
Resolution
Workaround:
-
Always enable SSH and start it on both ESXi hosts on the PowerStoreX.
- Verify that SSH is enabled and started using the following procedure:
- Connect to vCenter > ESXi > ESXi Configuration.
- Select Services > SSH.
- Ensure that the SSH service is set up as follows:
- SSH service is started.
- SSH service is configured as "Start and Stop with host" to ensure that the service is started upon ESXi reboot.
-
If the node enters service mode, contact technical support for further assistance.