how can I check current driver for a device?

[Morten Kristiansen]

Hi,

We have a problem with some disks that gets a EMS Notification, event# 100376. Which says:
----------- snip --------------------------
Description of Error:

The device was unsuccessful in processing the current request message
because the message contained an invalid command operation code. 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.
--------------------snap---------------

In the STM, all 6 disks are yellow and says "Information incomplete". Those are SCSI Disks (DGCC4400WDR10). One of the disks is "Unknown" in STM, but it's a SCSI disk (DGCC4400WD).

Does anybody know how I can check which driver that's used and which version the driver is. In the STM I can see that it's a "Fibre Channel Driver (Mass_Storage)". But how can I get the version and how do I upgrade it?

We are running HP-UX 11.00 on an L2000 9000/800.

[Robert-Jan Goossens]

Morten,

Could you post the output of
# ioscan -fnCdisk

Regards,
Robert-Jan

[Morten Kristiansen]

Yes, of course, I forgot to tell you that the "unknown" disk has "S/W state" = "NO_HW" as you can see in the output from ioscan which is attached.

[Florian Heigl (new acc)]

The 'Information Incomplete' for the DGC luns won't go away, as they're unsupported in stm. there are modules in EMS/STM for various arrays made by HP, but EMC^2 never supplied additional ones for the Clariion / CX series.

On the driver version, please use
ioscan -fnkCfc to gather the fc adapter names and then /opt/fcms/bin/tdutil /dev/tdN for the adapters' driver version.

(ioscan -fknd will give You the driver that attached to the fc adapter, but not it's version)

You can also ask EMC^2 for the utility 'emcgrab' (also found at their ftp site) and have them analyze the output.

[Florian Heigl (new acc)]

first, what I tried to say is: the 'information incomplete' is normal as EMS has no monitoring component for the non-hp array.

The ioscan output looks let's me think of two scenarios, both of them unrelated to driver (same is used for the other disks) and ems (which is only reporting).

- The LUN got unreachable
-> is there an alternate path for it?
-> is the zoning okay?
-> was it mapped away in the Clariion?

- The LUN is gone
-> it might have become unbound in the Clariion (open EMC^2 call...)

use /opt/Navisphere/bin/navicli -h getdisk | more to get information about the physical disks in there and
/opt/Navisphere/bin/navicli -h getlog | more to pull the error logs

A manual page can be found at:
http://cowofdoom.com/~galt/public_html_old/stories/navicli-man.txt

If You have two SPs in it, there are two IPs and You should poll both logs.

If the Clariion reports everything to be ok, I'd try diskinfo etc. on the lost LUN. (but I probably never saw a Clariion reporting everything to be ok)

If You want, attach the STM formatted log from logtool to Your next post.