NetWorker 7.3.1 with RedHat 4 I/O Errors

Question

Hi,

Environment
- Server and Storage Node with NetWorker 7.3.1
- OS is Redhat 4 ES
- Jukebox is Dell PV136T with 2 drives LTO-3

When I try to configure the jukebox into a server or storage node, NetWorker cannot "watch" the jukebox with the commando jbconfig or inquire

I execute inquire command with the options -v and -cl, but it display i/o errors. I changed the FC card from a Qlogic2340 to emulex LP9002, but it is the same.

With the qlogic card the the scsi devices is display but the inquire command "watch" them like a disk, because the machine has EMC Clariion in another qlogic card.

What do you need to configure in the Redhat?

I was backing with RedHat 3 with the same hardware arquitecture and it didnt have problems, the jukebox was configure.

In the NetWorker compatibility guide, you can read it is compatible

Regards

Edgar

jherlihy · Answer

This almost sounds like a connectivity issue if you can't see any tape drives or the robot. I'm assuming that the server, storage node, LTO-3 drives and robot are connected to the same SAN fabric.

Are the tape/robot native fibre or do they go through a SCSI-FC bridge? I believe the PV136T can have a rebadged ADIC Pathlight 6101 bridge in it - this bridge has the ability to do its own zoning ("virtual private san"), so you should check to see if this has been enabled also (if you have one).

Have you zoned them correctly on the SAN so that the fibre port on your server's / storage node's HBA is zoned to all of the devices from the library?

With the emulex HBA, have you tried installing/running HBAnyware or using its CLI utilities (lputil etc) to check you can actually see the devices over the fibre? If you can't see anything across the SAN here, then you're not going to be able to see them from the OS either. Make sure you've got the correct emulex driver also, and try re-installing it if you added the card after installing the driver.

Check your HBA's driver config so that it's logging into the SAN with the correct options (point-to-point or loop etc) - also check the port on your switch (if possible) to make sure the HBA is logging in correctly, and check the lights on the back of the card to see if any warning lights are flashing (or hard-on as the case may be).

wangyd · Answer

you can use the HBA's drive scanning the devices,then inquire -cl.
ey:
QL2300,use HP driver unlity:
#cd /opt/hp/hp_fibreutils
#./hp_rescan -a
Rescanning /proc/scsi/qla2300/0...
Rescanning /proc/scsi/qla2300/1...
scsi0 00 00 00 IBM 03584L32 4.02 Medium
scsi0 00 00 01 IBM ULT3580-TD 53Y2 Sequential-Access
scsi0 00 00 02 IBM ULT3580-TD 53Y2 Sequential-Access
scsi0 00 00 03 IBM ULT3580-TD 53Y2 Sequential-Access
scsi0 00 00 04 IBM ULT3580-TD 53Y2 Sequential-Access
scsi0 00 00 05 IBM ULT3580-TD 53Y2 Sequential-Access
scsi0 00 00 06 IBM ULT3580-TD 53Y2 Sequential-Access

[root@jsbackup hp_fibreutils]# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: 03584L32 Rev: 4.02
Type: Medium Changer ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 01
Vendor: IBM Model: ULT3580-TD2 Rev: 53Y2
Type: Sequential-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 02
Vendor: IBM Model: ULT3580-TD2 Rev: 53Y2
Type: Sequential-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 03
Vendor: IBM Model: ULT3580-TD2 Rev: 53Y2
Type: Sequential-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 04
Vendor: IBM Model: ULT3580-TD2 Rev: 53Y2
Type: Sequential-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 05
Vendor: IBM Model: ULT3580-TD2 Rev: 53Y2
Type: Sequential-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 06
Vendor: IBM Model: ULT3580-TD2 Rev: 53Y2
Type: Sequential-Access ANSI SCSI revision: 03
[root@jsbackup res]# inquire -l

-l flag found: searching all LUNs, which may take over 10 minutes per adapter
for some fibre channel adapters. Please be patient.

scsidev@0.0.0:IBM 03584L32 4.02|Autochanger (Jukebox), /dev/sg0
S/N: 0011492187510401
ATNN:IBM 03584L32 0011492187510401
scsidev@0.0.1:IBM ULT3580-TD2 53Y2|Tape, /dev/nst0
S/N: 1149218753
ATNN:IBM ULT3580-TD2 1149218753
scsidev@0.0.2:IBM ULT3580-TD2 53Y2|Tape, /dev/nst1
S/N: 1149218754
ATNN:IBM ULT3580-TD2 1149218754
scsidev@0.0.3:IBM ULT3580-TD2 53Y2|Tape, /dev/nst2
S/N: 1149218755
ATNN:IBM ULT3580-TD2 1149218755
scsidev@0.0.4:IBM ULT3580-TD2 53Y2|Tape, /dev/nst3
S/N: 1149218756
ATNN:IBM ULT3580-TD2 1149218756
scsidev@0.0.5:IBM ULT3580-TD2 53Y2|Tape, /dev/nst4
S/N: 1149218757
ATNN:IBM ULT3580-TD2 1149218757
scsidev@0.0.6:IBM ULT3580-TD2 53Y2|Tape, /dev/nst5
S/N: 1149218758
ATNN:IBM ULT3580-TD2 1149218758

dpinink_silva · Answer

I found that Linux sometimes is a bit hard to configure due to it's drivers. I would suggest to you verify if any additional drivers is required, and if it's loaded in the boot process.

The tapes should work from your OS without any problems, ie. try to use the mt command and/or tar to verify if everything is working from the OS side.

Zonning can also be a problem, but usually my problems with Linux and jukebox remains with drivers and it's load process.

NetWorker

NetWorker 7.3.1 with RedHat 4 I/O Errors

Was this post helpful?