How to configure OpenVMS V732 as a Legato Storage Node of V6.0-1D?

[Volker Halle]

lunew,

for further troubleshooting, you can use SYS$ETC:SCSI_INFO.

$ scsi_info:==$SYS$ETC:SCSI_INFO
$ scsi_info $2$MGA0: ! or $2$MGA1: or $2$GGA0:

The tool will first send a standard SCSI INQUIRY QIOW to the device and report the data returned. Then a lot more data will be returned...

The first 5 bits of the first byte returned specify the peripheral device type: 0=disk, 1=tape, 8=jukebox

SYSMAN IO FIND_WWID uses this data to decide, whether to configure a $2$MGA or $2$GGA device.

Lets see what your STK L20 loader returns...

Volker.

[lunew]

Hi Volker!
$> scsi_info $2$MGA0:
$! SCSI_INFO V3
$! Copyright (c) 1995 by DIGITAL Equipment Corporation, Maynard, Mass.
$! All Rights Reserved. Unpublished rights reserved under the copyright
$! laws of the United States.
$! Issuing INQUIRY QIOW
$! SCSI Inquiry Data (96 bytes) :
$! 000: 01 80 02 12 5B 00 00 00 48 50 20 20 20 20 20 20
$! 010: 55 6C 74 72 69 75 6D 20 32 2D 53 43 53 49 20 20
$! 020: 46 36 32 30 00 00 00 00 00 00 00 00 00 00 00 00
$! 030: 00 00 00 00 00 00 00 00 0C 00 00 54 0B 1C 02 77
$! 040: 02 1C 00 00 00 00 00 00 00 00 00 00 00 00 00 00
$! 050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
$! Peripheral Device Type : Sequential Access
$! Peripheral Device Qualifier :
$! Peripheral device type supported & connected to target
$! Vendor Identification : HP
$! Product Identification: Ultrium 2-SCSI
$! Product Revision Level: F620
$! ANSI Information:
$! Complies to SCSI-2
$! ISO Information:
$! 0 - does not claim ISO SCSI (ISO IS 9316) compliance
$! ECMA Information:
$! 0 - does not claim ECMA SCSI (ECMA-111) compliance
$! Removable Media: Yes
$! AEN Capability: No
$! Command Queuing: No
$! 16-Bit Wide Bus Data Transfers: No
$! 32-Bit Wide Bus Data Transfers: No
$! Linked Commands: No
$! Soft Reset Alternative: No
$! Relative Addressing: No
$! Synchronous Data Transfers: No
$! Issuing Test Unit Ready command
$! ========================== Read-Write Error Recovery Page ==================
$! Issuing 6-byte MODE SENSE QIOW to get current values for page 01h
$! SCSI 6-Byte Mode Sense command returned 24 bytes of data:
$! 000: 17 00 10 08 42 00 00 00 00 00 00 00 01 0A 08 15
$! 010: 00 00 00 00 0A 00 00 00
$! Mode Sense Data Length ...... 23
$! Medium Type ................. 00h
$! Device-Specific Parameter ... 10h
$! Block Descriptor Length ..... 8
$! Block Descriptor Data ....... 42 00 00 00 00 00 00 00
$! Page Code ................. 01h
$! Page Name ................. Read-Write Error Recovery
$! Saveable .................. No
$! Size ...................... 10
$! Hex Data .................. 08 15 00 00 00 00 0A 00
.........
That seems OK !
But $2$mga1: seems too bad!
$>scsi_info $2$MGA1:
$! SCSI_INFO V3
$!
$! Copyright (c) 1995 by DIGITAL Equipment Corporation, Maynard, 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

So I think the problem exists on ATTO Fibrebridge or STKL20 cable connection.
But my other windows storage nodes use this SAN attached devices OK. Legato network backup and recover these nodes via the STKL20 Lan-Free.

Thanks Volker!

[lunew]

Microsoft Windows [Copyright 5.2.3790]
(C)1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>inquire
Error in nt_lus_get_inquiry; error was 1
scsidev@2.1.0:STK L20 0207|Autochanger (Jukebox)
S/N: LLC02207756
scsidev@2.1.1:HP Ultrium 2-SCSI F620|Tape
scsidev@2.1.2:ATTO FB 1180L 2.10|Processor
S/N: FB1180L100859
scsidev@2.1.3:ATTO 1180 Services 2.10|(Unknown Device Type d)
S/N: FB1180L100859
scsidev@2.127.0:QLOGIC PSEUDO LUN |Processor

[Volker Halle]

lunew,

yes, $2$MGA0: now seems to be o.k.

As can be seen from your Windows Server, the STK L20 correctly identifies itself as an Autochanger (Jukebox). If OpenVMS would have seen this response to the SCSI INQUIRY command, it should also have configured the STK L20 as $2$GGA0:. If your Windows server sees this data correctly, there can be nothing wrong with the SCSI to FibreBridge cabling.

