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

[lunew]

I have a ES40 with OVMS7.3-2. ES40 joined the SAN with a STK-L20 Tape. I find the tape with name $2$MGA0:. But when I config ES40 as Legato storage node,I can’t. The legato user guide says the ES40 should have a tape with MK*nnn or GK*nnn.
Information as following:
OPER> r jbconfig
If on a storage node, enter the NSR server hostname? [es40] semhq60
using 'semhq60' as the NSR server
On a storage node, the hostname is a prefix to the jukebox name.
Enter the hostname to use as a prefix? [es40]
using 'es40' as the hostname prefix
1) Install a SmartMedia Jukebox.
2) Install an Autodetected SCSI Jukebox.
3) Install an Autodetected NDMP SCSI Jukebox.
4) Install an SJI Jukebox.
5) Install an STL Silo.
What kind of Jukebox are you installing? [1] 2
Unable to find any SCSI jukeboxes attached to this system.
SCSI libraries on an OpenVMS system are accessed through the
SCSI pass-through driver, sys$gkdriver. In order for this
program to find one of these libraries, you must first
create the GK device, as follows:
For devices that work with only one SCSI ID, the tape drive
is LUN 0 and the library (or loader) element is LUN 1.
Assuming the SCSI ID is 5, the device names are:
MKx500:
GKx501:
Where, x is the controller letter (A, B, C, etc.)
The MK device is created and configured automatically by
OpenVMS. To create the GK device, you must issue the
following command:

$ mcr sysman io connect -
_$ GKx501/noadapter/driver=sys$loadable_images:sys$gkdriver
Please re-run this program when you have connected the SCSI
jukebox you want to install

[Volker Halle]

lunew,

are you sure that Legato V6.0-1D supports SAN attached storage ?

A SAN attached storage library should show up as $1$GGAn: under OpenVMS.

Volker.

[lunew]

Yes! Legato V601-D support SAN on OpenVMS.I reconfig the Lib and drive.
SYSMAN> IO FIND
%SYSMAN-I-OUTPUT, command execution on node ALPHA
On port _PGA0:, the following tape WWIDs and their proposed device
names have been found but not yet configured:
[Device $2$MGA1]
WWID=04100023:"STK L20 LLC02207756"
[Device $2$MGA0]
WWID=02000008:5006-0B00-0036-C919
Run SYSMAN IO AUTO to configure the above device(s).
SYSMAN> IO AUTO /LOG
%SYSMAN-I-OUTPUT, command execution on node ALPHA
%IOGEN-I-PREFIX, searching for ICBM with prefix SYS$
%IOGEN-I-PREFIX, searching for ICBM with prefix DECW$
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKA0
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKB0
%IOGEN-I-FIBREPOLL, scanning for devices through FIBRE port PGA0
%IOGEN-I-CONFIGURED, configured device MGA1
%IOGEN-I-CONFIGURED, configured device MGA0
SYSMAN>

After doing that I can init $2$mga0 and mount $2$mga0 on ES40 with OpenVMS V7.32.
But when I run Legato Jbconfig it says unaccess the device.
Deltail as following:
$> run jbconfig
cannot connect to NSR service on es40
jbconfig: RPC error: Remote system error

If on a storage node, enter the NSR server hostname? [es40] semhq60
On a storage node, the hostname is a prefix to the jukebox name.
Enter the hostname to use as a prefix? [es40]
using 'es40' as the hostname prefix

1) Install a SmartMedia Jukebox.
2) Install an Autodetected SCSI Jukebox.
3) Install an Autodetected NDMP SCSI Jukebox.
4) Install an SJI Jukebox.
5) Install an STL Silo.

What kind of Jukebox are you installing? [1] 4
Enter the number corresponding to the type of jukebox you are installing:
1) ADIC-1200c/ADIC-1200d 17) Exabyte 230D 33) IBM 3570
2) ADIC-VLS 18) Exabyte 400 Series 34) IBM 7331/IBM 9427
3) ARC DiamondBack 19) Exabyte 690D 35) ATL/Odetics SCSI
4) Breece Hill 20) Exabyte Jukebox 36) HP-Optical
5) Breece Hill Saguaro 21) Hitachi ML010 Series 37) Sony TSL-7000
6) Philips Blackjack 22) HP-C1553A/Surestore 12000e 38) Digital 4mm DAT TL
7) DLI Libra Series 23) HP-C1557A/Surestore 12000e 39) Digital 4mm DAT ()
8) Quantum DLT/Digital DLT 24) Metrum (SCSI) 40) Digital TL800 Series
9) Exabyte 10e or 10h 25) Qualstar 41) Digital TL810 Series
10) Exabyte 10i 26) Spectralogic 42) Digital TL820 Series
11) Exabyte 18D 27) STK 9704/Lago 340 43) Digital TL893
12) Exabyte 60 28) STK 9708/Lago 380 (SCSI) Datawheel 44) Digital T
13) Exabyte 120 29) StorageTek 9730 45) Digital TL899
14) Exabyte 210 30) StorageTek 9738 46) Digital Optical
15) Exabyte 218 31) Dell PowerVault 130T 47) Digital TK Series
16) Exabyte 220 32) Hewlett-Packard A4853A 48) Standard SCSI Jukebox

