> 1) If tag and trunks are used for VLAN, under what use cases we need > to use SET_VLAN_ID, STRIP_VLAN_ID actions in openflow in openvswitch, > or they are useless in openvswitch?
Tag and trunks apply to packets as their processed by the OpenFlow NORMAL action. If you don't want to use the NORMAL action, or if you want to modify the VLAN before or after the NORMAL action, you need to use SET_VLAN_ID/STRIP_VLAN_ID. > 2) Is multi-cast and broad-cast handled in openvswitch as well without > openflow? The NORMAL action behaves as a standard L2 switch, and thus properly forward multicast and broadcast traffic. > 3) If multi-cast and broad-cast to be achieved using openflow, would > we need an output action for each forwarding port? Yes. > 4) What is the max. limit of action-lists in a openflow message? There's a 64k limit on the size of an OpenFlow message, so the size in bites of the actions list must be strictly less than this. > 5) What will happen if tag and trunks are used in openvswitch and some > openflow VLAN actions are also specified? What is the order is > processing of both? Or should this combination be forbidden? Depends on the order in which the NORMAL action appears. If, for example, you do set_vlan:5,NORMAL,set_vlan:6,output:7. The NORMAL action will process the packet as if it came in on vlan:5, forward it like a standard ethernet switch, then set the vlan to 6, and forward it on port 7. If you have further questions it may be worth experimenting directly by running the switch and running various combinations. Ethan > > It is a lot of questions. I really appreciate if you could clarify my doubts! > > Thanks! > Yimin > > On Wed, Jun 20, 2012 at 9:26 AM, YIMIN CHEN <ymchen.n...@gmail.com> wrote: >> Hi Ethan, >> >> Thank you very much for your reply! I will take a look at >> ovs-vswitch.conf.db man page. >> >> >> Thanks! >> Yimin >> >> On Wed, Jun 20, 2012 at 4:45 AM, Ethan Jackson <et...@nicira.com> wrote: >>> I'd have a look in the ovs-vswitchd.conf.db man page which documents >>> the tag and trunks options in the port table. With those, you >>> shouldn't need to mess around with OpenFlow at all. >>> >>> Ethan >>> >>> On Mon, Jun 18, 2012 at 8:44 PM, YIMIN CHEN <ymchen.n...@gmail.com> wrote: >>>> Hello, >>>> >>>> I am trying to set up 4 VMs on 2 HOSTs running openflow openvswitchs. >>>> >>>> >>>> HOST 1 HOST2 >>>> >>>> VM1 (vlan 1) VM4 (vlan1) >>>> VM2 (vlan 1) >>>> VM3 (vlan 2) >>>> >>>> The goal is to have VM1, VM2, and VM4 be able to talk to each other, >>>> but not VM3. VM ports are access mode, so VMs do not have VLAN >>>> knowledge. >>>> >>>> My question is how to setup openflow flows to achieve these. I can see >>>> the use of SET_VLAN_ID, OUTPUT, STRIP_VLAN_ID actions in this case, >>>> but couldn't figure out how FLOOD_ACTIONS can be used here. Do I need >>>> to configure STP in order to use FLOOD? Will openvswitch automatically >>>> learn which ports to flood in ARP broadcast case? Or I need explicitly >>>> specify which ports to forward for vlan1, etc? >>>> >>>> Thank you! >>>> Yimin >>>> _______________________________________________ >>>> openflow-discuss mailing list >>>> openflow-discuss@lists.stanford.edu >>>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
