All-
Has anyone ever seen inquire and/or jbconfig report that a robot is on
a different SCSI b/t/l combo than the OS reports?
We recently upgraded one of our two NetWorker servers to NetWorker 7.4, as
well as switching the OS from Red Hat Enterprise Linux 2.1 (2.4 kernel) to
Red Hat Enterprise Linux 4 (2.6 kernel).
The library (a partitioned L700) and drives are connected over fibre via
a QLA2342 dual-port FC HBA. The 2.6 kernel probes the busses in a
different order than the 2.4 kernel did, so the QLA2342 HBA now appears
as SCSI bus 2 & 3, whereas before it appeared as 0 & 1. That meant a
re-run of jbconfig.
Here's what "cat /proc/scsi/scsi" reports:
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST336607LC Rev: 0007
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: SEAGATE Model: ST336607LC Rev: 0007
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 06 Lun: 00
Vendor: ESG-SHV Model: SCA HSBP M15 Rev: 0.11
Type: Processor ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: STK Model: L700 Rev: 0314
Type: Medium Changer ANSI SCSI revision: 03
Host: scsi3 Channel: 00 Id: 01 Lun: 00
Vendor: HP Model: Ultrium 3-SCSI Rev: L25S
Type: Sequential-Access ANSI SCSI revision: 03
Host: scsi3 Channel: 00 Id: 02 Lun: 00
Vendor: HP Model: Ultrium 3-SCSI Rev: L25S
Type: Sequential-Access ANSI SCSI revision: 03
That clearly shows that the robot and drives are on bus 3.
However, here's what inquire reports:
[email protected]:SEAGATE ST336607LC 0007|Disk, /dev/sg0
S/N: 3JA2XYYZ00007406QDS0
[email protected]:SEAGATE ST336607LC 0007|Disk, /dev/sg1
S/N: 3JA6XYYH00007426R6Z2
[email protected]:ESG-SHV SCA HSBP M15 0.11|Processor, /dev/sg2
[email protected]:STK L700 0314|Autochanger (Jukebox), /dev/sg3
S/N: STKA02H3W01
ATNN=STK L700 STKA02H3J27
[email protected]:HP Ultrium 3-SCSI L25S|Tape, /dev/nst0
S/N: HU10257N9V
ATNN=HP Ultrium 3-SCSI
HU10257N9V
WWNN=50060B00002E1AFE
WWPN=500104F0006176C9
WW2N=500104F0006176C8
PORT=00000001
[email protected]:HP Ultrium 3-SCSI L25S|Tape, /dev/nst1
S/N: HU10258TAN
ATNN=HP Ultrium 3-SCSI
HU10258TAN
WWNN=50060B00002E216E
WWPN=500104F0006176C6
WW2N=500104F0006176C5
PORT=00000001
Both inquire and jbconfig say that the robot and drives are on bus 1.
Since the drives are accessed via /dev/nst0 and /dev/nst1, they're not
really affected by this discrepancy.
The robot is (or at least it should be). If we use the autodetect choice
with jbconfig, it always picks [email protected] as the control port AND that
seems to work just fine. nsrjb can control the robot correctly.
I don't understand why, though. Anyone encountered this before?
Thanks,
Tim
--
Tim Mooney Tim.Mooney AT ndsu DOT edu
Information Technology Services (701) 231-1076 (Voice)
Room 242-J6, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the body of the email. Please write to networker-request
AT listserv.temple DOT edu if you have any problems with this list. You can access the
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
