Hello Frank,
When doing the 'snoop', I find it best to filter on tcp port 3260
traffic, like this:
# snoop -d {device} -o {filename} tcp port 3260
That way you only capture the iscsi traffic, and avoid
collecting a load of SSH traffic on tcp port 22, like you
have just done.
But no real problem, as you can easily filter out the non
interesting TCP streams with Ethereal or WireShark,
using 'Analyze > Follow TCP Stream'.
Ok, so what do we see in your snoop capture:
Packet #25: Initiator -> Target: Login
SessionType=Discovery
AuthMethod=CHAP
InitiatorName=iqn.2005-03.com.sns:mac-manul-pordss-macboo
Packet #27/28: Target->Initiator: login Response
(Success)
AuthMethod=None
Packet #31: Initiator -> Target: Login
HeaderDigest=None
DataDigest=None
Packet #33/34/35: Target->Initiator: Login Response
(Success)
HeaderDigest=None
DataDigest=None
Packet #39: Initiator -> Target: Text Command
SendTargets=All
Packet #40/41: Target->Initiator: Text Response
TargetName=iqn.1986-03.com.sun:02:25515cb7-069d-e4a2-c701-82ef4809bffb
TargetAddress=192.168.1.100,1
TargetAddress=0.0.0.0,1
TargetAddress=[fe80::2e0:81ff:fe57:11d0],1
Packet #44: Initiator -> Target: Logout
(Immediate Delivery - Close Session)
Packet #45: Target->Initiator: Logout Response
(Connection Closed Sucessfully)
So my initial guess would be that the Initiator does not
like the 'Text response' (Packets 40/41) from the Target,
as the Initiator imediately decides to Logout!
(Although there also seem a low number of Key/Value pairs
during the login.)
Regards
Nigel Smith
--
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
