Event Monitoring Service Event Notification

[Francois Bariselle_3]

Hi all,

I have Theses messages in mail root every day !!!

HP-UX10.20 HP9000 S800 K580

Someone have solution?
Help please.

Thanks in advance.

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Mon Nov 3 13:46:43 2003

quebec sent Event Monitor notification information:

/storage/events/disks/default/10_0.5.0 is >= 3.
Its current value is CRITICAL(5).

Event data from monitor:

Event Time : Mon Nov 3 13:46:42 2003
Hostname : quebec IP Address : 192.168.3.246
Event Id : 0x003fa6a29200000001 Monitor : disk_em
Event # : 100172 Event Class : I/O
Severity : CRITICAL

Disk at hardware path 10/0.5.0 :

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Mon Nov 3 13:46:42 2003

quebec sent Event Monitor notification information:

/storage/events/disks/default/10_0.4.0 is >= 3.
Its current value is CRITICAL(5).

Event data from monitor:

Event Time : Mon Nov 3 13:46:42 2003
Hostname : quebec IP Address : 192.168.3.246
Event Id : 0x003fa6a29200000000 Monitor : disk_em
Event # : 100172 Event Class : I/O
Severity : CRITICAL

Disk at hardware path 10/0.4.0 :

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Mon Nov 3 13:46:43 2003

quebec sent Event Monitor notification information:

/storage/events/disks/default/10_0.6.0 is >= 3.
Its current value is CRITICAL(5).

Event data from monitor:

Event Time : Mon Nov 3 13:46:43 2003
Hostname : quebec IP Address : 192.168.3.246
Event Id : 0x003fa6a29300000000 Monitor : disk_em
Event # : 100172 Event Class : I/O
Severity : CRITICAL

Disk at hardware path 10/0.6.0 :

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Mon Nov 3 13:46:44 2003

quebec sent Event Monitor notification information:

/storage/events/disks/default/10_12_5.2.0 is >= 3.
Its current value is CRITICAL(5).

Event data from monitor:

Event Time : Mon Nov 3 13:46:44 2003
Hostname : quebec IP Address : 192.168.3.246
Event Id : 0x003fa6a29400000000 Monitor : disk_em
Event # : 100172 Event Class : I/O
Severity : CRITICAL

Disk at hardware path 10/12/5.2.0 :

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Mon Nov 3 14:46:46 2003

quebec sent Event Monitor notification information:

/storage/events/disks/default/8_0.4.0 is >= 3.
Its current value is CRITICAL(5).

Event data from monitor:

Event Time : Mon Nov 3 14:46:46 2003
Hostname : quebec IP Address : 192.168.3.246
Event Id : 0x003fa6b0a600000000 Monitor : disk_em
Event # : 100172 Event Class : I/O
Severity : CRITICAL

Disk at hardware path 8/0.4.0 :

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Mon Nov 3 14:46:44 2003

quebec sent Event Monitor notification information:

/storage/events/disks/default/8_0.0.0 is >= 3.
Its current value is CRITICAL(5).

Event data from monitor:

Event Time : Mon Nov 3 14:46:44 2003
Hostname : quebec IP Address : 192.168.3.246
Event Id : 0x003fa6b0a400000000 Monitor : disk_em
Event # : 100172 Event Class : I/O
Severity : CRITICAL

Disk at hardware path 8/0.0.0 :

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Mon Nov 3 14:46:47 2003

quebec sent Event Monitor notification information:

/storage/events/disks/default/8_0.5.0 is >= 3.
Its current value is CRITICAL(5).

Event data from monitor:

Event Time : Mon Nov 3 14:46:47 2003
Hostname : quebec IP Address : 192.168.3.246
Event Id : 0x003fa6b0a700000000 Monitor : disk_em
Event # : 100172 Event Class : I/O
Severity : CRITICAL

Disk at hardware path 8/0.5.0 :

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Mon Nov 3 14:46:45 2003

quebec sent Event Monitor notification information:

/storage/events/disks/default/8_0.1.0 is >= 3.
Its current value is CRITICAL(5).

Event data from monitor:

Event Time : Mon Nov 3 14:46:45 2003
Hostname : quebec IP Address : 192.168.3.246
Event Id : 0x003fa6b0a500000000 Monitor : disk_em
Event # : 100172 Event Class : I/O
Severity : CRITICAL

Disk at hardware path 8/0.1.0 :

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Mon Nov 3 14:46:45 2003

quebec sent Event Monitor notification information:

/storage/events/disks/default/8_0.2.0 is >= 3.
Its current value is CRITICAL(5).

Event data from monitor:

Event Time : Mon Nov 3 14:46:45 2003
Hostname : quebec IP Address : 192.168.3.246
Event Id : 0x003fa6b0a500000001 Monitor : disk_em
Event # : 100172 Event Class : I/O
Severity : CRITICAL

Disk at hardware path 8/0.2.0 :

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Mon Nov 3 14:46:47 2003

quebec sent Event Monitor notification information:

/storage/events/disks/default/8_0.6.0 is >= 3.
Its current value is CRITICAL(5).

Event data from monitor:

Event Time : Mon Nov 3 14:46:47 2003
Hostname : quebec IP Address : 192.168.3.246
Event Id : 0x003fa6b0a700000001 Monitor : disk_em
Event # : 100172 Event Class : I/O
Severity : CRITICAL

Disk at hardware path 8/0.6.0 :

>------------ Event Monitoring Service Event Notification ------------<

[Steven E. Protter]

Take a look at /dev/dsk and find a disk driver equivalent to the disk hardware path.

There will be one.

We get one like this when we connect a fiber card to our disk array and do not assign a disk to lun0.

The card detects the disk array, thinks its a disk. Its not a disk, doesn't function like one and generates the ems error.

As silly as this sounds, unless that path points to a physical disk, you can safely ignore it.

SEP

[Francois Bariselle_3]

More informations for you...

Storage devices HW Path Interface
SEAGATE ST318203LC 17358 Mb 8/0.0.0 GSC add-on Fast/Wide SCSI
SEAGATE ST318203LC 17366 Mb 8/0.6.0 GSC add-on Fast/Wide SCSI
SEAGATE ST318203LC 17366 Mb 8/0.5.0 GSC add-on Fast/Wide SCSI
SEAGATE ST318275LC 17366 Mb 8/0.4.0 GSC add-on Fast/Wide SCSI
SEAGATE ST318275LC 17366 Mb 8/0.2.0 GSC add-on Fast/Wide SCSI
SEAGATE ST318275LC 17366 Mb 8/0.1.0 GSC add-on Fast/Wide SCSI
SEAGATE ST34371W 4095 Mb 10/0.6.0 GSC built-in Fast/Wide SCSI
SEAGATE ST34572WD 4340 Mb 10/0.5.0 GSC built-in Fast/Wide SCSI
SEAGATE ST34573WD 4340 Mb 10/0.4.0 GSC built-in Fast/Wide SCSI

Other Storage devices HW Path Interface
TOSHIBA CD-ROM XM-5701TA 10/12/5.2.0 Built-in SCSI
HP C1537A (TAPE DDS3) 10/12/5.0.0 Built-in SCSI

[Francois Bariselle_3]

Other informations...

Disk layout
LVM disk Device file HW Addr size vol. grp
SEAGATE ST34371W /dev/dsk/c1t6d0 10/0.6.0 4095 /dev/vg00
SEAGATE ST318203LC /dev/dsk/c0t0d0 8/0.0.0 17358 /dev/vg01
SEAGATE ST318275LC /dev/dsk/c0t1d0 8/0.1.0 17366 /dev/vg01
SEAGATE ST318275LC /dev/dsk/c0t2d0 8/0.2.0 17366 /dev/vg02
SEAGATE ST318275LC /dev/dsk/c0t4d0 8/0.4.0 17366 /dev/vg03

File System layout
LVM Device file mount point size fs type
/dev/vg00:
/dev/vg00/lvol1 /stand 48 hfs
/dev/vg00/lvol2 swap 1024
/dev/vg00/lvol3 / 128 vxfs
/dev/vg00/lvol4 /home 500 vxfs
/dev/vg00/lvol5 /opt 300 vxfs
/dev/vg00/lvol6 /tmp 128 vxfs
/dev/vg00/lvol7 /usr 632 vxfs
/dev/vg00/lvol8 /var 504 vxfs
/dev/vg00 unallocated 828

[Andrew Merritt_2]

What version of the OnlineDiags do you have installed? The latest for 10.20 is A.29.00 (see http://www.docs.hp.com/hpux/onlinedocs/diag/stm/stm_upd.htm#table) and the latest patch is PHSS_29444. These should be installed if not already.

This event indicates that device has failed to respond to a query.
From the event description (http://www.docs.hp.com/hpux/onlinedocs/diag/ems/scsi.htm#100172):

Probable Cause / Recommended Action: If the device is a removable medium, this message is informational, indicating that I/O was attempted when a diskette was not inserted in the drive. Place a diskette in the drive before trying to use it.
Alternatively, the device may be in a state where it could not process this, or any, request. Cycle power to the device.
Alternatively, there could be more than one device having the same address on the SCSI bus. Make all the addresses on the SCSI bus unique.
Alternatively, one or both of the terminators on the SCSI bus may be missing. Install the terminators in their proper locations at the ends of the SCSI bus.
Alternatively, the SCSI cable may have become detached from the device. Re-attach the cable.
Alternatively, the SCSI cable may have failed. Replace it.
Alternatively, if another entry corresponding to this condition appears in the log for this device, the device has experienced a hardware failure. Repair or replace the device, as necessary.


There was a similar problem seen before where it turned out one of the disks was responding slowly, and the way this was detected was by running the 'diskinfo' command for each disk and observing how long that took, or if it fails to complete. Replacing the slow disk in that case fixed the problem, so it would be worth seeing if any of the disks has a noticeably slow response.

Is there any more detail in the events logged to /var/opt/resmon/log/event.log?

Andrew Merritt