Tape Libraries and Drives
cancel
Showing results for 
Search instead for 
Did you mean: 

Connecting to 3583 LTO with A6795A card

SOLVED
Go to solution
Murray Lawrence
Occasional Advisor

Connecting to 3583 LTO with A6795A card

Im trying to connect an IBM 3583 LTO tape library to a HP-UX 11.00 L2000 box across 2 Tachyon A6795A card. After installing the ATDD driver and running ioscan, the device files for the 3580 drives (/dev/rmt/*m) are missing but the media changer device files are there (/dev/rmt/*chng)
Please can anyone help.
11 REPLIES
Spyros Fidas_1
Occasional Advisor

Re: Connecting to 3583 LTO with A6795A card

Run insf -e -C tape. It will create the driver for all tape devices or insf -e -H
Murray Lawrence
Occasional Advisor

Re: Connecting to 3583 LTO with A6795A card

Hi Spyros, insf -e -C tape didn't work.
It installed special files for existing tape drive. I don't have the hardware path.
Any other suggestions.
Spyros Fidas_1
Occasional Advisor

Re: Connecting to 3583 LTO with A6795A card

Running ioscan, the changer must appear as Class autochr , Driver schgr. If it has the atdd driver, then you must change atdd_autochk parameter from 1 to 0.
In order to confirm that you see the changer correctly try
mc -p /dev/rmt/*chng -r DS
It will report the The slots and drives. If this doesn't work try removing the atdd driver and let unix handle the device with stape (tape) and schgr (changer) drivers.
Murray Lawrence
Occasional Advisor

Re: Connecting to 3583 LTO with A6795A card

an extract of the ioscan -fun output :
tape 1 0/1/0/0.1.17.239.0.0.7 atdd CLAIMED DEVICE IBM
ULT3583-TL

(there are 68 instances of CLAIMED devices for the media changer ; why I don't know).

The kernel parm is set to 1 :
"atdd_autoch 1"

the output of the mc -p is :
DT_slot_1 EMPTY
DT_slot_2 EMPTY
ST_slot_1 EMPTY
ST_slot_2 EMPTY
ST_slot_3 EMPTY
ST_slot_4 EMPTY
ST_slot_5 EMPTY
ST_slot_6 EMPTY
ST_slot_7 EMPTY
ST_slot_8 EMPTY
ST_slot_9 EMPTY
ST_slot_10 EMPTY
ST_slot_11 EMPTY
ST_slot_12 EMPTY
ST_slot_13 EMPTY
ST_slot_14 EMPTY
ST_slot_15 EMPTY
ST_slot_16 EMPTY
ST_slot_17 EMPTY
ST_slot_18 EMPTY
ST_slot_19 EMPTY
ST_slot_20 EMPTY
ST_slot_21 EMPTY
ST_slot_22 EMPTY
ST_slot_23 EMPTY
ST_slot_24 EMPTY
Spyros Fidas_1
Occasional Advisor

Re: Connecting to 3583 LTO with A6795A card

The tape and the changer are correctly configured. Try
ioscan -fnC tape
The device file will be /dev/rmt/*m , /dev/rmt/*mn ,/dev/rmt/*mnb
You shuld see 2 tapes, one for each drive of the library.
About the 68 times you see the claimed media changer driver, could you send an output of
ioscan -fnC autoch
Murray Lawrence
Occasional Advisor

Re: Connecting to 3583 LTO with A6795A card

The # ioscan -fnC tape only generates the /dev/rmt/*chng device files. It does not generate the /dev/rmt/*m[nb] etc device files. This is the crux of the problem. Also , the library does not get configured as "autochgr", but as "atdd". We are using the IBM's device driver called "atdd" which is custom written for the IBM 3583 Ultrium Scalable Tape Library. We are now looking at configuring the device HW paths (combining the library HW paths with the instance numbers 1 and 2) inside the kernel in "driver $address atdd" into the kernel, as well as putting it into /etc/rc.config.d/atdd.cfg as suggested in some other thread on this subject.
Spyros Fidas_1
Occasional Advisor

Re: Connecting to 3583 LTO with A6795A card

According to IBM & HP the media changer must be configured with schgr driver and not atdd. We had the same problem and we solved removing the atdd driver and reinstalling but at the prompt for autoconfiguation replied with no (atdd_autoch). Try the following link

http://www-1.ibm.com/support/docview.wss?uid=ssg1S7000699
Spyros Fidas_1
Occasional Advisor

Re: Connecting to 3583 LTO with A6795A card

Re: Connecting to 3583 LTO with A6795A card

Unfortunately ioscan/insf won't create the device files for tapes drives handled by atdd. The default atdd installation should have done it, but you can run the atdd_mksf script if/when updates are necessary:

# /opt/OMImag/bin/atdd_mksf | sh

Good luck.
Tom
Murray Lawrence
Occasional Advisor

Re: Connecting to 3583 LTO with A6795A card

Actually, the solution was in the fact that both of the IBM 3583 SAN Data Gateway fibre channel ports (FC1 and FC2) defaults to HostType 2 (aix) and aix uses soft addressing. This means that HP-UX servers cannot connect to these ports and so the ports cannot be shared by hp-ux and aix servers. We had to dedicate one port to aix and the other to hp-ux access.We will leave FC1 to aix and soft addressing, and reconfigure FC2 to HostType hpux and set FC2 to use hard addressing by doing a "setFcHardId 2,100" on the SAN data gateway, ie setting the FCHardID to anything else than 0 or 255. The rest of the setup follows the ATDD install guide.
Solution

Re: Connecting to 3583 LTO with A6795A card

Ah, you're original post just indicated that the device files were missing. HP-UX does require the corresponding SNC FC port to have the HostType set to HP-UX which pretty much precludes sharing that port with any other OS. Using the Autosense/NT HostType on the other port will allow you to use it for others (e.g. we share AIX, SunOS and Windows). Soft vs. hard addressing method is specific to the SAN environment / configuration rather than the OS though.

As previously mentioned, please note that insf will not create the device files any tape devices managed by atdd â the atdd_mksf script has to be run (atdd_mksf | sh) to make the corresponding nodes. The default atdd installation runs this automatically and it will have to be run manually if the configuration changes.