vinvishwa wrote:
> here's the capture file.
> -vinvishwa
>
>
> On Thu, Mar 4, 2010 at 1:29 AM, vinvishwa <[email protected]
> <mailto:[email protected]>> wrote:
>
> Hello Sir,
> we are a group of 4 students doing a project titled 'FCoE support
> for gPXE'
> as our academic project.
> I have got open fcoe 2.6.25 initiator
> and 2.6.23 target installed on separate machines on Fedora 8
> and connected point to point via lossless ethernet.
>
> Need some help with the login process
> *>*I am not getting a LS ACC for FLOGI
> while I get LS ACC for PLOGI & PRLI
> why is it so?
> Does it mean the login is not successful?
The frame after FLOGI in your trace is the LS_ACC for the FLOGI.
If you're using Wireshark, it has a bug where it doesn't recognize
the LS_ACC as belonging to the FLOGI, because the addresses are
different. BTW, we're using a non-standard use of FLOGI besides,
which might be why Wireshark doesn't associate the LS_ACC with it.
So, your login is successful.
By the way, the FLOGI frame had a bad FC CRC, according to the capture.
It should've been ignored, but wasn't. Curious. Other frames looked
OK, so maybe the FLOGI frame was altered after the CRC was computed.
> Also its sends a RTV frame
> and replied with LS_RJT
> *>*what does RTV stands for ?
> and what is its importance?
RTV is Request Timeout Value (or something like that). It's
rejected by most targets, and it's optional. The initiator
shouldn't care that it is rejected, and should just go on.
You can ignore it.
> After this it halts.
> Why is it so and what am i missing?
> wireshark capture file attached.
I don't know why it logs off, but it's about 200 seconds after
the RTV reject. What did the initiator do after it logged in?
The PRLI worked and the LS_ACC does indicate target mode.
Usually the initiator will do a Report LUNs or other SCSI
query next, but it didn't.
Good luck.
Joe
_______________________________________________
devel mailing list
[email protected]
http://www.open-fcoe.org/mailman/listinfo/devel
