Just tried OSOL b130, after b122 in which one of my initiators worked using 
qla2342 (though another PC was stopping seeing FC network until rebooting the 
target)
so with  b122 target one of my initiators was seeing LUNs, both in its BIOS and 
OS (windows 7) and rebooting it didnt couse any trouble.
with b130 target the same initiator does not see any LUNs nor target's ports in 
the OS and HBA's bios cannot find find anything either (and sans fabric for 
excessively long time while the target is connected to the switch)
On the target host fcinfo shows that the port is functioning in target mode:
HBA Port WWN: 10000000c94b710c
        Port Mode: Target
        Port ID: 610100
        OS Device Name: Not Applicable
        Manufacturer: Emulex
        Model: LP10000DC
        Firmware Version: 1.92a1 (T2D1.92A1)
        FCode/BIOS Version: none
        Serial Number: VM53084503
        Driver Name: emlxs
        Driver Version: 2.50l (2009.12.02.13.00)
        Type: F-port
        State: online
        Supported Speeds: 1Gb 2Gb
        Current Speed: 2Gb
        Node WWN: 20000000c94b710c

However fcinfo remote-port and stmfadm list-target -v do not return anything.
diffs of my emlxs.conf against stock file
--- /export/home/sivanov/emlxs.conf     Tue Jan 19 21:51:22 2010
+++ /kernel/drv/emlxs.conf      Tue Jan 19 21:53:07 2010
@@ -304,8 +304,8 @@
 # Range:  Min:0  Max:1  Default:0
 #
 target-mode=0;
+emlxs0-target-mode=1

-
 # ddi-forceattach:  Force driver attach during system boot.
 #
 # 0 = Disables forced driver attach during system boot. (Default)
@@ -319,7 +319,7 @@
 # Range:  Min:0  Max:1  Default:0
 #
 # *Uncomment this parameter when target-mode is enabled
-#ddi-forceattach=1
+ddi-forceattach=1


 # fct-bufpool:  Controls buffer pool used by COMSTAR for FCP IOs
@@ -364,4 +364,4 @@
 #                 boot to be available for the emlxs root instance to use.
 #                 This value should not be modified by the user.
 #
-ddi-forceload = "misc/emlxs/emlxs_fw";
+ddi-forceload = "misc/emlxs/emlxs_fw", "drv/fct";

relevant /var/adm/messages entries: 
Jan 19 21:55:28 storage emlxs: [ID 349649 kern.info] [ 6.0ABE]emlxs0: 
NOTICE:1502: Firmware Library (LP10000-S: v1.92a1 (td192a1.all))
Jan 19 21:55:28 storage emlxs: [ID 349649 kern.info] [ 6.0ABE]emlxs0: 
NOTICE:1502: Firmware Library (LP11000-S: v2.82a4 (bd282a4.all))
Jan 19 21:55:28 storage emlxs: [ID 349649 kern.info] [ 6.0ABE]emlxs0: 
NOTICE:1502: Firmware Library (LP11002-S: v2.82a4 (bf282a4.all))
Jan 19 21:55:28 storage emlxs: [ID 349649 kern.info] [ 6.0ABE]emlxs0: 
NOTICE:1502: Firmware Library (LPe11000-S: v2.82a4 (zd282a4.all))
Jan 19 21:55:28 storage emlxs: [ID 349649 kern.info] [ 6.0ABE]emlxs0: 
NOTICE:1502: Firmware Library (LPe11002-S: v2.82a4 (zf282a4.all))
Jan 19 21:55:28 storage emlxs: [ID 349649 kern.info] [ 6.0ABE]emlxs0: 
NOTICE:1502: Firmware Library (LPe12000-S: v1.11a5 (ud111a5.all))
Jan 19 21:55:28 storage emlxs: [ID 349649 kern.info] [ B.175E]emlxs0: NOTICE: 
100: Driver attach. (Emulex-S s11-64 i386 v2.50l (2009.12.02.13.00))
Jan 19 21:55:28 storage emlxs: [ID 349649 kern.info] [ B.1761]emlxs0: NOTICE: 
100: Driver attach. (LP10000DC Dev_id:fa00 Sub_id:fa00 Id:13)
Jan 19 21:55:28 storage emlxs: [ID 349649 kern.info] [ B.1768]emlxs0: NOTICE: 
100: Driver attach. (Firmware:1.92a1 (T2D1.92A1) Boot:none)
Jan 19 21:55:28 storage emlxs: [ID 349649 kern.info] [ B.1797]emlxs0: NOTICE: 
100: Driver attach. (SLI:2 MSI:0 NPIV:0 FCT)
Jan 19 21:55:28 storage emlxs: [ID 349649 kern.info] [ B.179D]emlxs0: NOTICE: 
100: Driver attach. (WWPN:10000000C94B710C WWNN:20000000C94B710C)
Jan 19 21:55:28 storage pci_pci: [ID 370704 kern.info] PCI-device: 
pci10df,f...@2, emlxs0
Jan 19 21:55:28 storage genunix: [ID 936769 kern.info] emlxs0 is 
/p...@0,0/pci1022,7...@a/pci10df,f...@2
Jan 19 21:55:29 storage emlxs: [ID 349649 kern.info] [ 5.053E]emlxs0: NOTICE: 
720: Link up. (2Gb, fabric, target)
Jan 19 21:55:29 storage emlxs: [ID 349649 kern.info] [ 5.031C]emlxs0: NOTICE: 
710: Link down.
Jan 19 21:55:29 storage emlxs: [ID 349649 kern.info] [ 5.05F5]emlxs0: NOTICE: 
730: Link reset. (Disabling link...)
Jan 19 21:55:59 storage emlxs: [ID 349649 kern.info] [ 5.05F5]emlxs0: NOTICE: 
730: Link reset. (Disabling link...)
Jan 19 21:55:59 storage emlxs: [ID 349649 kern.info] [ 5.061E]emlxs0: NOTICE: 
730: Link reset.
Jan 19 21:56:01 storage emlxs: [ID 349649 kern.info] [ 5.053E]emlxs0: NOTICE: 
720: Link up. (2Gb, fabric, target)
Jan 19 21:56:01 storage fct: [ID 132490 kern.notice] NOTICE: emlxs0 LINK UP, 
portid 610100, topology Fabric Pt-to-Pt,speed 2G
echo "*stmf_trace_buf/s" | mdb -k in the file attached
-- 
This message posted from opensolaris.org

Attachment: mdb.out
Description: Binary data

_______________________________________________
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to