[Veritas-bu] JNI and drives

> -----Original Message-----
> From: Cornely, David [mailto:David_Cornely AT intuit DOT com]
> Sent: Thursday, February 07, 2002 12:01 PM
> To: Veritas-BU
> Subject: RE: [Veritas-bu] JNI and drives
> 
> 
> Try a boot -r.  The /reconfigure method isn't always reliable.
> If you still have a problem run a probe-scsi-all from the ok 
> prompt -- if
> you can't see your drives at that level then you know you have a
> connectivity problem.
> -Dave
>
I concur on the boot -r.

No point in trying probe-scsi-all as JNI card is fibre and
you will not see the drives until the system is booting
and the driver loads.

Question:
Are you using persistent binding? ie. Are you
listing the devices (with WWNN)in the fca-pci/fcaw (assuming
you are not using new Emerald cards) and then
creating the devices in st.conf?  

Look in /var/adm/messages.  You should see messages there
something like:
Jan 23 12:03:42 udal003app unix: fca-pci0: JNI Fibre Channel Adapter model
FCI-1
063
Jan 23 12:03:42 udal003app unix: fca-pci0: SCSI ID 125 / AL_PA 0x1
Jan 23 12:03:42 udal003app unix: fca-pci0: Fibre Channel WWNN:
100000e069c0337b
 WWPN: 200000e069c0337b
Jan 23 12:03:42 udal003app unix: fca-pci0: FCA SCSI/IP Driver Version 2.4.1,
Feb
 14, 2000 for Solaris 2.5,2.6

That is the connection to the switch for the JNI card.

Jan 23 12:03:42 udal003app unix: NOTICE: pci1242,46430 NPORT Initialization
Comp
lete, SID=c0337b
Jan 23 12:03:42 udal003app unix: NOTICE: pci1242,46430 got_plogi_acc: fffffc
Ret
urned version_bb_credit 20060010 common_features_size 80000840
Jan 23 12:03:42 udal003app unix: fca-pci0: New Fabric Parameters Received.
Reset
ting...
Jan 23 12:03:42 udal003app unix: fca-pci0: LINK DOWN
Jan 23 12:03:42 udal003app unix: NOTICE: pci1242,46430 NPORT Initialization
Comp
lete, SID=c0337b
Jan 23 12:03:42 udal003app unix: fca-pci0: LINK UP   (180002ff)

This is the link initializing.

Jan 23 12:03:42 udal003app unix: fca-pci0: Target 0: Port 011301
(100000e0020228
fc:100000e0020228fc) online.
Jan 23 12:03:42 udal003app unix: fca-pci0: Target 0 Lun 0: Port 011301
(100000e0
020228fc:100000e0020228fc) present.
Jan 23 12:03:42 udal003app unix: fca-pci0: Target 1: Port 021800
(100000e00201e2
42:100000e00221e242) online.
Jan 23 12:03:42 udal003app unix: fca-pci0: Target 1 Lun 0: Port 021800
(100000e0
0201e242:100000e00221e242) present.
Jan 23 12:03:42 udal003app unix: fca-pci0: Target 2: Port 021a00
(100000e00201e2
13:100000e00221e213) online.
Jan 23 12:03:42 udal003app unix: fca-pci0: Target 2 Lun 0: Port 021a00
(100000e0
0201e213:100000e00221e213) present.

These are the LUNs

Jan 23 12:03:42 udal003app unix: fca-pci0: Target 0 Lun 1: Port 011301
(100000e0
020228fc:100000e0020228fc) present.
Jan 23 12:03:42 udal003app unix: st127: <QUANTUM DLT7000>
Jan 23 12:03:42 udal003app unix: st127 at pci1242,46430: target 0 lun 1
Jan 23 12:03:42 udal003app unix: st127 is /pci@4,4000/fibre-channel@3/st@0,1
Jan 23 12:03:42 udal003app unix: fca-pci0: Target 0 Lun 2: Port 011301
(100000e0
020228fc:100000e0020228fc) present.

That is the first drive being addressed.


You should see most of these messages (not the drive portion) even if the
entries are not being created in /dev/rmt.  If you are not then something
is wrong with the JNI config.  All of our drives are SCSI based so we
use a fibre to scsi bridge.  If the Gator drives are true fibre it might
look a little different.





Ken Sibley
Sr. Unix Administrator
Accor Economy Lodging
ksibley AT accorel DOT com
469-737-3370
 
> -----Original Message-----
> From: Robert L. Harris [mailto:Robert.L.Harris AT rdlg DOT net]
> Sent: Thursday, February 07, 2002 9:51 AM
> To: Veritas-BU
> Subject: [Veritas-bu] JNI and drives
> 
> 
> 
> I'm rebuilding a server.  It has 2 JNI cards and is attached 
> to a Gator
> with 20 drives.  I have 12 of the drived partitioned off to 
> this server
> in the Gator config.
> 
> Downloaded the latest JNI drivers and ezfibre, installe both.  EZFibre
> is slow as all get out (Java GUI) but still doesn't seem to find the
> drives.  Rebooted with a /reconfigure (same as boot -r).  There are no
> entries created in /dev/rmt meaning it's not seeing the drives.  Has
> anyone run into anything like this?
> 
> 
> 
> :wq!
> --------------------------------------------------------------
> -------------
> Robert L. Harris                |  Micros~1 :  
> Senior System Engineer          |    For when quality, reliability 
>   at RnD Consulting             |      and security just aren't
>                                 \_       that important!
> DISCLAIMER:
>       These are MY OPINIONS ALONE.  I speak for no-one else.
> FYI:
>  perl -e 'print 
> $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>