You have to get rid of the offline $2$MGA1: device in OpenVMS and try to reconfigure with SYSMAN IO FIND_WWID.

The WWID to device name mapping in OpenVMS is both stored in SYS$SYSTEM:SYS$DEVICES.DAT and in the cluster-wide logical name table LNM$DEV_WWID_TABLE (see $ SHOW LOG/TABLE=LNM$DEV_WWID_TABLE). To get rid of the bad information about $2$MGA1:, you should delete the entry about the STK L20 loader by editing SYS$DEVICES.DAT and then reboot your ES40 (assuming it is a standalone node, otherwise you need to reboot the whole cluster). Then start again with SYSMAN IO FIND_WWID. This command should then see the STK L20 and map it to $2$GGA0:, as it should report itself as an Autochanger (Jukebox) to the SCSI INQUIRY command - as it did when inquired from Windows.

Volker.

[lunew]

OK. I have deleted the file sys$system:sys$devices.dat. And I will reboot the cluster system later,and reconfig the tape devices.

Under my ES40's console,I found the information as followed:
P00>>>wwidmgr -show wwid
[0] UDID:-1 WWID:01000010:6000-1fe1-0005-8d90-0009-9480-8412-00a4 (ev:wwid0)
............
[8] UDID:-1 WWID:04100023:"STK L20 LLC02207756" (ev:none)
[9] UDID:-1 WWID:01000010:5006-0b00-0036-c919-0000-0000-0000-0000 (ev:none)
[10] UDID:20 WWID:01000010:6005-08b4-0008-e7de-0000-9000-000f-0000 (ev:none)

The item 9 is LTO2 drive. The item 8 is STKL20. Volkerï¼ from these information could you guess the where the problem is ? Haha, thank U very much!

[Volker Halle]

lunew,

the only 'problem' so far has been, that the STK L20 loader had been configred as a $2$MGA device instead of a $2$GGA device.

The code in SYSMAN IO FIND_WWID send a SCSI INQUIRY command to the unit, once it has found it by scanning the SAN. If the unit replies with a device type 08 (=jukebox), it will be configured as a $2$GGA device.

As you're running in a clsuter, be sure to read chapter 7.5 'Fibre Channel Tape Support' of the Guidelines for OpenVMS Clusters Configurations Manual:

http://h71000.www7.hp.com/doc/82final/6318/6318pro_010.html#fctapes

If everythign else fails, you may be able to configure the $2$GGA0: device manually with:

$ MC SYSMAN IO CREATE_WWID $2$GGA0:/WWID=04100023:"STK L20 LLC02207756"

Then we'll have to see, if JBCONFIG can works with $2$GGA0:

Please note that GG devices are also driven by SYS$GKDRIVER, same as the GK devices for direct SCSI connected loaders.

Good luck,

Volker.

[lunew]

I have not rebooted my cluster. I browse a PDF Document.

[Volker Halle]

lunew,

if you can leave the handling of the STK L20 loader/jukebox to your Windows server, you can certainly use the $2$MGA0: tape device for backup under OpenVMS. Then you wouldn't need to run jbconfig under OpenVMS.

But I'm not familiar with Legato Networker configurations, so I can't tell whether and how this needs to be configured.

Volker.

[Volker Halle]

lunew,

I found the following article at the EMC Powerlink site:

---------------------------------------------
Fact: OpenVMS 7.3-2

Fact: NetWorker 6.0.1-D ECO1

Fact: OpenVMS backup command works on the devices

Symptom: Error:'Path PGA0.1000-00E0-0222-DE85 (server_name), primary path, current path, not responding'

Symptom: SHOW DEVICE/FULL gives the above error

Symptom: When trying to mount or unmount devices on OpenVMS storage node getting 'I/O error'

Symptom: jbconfig cannot find jukebox on VMS storage node

Symptom: Error: 'ww_libvms (748): scsi cmd error: %SYSTEM-F-ILLIOFUNC, illegal I/O function code'

Change: Changed the port on the Fibre Switch for HBA connected to storage node

Fix: Recycle the SAN switch, autochanger and system in sequence.


Run 'SHOW DEVICE GGA0/FULL' to verify that the jukebox is online now.


Run jbconfig as example below and configure the jukebox:

$ mcr sys$disk:[]JBCONFIG.EXE "-s" "nsr_server_name"
---------------------------------------------

This seems to clearly indicate, that GGA0 devices are expected for the loader/jukebox and should work with Legato Networker jbconfig.

You may also want to check for ECO 1.

Volker.

[lunew]

Thank U! My Legato V60-1D has installed ECO 14 which is the latest. I will recyle my cluster nodes later and then verify you told me to reconfig the devices.