[Info-vax] Error using fibre channel target on FreeBSD from OpenVMS

[Matthew R. Wilson]

Hi David,

Thanks for your thoughts.

> You may also have a zoning visibility problem or a host behavior
> definition problem.
>
> Make sure that both the FC switch and the FreeBSD UDID source allows
> read/write access from the WWIDs of the Integrity systems, and that
> they are all in the same zone (or no zone is set).

Doesn't look like a visibility problem. OpenVMS sees the target and LUNs
just fine; it creates the DGAxx devices that correspond to the LUNs with
the correct UDID, and SYS$ETC:FIBRE_SCAN reports everything with the
correct addresses.

> I know that some SAN Arrays (specifically Infortrend) will not
> connect, due to the fact that they don't support the UDID correctly.

Yeah, the first problem I had was that the LUNs weren't showing up as
DGAxx devices at all in OpenVMS. That's when I learned about UDID and
figured out how to set it from the FreeBSD target side, and the devices
magically started showing up in OpenVMS... albeit stuck offline.

> I do know that OpenVMS requires specific SCSI-3 commands to be
> supported by the SAN Array, in addition to the UDID. For both the EMC
> VNX5500 and the MSA units, you have to tell the SAN Array that the
> OpenVMS host WWIDs are specifically OpenVMS or TRU64 ("profile"),
> which enables certain behavior patterns, or else the systems won't
> connect properly, as the LUNs assume the (non-OpenVMS-compliant)
> Windows/VMware/Linux behavior by default.

I think that's where the problem probably is: some SCSI command that
OpenVMS isn't liking FreeBSD's response to. I'm trying to track down
what it might be. I have seen the documentation in several SAN products
that they have the "OpenVMS profile/host mode" that you refer to. But
I can't find any documentation on what the SANs do differently when set
in that mode.

My guess is there's some SCSI INQUIRY message or something that needs
certain values in the response to make VMS happy. I just can't find any
documentation about what the specific protocol requirements are...

I just figured out how to turn on debuggin in FreeBSD's SCSI target
driver, so I think I'll be able to see the individual SCSI commands
instead of just the packets from the fibrce channel driver that I was
able to enable debugging on.

I'm probably just going to hit a dead end with all of this... but you
never know. I can afford to burn some more time on it for fun.

Thanks,
Matthew