Diagnostic System Warning -- Help

[C_V]

Jan 7 12:38:07 vfauh427 vmunix: DIAGNOSTIC SYSTEM WARNING:
Jan 7 12:38:07 vfauh427 vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
Jan 7 12:38:07 vfauh427 vmunix: in stm to start it.
Jan 7 12:38:07 vfauh427 vmunix: If the diaglogd daemon is active, use the logtool utility in stm
Jan 7 12:38:07 vfauh427 vmunix: to determine which I/O subsystem is logging excessive errors.
Jan 7 12:38:08 vfauh427 vmunix: DIAGNOSTIC SYSTEM WARNING:
Jan 7 12:38:08 vfauh427 vmunix: The diagnostic logging facility is no longer receiving excessive
Jan 7 12:38:08 vfauh427 vmunix: errors from the I/O subsystem. 2 I/O error entries were lost.
Jan 7 12:38:13 vfauh427 vmunix: The diagnostic logging facility has started receiving excessive
Jan 7 12:38:13 vfauh427 vmunix: errors from the I/O subsystem. I/O error entries will be lost
Jan 7 12:38:13 vfauh427 vmunix: until the cause of the excessive I/O logging is corrected.
Jan 7 12:38:13 vfauh427 vmunix: DIAGNOSTIC SYSTEM WARNING:
Jan 7 12:38:13 vfauh427 vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
Jan 7 12:38:13 vfauh427 vmunix: in stm to start it.
Jan 7 12:38:13 vfauh427 vmunix: If the diaglogd daemon is active, use the logtool utility in stm
Jan 7 12:38:13 vfauh427 vmunix: to determine which I/O subsystem is logging excessive errors.
Jan 7 12:38:14 vfauh427 vmunix: DIAGNOSTIC SYSTEM WARNING:
Jan 7 12:38:14 vfauh427 vmunix: The diagnostic logging facility is no longer receiving excessive
Jan 7 12:38:14 vfauh427 vmunix: errors from the I/O subsystem. 2 I/O error entries were lost.
Jan 7 12:38:19 vfauh427 vmunix: The diagnostic logging facility has started receiving excessive
Jan 7 12:38:19 vfauh427 vmunix: errors from the I/O subsystem. I/O error entries will be lost
Jan 7 12:38:19 vfauh427 vmunix: until the cause of the excessive I/O logging is corrected.
Jan 7 12:38:19 vfauh427 vmunix: DIAGNOSTIC SYSTEM WARNING:
Jan 7 12:38:19 vfauh427 vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
Jan 7 12:38:19 vfauh427 vmunix: in stm to start it.
Jan 7 12:38:19 vfauh427 vmunix: If the diaglogd daemon is active, use the logtool utility in stm
Jan 7 12:38:19 vfauh427 vmunix: to determine which I/O subsystem is logging excessive errors.
Jan 7 12:38:20 vfauh427 vmunix: DIAGNOSTIC SYSTEM WARNING:
Jan 7 12:38:20 vfauh427 vmunix: The diagnostic logging facility is no longer receiving excessive
Jan 7 12:38:20 vfauh427 vmunix: errors from the I/O subsystem. 2 I/O error entries were lost.


- Hi guys we received that above error daily and keeps rearming, unfortunately i do not know how to use stm and cant find any good materials to learn it

- After searching some say that it could be related to a fiber channel, in which one of the fiber channel of the server has a problem and its being check, if this error is related to the fiber channel how do we verify it?

[Robert-Jan Goossens]

Hi Sigfred,

Could you post or attach the output of

# ioscan -fnCdisk
# ioscan -fnCfc

and have a look at this thread.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=77495

Regards,
Robert-Jan

[Andrew Rutter]

hi,

it could be one of many things really and more info would really help.

what is the server type/model?
what is the os running?
what version of online diagnostics are you running?

the upto date manual for using stm can be found here

http://docs.hp.com/en/5992-5755/index.html

and a quick refence here

http://docs.hp.com/en/diag/stm/stm_qik.pdf

send us some more info and outputs robert-jan has asked for please.

more info may be gained from the error logs in the MP/GSP if the server has one?

Andy