Last night I did bfu upgrade to snv_128. snv_128 shows some hope, but although 
I have changed settings in emlxs driver (/kernel/drv/emlxs.conf ) to use target 
mode, HBAs are still coming up in initiator mode (I am using LP9002DC which is 
dual port HBA):

r...@opensolaris:~# fcinfo hba-port
HBA Port WWN: 10000000c9328447
        [b]Port Mode: Initiator[/b]
        Port ID: 10000
        OS Device Name: /dev/cfg/c8
        Manufacturer: Emulex
        Model: LP9002L
        Firmware Version: 3.93a0 (C2D3.93A0)
        FCode/BIOS Version: Boot:5.00a5
        Serial Number: 0000C9328447
        Driver Name: emlxs
        Driver Version: 2.50h (2009.10.23.17.15)
        Type: N-port
        State: online
        Supported Speeds: 1Gb 2Gb 
        Current Speed: 2Gb 
        Node WWN: 20000000c9328447
        NPIV Not Supported
HBA Port WWN: 10000000c9328448
        [b]Port Mode: Initiator[/b]
        Port ID: 10100
        OS Device Name: /dev/cfg/c9
        Manufacturer: Emulex
        Model: LP9002L
        Firmware Version: 3.93a0 (C2D3.93A0)
        FCode/BIOS Version: Boot:5.00a5
        Serial Number: 0000C9328448
        Driver Name: emlxs
        Driver Version: 2.50h (2009.10.23.17.15)
        Type: N-port
        State: online
        Supported Speeds: 1Gb 2Gb 
        Current Speed: 2Gb 
        Node WWN: 20000000c9328448
        NPIV Not Supported

Here is content of /kernel/drv/emlxs.conf (without commented lines)

r...@opensolaris:~# grep -P "^[^#\s]" /kernel/drv/emlxs.conf 
console-notices=0;
console-warnings=0;
console-errors=0;
log-notices=0xffffffff;
log-warnings=0xffffffff;
log-errors=0xffffffff;
num-iocbs=1024;
max-xfer-size=339968;
ub-bufs=1000;
network-on=0;
topology=0;
link-speed=0;
ack0=0;
cr-delay=0;
cr-count=1;
assign-alpa=0x00;
adisc-support=1;
pm-support=0;
num-nodes=0;
linkup-delay=10;
enable-npiv=0;
vport-restrict-login=1;
enable-auth=0;
[b]target-mode=1;
ddi-forceattach=1;[/b]

My understanding is the things in the driver config that I need to change are 
to make: "target-mode=1;" and "ddi-forceattach=1;" which I did, but still my 
HBAs are reporting that they are in initiator mode.

Dmesg is reporting a bunch of "Driver attach" messages during the boot, I am 
not sure if they are related to inability of HBAs to work in target mode:

r...@opensolaris:/kernel/drv# dmesg|grep emlxs
Nov 28 23:40:13 opensolaris pci_pci: [ID 370704 kern.info] PCI-device: 
pci10df,f...@5, emlxs1
Nov 28 23:40:13 opensolaris genunix: [ID 936769 kern.info] emlxs1 is 
/p...@0,0/pci10de,7...@8/pci8086,b...@8/pci10df,f...@5
Nov 28 23:40:18 opensolaris emlxs: [ID 349649 kern.info] [ B.0658]emlxs0: 
NOTICE: 720: Link up. (2Gb, fabric)
Nov 28 23:40:18 opensolaris emlxs: [ID 349649 kern.info] [ B.0658]emlxs1: 
NOTICE: 720: Link up. (2Gb, fabric)
Nov 28 23:40:18 opensolaris emlxs: [ID 349649 kern.info] [ B.0AEC]emlxs1: 
NOTICE: 100: Driver attach. (ub_alloc failed: IP support is disabled.)
Nov 28 23:40:18 opensolaris emlxs: [ID 349649 kern.info] [ B.0AEC]emlxs0: 
NOTICE: 100: Driver attach. (ub_alloc failed: IP support is disabled.)
Nov 28 23:40:55 opensolaris emlxs: [ID 349649 kern.info] [ B.0AEC]emlxs1: 
NOTICE: 100: Driver attach. (ub_alloc failed: IP support is disabled.)
Nov 28 23:40:55 opensolaris emlxs: [ID 349649 kern.info] [ B.0AEC]emlxs0: 
NOTICE: 100: Driver attach. (ub_alloc failed: IP support is disabled.)

I would appreciate if someone can please help to resolve this problem.

BTW: I am also getting "emlxs: ddi_modopen drv/fct failed: err 6" messages 
during the boot (1 per HBA)
-- 
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to