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 - to delete the fcoe interface, run the following commands: echo <ethx> > /sys/module/libfcoe/parameters/destroy The ethx could be real i/f or vlan i/f. I've used only vlan i/f but real i/f also should work. Anycase your switch is required to forward VN2VN frames which it should w/o having FCF. //Vasu _______________________________________________ devel mailing list devel@open-fcoe.org https://lists.open-fcoe.org/mailman/listinfo/devel
