hi , I think ovs is not necessary to suppot q-in-q which used in pubulic network switch. OVS is used as TOR switch. Let me know, if there are any errors.
-------- 原始邮件 -------- 发件人：discuss-requ...@openvswitch.org 时间：周六 5月14日 02:06 收件人：discuss@openvswitch.org 主题：discuss Digest, Vol 83, Issue 62 >Send discuss mailing list submissions to > discuss@openvswitch.org > >To subscribe or unsubscribe via the World Wide Web, visit > http://openvswitch.org/mailman/listinfo/discuss >or, via email, send a message with subject or body 'help' to > discuss-requ...@openvswitch.org > >You can reach the person managing the list at > discuss-ow...@openvswitch.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of discuss digest..." > > >Today's Topics: > > 1. Multiple vlan headers (Abhijit Bhadra) > 2. Re: Multiple vlan headers (Scott Lowe) > 3. Re: Multiple vlan headers (Scott Lowe) > 4. How to bring a patch port down? (Krishna Pratap) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Fri, 13 May 2016 18:49:33 +0530 >From: Abhijit Bhadra <abhijit.bha...@broadcom.com> >To: discuss@openvswitch.org >Subject: [ovs-discuss] Multiple vlan headers >Message-ID: > <CAPZrj017EDYiovCCnLssXg3Yz5kHCwymJsJA6LiXwZy=v6-...@mail.gmail.com> >Content-Type: text/plain; charset="utf-8" > >Hi, >Is Multiple VLAN headers supported in ovs 2.3.0? I want to achieve q-in-q >by doing push_vlan operations. If it is not supported, which version of >OVS do I need to upgrade to? >Regards, >Abhijit >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: ><http://openvswitch.org/pipermail/discuss/attachments/20160513/a0eae818/attachment-0001.html> > >------------------------------ > >Message: 2 >Date: Fri, 13 May 2016 10:28:47 -0600 >From: Scott Lowe <scott.l...@scottlowe.org> >To: Abhijit Bhadra <abhijit.bha...@broadcom.com> >Cc: discuss@openvswitch.org >Subject: Re: [ovs-discuss] Multiple vlan headers >Message-ID: <78dc5a45-d140-47c5-b2c1-fdadc27b2...@scottlowe.org> >Content-Type: text/plain; charset=us-ascii > >Please see my response below. > > >> On May 13, 2016, at 7:19 AM, Abhijit Bhadra <abhijit.bha...@broadcom.com> >> wrote: >> >> Hi, >> Is Multiple VLAN headers supported in ovs 2.3.0? I want to achieve q-in-q by >> doing push_vlan operations. If it is not supported, which version of OVS do >> I need to upgrade to? > > >I could be mistaken so I'll defer to others more knowledgeable, but I don't >believe Q-in-Q (802.1ad) is supported by OVS: > ><http://openvswitch.org/pipermail/discuss/2015-April/017319.html> > >Things may have changed since that e-mail thread, of course. > >-- >Scott > > > >------------------------------ > >Message: 3 >Date: Fri, 13 May 2016 11:21:24 -0600 >From: Scott Lowe <scott.l...@scottlowe.org> >To: Abhijit Bhadra <abhijit.bha...@broadcom.com> >Cc: "discuss@openvswitch.org ML" <discuss@openvswitch.org> >Subject: Re: [ovs-discuss] Multiple vlan headers >Message-ID: <13d199d2-b47a-4fc6-a962-97935ae97...@scottlowe.org> >Content-Type: text/plain; charset=us-ascii > >Please don't drop the list. Please see my responses inline, prefixed by [SL]. > > >> On May 13, 2016, at 11:09 AM, Abhijit Bhadra <abhijit.bha...@broadcom.com> >> wrote: >> >> Scott, >> Thanks. Then what is the purpose of push_vlan operation? Is it supported on >> ovs 230? Can you provide me an example of ovs-ofctl which involves push_vlan >> operation? > > >[SL] As I understand it (and I'm not an expert), push_vlan would be for adding >a VLAN ID to matched packets, and would be used in a case where you want OVS >to add a VLAN ID to traffic (for whatever reason). More details are available >via the ovs-ofctl(8) man page: > ><http://openvswitch.org/support/dist-docs/ovs-ofctl.8.pdf> > >Your second question is probably best addressed by others on the list. > > >> Regards, >> Abhijit >> >> On May 13, 2016 9:58 PM, "Scott Lowe" <scott.l...@scottlowe.org> wrote: >> Please see my response below. >> >> >> > On May 13, 2016, at 7:19 AM, Abhijit Bhadra <abhijit.bha...@broadcom.com> >> > wrote: >> > >> > Hi, >> > Is Multiple VLAN headers supported in ovs 2.3.0? I want to achieve q-in-q >> > by doing push_vlan operations. If it is not supported, which version of >> > OVS do I need to upgrade to? >> >> >> I could be mistaken so I'll defer to others more knowledgeable, but I don't >> believe Q-in-Q (802.1ad) is supported by OVS: >> >> <http://openvswitch.org/pipermail/discuss/2015-April/017319.html> >> >> Things may have changed since that e-mail thread, of course. >> >> -- >> Scott >> > > > >------------------------------ > >Message: 4 >Date: Fri, 13 May 2016 14:06:33 -0400 >From: Krishna Pratap <singh.pratapkris...@gmail.com> >To: "discuss@openvswitch.org" <discuss@openvswitch.org> >Subject: [ovs-discuss] How to bring a patch port down? >Message-ID: > <CAOTV=VzJ4xd0=xrn99jZgN5-pYCZmw-uHNTrpQz90=xi-tx...@mail.gmail.com> >Content-Type: text/plain; charset="utf-8" > >Hi, > >I am trying to use the "ovs-ofctl mod-port switch port <action>" command to >bring down the patch port I have on my switch . I am using the patch port >to create a link between two switches. I am using ovs 2.1 version. > >When I use the command "ovs-ofctl mod-port br1 port1 down" the patch port >on switch doesn't go down. > > >When I use the command with veth pair ports it works fine. I wanted to know >if I am doing anything wrong or patch port is not supported. > >Thanks >KP > >----------------------------------------------------------------------------- >The log says : > >2016-05-13T17:58:08.474Z|00042|netdev|WARN|failed to set flags for network >device port1: Operation not supported > > >------------------------------------------------------------------------------ > >here is the sample output of what i am trying to do: > > > root@mininet-vm:/root# ovs-vsctl show >aaa4c93f-aa5a-4e41-b565-47c6f100c291 > Bridge "br1" > Port "port1" > Interface "port1" > type: patch > options: {peer="port2"} > Port "br1" > Interface "br1" > type: internal > Bridge "br2" > Port "br2" > Interface "br2" > type: internal > Port "port2" > Interface "port2" > type: patch > options: {peer="port1"} > > >root@mininet-vm:/root# ovs-ofctl show br1 OFPT_FEATURES_REPLY (xid=0x2): >dpid:00006a6100110d4c n_tables:254, n_buffers:256 capabilities: FLOW_STATS >TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP actions: output enqueue >set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src mod_dl_dst mod_nw_src >mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst 1(port1): >addr:2e:2d:25:2b:ae:e7 config: 0 state: 0 speed: 0 Mbps now, 0 Mbps max >LOCAL(br1): addr:6a:61:00:11:0d:4c config: 0 state: 0 speed: 0 Mbps now, 0 >Mbps max OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0 > > > >root@mininet-vm:/root# ovs-ofctl mod-port br1 port1 down > > > >root@mininet-vm:/root# ovs-ofctl show br1 OFPT_FEATURES_REPLY (xid=0x2): >dpid:00006a6100110d4c n_tables:254, n_buffers:256 capabilities: FLOW_STATS >TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP actions: output enqueue >set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src mod_dl_dst mod_nw_src >mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst 1(port1): >addr:2e:2d:25:2b:ae:e7 config: 0 state: 0 speed: 0 Mbps now, 0 Mbps max >LOCAL(br1): addr:6a:61:00:11:0d:4c config: 0 state: 0 speed: 0 Mbps now, 0 >Mbps max OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0 >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: ><http://openvswitch.org/pipermail/discuss/attachments/20160513/2b1bc8a7/attachment.html> > >------------------------------ > >Subject: Digest Footer > >_______________________________________________ >discuss mailing list >discuss@openvswitch.org >http://openvswitch.org/mailman/listinfo/discuss > > >------------------------------ > >End of discuss Digest, Vol 83, Issue 62 >***************************************
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
