What you describe sounds like normal behavior to me.  AIX can dynamically 
recognize new devices and can talk to them.  TSM Define Drive does not try to 
communicate with a device.  The Define Path does try to connect to the device 
but in my experience TSM has to be cycled before it will recognized newly 
defined devices.

David

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Tailor, Mahesh C.
Sent: Wednesday, January 18, 2012 9:41 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Drive and Path Definition

Hello.

I have a PMR on this, but not making much progress on it so thought I would 
send this out on the User List to see if anyone else encountered this issue and 
can suggest a fix.

Here's what I have:

TSM 6.2.3.100
AIX 7.1 (oslevel: 7100-00-04-1140)
IBM FC 5729 8-Gbps FC adapters

SAN Switch: IBM SAN-768A (Brocade DCX)

Atape 12.1.5.0
Sepaton VTL emulating 3584L22 and 3592 tape drives
SANDISCOVERY ON

We define a tape drive on the VTL and present it to the TSM server.  AIX 
discovers the tape drive and I can use itdt (tapeutil) to query the drive.  For 
example...

./itdt -f /dev/rmt0 inquiry
Issuing std inquiry...
Inquiry Data,  Length 96
            0 1  2 3  4 5  6 7  8 9  A B  C D  E F   0123456789ABCDEF
    0000 - 0180 0302 3300 1130 4942 4D20 2020 2020  [.�..3..0IBM     ]
    0010 - 3033 3539 324A 3141 2020 2020 2020 2020  [03592J1A        ]
    0020 - 3035 3039 3638 3030 5347 3131 3032 3330  [05096800SG110230]
    0030 - 3031 2030 0500 0181 0000 0000 0000 0000  [01 0...�........]
    0040 - 0000 0000 0000 0000 0000 0000 0000 0000  [................]
    0050 - 0000 0000 0000 0000 0000 0000 0000 0000  [................]

Exit with code: 0
./itdt -f /dev/rmt0 inquiry 80
Issuing inquiry for page 0x80...
Inquiry Page 0x80,  Length 14
            0 1  2 3  4 5  6 7  8 9  A B  C D  E F   0123456789ABCDEF
    0000 - 0180 000A 5347 3131 3032 3330 3031       [.�..SG11023001  ]

Exit with code: 0

I log into TSM and define the drive.

01/17/12   11:55:36      ANR2017I Administrator ADMIN issued command: DEFINE 
DRIVE
                          kvtl1p1 rmt11 serial=autod elem=autod  (SESSION: 15)
01/17/12   11:55:36      ANR8404I Drive RMT11 defined in library KVTL1P1. 
(SESSION:
                          15)

Then I try to define the path.

01/17/12   11:56:16      ANR2017I Administrator ADMIN issued command: DEFINE 
PATH
                          tsmprd01 rmt11 srct=server destt=drive autod=yes
                          devi=/dev/rmt11 library=kvtl1p1 online=yes  (SESSION: 
15)
01/17/12   11:56:16      ANR8972E DEFINE PATH: Unable to find the element number
                          for drive RMT11 in library KVTL1P1.  (SESSION: 15)
I stop and restart TSM and issue the same command.

01/17/12   12:00:00      ANR2017I Administrator ADMIN issued command: DEFINE 
PATH
                          tsmprd01 rmt11 srct=server destt=drive autod=yes
                          devi=/dev/rmt11 library=kvtl1p1 online=yes  (SESSION: 
1)
01/17/12   12:00:00      ANR8955I Drive RMT11 in library KVTL1P1 with serial 
number
                           is updated with the newly discovered serial number
                          SG11023012. (SESSION: 1)
01/17/12   12:00:00      ANR1720I A path from TSMPRD01 to KVTL1P1 RMT11 has been
                          defined. (SESSION: 1)
Has anyone else seen this problem?  Any ideas?

TIA

Mahesh

________________________________
Notice: The information and attachment(s) contained in this communication are 
intended for the addressee only, and may be confidential and/or legally 
privileged. If you have received this communication in error, please contact 
the sender immediately, and delete this communication from any computer or 
network system. Any interception, review, printing, copying, re-transmission, 
dissemination, or other use of, or taking of any action upon this information 
by persons or entities other than the intended recipient is strictly prohibited 
by law and may subject them to criminal or civil liability. Carilion Clinic 
shall not be liable for the improper and/or incomplete transmission of the 
information contained in this communication or for any delay in its receipt.