Netservers
1833016 Members
2260 Online
110048 Solutions
New Discussion

Re: Netserver Event Log

 

Netserver Event Log

The netserver event log indicates the follow message:

ScsiSMART: Device failed: host adapter 1, Target ID 0 and LUN 7.

The next message:

ScsiSMART: Device recovered: host adapter 1, Target ID 0 and LUN 7

Both messages by each LUN.

This messages repeats every thirty minutes.

What could be wrong?
2 REPLIES 2
Terri Harris
Honored Contributor

Re: Netserver Event Log

It sounds like you have outdated HP Netserver agents. These agents included a SCSI Smart agent which would erroneously report errors.
Uninstall the existing Netserver agents (from START - PROGRAMS - HP NetServer Agents - Agents Uninstall). Then if you wish to have TopTools agents, install the latest (which does not generate this message) from:
http://www.hp.com/toptools/download/server_agents.html
kris rombauts
Honored Contributor

Re: Netserver Event Log

Hello Diego,

pls have a look at the URL below where i gave the 3 steps to get rid of this error message.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xe18785079106d71190050090279cd0f9,00.html


This error message can still reoccur even with the latest agents because it means that at the scanning interval (which is default 30 minutes) the devices that are present and detected by the agents do not match the device database that has been discovered initially when the agents were first installed (or when the device database was recreated last time).

If your environment is a SAN then the advise is to not load the SCSI smart agent. This agent was never intended to support the fiber channel devices and it does not add any value for those devices. If those devices do not reply in due time, the agent thinks they are not present anymore, hence the error message.

We have asked the division to add this note to the readme file (see under known issues) so that customers are aware it's best not to load this agent. If no SAN environment the above is not applicable.


If no SAN environment then the most probable cause is that either a disk or a logical drive has been removed after the initial device database was been build. In some cases this can also occur if you update a driver and the \scsi port number changes (due to the driver using another TAG value).


HTH
Kris