StoreEver Tape Storage
1751974 Members
4467 Online
108784 Solutions
New Discussion юеВ

NW6 + HP_LTT 3.5 + MSL5026 = Error

 
Marc Gerritsen
Occasional Advisor

NW6 + HP_LTT 3.5 + MSL5026 = Error

Our MSL5026 2xSDLT1 has a very old firmware.
The only connection it has is via FC to a Netware 6 server. I installed HP_LTT 3.5 on the server and when selecting the changer the application errors:
"OC_Exception_c caught: Application Exception 1020 (Logical Device: non-fatal I/O failure, function will continue)"
The application is aborted and the FC adapter driver reports:
"CPQFC: A request with an invalid data buffer length (not mult 4) has been rejected by the driver."

Selecting one of the SDLT drives gives no error.

Anybody a clue on how to upload a new firmnware into the changer?
I do have a serial cable and mslutil, but no firmware image.

Cheers,
Marc
4 REPLIES 4
CA1140755
New Member

Re: NW6 + HP_LTT 3.5 + MSL5026 = Error

Hi

I have a big trouble regarding the use of MSL5026 with netware...can you please help me?...how did you manage connecting nw 6 server with MSL5026?...do you have any drivers for library on netware 6?....please help

I have the following configuration:

1 server DL380 G2 with Win2K SP4 and Backup Software Netvault 7.1, connected into 2/16 FO switch using 2 HBAs and SecurePath (for redundancy); it also has some volumes into a StorageWotks MSA1000 with HSG80 controlers

1 server DL380 G2 with Netware 6.0 SP2 connected into the same 2/16 FO switch using 2 HBAs using SecurePath(for redundancy); ; it also has some volumes into the same StorageWotks MSA1000 with HSG80 controlers

2 server DL380 G2 with RH 2.1AS 2.4.9-e.40 kernel version connected into the same 2/16 FO switch using a HBA for each server

1 MSL5026 with 2 SDLT 160/320 drives connected into the same 2/16 FO switch using 1 NSR 1200E FO router

From the win2K and RH 2.1AS 2.4.9-e.40 kernel version servers I can do bakup just fine (at about 1.2GB/min)through the 2/16 FO switch

The problem is with the Netware server; using the console command

LIST STORAGE ADAPTERS

I can see the following result:

Novell ATA/IDE Host Adapter Module
COMPAQ CD-ROM SN-124 N104
Compaq Unified RAID Driver
Compaq Smart Array 5i Slot 0 ID 0 LUN 0
Compaq StorageWorks 64-Bit/66Mhz FC HBA in Slot 2
COMPAQ NS ROUTER E1200 FW:0316 ID:4 LUN:3
Compaq RA8000 CTRL ID 0 (5000-1FE1-001D-9C10)
Compaq RA8000 CTRL ID 1 (5000-1FE1-001D-9C10)
Compaq RA8000 ID 1 LUN 1 (5000-1FE1-001D-9C10)
Compaq RA8000 ID 1 LUN 2 (5000-1FE1-001D-9C10)
Compaq RA8000 ID 1 LUN 3 (5000-1FE1-001D-9C10)
Unbound Device Object
Unbound Device Object
Unbound Device Object
Compaq StorageWorks 64-Bit/66Mhz FC HBA in Slot 3

Also if I use:

NWCONFIG/DRIVER OPTIONS/CONFIGURE DISK AND STORAGE DEVICES/DISCOVER AND LOAD ADDITIONAL DRIVERS

I can see the following result:

Install found the following hardware but
was unable to find a matching driver:

COMPAQ MSL5000 Series 0421


Press for a list of drivers to
choose from or to continue.

Plese help me find a resolution for may problem
Marc Gerritsen
Occasional Advisor

Re: NW6 + HP_LTT 3.5 + MSL5026 = Error

I use SDLT1 Drives and do not see the MSL as a device (hmmm, cause of problem?)

My list is:
0x0001: Integrated Smart Slot 0 Disk 1 MIR
0x0002: Integrated Smart Slot 0 Disk 2 MIR
0x0004: Compaq StorageWorks Fibre Channel Data Router
0x0006: COMPAQ SuperDLT1 4B4B
0x0007: COMPAQ SuperDLT1 4B4B
0x0008: Compaq RA8000 CTRL ID 1 (5000-1FE1-0010-9FC0)
0x0009: Compaq RA8000 CTRL ID 2 (5000-1FE1-0010-9FC0)

Much shorter, but the server we use for backups has no access to other parts of the SAN, just the tape device, connected via an MDR to a SAN Switch 16.
CA1140755
New Member

Re: NW6 + HP_LTT 3.5 + MSL5026 = Error

Hi Marc

what drivers do you use for your sdlt1 drives....all i can see with LIST STORAGE DEVICES in 3 unbound objects...1 should be the robotic and the other 2 must be the tape drives but my netware 6 sees them as unbound...can you give me some clue?....
Marc Gerritsen
Occasional Advisor

Re: NW6 + HP_LTT 3.5 + MSL5026 = Error

I use Veritas BackupExec v9.0.4202 and I think the OTMCDM.CDM could cause us to see the drive as a SDLT1.
Another server that (accidentely) access to the changer sees the drives as unbound devices, but it does not see the canger.