Ultrium2 448 LTO not detected by BackupExec 9.1 b1158.9 - Veritas Backup Exec

This is a discussion on Ultrium2 448 LTO not detected by BackupExec 9.1 b1158.9 - Veritas Backup Exec ; Hi! We have a new tape library: Hp StorageWorks Ultrium2 448 LTO 1x8 autoloader. This tape library doesn't use multiple scsi id's. It uses only one shared for the loader and the drive. Instead of using multiple ID's it uses ...

+ Reply to Thread
Results 1 to 9 of 9

Thread: Ultrium2 448 LTO not detected by BackupExec 9.1 b1158.9

  1. Ultrium2 448 LTO not detected by BackupExec 9.1 b1158.9


    Hi!

    We have a new tape library: Hp StorageWorks Ultrium2 448 LTO 1x8 autoloader.
    This tape library doesn't use multiple scsi id's. It uses only one shared
    for the loader and the drive. Instead of using multiple ID's it uses different
    LUNS to seperate the loader robotics from the drive itself.

    When I boot the server (Novell Open Enterprise (6.5sp3)), the drive is detected.
    However, a "list storage adapters" on the console, shows only the drive and
    not the loader (probably because nwtape.cdm doesn't support the tape library).
    When I start backupexec, becdm.cdm is loaded. After becdm.cdm is loaded,
    a list storage adapters at console DOES show both the loader as well as the
    drive. However, backupexec itself, reports that it cannot find a tape device
    at all!

    Weird is, that when I boot the server, with a tape manually loaded into the
    tape unit, backupexec DOES recognize the drive and gives the message that
    I have to unload the tape from the drive, before doing anything. However,
    as soon as I do that, the drive shows as "disconnected" in backupexec.

    Another thing:
    When I attach the tape library to a scsi adapter which doesn't support multiple
    LUN configuration, the tape device is recognized by Backupexec, but only
    a a standalone device, NOT as a robot.

    The tape library is fairly new. Does anyone of you have any idea how to solve
    this problem? HEEEEELP!!!

  2. Re: Ultrium2 448 LTO not detected by BackupExec 9.1 b1158.9

    Jonas Driessen wrote:

    >
    > Hi!
    >
    > We have a new tape library: Hp StorageWorks Ultrium2 448 LTO 1x8
    > autoloader. This tape library doesn't use multiple scsi id's. It
    > uses only one shared for the loader and the drive. Instead of using
    > multiple ID's it uses different LUNS to seperate the loader robotics
    > from the drive itself.
    >
    > When I boot the server (Novell Open Enterprise (6.5sp3)), the drive
    > is detected. However, a "list storage adapters" on the console,
    > shows only the drive and not the loader (probably because nwtape.cdm
    > doesn't support the tape library). When I start backupexec,
    > becdm.cdm is loaded. After becdm.cdm is loaded, a list storage
    > adapters at console DOES show both the loader as well as the drive.
    > However, backupexec itself, reports that it cannot find a tape device
    > at all!
    >
    > Weird is, that when I boot the server, with a tape manually loaded
    > into the tape unit, backupexec DOES recognize the drive and gives the
    > message that I have to unload the tape from the drive, before doing
    > anything. However, as soon as I do that, the drive shows as
    > "disconnected" in backupexec.
    >
    > Another thing:
    > When I attach the tape library to a scsi adapter which doesn't
    > support multiple LUN configuration, the tape device is recognized by
    > Backupexec, but only a a standalone device, NOT as a robot.
    >
    > The tape library is fairly new. Does anyone of you have any idea how
    > to solve this problem? HEEEEELP!!!


    With Backup Exec loaded, can you type LIST STORAGE ADAPTERS and then
    post back here with the results.

    Also, can you post a copy of STARTUP.NCF as well.

    Chris


  3. Re: Ultrium2 448 LTO not detected by BackupExec 9.1 b1158.9


    Hi Chris,

    Thanks for your fast reply!

    list storage adapters after backupexec is started:

    SVSRVC01:list storage adapters
    0x00 [V100-A100] USB UHCI Controller [slot 0]
    0x01 [V100-A101] USB UHCI Controller [slot 0]
    0x02 [V100-A102] USB UHCI Controller [slot 0]
    0x03 [V100-A103] USB UHCI Controller [slot 0]
    0x04 [V100-A104] USB EHCI Controller [slot 0]
    0x05 [V025-A0] Novell ATA/IDE Host Adapter Module [slot 0]
    0x10 [V025-A0-D0:0] TSSTcorp CD-ROM TS-L162C f/w:N204
    0x06 [V504-A1] HP Unified RAID Driver [slot 10019]
    0x09 [V504-A1-D0:0] HP Smart Array 6i Slot 0 ID 0 LUN 0
    0x07 [V358-A2] LSI_53C1030:00101 [slot 101]
    0x12 [V358-A2-D5:1] HP 1x8 autoloader 1.50
    0x11 [V358-A2-D5:0] HP ULTRIUM 2-SCSI S53W
    0x08 [V358-A3] LSI_53C1030:00102 [slot 102]

    Startup.ncf

    LOAD ACPIDRV.PSM
    LOAD IDECD.CDM
    LOAD CPQSHD.CDM
    LOAD IDEATA.HAM SLOT=10011
    LOAD CPQRAID.HAM SLOT=10019
    LOAD LSIMPTNW.HAM SLOT=101
    LOAD LSIMPTNW.HAM SLOT=102

    P.S. Although nwtape.cdm is not started in startup.ncf, it is automaticaly
    loaded.

    With regards!

    Jonas Driessen


    "Chris" wrote:
    >Jonas Driessen wrote:
    >
    >>
    >> Hi!
    >>
    >> We have a new tape library: Hp StorageWorks Ultrium2 448 LTO 1x8
    >> autoloader. This tape library doesn't use multiple scsi id's. It
    >> uses only one shared for the loader and the drive. Instead of using
    >> multiple ID's it uses different LUNS to seperate the loader robotics
    >> from the drive itself.
    >>
    >> When I boot the server (Novell Open Enterprise (6.5sp3)), the drive
    >> is detected. However, a "list storage adapters" on the console,
    >> shows only the drive and not the loader (probably because nwtape.cdm
    >> doesn't support the tape library). When I start backupexec,
    >> becdm.cdm is loaded. After becdm.cdm is loaded, a list storage
    >> adapters at console DOES show both the loader as well as the drive.
    >> However, backupexec itself, reports that it cannot find a tape device
    >> at all!
    >>
    >> Weird is, that when I boot the server, with a tape manually loaded
    >> into the tape unit, backupexec DOES recognize the drive and gives the
    >> message that I have to unload the tape from the drive, before doing
    >> anything. However, as soon as I do that, the drive shows as
    >> "disconnected" in backupexec.
    >>
    >> Another thing:
    >> When I attach the tape library to a scsi adapter which doesn't
    >> support multiple LUN configuration, the tape device is recognized by
    >> Backupexec, but only a a standalone device, NOT as a robot.
    >>
    >> The tape library is fairly new. Does anyone of you have any idea how
    >> to solve this problem? HEEEEELP!!!

    >
    >With Backup Exec loaded, can you type LIST STORAGE ADAPTERS and then
    >post back here with the results.
    >
    >Also, can you post a copy of STARTUP.NCF as well.
    >
    >Chris
    >



  4. Re: Ultrium2 448 LTO not detected by BackupExec 9.1 b1158.9

    Jonas Driessen wrote:

    >
    > Hi Chris,
    >
    > Thanks for your fast reply!
    >
    > list storage adapters after backupexec is started:
    >
    > SVSRVC01:list storage adapters
    > 0x00 [V100-A100] USB UHCI Controller [slot 0]
    > 0x01 [V100-A101] USB UHCI Controller [slot 0]
    > 0x02 [V100-A102] USB UHCI Controller [slot 0]
    > 0x03 [V100-A103] USB UHCI Controller [slot 0]
    > 0x04 [V100-A104] USB EHCI Controller [slot 0]
    > 0x05 [V025-A0] Novell ATA/IDE Host Adapter Module [slot 0]
    > 0x10 [V025-A0-D0:0] TSSTcorp CD-ROM TS-L162C f/w:N204
    > 0x06 [V504-A1] HP Unified RAID Driver [slot 10019]
    > 0x09 [V504-A1-D0:0] HP Smart Array 6i Slot 0 ID 0 LUN 0
    > 0x07 [V358-A2] LSI_53C1030:00101 [slot 101]
    > 0x12 [V358-A2-D5:1] HP 1x8 autoloader 1.50
    > 0x11 [V358-A2-D5:0] HP ULTRIUM 2-SCSI S53W
    > 0x08 [V358-A3] LSI_53C1030:00102 [slot 102]
    >
    > Startup.ncf
    >
    > LOAD ACPIDRV.PSM
    > LOAD IDECD.CDM
    > LOAD CPQSHD.CDM
    > LOAD IDEATA.HAM SLOT=10011
    > LOAD CPQRAID.HAM SLOT=10019
    > LOAD LSIMPTNW.HAM SLOT=101
    > LOAD LSIMPTNW.HAM SLOT=102
    >
    > P.S. Although nwtape.cdm is not started in startup.ncf, it is
    > automaticaly loaded.


    Hi Jonas,

    Not good news I'm afraid - looks like you need to replace your SCSI
    controller:

    http://support.veritas.com/docs/278402

    Hope that helps.

    Chris


  5. Re: Ultrium2 448 LTO not detected by BackupExec 9.1 b1158.9


    Thanks for your answer. Replacing the scsi controller. Well, worth a shot!
    I'm going to discuss this with the supplier! I'll let you know if this solved
    the problem!

    Thanks again!

    Jonas Driessen

    "Chris" wrote:
    >Jonas Driessen wrote:
    >
    >>
    >> Hi Chris,
    >>
    >> Thanks for your fast reply!
    >>
    >> list storage adapters after backupexec is started:
    >>
    >> SVSRVC01:list storage adapters
    >> 0x00 [V100-A100] USB UHCI Controller [slot 0]
    >> 0x01 [V100-A101] USB UHCI Controller [slot 0]
    >> 0x02 [V100-A102] USB UHCI Controller [slot 0]
    >> 0x03 [V100-A103] USB UHCI Controller [slot 0]
    >> 0x04 [V100-A104] USB EHCI Controller [slot 0]
    >> 0x05 [V025-A0] Novell ATA/IDE Host Adapter Module [slot 0]
    >> 0x10 [V025-A0-D0:0] TSSTcorp CD-ROM TS-L162C f/w:N204
    >> 0x06 [V504-A1] HP Unified RAID Driver [slot 10019]
    >> 0x09 [V504-A1-D0:0] HP Smart Array 6i Slot 0 ID 0 LUN 0
    >> 0x07 [V358-A2] LSI_53C1030:00101 [slot 101]
    >> 0x12 [V358-A2-D5:1] HP 1x8 autoloader 1.50
    >> 0x11 [V358-A2-D5:0] HP ULTRIUM 2-SCSI S53W
    >> 0x08 [V358-A3] LSI_53C1030:00102 [slot 102]
    >>
    >> Startup.ncf
    >>
    >> LOAD ACPIDRV.PSM
    >> LOAD IDECD.CDM
    >> LOAD CPQSHD.CDM
    >> LOAD IDEATA.HAM SLOT=10011
    >> LOAD CPQRAID.HAM SLOT=10019
    >> LOAD LSIMPTNW.HAM SLOT=101
    >> LOAD LSIMPTNW.HAM SLOT=102
    >>
    >> P.S. Although nwtape.cdm is not started in startup.ncf, it is
    >> automaticaly loaded.

    >
    >Hi Jonas,
    >
    >Not good news I'm afraid - looks like you need to replace your SCSI
    >controller:
    >
    >http://support.veritas.com/docs/278402
    >
    >Hope that helps.
    >
    >Chris
    >



  6. SOLVED: Re: Ultrium2 448 LTO not detected by BackupExec 9.1 b1158.9


    Hi Chris!

    According the the compatibility matrix of HP, the driver for the scsi adpater
    needed to be upgraded from 3.08 to 4.01. I did this and the problem is solved!
    Pfew!

    Thanks for all the help!
    http://www.hp.com/products1/storage/...0029-0059.html


    "Jonas Driessen" wrote:
    >
    >Thanks for your answer. Replacing the scsi controller. Well, worth a shot!
    >I'm going to discuss this with the supplier! I'll let you know if this solved
    >the problem!
    >
    >Thanks again!
    >
    >Jonas Driessen
    >
    >"Chris" wrote:
    >>Jonas Driessen wrote:
    >>
    >>>
    >>> Hi Chris,
    >>>
    >>> Thanks for your fast reply!
    >>>
    >>> list storage adapters after backupexec is started:
    >>>
    >>> SVSRVC01:list storage adapters
    >>> 0x00 [V100-A100] USB UHCI Controller [slot 0]
    >>> 0x01 [V100-A101] USB UHCI Controller [slot 0]
    >>> 0x02 [V100-A102] USB UHCI Controller [slot 0]
    >>> 0x03 [V100-A103] USB UHCI Controller [slot 0]
    >>> 0x04 [V100-A104] USB EHCI Controller [slot 0]
    >>> 0x05 [V025-A0] Novell ATA/IDE Host Adapter Module [slot 0]
    >>> 0x10 [V025-A0-D0:0] TSSTcorp CD-ROM TS-L162C f/w:N204
    >>> 0x06 [V504-A1] HP Unified RAID Driver [slot 10019]
    >>> 0x09 [V504-A1-D0:0] HP Smart Array 6i Slot 0 ID 0 LUN 0
    >>> 0x07 [V358-A2] LSI_53C1030:00101 [slot 101]
    >>> 0x12 [V358-A2-D5:1] HP 1x8 autoloader 1.50
    >>> 0x11 [V358-A2-D5:0] HP ULTRIUM 2-SCSI S53W
    >>> 0x08 [V358-A3] LSI_53C1030:00102 [slot 102]
    >>>
    >>> Startup.ncf
    >>>
    >>> LOAD ACPIDRV.PSM
    >>> LOAD IDECD.CDM
    >>> LOAD CPQSHD.CDM
    >>> LOAD IDEATA.HAM SLOT=10011
    >>> LOAD CPQRAID.HAM SLOT=10019
    >>> LOAD LSIMPTNW.HAM SLOT=101
    >>> LOAD LSIMPTNW.HAM SLOT=102
    >>>
    >>> P.S. Although nwtape.cdm is not started in startup.ncf, it is
    >>> automaticaly loaded.

    >>
    >>Hi Jonas,
    >>
    >>Not good news I'm afraid - looks like you need to replace your SCSI
    >>controller:
    >>
    >>http://support.veritas.com/docs/278402
    >>
    >>Hope that helps.
    >>
    >>Chris
    >>

    >



  7. Re: SOLVED: Re: Ultrium2 448 LTO not detected by BackupExec 9.1 b1158.9

    Jonas Driessen wrote:

    >
    > Hi Chris!
    >
    > According the the compatibility matrix of HP, the driver for the scsi
    > adpater needed to be upgraded from 3.08 to 4.01. I did this and the
    > problem is solved! Pfew!
    >
    > Thanks for all the help!
    > http://www.hp.com/products1/storage/...ckup/ISS/Detai
    > l/16-0029-0059.html



    Hi Jonas,

    Thanks for the update. Did HP advise you to update the LSIMPTNW.HAM
    driver?

    Regards,

    Chris


  8. Re: SOLVED: Re: Ultrium2 448 LTO not detected by BackupExec 9.1 b1158.9


    Hi Chris,

    Indeed, according to the link I pasted:
    http://www.hp.com/products1/storage/...0029-0059.html
    (found it through your link)
    an update was available for the LSI driver.

    Now the drive is properly detected. I can also run inventories (checking
    backup as we speak).

    Greets!
    Jonas



    "Chris" wrote:
    >Jonas Driessen wrote:
    >
    >>
    >> Hi Chris!
    >>
    >> According the the compatibility matrix of HP, the driver for the scsi
    >> adpater needed to be upgraded from 3.08 to 4.01. I did this and the
    >> problem is solved! Pfew!
    >>
    >> Thanks for all the help!
    >> http://www.hp.com/products1/storage/...ckup/ISS/Detai
    >> l/16-0029-0059.html

    >
    >
    >Hi Jonas,
    >
    >Thanks for the update. Did HP advise you to update the LSIMPTNW.HAM
    >driver?
    >
    >Regards,
    >
    >Chris
    >



  9. Re: SOLVED: Re: Ultrium2 448 LTO not detected by BackupExec 9.1 b1158.9

    Jonas Driessen wrote:

    >
    > Hi Chris,
    >
    > Indeed, according to the link I pasted:
    > http://www.hp.com/products1/storage/...ckup/ISS/Detai
    > l/16-0029-0059.html (found it through your link)
    > an update was available for the LSI driver.
    >
    > Now the drive is properly detected. I can also run inventories
    > (checking backup as we speak).


    OK, glad to hear that all is working well now :-)

    Chris


+ Reply to Thread