Networker inquire issues

[Martin999]

Guys,

Could someone help ... thanks,

The JNI driver has been upgraded from 5.0.x to 5.3.1.3 - the sd, st and jnic146x.conf files were saved and then copied back after the upgrade (reinstall) of the new driver. Box was them re-booted.
As below, the inquire command picks the correct devices and then goes off and lists hundreds of non-exsistant devices ??
Figure the problem is with lus.conf, but it appears ok, have even copied from another working server at same JNI driver level, but no difference.

Any ideas,

Thanks in advance,

Martin

root@xx# inquire -lc

-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 ULT3580-TD1 4561|Tape, /dev/rmt/0cbn
scsidev@0.0.1:IBM 03584L32 4390|Autochanger (Jukebox)
scsidev@0.8.0:IBM ULT3580-TD1 4561|Tape, /dev/rmt/1cbn
scsidev@0.9.0:IBM ULT3580-TD1 4561|Tape, /dev/rmt/9cbn
scsidev@0.10.0:IBM ULT3580-TD1 4561|Tape
scsidev@0.10.1:IBM ULT3580-TD1 4561|Tape
scsidev@0.10.2:IBM ULT3580-TD1 4561|Tape
scsidev@0.10.3:IBM ULT3580-TD1 4561|Tape
scsidev@0.10.4:IBM ULT3580-TD1 4561|Tape
scsidev@0.10.5:IBM ULT3580-TD1 4561|Tape
scsidev@0.10.6:IBM ULT3580-TD1 4561|Tape
scsidev@0.10.7:IBM ULT3580-TD1 4561|Tape
scsidev@0.10.8:IBM ULT3580-TD1 4561|Tape
scsidev@0.10.9:IBM ULT3580-TD1 4561|Tape
scsidev@0.10.10:IBM ULT3580-TD1 4561|Tape
root@xx# pkginfo |grep -i jni
system JNIC146x JNI Fibre Channel SCSI HBA Driver
application JNIsnia JNI SNIA Fibre Channel HBA LIBRARY (Solaris)
system SUNWjfca JNI Fibre Channel Adapter (FCA) Driver
system SUNWjfcau JNI Fibre Channel Adapter (FCA) (usr)
system SUNWjfcaux JNI Fibre Channel Adapter (FCA) (usr) (64-bit)
system SUNWjfcax JNI Fibre Channel Adapter (FCA) Driver (64-bit)
root@ssbak22# pkginfo -l JNIC146x
PKGINST: JNIC146x
NAME: JNI Fibre Channel SCSI HBA Driver
CATEGORY: system,scsi
ARCH: sparc
VERSION: v5.3.1.3 (05012600)
VENDOR: JNI Corp.
PSTAMP: JNIC,HBA
INSTDATE: Sep 12 2005 11:52
EMAIL: support@jni.com <mailto:support@jni.com>
STATUS: completely installed
FILES: 9 installed pathnames
1 directories
6 executables
6489 blocks used (approx)

 

[RMinNJ]

Oh yes, we have this. I reported it to AMCC and Legato;
unfortunately AMCC is no longer updating the driver so it
will not be fixed. That said, the driver is more stable
than all previous ones.

To work around we limited the targets that inquire and (Networker's lus) see. In the lus.conf change;

JNI,FCR:126-1C

to

JNI,FCR:5-1C

This will then display tapes drives and libary arms at targets 0-4. Increase this if your arm or drive is at a
higher target number. Of course, for buses with no targets
at these numbers one still gets phantom devices in inquire;
the output is much less though.

 

[Martin999]

Ah, glad to hear I'm not the only one - I wasn't sure about changing lus.conf, I thought that that would fix, but wanted a bit of reasurance. Thanks

Funny thing is though, this isn't affecting all out machines, with have many at this level of JNI driver, all with the same lus.conf that work fine.

One of those strange ones I think.

Martin