From: lawries@btinternet.com
Date: Mon Feb 16 2004 - 07:17:03 EST
Admins,
Thanks to all those who replied.
It seems that with later versions of Tru64 the CAM layered
products are integral to the base buld.
I am running V5.1B-1 (SRM6.6) attaching to the Overland via HBA
(DS-KGPSA-DA) and Cisco MDS9216 SAN switch. I have just attached
an Overland Neo 2000 tape library (Same as the HP MSL5030)
The special file /dev/changer/mc0 does not exist.
If I do a scu show edt, I get:
CAM Equipment Device Table (EDT) Information:
Bus/Target/Lun Device Type ANSI Vendor ID Product ID Revision N/W
-------------- ----------- ------ --------- ---------------- -------- ---
6 0 0 Sequential SCSI-3 OVERLAND NEO VIA FCO T520 N
6 0 1 Changer SCSI-3 OVERLAND NEO VIA FCO T520 N
6 0 2 Sequential SCSI-3 OVERLAND NEO VIA FCO T520 N
6 0 3 Processor SCSI-3 OVERLAND NEO VIA FCO T520 N
But If I do :
hwmgr -show scsi -id 115 -full
SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH
-------------------------------------------------------------------------
115: 7 ch004 processor none 0 4 (null) [6/0/0]
WWID:0b000008:1000-0050-1300-254c
BUS TARGET LUN PATH STATE
---------------------------------
6 0 0 valid
6 0 1 valid
6 0 2 valid
6 0 3 valid
I need some mechanism to resolve the LUN's into seperate devices at OS level. I believe that what I need is an entry for the
Neo 2000 in the /etc/ddr.dbase file but I have no idea what to
enter.
Can anyone help me out with an entry for the ddr.dbase file
(and mcicap) for an Overland Neo 2000 or HP MSL5000 series library?
Thank you.
Lawrie.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:51 EDT