Choice? 48
Installing an 'Standard SCSI Jukebox' jukebox.
Name you would like to assign to the jukebox device? rd=es40:STKL20
Pathname of the control port for the jukebox device? [] rd=es40:$2$mga0:
Unable to access device "Standard SCSI Jukebox" on control port "rd=es40:$2$mga.
There appears to be something incorrect about your driver
installation. Please consult your driver documentation
to help you troubleshoot your installation.
Would you like to configure another jukebox? (yes/no)

Give me a hand to do that.

[marsh_1]

hi,

the controller is a gga device ($ sh dev g) as stated by volker, you have used one of the tape drive device names.

hope this helps

[Volker Halle]

lunew,

if you can INIT and MOUNT $2$MGA0; then $2$MGA1: should be the library/jukebox device. Although I would have expected that to be configured as $1$GGAx:

Try answering the following question like this:

Pathname of the control port for the jukebox device? [] $2$MGA0:

Sorry, but documentation on this seems to be hard to find, so this is just a best guess.

Volker.

[lunew]

Thanks Mark and Volker. As Volker guessed what is the exact pathname for my $2$mga0 and $2$mga1 ?

[Volker Halle]

lunew,

I've finally found Legato Networker V6.0.1-D fieldtest documentation for OpenVMS on:

ftp://ftp.legato.com/pub/NetWorker/OpenVMS/6.01D/

The installation guide only has examples related to SCSI tape devices and SCSI jukeboxes/loaders. They all rely on creating an appropriate GKxnnn: ROBOT unit (GK) device - I believe the equivalent device for Fibre Channel tape loader is a $2$GGAx: device. It also talks about Fibre Channel Tape Devices, but does not provide any example.

From the jbconfig examples shown, path names should really be valid OpenVMS device names, so in your case ($2$MGA0: = tape device and $2$MGA1: the STK L20 loader), I can only suggest to try to answer the questions like this:

...
Name you would like to assign to the jukebox device? STKL20
Pathname of the control port for the jukebox device? [] $2$mga1:
...

I've checked that a HP MSL6000 loader control port shows up as $2$GGA0: (I incorrectly typed $1$GGA0: in a previous reply).

Volker.

[Volker Halle]

lunew,

the STK L20 should include a 'Fibre Channel to LVD router'. This router may need to be correctly configured to present the library loader as a loader and not as a tape device.

Volker.

[lunew]

Thanks Volker! Yes,after reconfiged the $2$mga0 and $2$mga1,I showed the devices. I found that $2$mga0 was online and $2$mga1 is offline. My question is these status are normal ? If they should be both online, I think Fibre Router may be not configured correctly,that as your guess! My Fibre Router is "ATTO FibreBridge 1180" .

[Volker Halle]

lunew,

for a tape library with one tape drive and a loader connected to the SAN, there should be a $2$MGA0: device (the tape) and a $2$GGA0: device (the loader/jukebox). Both must be online. To load/unload/move tapes etc., your application needs to send commands to the $2$GGA0: device. The actual backup application then accesses the tape via $2$MGA0:

If your $2$MGA0: is online and you can INIT and MOUNT the tape, part of your job is done. The other part is configuring the loader access and then configuring the Legato backup application.

Look at the various SYSMAN IO subcommands for ways try to configure the loader. Use SCSI_PATH_VERIFY to verify your FC configuration. Use IO FIND_WWID and LIST_WWID to obtain the WWID of the tape and loader.

Does the ATTO FibreBridge see both the tape and the loader on the SCSI bus ? Does it map them to different LUNs on the Fibre Port ?

Volker.

