Hi List,

This is a problem on Solaris 10u{3,4,5}, so sorry to post to the Open 
Solaris list.  Hopefully someone will have some advice for me.

I've got an ongoing problem where my iSCSI scsi_vhci multipaths over 
GigE are not binding to different interfaces.  I've got 5 different 
initiator systems, and they all, to varying degrees, suffer from this 
problem (Make note of IP addresses):

[EMAIL PROTECTED] # iscsiadm list initiator-node
Initiator node name: iqn.1986-03.com.sun:01:00144f7110a0.468d47e4
Initiator node alias: -
        Login Parameters (Default/Configured):
                Header Digest: NONE/-
                Data Digest: NONE/-
        Authentication Type: NONE
        RADIUS Server: NONE
        RADIUS access: unknown
        Configured Sessions: 192.168.0.11 192.168.1.11

[EMAIL PROTECTED] # iscsiadm list target-param -v
Target: iqn.2007-07.edu.berkeley.ssl:iscsi-2.target0
        Alias: -
        Bi-directional Authentication: disabled
        Authentication Type: NONE
        Login Parameters (Default/Configured):
                Data Sequence In Order: yes/-
                Data PDU In Order: yes/-
                Default Time To Retain: 20/-
                Default Time To Wait: 2/-
                Error Recovery Level: 0/-
                First Burst Length: 65536/-
                Immediate Data: yes/-
                Initial Ready To Transfer (R2T): yes/-
                Max Burst Length: 262144/-
                Max Outstanding R2T: 1/-
                Max Receive Data Segment Length: 8192/-
                Max Connections: 1/-
                Header Digest: NONE/-
                Data Digest: NONE/-
        Configured Sessions: 192.168.0.201 192.168.1.201



[EMAIL PROTECTED] # iscsiadm list target -v
Target: iqn.2007-07.edu.berkeley.ssl:iscsi-2.target0
        Alias: -
        TPGT: 1
        ISID: 4000002a0001
        Connections: 1
                CID: -1
                  IP address (Local): 192.168.1.11:32772
                  IP address (Peer): 192.168.1.201:3260
                  Discovery Method: SendTargets
                  Login Parameters (Negotiated):
                        Data Sequence In Order: yes
                        Data PDU In Order: yes
                        Default Time To Retain: 20
                        Default Time To Wait: 2
                        Error Recovery Level: 0
                        First Burst Length: 65536
                        Immediate Data: no
                        Initial Ready To Transfer (R2T): yes
                        Max Burst Length: 262144
                        Max Outstanding R2T: 1
                        Max Receive Data Segment Length: 8192
                        Max Connections: 1
                        Header Digest: NONE
                        Data Digest: NONE

Target: iqn.2007-07.edu.berkeley.ssl:iscsi-2.target0
        Alias: -
        TPGT: 1
        ISID: 4000002a0000
        Connections: 1
                CID: 0
                  IP address (Local): 192.168.1.11:32774
                  IP address (Peer): 192.168.1.201:3260
                  Discovery Method: SendTargets
                  Login Parameters (Negotiated):
                        Data Sequence In Order: yes
                        Data PDU In Order: yes
                        Default Time To Retain: 20
                        Default Time To Wait: 2
                        Error Recovery Level: 0
                        First Burst Length: 65536
                        Immediate Data: no
                        Initial Ready To Transfer (R2T): yes
                        Max Burst Length: 262144
                        Max Outstanding R2T: 1
                        Max Receive Data Segment Length: 8192
                        Max Connections: 1
                        Header Digest: NONE
                        Data Digest: NONE


Note that both paths are on the 192.168.1.0/24 network.  Sometimes I can 
fix this after boot by reseting the discovery addresses, target-param 
and initiator node, but not always.  This effectively breaks the HA 
aspect of my setup, and can impact performance as well. 

The iSCSI SAN devices are the little known Open-E software on module 
running on mostly SuperMicro hardware.  In all other respects, they work 
great.  It's entirely possible that the Open-E end is what is confusing 
Solaris, but is there some way to force one path per network interface?  
I've tried setting static routes, various things with mpathadm, but 
nothing works.  There's some sort of auto-detection gone wrong and user 
commands all seem to work at a higher level.  I hope I'm missing something.

Thanks in advance.

-- 


-     _____/     _____/      /           - Jonathan Loran -           -
-    /          /           /                IT Manager               -
-  _____  /   _____  /     /     Space Sciences Laboratory, UC Berkeley
-        /          /     /      (510) 643-5146 [EMAIL PROTECTED]
- ______/    ______/    ______/           AST:7731^29u18e3
                                 


_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to