STM and HP EVA 5000

[Jeff Miller - 1]

I had STM release A.26.00 installed on an RP5470 running HPUX 11.11. When I ran the initial scan, it did not see any of the disks on the EVA. After installing STM patch PHSS_26106, I was able to view the disks.

I then decided to upgrade to the latest release of STM (A.53.00) plus the latest patch PHSS_35808. Guess what?? I cannot see the disks anymore.

I have tried doing a "System -> Remap System" multiple times to no avail.

Based on the output of "ioscan -fnCdisk", I know that the EVA disks are at HW path 255/255/0/0.0 thru 255/255/0/8.0. Below are a few of the messages logged in the STM Map Log. The error message states that this product is not supported, yet it worked with release A.26.00 of STM.

Thoughts???

Thanks,

Jeff

Tue Feb 27 14:41:32 2007: Identify routine scsi_arry on path (255/255/0/6.5)
has been requested to initiate.

Tue Feb 27 14:41:32 2007: Identify routine (scsi_arry) starting on path
(255/255/0/6.5).

Tue Feb 27 14:41:32 2007: Tool completed with exit_status PROD_NOT_SUPPORTED
(3) indicating the tool exited because the product
identifier is not supported by this tool.

Tue Feb 27 14:41:33 2007: Identify routine (scsi_arry) for hardware at path
(255/255/0/6.5) indicated hardware path is not
supported. A subsequent identify routine should
support the hardware.

Tue Feb 27 14:41:33 2007: Identify routine scsi_dev on path (255/255/0/6.5) has
been requested to initiate.

Tue Feb 27 14:41:33 2007: Identify routine (scsi_dev) starting on path
(255/255/0/6.5).

Tue Feb 27 14:41:33 2007: Tool completed with exit_status IGNORE_DEVICE (16)
indicating the tool completed successfully but device
should be ignored.

Tue Feb 27 14:41:34 2007: Identify routine (scsi_dev) for hardware at path
(255/255/0/6.5) indicated hardware path should be
ignored. This hardware will not appear in the map.

[Andrew Merritt_2 · Accepted solution]

Hi Jeff,
The OnlineDiags (STM and EMS HW Monitors) do not monitor disks in an EVA or other virtual array. In fact, the devices that show up in ioscan are not physical disks, but LUNs. There should be software that comes with the hardware that monitors it.

Earlier versions of the OnlineDiags did erroneously try to monitor the LUNs, but this has been fixed for some time; that's almost certainly what you were seeing with A.26.00 (June 2001 release!). Upgrading from such an old version was definitely the right thing to do!

Andrew

[Jeff Miller - 1]

Makes sense.

Thanks Andrew!!

[Jeff Miller - 1]

Thanks