Prasad,

This is one way of doing it.  I did have a problem once where mt just didn't
return any status so you can also do the following:

1) Use tpconfig to map your drives intitially (yes, it will be incorrect but
you'll fix it later)
2) load your tape in the drive with robtest, noting the robotic drive number
3) Use vmoprcmd -d to display the drives and it will show you what drive
index currently has the tape you just loaded.
4) Correlate this index to the initial drive mapping and you now know what
device file corresponds to what robotic drive.
5) Do this for all the drives and then reconfigure your drives properly with
tpconfig.

Hope this helps.

-Dave

-----Original Message-----
From: Prasad Chalikonda [mailto:prasadchalikonda AT yahoo DOT com]
Sent: Saturday, November 17, 2001 2:48 PM
To: veritas-bu
Subject: [Veritas-bu] Ensuring drives are mapped correctly in a SAN env.


Is there a recommended procedure to ensure drives in a Unix env. with 
SSO are mapped correctly?

Let's say my Library has 10 drives, and the device files on my Master go 
from 0cbn to 9cbn.
My strategy is:
1. Manually load a tape in to each drive in the Library.
2. From the server, do an   "mt   -f   /dev/rmt/0cbn offline", and note 
the drive# the tape is ejected from.
3. Let's say it was Drive 1 in the Library. Drives in the Library for 
NBU go from 1 on up, right? In NBU Drive Configuration, I make sure when 
I type the device file as "/dev/rmt/0cbn", the drive is "Drive 1".
4. Repeat step 2 for each drive and note down correspong the Drive # 
which ejects the tape.

Is this a good and sufficient test to ensure everything will work 
properly? Does anyone have a better way of doing this?

Thanks very much.
Prasad.

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu