Events | Agent status | Management | Management | ||
|
| Server 1 status | Server 2 status | ||
|
|
|
|
|
|
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 35).
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.
Action: Refer to the Microsoft® Knowledge Base article 819760.
Shutdowns not functioning when Any Server is configured in a redundant configuration
Action: Reconfigure the management server information on the agent.
1.Open the agent configuration program for your operating system.
o Windows ("Reconfiguring the agent on Windows operating systems" on page 32) o Linux ("Reconfiguring the agent on Linux operating systems" on page 36)
o
2.Enter the correct IP address, host name, communications port, or serial path for the first management server that should communicate with the agent. Do not select Any Server from the dropdown box in Windows or enter an asterisk (*) where prompted for Linux or
3.Enter the correct IP address, host name, communications port, or serial path for the second management server that should communicate with the agent. Do not select Any Server from the dropdown box in Windows or enter an asterisk (*) where prompted for Linux or
4.Close the configuration program.
Silent install did not execute successfully
Action:
Troubleshooting 95