topic Re: hwmgr status comp (critical) in Operating System - Tru64 Unix

hwmgr status comp (critical)

Ivan Ferreira — Thu, 30 Mar 2006 16:34:11 GMT

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?

Re: hwmgr status comp (critical)

Aaron Biver_2 — Thu, 30 Mar 2006 22:05:52 GMT

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.

Re: hwmgr status comp (critical)

Harmanjit_1 — Fri, 31 Mar 2006 01:19:10 GMT

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.

Re: hwmgr status comp (critical)

Ivan Ferreira — Fri, 31 Mar 2006 08:10:23 GMT

Thanks for the responses.

Information also available on:

Online Addition and Removal

man hwmgr_ops