> On Fri, 2012-08-17 at 09:32 -0700, Vasu Dev wrote: > > On Thu, 2012-08-16 at 11:24 -0500, Andrew Theurer wrote: > > > > Aug 16 09:02:01 spv-20 fcoemon: eth9, DONE -> INIT > > > > > > I just need to get FIP VLAN requests to work now :) > > > > You would need FCF to respond to the FIP VLAN request with DCBX FCoE > > APP TLV in sync. > > > > > > > > > Aug 16 09:02:02 spv-20 fcoemon: eth9: VLAN discovery TIMEOUT [1] > > > > Aug 16 09:02:02 spv-20 fcoemon: creating netlink socket Aug 16 > > > > 09:02:02 spv-20 fcoemon: sending FIP VLAN request Aug 16 09:02:03 > > > > spv-20 fcoemon: eth9: VLAN discovery TIMEOUT [2] Aug 16 09:02:03 > > > > spv-20 fcoemon: creating netlink socket Aug 16 09:02:03 spv-20 > > > > fcoemon: sending FIP VLAN request > > > > > > I assume this is a switch-side problem which I'll investigate. I am > > > not using an FCF so I guess I need to manually create a VLAN for my > > > FCoE ports? > > > > Without FCF, no FIP VLAN discovery. You could use VN2VN instead w/o > > FCF as Ross mentioned in earlier post :- > > > > Yes, with VN2VN and the TCM target. > > http://www.open-fcoe.org/open-fcoe/wiki/tcm-fcoe-target-guide > > > > - Virtual N-port to virtual N-port (back-to-back) connection: > > > > - run the following commands to create vn-to-vn interface in both > > initiator and target: > > echo <ethx> > /sys/module/libfcoe/parameters/create_vn2vn > > assuming using interface eth2 > > I am getting an error when trying that: > > > [root@spv-20 ~]# echo eth8 > > >/sys/module/libfcoe/parameters/create_vn2vn > > -bash: echo: write error: File exists > > I tried this in RHEL 6.3 kernel and a newly built 3.6-rc2 kernel. Is there > some > kernel build option I am missing? Or perhaps "eth8" is somehow not > compatible? Or something already done by fcoemon prevents this from > working?
There shouldn't be anything special about a port that would make it compatible for VN2VN or not. Also, fcoemon doesn't know about VN2VN right now. The VN2VN instructions have you interact directly with the kernel. In "Fabric" mode you use 'fcoeadm' or the cfg-ethX files for actions (i.e. create, destroy, etc...). In both of those cases it is 'fcoemon' that ultimately tells the kernel to create or destroy. We simply don't have VN2VN support in fcoemon/fcoeadm at this point although it is loosely planned. 'fcoeadm' will still display information about VN2VN ports however, it just won't take any VN2VN actions. There is also no kernel parameter needed, so you should be all set there... I don't know why you'd get that error off the top of my head. You could try turning on some debug logging to see if there's anything interesting going on. echo 0xFFFF > /sys/module/libfcoe/parameters/debug_logging There's debug logging for libfc, libfcoe and fcoe, but I start with libfcoe. //Rob _______________________________________________ devel mailing list devel@open-fcoe.org https://lists.open-fcoe.org/mailman/listinfo/devel
