Lin Zhu wrote:
> Hello All,
>
> I was trying to use FCGW program to inter-connect two Brocade 200E FC
> switches for testing purposes. I used
>
the following connection topologies:
>
> BRCD-1 <==> ATTO (efc0) ---- ETH (eth1) <==> ETH (eth2) ---- ATTO (efc1)
> <==> BRCD-2
>
> Where "<==>" is physical connections.
>
> I ran the following two commands with debug mode turned on.
> # fcgw -i eth1 -f efc0 -d
> # fcgw -i eth2 -f efc1 -d
>
> After launched the above commands, I saw SW_ILS_ELP (exchange link parameter)
> was successfully exchanged
> between two FC switches and the FC port became E_Port, which is good.
> However, the following SW_ILS_EFP
> (exchange fabric parameter) was rejected (rejection code: unable to perform
> command), causing fabric unable to
> rebuild.
>
> Does anyone has success experience to ISL with FCGW, or FCGW is not intended
> to run ISL?
I don't think this has been tried. It might work, since fcgw (unless -n is
used, which you
wouldn't want) is just a pass-through. You might gry it without the ethernet
step there,
just do 'fcgw -i efc0 -f efc1 -d'. The tachynet driver delivers FCoE
encapsulated frames.
However, the tachynet driver also snoops FLOGIs to get the buffer-to-buffer
credit parameters
correct. Since ISL don't do FLOGI, you may need to do something similar to the
tachynet
driver to get it to do the same for ELP or EFP or whatever.
Good luck, and please let us know how it goes.
Thanks,
Joe
_______________________________________________
devel mailing list
[email protected]
http://www.open-fcoe.org/mailman/listinfo/devel
