SUMMARY: can't see HSZ LUNs

From: McCracken, Denise <Denise.McCracken_at_misyshealthcare.com>
Date: Tue, 14 Oct 2003 12:06:53 -0700

        Thanks to the multitudes who replied to this problem.

        Some HSZ40 controllers are not compatible with 5.1a. We had one
machine that had just had them replaced, and their vendor ID strings said
something like this:

        HSZ40 (C) DEC ZG64306397 Firmware V37Z-0, Hardware A01

        These controllers had no problems.

        The other HSZ40 controllers had ID strings like this:

        HSZ40 ZG65009132 Firmware V37Z-0, Hardware A01

        The LUNs showed up in hwmgr -show scsi -full but dsfmgr couldn't
make device files for its LUNs no matter what I tried. Applying Occam's
razor, we might think that the vendor ID string had to say (C) DEC in it,
but that is not a valid test for compatibility, because...

        We had the HSZ controllers replaced and firmware cards flashed on
the box that had the problem, and they work now. The firmware still shows
up as V37Z-0, there is no (C) DEC in the ID string, but they work properly.

        John Lanier sent me these commands, and I think this may be the key
to detecting compatibility before an upgrade is done from 4.0f.

        In scu,

        scu> scan edt
        scu> show edt
        scu> sbtl <port> <target> <lun>
        scu> show inquiry

        If you don't see (DEC) in this output as follows:

        Vendor Identification: DEC

        then the controller probably has to be replaced. I have heard of a
patch V37Z-1, but I don't know where to get it or how to apply it, and some
sources I've run across say that it doesn't completely fix the problem

        I haven't verified that the above test works on any system but this
one; however, it is the only method I have yet run across.


Again, thanks to all!

-denise
Received on Tue Oct 14 2003 - 19:08:19 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:44 NZDT