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

Thu Apr 28 00:09:45 EDT 2022

On 2022-04-28, Robert A. Brooks <FIRST.LAST at vmssoftware.com> wrote:
> On 4/27/2022 10:49 PM, Matthew R. Wilson wrote:
>
>> 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
>
> $ scsi_info :== sys$etc:scsi_info
> $ scsi_info $1$dga1:

Ah... that could help! Perhaps a useful clue:

  $ scsi_info $1$DGA2:
  $!
  $! SCSI_INFO X-5
  $!
  $!      Copyright (c) 2019 by VMS Software, Bolton Mass.
  $!      All Rights Reserved. Unpublished rights reserved under the copyright
  $!      laws of the United States.
  $!
  $! Issuing INQUIRY QIOW
  $!
  $!   QIO status of 132 causing program exit
  $!
  %SYSTEM-F-DEVOFFLINE, device is not in configuration or not available

Is that SCSI_INFO telling me the device is offline because of a response
it doesn't like to INQUIRY QIOW, or is it SCSI_INFO telling me that it
refuses to run because VMS is telling it the device it offline?

I have the SCSI commands and responses in a debug log on the FreeBSD
side now. I have some SCSI books and specs open and am decoding them...
but the general INQUIRY messages and responses during VMS startup are...

 INQUIRY. CDB: 12 00 00 00 ff 00  Tag: 0x118b60/1, Prio: 0
  0x118b60:0000: 00 00 07 12 5b 18 10 02  43 4f 4d 50 41 51 20 20
  0x118b60:0010: 4d 53 41 31 30 30 30 20  56 4f 4c 55 4d 45 20 20
  0x118b60:0020: 34 2e 33 32 00 00 00 00  00 00 00 00 00 00 00 00
  0x118b60:0030: 00 00 00 00 00 00 00 00  00 00 00 c0 05 c0 09 17
  0x118b60:0040: 06 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
  0x118b60:0050: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00

 INQUIRY. CDB: 12 01 00 00 50 00  Tag: 0x118bf0/1, Prio: 0
  0x118bf0:0000: 00 00 00 0b 00 80 83 86  87 88 8f 92 b0 b1 b2 00
  0x118bf0:0010: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
  0x118bf0:0020: 00 00 00 00 00 00 00 00  00 00 00 00

 INQUIRY. CDB: 12 01 83 00 ff 00  Tag: 0x118c80/1, Prio: 0
  0x118c80:0000: 00 83 00 58 02 81 00 18  43 4f 4d 50 41 51 20 20
  0x118c80:0010: 35 30 30 30 63 35 30 30  31 64 35 62 61 33 30 63
  0x118c80:0020: 01 83 00 10 60 08 05 f3  00 12 00 f0 00 00 00 00
  0x118c80:0030: 03 75 00 01 01 93 00 08  50 01 43 80 28 cc 9a 38
  0x118c80:0040: 01 94 00 04 00 00 00 03  01 95 00 04 00 00 00 01
  0x118c80:0050: 01 a3 00 08 50 01 43 80  28 cc 9a ff

There's also this during VMS startup... not sure if this is an _actual_
error or if the "power on occurred" unit attention "error" is an
expected part of the process:

 MAINTENANCE (IN). CDB: a3 05 00 00 00 00 00 00 00 0c 00 00  Tag: 0x118c20/1, Prio: 0
 CTL Status: SCSI Error
 SCSI Status: Check Condition
 SCSI sense: UNIT ATTENTION asc:29,1 (Power on occurred)
 MAINTENANCE (IN). CDB: a3 05 00 00 00 00 00 00 00 0c 00 00  Tag: 0x118c50/1, Prio: 0
  0x118c50:0000: 00 00 00 04 00 00 00 02  00 00 00 00

Then every 30 seconds:

 INQUIRY. CDB: 12 00 00 00 80 00  Tag: 0x118da0/0, Prio: 0
  0x118da0:0000: 00 00 07 12 5b 18 10 02  43 4f 4d 50 41 51 20 20
  0x118da0:0010: 4d 53 41 31 30 30 30 20  56 4f 4c 55 4d 45 20 20
  0x118da0:0020: 34 2e 33 32 00 00 00 00  00 00 00 00 00 00 00 00
  0x118da0:0030: 00 00 00 00 00 00 00 00  00 00 00 c0 05 c0 09 17
  0x118da0:0040: 06 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
  0x118da0:0050: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00

Will have to see if any of this makes sense in the context of the
SCSI_INFO command saying "INQUIRY QIOW" and "QIO status of 132 causing
program exit", or if that's just an internal VMS thing. No hex 0x84 (132
decimal) is in any of the command responses above.

Thanks,
Matthew