DIAGNOSTIC SYSTEM WARNING:

[Kishore Vinjam]

I am recieving the following message on one of the hp-ux 11.0 servers, however the system is running fine.

vmunix: DIAGNOSTIC SYSTEM WARNING:
vmunix: The diagnostic logging facility has started receiving excessive
vmunix: The diagnostic logging facility has started receiving excessive
vmunix: errors from the I/O subsystem. I/O error entries will be lost
vmunix: errors from the I/O subsystem. I/O error entries will be lost
vmunix: until the cause of the excessive I/O logging is corrected.
vmunix: until the cause of the excessive I/O logging is corrected.
vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
vmunix: in stm to start it.
vmunix: in stm to start it.
vmunix: If the diaglogd daemon is active, use the logtool utility in stm
vmunix: If the diaglogd daemon is active, use the logtool utility in stm
vmunix: to determine which I/O subsystem is logging excessive errors.
vmunix: to determine which I/O subsystem is logging excessive errors.

Could somebody help me in tracing the reason for this problem.

[RAC_1 · Accepted solution]

Do a dmesg on system and check what exactly is causing the problem.

Also check /var/opt/resmon/log/event.log

Anil

[Steven E. Protter]

A common cause of this is disk/scsi device failure.

mstm excrcize can help you determine what device is in trouble.

SEP

[Kishore Vinjam]

I checked in the dmesg, even there i get only this message.

DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.

[Kishore Vinjam]

Sorry, i missed out in last message. I had also checked /var/opt/resmon/log/event.log.
There is no error/warning notified in it.

Thanks,
Kishore.

[RAC_1]

Start STM and check what is causing problem.

cstm, mstm or xstm.

Anil

[Kishore Vinjam]

Thanks a lot. I had started stm and see that the following devices are in YELLOW color with status Information incomplete.

EMC Array -- 0/10/0/0.8.0.255.1.13.0
EMC Array -- 1/8/0/0.8.0.255.0.2

I checked them through ioscan and it shows as

ctl 9 0/10/0/0.8.0.255.1.13.0 sctl CLAIMED DEVICE EMC SYMMETRIX
/dev/rscsi/c11t13d0

ctl 10 1/8/0/0.8.0.255.0.2.0 sctl CLAIMED DEVICE EMC SYMMETRIX
/dev/rscsi/c12t2d0

I have a question here, i see it shows device name as /dev/rscsi/*.. what does it imply.

Thanks once again.

[RAC_1]

check if you get diskinfo -v /dev/rscsi/cxtxdx OK? On STM you can get more information on what could be problem with those disks. Could be EMC zoning problem.

Anil

[Kishore Vinjam]

Sorry i missed providing this informaiton earlier. when i run diskinfo on this device it gives the following message.
hpprod04_root:/> diskinfo -v /dev/rscsi/c12t2d0
diskinfo: class ctl not recognized

I dont have much idea about stm, could you please let me know, what all i need to check on stm.

TIA,
Kishore.

[Patrick Wallek]

Once you start xstm you must do the following:

1) Go to the TOOLS menu, under TOOLS, select RUN.
2) When the RUN UTILITY box pops up select 'logtool' and click on OK.
3) When the LOGTOOL UTILITY window opens, go to the FILE menu and select 'SELECT RAW' when the 'LOGTOOL UTILITY: SELECT RAW LOG FILE' window opens it will display a log file name like '/var/stm/logs/os/log??.raw.cur' (where ?? is some number). Just click on OK here. This will read the log file and bring up the 'LOGTOOL UTILITY: VIEW RAW SUMMARY' window which will tell you what device or devices had errors.

The yellow icons don't necessarily mean the device is bad. The above procedure use the will tell you what the diagnostic daemon saw. That is why one of the messages is "use the logtool utility in stm to determine which I/O subsystem is logging excessive errors."

[Kishore Vinjam]

Thanks for the help, I get the following report from logtool. I am ataching it, could you please help me in analysing it.

TIA,

[Naveej.K.A]

hi,
run xstm or mstm,

It will show all the devices the system has in it. select the device, on which the logtool has given error.
Go to tools and then select verify or diagnose and run the test. It will give detailed error relating to the selected subsystem.

regds
naveej

[Kishore Vinjam]

When i clicked on the device that was shown yellow and selected verify from tools, it turned green saying verified sucessfully.

What does this verify do...? any more clues on it please..

TIA.