Introduced new parameter dvlan-tags in other-config to support
provider VLANs at access port.

Help and usage of this new parameter is updated vswitch.xml

Signed-off-by: Avinash <avinashand...@gmail.com>
---
 vswitchd/bridge.c    |  3 +++
 vswitchd/vswitch.xml | 32 ++++++++++++++++++++++++++++++++
 2 files changed, 35 insertions(+)

diff --git a/vswitchd/bridge.c b/vswitchd/bridge.c
index 9764c1f..1dc4dc9 100644
--- a/vswitchd/bridge.c
+++ b/vswitchd/bridge.c
@@ -901,6 +901,9 @@ port_configure(struct port *port)
     s.use_priority_tags = smap_get_bool(&cfg->other_config, "priority-tags",
                                         false);

+    s.support_dvlan = smap_get_bool(&cfg->other_config, "dvlan-tags",
+                                    false);
+
     /* Get LACP settings. */
     s.lacp = port_configure_lacp(port, &lacp_settings);
     if (s.lacp) {
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index acefed2..0ea9871 100644
--- a/vswitchd/vswitch.xml
+++ b/vswitchd/vswitch.xml
@@ -940,6 +940,38 @@
           this setting is not meaningful on native-tagged ports.
         </p>
       </column>
+
+      <column name="other_config" key="dvlan-tags"
+              type='{"type": "boolean"}'>
+        <p>
+          This parameter enables double VLAN taggings by the switch ports.
+        </p>
+
+        <p>
+          By setting this parameter as <code>true</code> service provider
+          supports customer VLANs by double tagging the VLAN tag. Each
+          customer packet traversing the service provider network is tagged
+          twice:
+          the inner-most 802.1Q header contains the customer-chosen VLAN ID,
+          and the outer-most header contains the VLAN ID assigned to the
+          customer by the service provider
+        </p>
+
+        <p>
+          By enabling this parameter, the switch port becomes a service
+          provider port and access ports can accept both tagged and untagged
+          frames. Access ports without 'dvlan tags' are called customer ports.
+        </p>
+
+        <p>
+          The behavior of native-tagged, native-untagged and trunk ports
+          remains same regardless of this setting.
+        </p>
+
+        <p>
+          By default, this field is <code>false</code>.
+        </p>
+      </column>
     </group>

     <group title="Bonding Configuration">
--
1.9.0
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to