HP Pro UPS 500 240V HP Power Protector User Guide - Page 129

Notification window is not available on SLES 10, On battery alarm, On boost alarm, Overload alarm

Get HP Pro UPS 500 240V PDF manuals and user guides View all HP Pro UPS 500 240V manuals
Add to My Manuals
Save this manual to your list of manuals

Page 129 highlights

Notification window is not available on SLES 10 Symptom: The notification window does not appear on SLES 10. Possible cause: This version of the operating system does not contain the required GTK 2.10 dependency for notification functionality. Action: Update to a SLES operating system that supports GTK 2.10. On battery alarm Action: The UPS continues to run on battery power until the battery is completely discharged (or until utility power is restored), unless the shutdown parameters specify to power down all of the UPS load segments. On boost alarm Possible Cause: The input voltage is too low for the UPS. The UPS boosts the voltage up to acceptable limits. Action: For information on Boost mode, refer to the UPS documentation. On buck alarm Possible Cause: The input voltage is too high for the UPS. The UPS bucks the voltage down to acceptable limits. Action: For information on Buck mode, refer to the UPS documentation. Overload alarm Possible Cause: The device load has exceeded the UPS power rating. Action: Verify all equipment is drawing within the rated requirements. If necessary, reduce the equipment connected to the UPS. The UPS might need to be reset. Receiving a security error Symptom: Security error: Domain Name mismatch message when trying to browse with SSL. Possible Cause: The IP address or server name has changed. Action: Stop the service, delete the certificate file, and restart the service. 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. Troubleshooting 129

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
Troubleshooting 129
Notification window is not available on SLES 10
Symptom:
The notification window does not appear on SLES 10.
Possible cause:
This version of the operating system does not contain the required GTK 2.10 dependency for
notification functionality.
Action:
Update to a SLES operating system that supports GTK 2.10.
On battery alarm
Action:
The UPS continues to run on battery power until the battery is completely discharged (or until utility
power is restored), unless the shutdown parameters specify to power down all of the UPS load segments.
On boost alarm
Possible Cause:
The input voltage is too low for the UPS. The UPS boosts the voltage up to acceptable limits.
Action:
For information on Boost mode, refer to the UPS documentation.
On buck alarm
Possible Cause:
The input voltage is too high for the UPS. The UPS bucks the voltage down to acceptable
limits.
Action:
For information on Buck mode, refer to the UPS documentation.
Overload alarm
Possible Cause:
The device load has exceeded the UPS power rating.
Action:
Verify all equipment is drawing within the rated requirements. If necessary, reduce the equipment
connected to the UPS. The UPS might need to be reset.
Receiving a security error
Symptom:
Security error: Domain Name mismatch message when trying to browse with SSL.
Possible Cause:
The IP address or server name has changed.
Action:
Stop the service, delete the certificate file, and restart the service.
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.