Another Partial Summary: hba name anomaly

Jarkko Airaksinen JAiraksinen at zed.com
Thu Nov 23 14:41:37 EST 2006


Hello once more,



Almost there!



For some reason scli shows the adapters' models to be different:



        Enter Selection: 1

------------------------------------------------------------------------
------

Host Name                  : superserver2

HBA Model                  : QLA2310

Port                       : 1

Node Name                  : 20-00-00-E0-8C-80-9F-5A

Port Name                  : 21-00-00-E0-8C-80-9F-5A

Port ID                    : A1-0F-00

Serial Number              : A32159

Driver Version             : qlc-20060630-2.16

FCode Version              : 1.14.15

Firmware Version           : 3.03.117 IP

HBA Instance               : 0

OS Instance                : 0

HBA ID                     : 0-QLA2310

Actual Connection Mode     : Point to Point

Actual Data Rate           : 2 Gbps

PortType (Topology)        : NPort

Total Number of Devices    : 4

HBA Status                 : Online

------------------------------------------------------------------------
------



And



        Enter Selection: 2

------------------------------------------------------------------------
------

Host Name                  : superserver2

HBA Model                  : qlc

Port                       : 1

Node Name                  : 20-00-00-E2-8C-1D-3A-3B

Port Name                  : 21-00-00-E2-8C-1D-3A-3B

Port ID                    : A1-00-05

Serial Number              : T52570

Driver Version             : qlc-20060630-2.16

FCode Version              : N/A

Firmware Version           : 3.03.117 IP

HBA Instance               : 1

OS Instance                : 4

HBA ID                     : 1-qlc

Actual Connection Mode     : Point to Point

Actual Data Rate           : 2 Gbps

PortType (Topology)        : NPort

Total Number of Devices    : 4

HBA Status                 : Online

------------------------------------------------------------------------
------



Due to this difference also the devices are in different paths. In dmesg
they show as:

        SUNW,qlc, instance #0

        fibre-channel, instance #4



Do I really have two different models of adapters or is the model
difference due to some misconfiguration? The firmware versions match
though, as well as the driver version.



The one that reports itself to be QLA2310 behaves much better, for
example it accepts new fcode.



Any ideas at all would be much appreciated.



Br,

Jarkko





________________________________

From: Jarkko Airaksinen
Sent: jueves, 23 de noviembre de 2006 18:28
To: 'sunmanagers at sunmanagers.org'
Subject: Partial Summary: hba name anomaly



Hello again,



Well, after upgrading the QLA driver & the SAN, doing a reconfigure boot
and refreshing the fabric_WWN_map the server finally found adapter and
it works. I even downed and upped the ports in the two fc switches and
the failover worked like a charm.



 The only part that still fails is the fcode load: luxadm just doesn't
see the adapter.



Prtdiag shows:

PCI#00    fibre-channel-pcif77,fe05                             66Mhz

PCI#01    SUNW,qlc-pci1077,2300.10+                             66Mhz



Luxadm still finds only the PCI#01 adapter (I think?):

  Found Path to 1 FC100/P, ISP2200, ISP23xx Devices



  Opening Device: /devices/pci at 80,2000/SUNW,qlc at 2/fp at 0,0:devctl

  Detected FCode Version:       ISP2300 Host Adapter fcode version
1.14.15 05/16/06



One of responses I got suggested that the adapters are not identical
(like the name anomaly suggests). However what makes this weird is that
both adapters work with the latest qla driver.



Does anyone know how luxadm searches for the adapters? How come the
QLA2300 driver has no problem with the adapter but luxadm doesn't even
see it?



Thank you,

Jarkko



________________________________

From: Jarkko Airaksinen
Sent: jueves, 23 de noviembre de 2006 14:23
To: 'sunmanagers at sunmanagers.org'
Subject: hba name anomaly



Hello all Gurus out there,



This is another of my FC problems. It's not related to the write
timeouts that I posted here two days ago.



I have obtained another Fujitsu-Siemens Primepower 450 with 4 x 1.1GHz
Sparc64-V processors & 16GB main memory. I'm building it to be exactly
identical with the other PP I have, which means that it will have
exactly the same IO cards:

-2 x QLogic 2300 HBA's

-quad Ethernet adapter



