Ronnie koch wrote:
Nigel Smith wrote:
Hi Ronnie
Many thanks for cross-posting that interesting &
fairly detailed feedback from the open-fcoe list.
Sometimes detail is good :)
Zhong Wang wrote:
Thanks Ronnie, that explains the Open FCoE initiator
behavior. The debug > trace of Solaris FCoE software can be retrieved by
issuing "echo *ftb/s | mdb -k" with root access. The information could be
hard to understand since it's only for developers, and I can help you
with it.
Thanks for the offer - I might take you up on it :)
Would you please send me a Wireshark capture of the traffic in
your setup? I'd like to see if there are differences from Nigel's
setup.
My setup is in VMware Server with only the 2 VM's (and the VMware host) on a "host-only" vswitch. The target is up to 122 and the initiator Ubuntu 9.04 with kernel 2.6.30-4. I will attach 3 tcpdump traces showing target started first, initiator started first and initiator with nic that supports jumbo frames. The end result is fairly similar
Yes, the first two captures are almost identical to Nigel's.
but the frame sizes negotiation in the last trace is interesting. The target suggests 2048 in a couple of FLOGIs but then accepts a FLOGI from initiator suggesting 2112 but the frame size in the ACC is 1452.
This is a FCoE target bug -- it's hard coded to 1452 when sending ACC
to a FLOGI. I'm opening a CR to track this.
Thanks,
Zhong
The traces were captured with "no ip and no arp" as the Open-FCoE initiator used a single interface for FCoE and IP.
Regards
Ronnie
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
|
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
