I asked Pierre to reboot his Solaris box & then run 'netstat -i' and 'netstat 
-s',
both before and after generating some activity to his 'Overland' iscsi target.

If you want the raw data, here are the links:
http://www.nwsmith.net/solaris/netstat-i.before
http://www.nwsmith.net/solaris/netstat-i.after
http://www.nwsmith.net/solaris/netstat-s.before
http://www.nwsmith.net/solaris/netstat-s.after

But here are my edited highlights from the 'after' results:

Name  Mtu  Net/Dest      Address        Ipkts  Ierrs Opkts  Oerrs Collis Queue 
lo0   8232 localhost     localhost      76     0     76     0     0      0     
qfe0  1500 epsu82        epsu82         1887   0     1176   0     0      0     
qfe1  1500 A3BBAE6C      A3BBAE6C       7625   0     6632   1170  1314   0     

TCP
        tcpRtoAlgorithm     =     4     tcpRtoMin           =   400
        tcpRtoMax           = 60000     tcpMaxConn          =    -1
        tcpActiveOpens      =    54     tcpPassiveOpens     =    12
        tcpAttemptFails     =     2     tcpEstabResets      =    14
        tcpCurrEstab        =     5     tcpOutSegs          =  6295
        tcpOutDataSegs      =  4842     tcpOutDataBytes     =5424740
        tcpRetransSegs      =  1209     tcpRetransBytes     =1761524
        tcpOutAck           =  1494     tcpOutAckDelayed    =   101
        tcpOutUrg           =     0     tcpOutWinUpdate     =     0
        tcpOutWinProbe      =     0     tcpOutControl       =   114
        tcpOutRsts          =     3     tcpOutFastRetrans   =     0
        tcpInSegs           =  8792
        tcpInAckSegs        =  2419     tcpInAckBytes       =5418881
        tcpInDupAck         =  2240     tcpInAckUnsent      =     0
        tcpInInorderSegs    =  4834     tcpInInorderBytes   =5139812
        tcpInUnorderSegs    =     0     tcpInUnorderBytes   =     0
        tcpInDupSegs        =     2     tcpInDupBytes       =    60
        tcpInPartDupSegs    =     0     tcpInPartDupBytes   =     0
        tcpInPastWinSegs    =     0     tcpInPastWinBytes   =     0
        tcpInWinProbe       =     0     tcpInWinUpdate      =     0
        tcpInClosed         =     0     tcpRttNoUpdate      =   918
        tcpRttUpdate        =  1456     tcpTimRetrans       =   169
        tcpTimRetransDrop   =     0     tcpTimKeepalive     =     0
        tcpTimKeepaliveProbe=     0     tcpTimKeepaliveDrop =     0
        tcpListenDrop       =     0     tcpListenDropQ0     =     0
        tcpHalfOpenDrop     =     0     tcpOutSackRetrans   =   814

IPv4
        ipForwarding        =     2     ipDefaultTTL        =   255
        ipInReceives        =  9117     ipInHdrErrors       =     0
        ipInAddrErrors      =     0     ipInCksumErrs       =     0
        ipForwDatagrams     =     0     ipForwProhibits     =     0
        ipInUnknownProtos   =     0     ipInDiscards        =     0
        ipInDelivers        =   212     ipOutRequests       =  7726
        ipOutDiscards       =     0     ipOutNoRoutes       =     0
        ipReasmTimeout      =    60     ipReasmReqds        =     0
        ipReasmOKs          =     0     ipReasmFails        =     0
        ipReasmDuplicates   =     0     ipReasmPartDups     =     0
        ipFragOKs           =     0     ipFragFails         =     0
        ipFragCreates       =     0     ipRoutingDiscards   =     0
        tcpInErrs           =     0     udpNoPorts          =   153
        udpInCksumErrs      =     0     udpInOverflows      =     0
        rawipInOverflows    =     0     ipsecInSucceeded    =     0
        ipsecInFailed       =     0     ipInIPv6            =     0
        ipOutIPv6           =     0     ipOutSwitchIPv6     =     0

So I think 'qfe1' must be the Ethernet port for iScsi, and it's
showing Output errors and collisions.
This looks bad to me. Maybe a 'duplex' mismatch problem?

On the TCP counters -   tcpRetransSegs, tcpRetransBytes, tcpOutAckDelayed
all look to be relatively high.

I think David was right in suggesting there are possibly two issue occuring here
at the same time.  I think the first is some sort of hardware fault or 
misconfiguration
on the ethernet interfaces or cabling between the initiator & the target.
There may also be some iScsi bug on the initiator or target, but it's difficult
to spot this until the Ethernet link is behaving with a much high level of 
reliability.
Thanks
Nigel Smith
 
 
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to