Redundant Ups Status; Sles 10 Agent Does Not Autostart After Power Fail Or Reboot; Servers Running Windows Server® 2003 Do Not Restart - HP UPS User Manual

Verify that the correct IP address, host name, communications port, or serial path is entered for the
2.
management server that should communicate with the agent. To allow any management server to
connect to the agent, select Any Server from the dropdown box in Windows, or enter an asterisk (*)
where prompted for Linux or HP-UX.
For a nonredundant configuration, be sure that no second management server is specified for
3.
communication with the agent.
Close the configuration program and check the Attach Devices screen
4.
page 69) to verify that the redundant UPS (RU) column is grayed out.

Redundant UPS status

The following table describes the possible combinations for the redundant UPS status icons found on the
Attached Devices screen
Events
Both UPSs are on utility power
Management Server 1 UPS is on
battery power and redundant power is
lost
Management Server 1 UPS has shut
down and redundant communication is
lost
Management Server 1 UPS has lost
communication and redundant
communication is lost
Two UPSs are on battery power and
redundant power is lost
Two UPSs have shut down
Both UPSs have lost communication
SLES 10 agent does not autostart after power fail or
reboot
Action: Follow the instructions for installing the agent on SLES 10 (on page 37).
Servers running Windows Server® 2003 do not
restart
Symptom: Servers running Windows Server® 2003 do not restart upon power restoration following a
power fail shutdown.
Possible Cause: This is a known Windows Server® 2003 behavior on some servers.
("Attached Devices menu" on page 69).
Agent status
-
("Attached Devices
Management Management Server
Server 1 status 2 status
RU AS RU
- -
- - -
menu" on
AS
-
Troubleshooting 98