On Fri, 2010-09-03 at 11:03 -0700, Joe Eykholt wrote: > On 9/3/10 9:41 AM, Kolte, Harshad wrote: > > Hi Joe, > > > > I attached one of your posts from the open-fcoe portal. > > > > I was wondering if I could ask a couple of questions regarding setting up > > an fcoe initiator in the latest code. > > > > I am doing the following : > > > >> Step 1 : Create a vlan subinterface for the vlan on which to initiate FIP > >> discovery with vconfig > > > >> > /vconfig add eth0 906/ :where vlan 906 is the intended vlan id for > >> > discovery. > >
You can also use the 'fipvlan' tool to do this for you. If I'm not using the service scripts I'll often use 'fipvlan -ac' which will scan all ports for VLANs and create the VLANs for each one discovered. > >> Step 2 : Create fcoe params > > > >> > echo eth0 > /sys/module/fcoe/parameters/create > > That's the old way of doing it, and it looks like you're starting on eth0 > instead > of on the vlan (eth0.906). > I think that 'fipvlan -acs' will discover, create the VLANs and create your FCoE connections on those VLANs. > Depending on the version of the kernel and the fcoe-util tools version, you > should > probably be using fcoeadm and not writing the /sys file directly. > > >> > cat /sys/class/fc_host/host0/symbolic_name > > > > fcoe v0.1 over eth0 > > Funny it still says 0.1 after all this time. We never update that version > number! > > >> Step 3 : Start lldpad daemon > > > >> > lldpad –d > > > >> Step 4 : Start fcoemon and use fcoeadm > > > >> > fcoemon -ds > > > >> > fcoeadm -c eth0 > > Take a look at the QUICKSTART guide within the fcoe-utils.git repository. It has step-by-step instructions on how to get started. What Joe suggested is just fine; the QUICKSTART will use show you how to use the "service" scripts to setup your connection. If you're using the "service" scripts then I would use the configuration files and fcoeadm. If you want to do it more manually I'd do as you and Joe discussed and maybe use 'fipvlan' it's pretty useful. > >> Step 5 : Create virtual port > > > > echo '1111222233334444:5555666677778888' > > > /sys/class/fc_host/host0/vport_create > > > > Should do this be the right sequence of configuration for FCoE ? > > I think that's right. Not sure if fcoe-utils has a more elegant way of > doing this or not. > No, that's the standard interface. I'd love to add a command to fcoeadm for vport creation and deletion, but it hasn't been a priority. Thanks, //Rob _______________________________________________ devel mailing list [email protected] http://www.open-fcoe.org/mailman/listinfo/devel
