- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: A3598A UPS Attention Light Soid Yellow
HPE 9000 and HPE e3000 Servers
1820123
Members
3049
Online
109619
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2003 03:53 AM
06-09-2003 03:53 AM
Came in this morning and the UPS Attention light is solid yellow. Solid alarm was also on. Turned alarm off. What's the problem now? What can I check? Here's the entries sent to syslog.
Jun 3 06:00:00 freoptp1 UPS: 180a181,200
Jun 3 06:00:00 freoptp1 UPS: > 06/02/2003 12:20:33 E SNMP request to node local
host timed out.
Jun 3 06:00:00 freoptp1 UPS: > Node is either down or no SNMP agent installed.
Jun 3 06:00:00 freoptp1 UPS: > 06/02/2003 12:21:06 I Changed a node entry (Firs
t old values).
Jun 3 06:00:00 freoptp1 UPS: > ObjectId 3, ObjectName: localhost:CLIENT, IpAdd
ress: localhost,
Jun 3 06:00:00 freoptp1 UPS: > System: 1.3.6.1.4.1.11.2.3.2.3, NodeType: 3, U
psId: 0, DeviceName: ,
Jun 3 06:00:00 freoptp1 UPS: > Controlled: TRUE, ManageType: 2, NodeStatus: 4
, Client: FALSE,
Jun 3 06:00:00 freoptp1 UPS: > NextUp: 0, MaxActionTime: 0, LastModify: 0, De
lete: FALSE
Jun 3 06:00:00 freoptp1 UPS: > Controlled: TRUE, ManageType: 2, NodeStatus: 3
, Client: FALSE,
Jun 3 06:00:00 freoptp1 UPS: > 06/02/2003 12:21:06 I Changed a node entry (Firs
t old values).
Jun 3 06:00:00 freoptp1 UPS: > NextUp: 0, MaxActionTime: 0, LastModify: 0, De
lete: FALSE
Jun 3 06:00:00 freoptp1 UPS: > Controlled: TRUE, ManageType: 2, NodeStatus: 3
, Client: FALSE,
Jun 3 06:00:00 freoptp1 UPS: > NextUp: 0, MaxActionTime: 0, LastModify: 0, De
lete: FALSE
Jun 3 06:00:01 freoptp1 UPS: > Controlled: TRUE, ManageType: 2, NodeStatus: 4
, Client: FALSE,
Jun 3 06:00:01 freoptp1 UPS: > NextUp: 0, MaxActionTime: 0, LastModify: 0, De
lete: FALSE
Jun 3 06:00:01 freoptp1 UPS: > ObjectId 3, ObjectName: localhost:CLIENT, IpAdd
ress: localhost,
Jun 3 06:19:45 freoptp1 above message repeats 3 times
Jun 3 06:00:01 freoptp1 UPS: > System: 1.3.6.1.4.1.11.2.3.2.3, NodeType: 3, U
psId: 0, DeviceName: ,
Jun 3 06:00:00 freoptp1 UPS: 180a181,200
Jun 3 06:00:00 freoptp1 UPS: > 06/02/2003 12:20:33 E SNMP request to node local
host timed out.
Jun 3 06:00:00 freoptp1 UPS: > Node is either down or no SNMP agent installed.
Jun 3 06:00:00 freoptp1 UPS: > 06/02/2003 12:21:06 I Changed a node entry (Firs
t old values).
Jun 3 06:00:00 freoptp1 UPS: > ObjectId 3, ObjectName: localhost:CLIENT, IpAdd
ress: localhost,
Jun 3 06:00:00 freoptp1 UPS: > System: 1.3.6.1.4.1.11.2.3.2.3, NodeType: 3, U
psId: 0, DeviceName: ,
Jun 3 06:00:00 freoptp1 UPS: > Controlled: TRUE, ManageType: 2, NodeStatus: 4
, Client: FALSE,
Jun 3 06:00:00 freoptp1 UPS: > NextUp: 0, MaxActionTime: 0, LastModify: 0, De
lete: FALSE
Jun 3 06:00:00 freoptp1 UPS: > Controlled: TRUE, ManageType: 2, NodeStatus: 3
, Client: FALSE,
Jun 3 06:00:00 freoptp1 UPS: > 06/02/2003 12:21:06 I Changed a node entry (Firs
t old values).
Jun 3 06:00:00 freoptp1 UPS: > NextUp: 0, MaxActionTime: 0, LastModify: 0, De
lete: FALSE
Jun 3 06:00:00 freoptp1 UPS: > Controlled: TRUE, ManageType: 2, NodeStatus: 3
, Client: FALSE,
Jun 3 06:00:00 freoptp1 UPS: > NextUp: 0, MaxActionTime: 0, LastModify: 0, De
lete: FALSE
Jun 3 06:00:01 freoptp1 UPS: > Controlled: TRUE, ManageType: 2, NodeStatus: 4
, Client: FALSE,
Jun 3 06:00:01 freoptp1 UPS: > NextUp: 0, MaxActionTime: 0, LastModify: 0, De
lete: FALSE
Jun 3 06:00:01 freoptp1 UPS: > ObjectId 3, ObjectName: localhost:CLIENT, IpAdd
ress: localhost,
Jun 3 06:19:45 freoptp1 above message repeats 3 times
Jun 3 06:00:01 freoptp1 UPS: > System: 1.3.6.1.4.1.11.2.3.2.3, NodeType: 3, U
psId: 0, DeviceName: ,
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2003 12:28 AM
06-10-2003 12:28 AM
Solution
Looks liek UPS went into bypass mode. This means that now your systems are receiving power from 'wall receptacle' and not protected by UPS because it is in shutdown state.
Please check your power source. Sometimes when UPS senses heavy overvoltage it turns off and turn off load for protective reason, sometimes it goes into bypass mode. If your power provider will show that power source is clean (at least WAS clean at the time UPS got offline) then call HP for troubleshooting.
Meanwhile your power provider is looking at his power source you can go to servers this UPS is protecting and check their logs to see if they were rebooted. If yes, note reboot time and ask power provider what's happened then
Eugeny
Please check your power source. Sometimes when UPS senses heavy overvoltage it turns off and turn off load for protective reason, sometimes it goes into bypass mode. If your power provider will show that power source is clean (at least WAS clean at the time UPS got offline) then call HP for troubleshooting.
Meanwhile your power provider is looking at his power source you can go to servers this UPS is protecting and check their logs to see if they were rebooted. If yes, note reboot time and ask power provider what's happened then
Eugeny
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP