topic Re: EMS SERIOUS alerts in Operating System - HP-UX

EMS SERIOUS alerts

totoperdu — Mon, 18 Sep 2006 10:03:16 GMT

Hello,

i often have this error in the syslog.log:
###
Sep 18 15:24:54 nr0u0253 EMS [3051]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_3_1_0.14.104.0
.0.0.1" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 199950395 -r /storage/events/disks/de
fault/0_3_1_0.14.104.0.0.0.1 -n 199950376 -a
###

The server doesn't seems to be unstable and i don't know what to do for resolv the problem (i don't know how to identify the problem).

the result of the indicated command is:
###
root@nr0u0253# /opt/resmon/bin/resdata -R 199950395 -r /storage/events/disks/default/0_3_1_0.14.104.0.0.0.1 -n 199950376 -a

CURRENT MONITOR DATA:

Event Time..........: Mon Sep 18 15:24:54 2006
Severity............: SERIOUS
Monitor.............: disk_em
Event #.............: 100876
System..............: nr0u0253

Summary:
Disk at hardware path 0/3/1/0.14.104.0.0.0.1 : Software configuration
error

Description of Error:

The device was unsuccessful in processing the current I/O request because
the request contained a logical unit number, which is not supported for
this device. The request was not processed.

Probable Cause / Recommended Action:

The error most likely indicates that the device is not fully supported by
the current driver. This may or may not cause a problem in the operation
of the device.

Additional Event Data:
System IP Address...: 10.92.80.46
Event Id............: 0x450e9e2600000000
Monitor Version.....: B.01.01
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_disk_em.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: 9000/800/rp3440
OS Version......................: B.11.11
STM Version.....................: A.49.00
EMS Version.....................: A.04.20
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100876

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v

Component Data:
Physical Device Path...: 0/3/1/0.14.104.0.0.0.1
Device Class...........: Disk
Inquiry Vendor ID......: DGC
Inquiry Product ID.....: CX700WDUNB
Firmware Version.......: HP03
Serial Number..........: CK200054300574

Product/Device Identification Information:

Logger ID.........: disc30; sdisk
Product Identifier: Disk
Product Qualifier.: DGC CX700WDR5
SCSI Target ID....: 0x00
SCSI LUN..........: 0x01

SCSI Command Data Block:

Command Data Block Contents:
0x0000: 00 00 00 00 00 00

Command Data Block Fields (6-byte fmt):
Command Operation Code...(0x00)..: TEST UNIT READY
Logical Unit Number..............: 0

Hardware Status: (not present in log record).

SCSI Sense Data:

Undecoded Sense Data:
0x0000: 70 00 05 00 00 00 00 0A 00 00 00 00 25 00 00 00
0x0010: 00 00

SCSI Sense Data Fields:
Error Code : 0x70
Segment Number : 0x00
Bit Fields:
Filemark : 0
End-of-Medium : 0
Incorrect Length Indicator : 0
Sense Key : 0x05
Information Field Valid : FALSE
Information Field : 0x00000000
Additional Sense Length : 10
Command Specific : 0x00000000
Additional Sense Code : 0x25
Additional Sense Qualifier : 0x00
Field Replaceable Unit : 0x00
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x00 0x00 0x00

Sense Key 0x05, ILLEGAL REQUEST, indicates that there was an illegal
parameter in the command data block or in the additional parameters
supplied as data for some commands (FORMAT UNIT, SEARCH DATA, etc.).
This sense key may also indicate that an invalid IDENTIFY message was
received.

The combination of Additional Sense Code and Sense Qualifier (0x2500)
indicates: Logical unit not supported.
###

someone could help me please?

thanks,
Cedrick Gaillard.

Re: EMS SERIOUS alerts

IT_2007 — Mon, 18 Sep 2006 10:21:13 GMT

What is the status of Hardware at 0/3/1/0.14.104.0.0.0.1

Check from ioscan and what kind of server, OS etc..?

Re: EMS SERIOUS alerts

Ludovic Derlyn — Mon, 18 Sep 2006 10:25:19 GMT

hi Mobidyc,

Perhaps more informations here :

http://docs.hp.com/en/diag/ems/disk_em.htm

Regards

L-DERLYN

Re: EMS SERIOUS alerts

totoperdu — Mon, 18 Sep 2006 10:43:40 GMT

Thansk for your answers.

this hardware is NO_HW:
root@nr0u0253# ioscan -fnH 0/3/1/0.14.104.0.0.0.1
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
disk 6 0/3/1/0.14.104.0.0.0.1 sdisk NO_HW DEVICE DGC CX700WDR5

it seems that the error is normal ;)
is there a way for delete this entry from ioscan? rmsf is not sufficient.

thanks again for your help.

Regards,
Cedrick Gaillard

Re: EMS SERIOUS alerts

IT_2007 — Mon, 18 Sep 2006 10:48:25 GMT

root@nr0u0253# ioscan -fnH 0/3/1/0.14.104.0.0.0.1
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
disk 6 0/3/1/0.14.104.0.0.0.1 sdisk NO_HW DEVICE DGC CX700WDR5

it seems that the error is normal ;)
is there a way for delete this entry from ioscan? rmsf is not sufficient.

+++++++++++++++++++++++++++++++++++++++++++
If you are sure that it is not being used and also check any other devices under same controller from ioscan.

To remove use: rmsf -KH 0/3/1/0.14.104.0.0.0.1

or system reboot will clear automatically.

Re: EMS SERIOUS alerts

Mridul Shrivastava — Mon, 18 Sep 2006 21:59:48 GMT

You are getting these events because event monitor is monitoring some DGC devices which it shouldn't be.

As a work around in the meantime, to stop the events being generated, add the paths of the affected devices to the disabled_instances file:

o Run /etc/opt/resmon/lbin/moncheck to determine the names of instances that should be disabled. (Direct this output to a file.)

o With editor of your choice, Add /delete /modify instances in /var/stm/data/tools/monitor/disabled_instances.
Add a line for each disk or LUN and run monconfig to re-enable monitoring.

Example:

1. Add the following line to the disabled_instances file:

"/storage/events/disks/default/0_3_1_0.14.104.*

Note that a wildcard was used here. "*" this means all devices starting with 0_3_1_0.14.104 will be disabled.

2. Run monconfig: select the "E)nable Monitoring" command, and wait for monitoring to be re-enabled.

3. Do a C)heck monitors. The resource class that you disabled should show up in the list with no description of what to do with events, i.e., there are no monitoring requests.

HTH

Re: EMS SERIOUS alerts

totoperdu — Tue, 19 Sep 2006 01:41:47 GMT

for the moment i have deleted the NO_HW entry from ioscan (thanks IT_2007).

if the alert comes back, i will look in the resmon's config (thanks HTH).

thanks all.

Cheers,
Cedrick Gaillard

Re: EMS SERIOUS alerts

Mridul Shrivastava — Tue, 19 Sep 2006 03:43:40 GMT

Hi,
HTH stands for Hope This helps
However you can call me Mridul

Please don't assign any point to this...

Thanks

Re: EMS SERIOUS alerts

totoperdu — Tue, 19 Sep 2006 12:11:54 GMT

oups Mridul, sorry for the mistake ;)