On 01/22/2014 09:55 PM, Natti Shwarts wrote:
_'fcoeadm -c eth2.10' _
doesn't work, I receive the error: ' fcoeadm: Failed to open
/sys/module/fcoe/parameters/create'
This is not how you start VN2VN, as I stated in my first reply, do not
do this anymore.
_'echo eth2.10 > /sys/module/libfcoe/parameters__/create_vn2vn'_
Nothing happens, in Wireshark trace I see the following messages:
Probe request
Claim notification
and a lot of beacon messages
This is the legacy way of starting VN2VN, it should work. It worked for
me, but I did not try with a VLAN. When I get a chance to get back to
this I will try with a VLAN.
_'echo eth2.10 > /sys/module/libfcoe/parameters__/create'_
I have the successful FLOGI , but the client can't connect me (I can't
find the PLOGI and PRLI accept, see attached file)
This is not how you start VN2VN, do not do this anymore.
Natti
I am unclear if you're just running these command successively or after
reboots/rmmod. If you just run them sequentially you're going to
initialize data structures with the 'fcoeadm -c eth2.10' and the
initiator will be in Fabric mode, so any commands after this won't do
anything. You need to make sure you destroy the interface before you try
a different style of creating.
I'd suggest that you reboot, i.e. start frest, and then just do 'echo
eth2.10 > /sys/module/libfcoe/parameters/create_vn2vn'.
I will take a look at your logs when I get a chance. I'm just replying
with this info because I won't have time to look at them today.
//Rob
_______________________________________________
fcoe-devel mailing list
[email protected]
http://lists.open-fcoe.org/mailman/listinfo/fcoe-devel
