HP UPS Network Module - Manual (Page 78)

Troubleshooting 78
Troubleshooting
Client communication failure with HP UPS Network
Module in a VMware operating system
Possible Cause: The Client was installed on the guest operating system.
Action: Install the Client on the host VMware operating system (for ESX) or on VIMA/VMA (for ESXi). Do not
install the Client on the guest operating system. When the Client receives a shutdown notification from the HP
UPS Network Module, it sends an operating system shutdown command to the VMware host operating
system, and then the VMware shuts down the guest operating system based on a preset configuration.
Client server is not restarting
Symptom: Utility power has been restored, the UPS and its load segments are powered on, but the Client
server does not restart.
Possible Cause: The “Automatic Power ON” server setup setting might be disabled.
Action: In the server system BIOS, change the setting for Automatic Power ON to "Enabled."
Clients cannot communicate with UPS after swapping
HP UPS Network Module with another UPS
Possible Cause: The HP UPS Network Module and Clients are configured with an old power source.
Action: Reconfigure the HP UPS Network Module power source, and then reconfigure the Client power
source.
Failure to communicate with the serial or USB ports
Symptom: There is a failure to communicate with the serial or USB ports while upgrading the UPS or
CommBoard firmware.
Possible Cause: A UPS Network Module is installed in the UPS minislot.
Action: Remove the UPS Network Module from the UPS minislot when upgrading the firmware using the serial
or USB ports.
Forgot login password
Action: To reset the login password, use the supplied serial cable to connect to the UPS Network Module
through a terminal emulation programs, such as HyperTerminal, with the following parameters: