- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: hwmgr status comp (critical)
Operating System - Tru64 Unix
1748165
Members
4232
Online
108758
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
Forums
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
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
тАО03-30-2006 08:34 AM
тАО03-30-2006 08:34 AM
When I run hwmgr status component on some of my servers, I get this output:
STATUS ACCESS INDICT
HWID: HOSTNAME SUMMARY STATE STATE LEVEL NAME
------------------------------------------------------------------------------
200: HOSTNAME critical online available high CPU0
201: HOSTNAME critical online available high CPU1
What this means? Why is critical? And what is the Indict Level?
STATUS ACCESS INDICT
HWID: HOSTNAME SUMMARY STATE STATE LEVEL NAME
------------------------------------------------------------------------------
200: HOSTNAME critical online available high CPU0
201: HOSTNAME critical online available high CPU1
What this means? Why is critical? And what is the Indict Level?
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-30-2006 02:05 PM
тАО03-30-2006 02:05 PM
Solution
Ivan
Most likely, WSEA or its predecessor (Compaq Analyze) is installed to monitor the system, and it detected one or more hardware errors that make it think these two cpus might be going bad. (try "whereis wsea; whereis ca" to verify whther wsea or compaq analyze are installed)
WSEA has logic to indict hardware components like this, so this is the most likely explanation. Its logic is not infallible, though.
You should have the /var/adm/binary.errlog analyzed using the wsea utility. If you have a service contract, they will take care of this.
If there is no service contract, it would probably be wise to look into the errors, and possibly remove one or more of the cpus before you start seeing real problems. In that case, I can give you a summary of wsea commands that would give you more info.
Most likely, WSEA or its predecessor (Compaq Analyze) is installed to monitor the system, and it detected one or more hardware errors that make it think these two cpus might be going bad. (try "whereis wsea; whereis ca" to verify whther wsea or compaq analyze are installed)
WSEA has logic to indict hardware components like this, so this is the most likely explanation. Its logic is not infallible, though.
You should have the /var/adm/binary.errlog analyzed using the wsea utility. If you have a service contract, they will take care of this.
If there is no service contract, it would probably be wise to look into the errors, and possibly remove one or more of the cpus before you start seeing real problems. In that case, I can give you a summary of wsea commands that would give you more info.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-30-2006 05:19 PM
тАО03-30-2006 05:19 PM
Re: hwmgr status comp (critical)
Hi,
I had experienced the same problem.
You can try following command
# hwmgr -unindict -id 200
# hwmgr -unindict -id 201
200 and 201 is CPU id
Sometimes alpha keeps the status of CPU inthis state if any crash has happened.
I had experienced the same problem.
You can try following command
# hwmgr -unindict -id 200
# hwmgr -unindict -id 201
200 and 201 is CPU id
Sometimes alpha keeps the status of CPU inthis state if any crash has happened.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-31-2006 12:10 AM
тАО03-31-2006 12:10 AM
Re: hwmgr status comp (critical)
Thanks for the responses.
Information also available on:
Online Addition and Removal
man hwmgr_ops
Information also available on:
Online Addition and Removal
man hwmgr_ops
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP