UNSOLVED

mesee2

updated

16 years ago

M

mesee2

6 Posts

0

3374

April 21st, 2010 05:00

Networker LUS Driver on AIX

I was having device numbering and discovery issues on AIX 5.2, while running NW 7.5.2

I have 2 libraries available via FC to the AIX server. Only one is currently licensed for use with NW.

When the primary library failed, I forgot about the secondary library and the library was discovered and moved into networker during a networker dev scan

I removed all libraries from networker and also all tape / smc devices from AIX .. now I can only discover the tape devices and single smc from AIX.

I am unable to see anything from the inquire command.

I believe my error was performing an 'rmdev -dl fcs0 -R' to clean up the AIX devices. This appears to have removed some of the definittions necessary for the LUS driver to load and condigure the Legator library contoler.


Any one know the process short of completely trying to Reject the Networker software and re-install?

(Or is that valid to do - without lossing any of my media and index data?)

Thanks

  • mesee2

    6 Posts

    862

    0

    Posted 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

    862

    0

    Posted 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

    862

    0

    Posted 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

    862

    0

    Posted 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