[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.

[lunew]

Hi Volkerï¼ I have the answer with your help. I config the $2$GGA0 and $2$MGA0 devices manually as you told me.
SYSMAN>IO LIST_WWID
%SYSMAN-I-OUTPUT, command execution on node ALPHA
On port _PGA0:, the following tape WWIDs are not yet configured:
Target 6, LUN 0, STK L20
WWID=04100023:"STK L20 LLC02207756"
Target 6, LUN 1, HP Ultrium 2-SCSI
WWID=02000008:5006-0B00-0036-C919
SYSMAN>IO CREATE_WWID $2$GGA0/WWID= 04100023:"STK L20 LLC02207756"
SYSMAN>IO CREATE_WWID $2$MGA0/WWID= 02000008:5006-0B00-0036-C919
SYSMAN>IO AUTO/LOG
New problem has occured, while I run Legato jbconfig file to config my jukebox.

$>run jbconfig
1) Install a SmartMedia Jukebox.
2) Install an Autodetected SCSI Jukebox.
3) Install an Autodetected NDMP SCSI Jukebox.
4) Install an SJI Jukebox.
5) Install an STL Silo.
What kind of Jukebox are you installing? [1] 2
These are the SCSI Jukeboxes currently attached to your system:
1) scsidev@29.0.0 ($2$GGA0:): Standard SCSI Jukebox, Vendor , Product
Which one do you want to install? 1
Installing an 'Standard SCSI Jukebox' jukebox.
Name you would like to assign to the jukebox device? STKL20
using 'rd=es40:STKL20' as jukebox device name
A brief description of the jukebox device? [scsidev@29.0.0 ($2$GGA0:): Standard SCSI Jukebox]
Pathname of the control port for the jukebox device? [$2$GGA0:]
using 'rd=es40:$2$GGA0:' as control port
Do you want automated device cleaning support enabled? (yes/NO)yes
Enter hostname that owns media drive 1: ? [es40]
An example of a valid device name for this OS is 'NODE$MKA400:'
Enter device name of media drive 1: ? $2$mga0:
using 'rd=es40:$2$MGA0:' as device name
Should the drive be configured as a NDMP device? (yes/no)no
select a media device type for rd=es40:$2$MGA0:.
1) 3480 24) 9840b 47) qic
.......
19) 8mm AIT-4 42) LTO Ultrium 65) VXA
20) 8mm AIT-5 43) LTO Ultrium-2 66) VXA-172
21) 8mm Mammoth-2 44) LTO Ultrium-3 67) VXA-2
Choice? 43
jbconfig: RAP error: Permission denied, user 'system' on 'es40' does not have 'Configure NetWorker' privilege to create this resource.
I donâ t know need which privilege because of the system has all the privileges.
$>show dev $2$gga0:/full
.....
protect:( S:RWPL,O:RWPL,G:RWPL,W:RWPL)
WWID 04100023:"STK L20 LLC02207756"
......

$>show dev $2$mga0:/full
.....
protect:( S:RWPL,O:RWPL,G:R,W)
WWID 02000008:5006-0B00-0036-C919
......

DO I need to set the mga0: protection ? How to set ?

[Volker Halle · Accepted solution]

I'm glad that you've now solved the OpenVMS and tape loader related issues.

The privilege problem is a Legato Networker configuration issue. Use Google and search for 'Configure NetWorker' privilege, you may find some articles, which could help you. The OpenVMS user SYSTEM needs to somehow be configured into Legato Networker to be allowed to create Networker resources. You may need to add this user on your Networker Server and grant it the appropriate privileges. This has nothing to do with OpenVMS privileges.

Volker.

[lunew]

Hi Volker, I found different protection settings between GGA0 and MGA0. See details as following:
$>show dev $2$gga0:/full
.....
protect:( S:RWPL,O:RWPL,G:RWPL,W:RWPL)
WWID 04100023:"STK L20 LLC02207756"
......

$>show dev $2$mga0:/full
.....
protect:( S:RWPL,O:RWPL,G:R,W)
WWID 02000008:5006-0B00-0036-C919
DO I need to set protection of mga0 same as the gga0? IF necessary how to set ? Thank U !

[lunew]

Hi Volker,I added "system" user entry to my Legato Networker Admin group. I'v solved all the issues. Thanks.

[lunew]

Hi Volker，I have the answer with your help. I config the $2$GGA0 and $2$MGA0 devices manually as you told me.
SYSMAN>IO LIST_WWID
%SYSMAN-I-OUTPUT, command execution on node ALPHA
On port _PGA0:, the following tape WWIDs are not yet configured:
Target 6, LUN 0, STK L20
WWID=04100023:"STK L20 LLC02207756"
Target 6, LUN 1, HP Ultrium 2-SCSI
WWID=02000008:5006-0B00-0036-C919
SYSMAN>IO CREATE_WWID $2$GGA0/WWID= 04100023:"STK L20 LLC02207756"
SYSMAN>IO CREATE_WWID $2$MGA0/WWID= 02000008:5006-0B00-0036-C919
SYSMAN>IO AUTO/LOG