To my knowledge the LUS driver set is not part of the IBM Atape drivers.
The IBM Atape drivers add information for the IBM LTO and other tape drives, and the SMC driver which is used by other backup software to control the library robotics.
The LUS driver has to be part of the the Storage node Networker package set.
(Cfgmgr)
---------------- Time: 26 LEDS: 0x538 invoking top level program -- "/usr/lib/methods/startlus" Time: 26 LEDS: 0x539 return code = 0 ****************** no stdout *********** ****************** stderr *********** mkdev: 0514-517 The information provided to this configuration command was not adequate to uniquely identify the device. Provide more device information than the following: type = 'lus' AND subclass = 'scsi' AND class = 'port'
# lsdev -Cc tape rmt0 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP) rmt1 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP) rmt2 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP) rmt3 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP) rmt4 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP) rmt5 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP) rmt6 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP) rmt7 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP) rmt8 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP) rmt9 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP) rmt10 Available 1Z-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt11 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP) rmt12 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP) smc0 Defined 1Z-08-02 IBM 3573 Tape Medium Changer (FCP)
I just put in the commands for changing the driver since I saw them in my AIX 'cheat sheet'. I implied, but didn't mean to, that you needed to use those drivers. Sorry!
mesee2
6 Posts
0
April 21st, 2010 07:00
To my knowledge the LUS driver set is not part of the IBM Atape drivers.
The IBM Atape drivers add information for the IBM LTO and other tape drives, and the SMC driver which is used by other backup software to control the library robotics.
The LUS driver has to be part of the the Storage node Networker package set.
(Cfgmgr)
----------------
Time: 26 LEDS: 0x538
invoking top level program -- "/usr/lib/methods/startlus"
Time: 26 LEDS: 0x539
return code = 0
****************** no stdout ***********
****************** stderr ***********
mkdev: 0514-517 The information provided to this configuration command
was not adequate to uniquely identify the device.
Provide more device information than the following:
type = 'lus' AND subclass = 'scsi' AND class = 'port'
# lsdev -Cc tape
rmt0 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP)
rmt1 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP)
rmt2 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP)
rmt3 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP)
rmt4 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP)
rmt5 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP)
rmt6 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP)
rmt7 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP)
rmt8 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP)
rmt9 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP)
rmt10 Available 1Z-08-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt11 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP)
rmt12 Available 1Z-08-02 LTO Ultrium Tape Drive (FCP)
smc0 Defined 1Z-08-02 IBM 3573 Tape Medium Changer (FCP)
tlemons1
1 Rookie
•
87 Posts
0
April 21st, 2010 07:00
Hi
I just put in the commands for changing the driver since I saw them in my AIX 'cheat sheet'. I implied, but didn't mean to, that you needed to use those drivers. Sorry!
tl
tlemons1
1 Rookie
•
87 Posts
0
April 21st, 2010 07:00
Hi
I'm certainly not an AIX expert, but here are some commands that I jotted down, for the few times I've needed to test with AIX:
lsdev -Cc tape - shows tape devices found
cfgmgr - scans for hardware changes
Replace AIX Atape driver:
rmdev -dl rmtX
/usr/lpp/Atape/deinstl/lpp.deinstal
installp -acXd /tmp/Atape....bin all
cfgmgr
Hope some of this helps!
tl
mesee2
6 Posts
0
April 21st, 2010 08:00
Actually as off as the anwer was it helped alot.
it drove me to /usr/lpp/LGTOnw.node/inst_root
which has the ODM objects to load and unload as well as the methods to configure the LUS device
I ran unodmadd and the odmadd info back followed by the config which brought the device defined and available