Connecting Data Domain VTL to an HP-UX 11.31 system

Fedon Kadifeli — Mon, 29 Nov 2010 08:15:35 GMT

I am unable to use EMC DataDomain VTL in our HP-UX 11.31 rx6600 test system.

This system has two FC cards:

# ioscan -fnkC fc
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
fc 0 0/7/0/0/0/0 fcd CLAIMED INTERFACE HP AH401A 8Gb Dual Port PCIe Fibre Channel Adapter

(FC Port 1)
/dev/fcd0
fc 1 0/7/0/0/0/1 fcd CLAIMED INTERFACE HP AH401A 8Gb Dual Port PCIe Fibre Channel Adapter

(FC Port 2)
/dev/fcd1

One card (/dev/fcd0) is used for disk I/O; HP EVA 8100 and P2000 disk systems are accessed from this port with no problem:

# ioscan -fnkC disk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
[...]
disk 8 0/7/0/0/0/0.5.0.0.0.0.1 sdisk CLAIMED DEVICE HP HSV210
/dev/dsk/c9t0d1 /dev/rdsk/c9t0d1
disk 56 0/7/0/0/0/0.5.0.0.0.0.2 sdisk CLAIMED DEVICE HP HSV210
/dev/dsk/c9t0d2 /dev/rdsk/c9t0d2
[...]
disk 12 0/7/0/0/0/0.5.3.0.1.8.2 sdisk CLAIMED DEVICE HP HSV210
/dev/dsk/c12t8d2 /dev/rdsk/c12t8d2
disk 13 0/7/0/0/0/0.5.3.0.1.8.3 sdisk CLAIMED DEVICE HP HSV210
/dev/dsk/c12t8d3 /dev/rdsk/c12t8d3
disk 65 0/7/0/0/0/0.15.11.0.0.0.1 sdisk CLAIMED DEVICE HP P2000 G3 FC
/dev/dsk/c24t0d1 /dev/rdsk/c24t0d1
disk 70 0/7/0/0/0/0.15.11.0.0.0.2 sdisk CLAIMED DEVICE HP P2000 G3 FC
/dev/dsk/c24t0d2 /dev/rdsk/c24t0d2
disk 75 0/7/0/0/0/0.15.11.0.0.0.3 sdisk CLAIMED DEVICE HP P2000 G3 FC
/dev/dsk/c24t0d3 /dev/rdsk/c24t0d3
disk 66 0/7/0/0/0/0.15.12.0.0.0.1 sdisk CLAIMED DEVICE HP P2000 G3 FC
/dev/dsk/c25t0d1 /dev/rdsk/c25t0d1
disk 69 0/7/0/0/0/0.15.12.0.0.0.2 sdisk CLAIMED DEVICE HP P2000 G3 FC
/dev/dsk/c25t0d2 /dev/rdsk/c25t0d2
disk 74 0/7/0/0/0/0.15.12.0.0.0.3 sdisk CLAIMED DEVICE HP P2000 G3 FC
/dev/dsk/c25t0d3 /dev/rdsk/c25t0d3
disk 4 255/1/0.0.0 sdisk CLAIMED DEVICE Optiarc DVD RW AD-5590A
/dev/dsk/c3t0d0 /dev/rdsk/c3t0d0

The other card (/dev/fcd1) is used for tape I/O. Until now only one MSL6060 tape library was used:

# ioscan -fnkC tape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
[...]
tape 2 0/7/0/0/0/1.20.13.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 4-SCSI
/dev/rmt/2m /dev/rmt/c16t0d1BEST
/dev/rmt/2mb /dev/rmt/c16t0d1BESTb
/dev/rmt/2mn /dev/rmt/c16t0d1BESTn
/dev/rmt/2mnb /dev/rmt/c16t0d1BESTnb
tape 3 0/7/0/0/0/1.20.13.255.0.0.2 stape CLAIMED DEVICE HP Ultrium 4-SCSI
/dev/rmt/3m /dev/rmt/c16t0d2BEST
/dev/rmt/3mb /dev/rmt/c16t0d2BESTb
/dev/rmt/3mn /dev/rmt/c16t0d2BESTn
/dev/rmt/3mnb /dev/rmt/c16t0d2BESTnb
tape 4 0/7/0/0/0/1.20.14.255.0.0.0 stape CLAIMED DEVICE HP Ultrium 4-SCSI
/dev/rmt/4m /dev/rmt/c17t0d0BEST
/dev/rmt/4mb /dev/rmt/c17t0d0BESTb
/dev/rmt/4mn /dev/rmt/c17t0d0BESTn
/dev/rmt/4mnb /dev/rmt/c17t0d0BESTnb
tape 5 0/7/0/0/0/1.20.14.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 4-SCSI
/dev/rmt/5m /dev/rmt/c17t0d1BEST
/dev/rmt/5mb /dev/rmt/c17t0d1BESTb
/dev/rmt/5mn /dev/rmt/c17t0d1BESTn
/dev/rmt/5mnb /dev/rmt/c17t0d1BESTnb

Recently we added a demo EMC DataDomain VTL to SAN; made the relevant zone definitions to use this library from (/dev/fcd1). However, the system does not detect this new library.

The FC card of the HP-UX server is connected to port #3 of SAN switch having domain ID 20.
MSL library's Int Ctrls are connected to ports #13 and #14 of the same SAN switch.
The new DataDomain VTL is connected to ports #1 and #2 of the same SAN switch. The primary port is defined as the VTL port connected to switch port #2, so the server should detect the tape library components (autochanger and tape drives) in hardware path 0/7/0/0/0/1.20.2....

The VTL library detects the FC of the HP-UX server with no problem. However when I do "ioscan" on the server side, the device detection completes with no device (autochanger and tape drives) from the VTL library.

The following messages are logged in the syslog:

Nov 29 09:44:29 tsisrv vmunix: class : tgtpath, instance 14
Nov 29 09:44:29 tsisrv vmunix: Target path (class=tgtpath, instance=14) has gone offline. The target path h/w path is 0/7/0/0/0/1.0x2101001b32b5fa2e
Nov 29 09:44:29 tsisrv vmunix:
Nov 29 09:44:30 tsisrv vmunix: Target path (class=tgtpath, instance=14) has gone online. The target path h/w path is 0/7/0/0/0/1.0x2101001b32b5fa2e
Nov 29 09:44:30 tsisrv vmunix: class : tgtpath, instance 14

LUNs as defined in VTL:

LUN Library Device In-Use Ports Primary Ports Secondary Ports
--- ------- ------ ------------ ------------- ---------------
1 VTL01 changer 2a 2a 2b
2 VTL01 drive 1 2a 2a 2b
3 VTL01 drive 2 2a 2a 2b
4 VTL01 drive 3 2a 2a 2b
5 VTL01 drive 4 2a 2a 2b
6 VTL01 drive 5 2a 2a 2b
7 VTL01 drive 6 2a 2a 2b
8 VTL01 drive 7 2a 2a 2b
9 VTL01 drive 8 2a 2a 2b

Notes:
1. The same VTL is used with no problem on a Windows server connected similarly to SAN.

2. The MSL library is used with no problem on this server.

Re: Connecting Data Domain VTL to an HP-UX 11.31 system

Fedon Kadifeli — Mon, 06 Dec 2010 14:34:16 GMT

The problem was solved with a Data Domain command to change FC addressing mode. For example:

vtl initiator set address-method vsa initiator
50:01:xx:xx:xx:xx:xx:xx

topic Connecting Data Domain VTL to an HP-UX 11.31 system in Operating System - HP-UX

Connecting Data Domain VTL to an HP-UX 11.31 system

Re: Connecting Data Domain VTL to an HP-UX 11.31 system