The problem with the new server is that the other adapter just doesn't
attach. I can't see it on my "cfgadm" list either. However at boot dmesg
says:

Nov 23 11:47:31 superserver2 qlc: [ID 308162 kern.info] Qlogic qlc FCA
Driver v20060630-2.16 (0)

Nov 23 11:47:32 superserver2 qlc: [ID 630585 kern.info] NOTICE: Qlogic
qlc(0): Link ONLINE

Nov 23 11:47:32 superserver2 qlc: [ID 694252 kern.info] NOTICE: qlc(0):
Firmware version 3.3.117

Nov 23 11:47:32 superserver2 pcipsy: [ID 370704 kern.info] PCI-device:
SUNW,qlc at 2, qlc0

Nov 23 11:47:32 superserver2 genunix: [ID 936769 kern.info] qlc0 is
/pci at 80,2000/SUNW,qlc at 2

Nov 23 11:47:32 superserver2 qlc: [ID 308162 kern.info] Qlogic qlc FCA
Driver v20060630-2.16 (4)

Nov 23 11:47:34 superserver2 qlc: [ID 630585 kern.info] NOTICE: Qlogic
qlc(4): Link ONLINE

Nov 23 11:47:34 superserver2 qlc: [ID 694252 kern.info] NOTICE: qlc(4):
Firmware version 3.3.117

Nov 23 11:47:34 superserver2 pcipsy: [ID 370704 kern.info] PCI-device:
fibre-channel at 1, qlc4

Nov 23 11:47:34 superserver2 genunix: [ID 936769 kern.info] qlc4 is
/pci at 80,2000/fibre-channel at 1



Also I can see the devices as:

superserver2:/ # ls /devices/pci\@80,2000

SUNW,qlc at 1              SUNW,qlc at 2              fibre-channel at 1

SUNW,qlc at 1:devctl       SUNW,qlc at 2:devctl       fibre-channel at 1:devctl



The prtdiag shows something weird though:

====================================IO
Cards====================================

Slot      Name                      Model                       max
freq.

--------- ------------------------- ---------------------------
----------------

PCI#00    fibre-channel-pcif77,fe05                             66Mhz

PCI#01    SUNW,qlc-pci1077,2300.10+                             66Mhz

PCI#02    pci-pci8086,b154                                      33Mhz



As opposed to a "healthy" server's adapter list:

====================================IO
Cards====================================

Slot      Name                      Model                       max
freq.

--------- ------------------------- ---------------------------
----------------

PCI#00    SUNW,qlc-pci1077,2300.10+                             66Mhz

PCI#01    SUNW,qlc-pci1077,2300.10+                             66Mhz

PCI#02    pci-pci8086,b154                                      33Mhz



I also tried loading the new fcode but the other adapter wasn't found.
Luxadm says:

  Found Path to 1 FC100/P, ISP2200, ISP23xx Devices



On the "healthy" server I see:

  Found Path to 2 FC100/P, ISP2200, ISP23xx Devices



I already have had the adapter replaced once so I can't believe that two
adapters would be defective. I've tried changing slots from the 66MHz
slots to the 33MHz ones but it didn't do any good.



Any ideas why I can't see the other adapter?



-j-



__________________________________________________________________________


La informacion incluida en el presente correo electronico es CONFIDENCIAL,
siendo para el uso exclusivo del/os destinatario/s arriba mencionado/s. Si
usted recibe y lee este correo electronico y no es el destinatario senalado,
el empleado o el agente responsable de entregar el mensaje al destinatario, o
ha recibido esta comunicacion por error, le informamos que esta totalmente
prohibida cualquier divulgacion, distribucion, uso o reproduccion del mismo, y
le rogamos que nos lo notifique inmediatamente respondiendo al mensaje
original a la direccion arriba mencionada y eliminando el mensaje a
continuacion.

The information contained in this e-mail is CONFIDENTIAL and is intended only
for the use of the addressee named above.If the reader of this message is not
the intended recipient or the employee or agent responsible for delivering the
message to the intended recipient, or you have received this communication in
error, please be aware that any diffusion, distribution or duplication of this
communication is strictly forbidden, and please notify us immediately by
return to the original message at the address above eliminating it
afterwards.
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



More information about the summaries mailing list