<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic G/D/C/B/A-Series f/w 6.03 Use of the LLDP-MED Network-Policy TLV feature in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/g-d-c-b-a-series-f-w-6-03-use-of-the-lldp-med-network-policy-tlv/m-p/42167#M94</link>
    <description>Article ID: 12931 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
G-Series, firmware 6.03.00.0022 and higher&lt;BR /&gt;
D-Series, firmware 6.03.01.0008 and higher&lt;BR /&gt;
C5-Series, all firmware&lt;BR /&gt;
C3-Series, firmware 6.03.00.0022 and higher&lt;BR /&gt;
B5-Series, all firmware&lt;BR /&gt;
B3-Series, firmware 6.03.00.0022 and higher&lt;BR /&gt;
A4-Series, firmware 6.61.02.0007 and higher &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Goals&lt;/B&gt;&lt;BR /&gt;
One of the new features cited in version 6.03 &lt;A href="http://extranet.enterasys.com/downloads/" target="_blank" rel="nofollow noreferrer noopener"&gt;release notes&lt;/A&gt;, in the '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;What's New in 6.03&lt;/PRE&gt;&lt;/DIV&gt;' section, is a new TLV (Type/Length/Value) option enhancement to LLDP-MED (&lt;A href="http://bit.ly/1cjCGTD" target="_blank" rel="nofollow noreferrer noopener"&gt;7573&lt;/A&gt;&lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;BR /&gt;
&lt;B&gt;&lt;/B&gt;&lt;PRE&gt;&lt;B&gt;LLDP-MED Network-Policy TLV&lt;/B&gt;&lt;/PRE&gt; &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;reduces deployment costs of VoIP deployments by enabling standards-based provisioning of VoIP phones. The switches can be configured to assign VLAN, QoS, rate-limiting, and others operational parameters for LLDP-MED enabled VoIP phones. When combined with Enterasys Policy at the edge, this is a powerful, low cost solution for deploying convergent networks.&lt;/PRE&gt;&lt;/DIV&gt; &lt;BR /&gt;
&lt;BR /&gt;
This document discusses the concept of configuring to use the new feature, including a sample configuration. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
The LLDP-MED Network-Policy TLV feature may be used to communicate some combination of VLAN, Priority, and/or DSCP value to an LLDP-MED-compliant IP Phone:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set lldp port network-policy voice state enable tag tagged vid&lt;/PRE&gt;&lt;/DIV&gt; &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;vlan&lt;/I&gt;&lt;/PRE&gt;&amp;gt; &lt;BR /&gt;
   &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;cos&lt;/PRE&gt;&lt;/DIV&gt; &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;priority&lt;/I&gt;&lt;/PRE&gt;&amp;gt; &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;dscp&lt;/PRE&gt;&lt;/DIV&gt; &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;dscp&lt;/I&gt;&lt;/PRE&gt;&amp;gt; &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;ports&lt;/I&gt;&lt;/PRE&gt;&amp;gt;&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set lldp port tx-tlv med-pol sys-name port-desc&lt;/PRE&gt;&lt;/DIV&gt;  &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;ports&lt;/I&gt;&lt;/PRE&gt;&amp;gt;&lt;BR /&gt;
&lt;BR /&gt;
Note: If just activating the above-stated tx-tlv advertisements does not have the desired effect, then consider activating &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;all&lt;/PRE&gt;&lt;/DIV&gt; advertisement ('&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set lldp port tx-tlv all&lt;/PRE&gt;&lt;/DIV&gt;  &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;ports&lt;/I&gt;&lt;/PRE&gt;&amp;gt;').&lt;BR /&gt;
&lt;BR /&gt;
Recognizing that an IP Phone typically transmits its traffic VLAN-tagged while its attached PC's traffic is transmitted untagged, the phone would accept and utilize those same values in its VLAN Tag (VLAN, Priority) and IP Header (DSCP)(&lt;A href="http://bit.ly/1rOVKny" target="_blank" rel="nofollow noreferrer noopener"&gt;5811&lt;/A&gt;). &lt;BR /&gt;
&lt;BR /&gt;
On the switch one might then configure Policy or DiffServ (&lt;A href="http://bit.ly/18F0WPL" target="_blank" rel="nofollow noreferrer noopener"&gt;5848&lt;/A&gt;) to interpret any incoming (probably DSCP) value to yield a Policy Role or DiffServ action. Since VLAN and Priority are directly assignable using Policy, it would make sense to advertise the VLAN and Priority via LLDP-MED only in the absence of Policy. However, this is totally up to the user, based on the network design. &lt;BR /&gt;
&lt;BR /&gt;
Here, LLDP-MED would replace the possible use of CiscoDP to communicate a "VVID" (Voice VLAN ID) to the phone (&lt;A href="http://bit.ly/JI2puL" target="_blank" rel="nofollow noreferrer noopener"&gt;5831&lt;/A&gt;). With CiscoDP, if the design calls for the phone to use a Priority or DSCP value, this requires phone configuration. &lt;BR /&gt;
&lt;BR /&gt;
For more background regarding the LLDP command set, please refer to the &lt;A href="http://extranet.enterasys.com/downloads/" target="_blank" rel="nofollow noreferrer noopener"&gt;Configuration Guide&lt;/A&gt; for your product and firmware line.</description>
    <pubDate>Wed, 01 Jan 2014 02:57:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2014-01-01T02:57:00Z</dc:date>
    <item>
      <title>G/D/C/B/A-Series f/w 6.03 Use of the LLDP-MED Network-Policy TLV feature</title>
      <link>https://community.extremenetworks.com/t5/faqs/g-d-c-b-a-series-f-w-6-03-use-of-the-lldp-med-network-policy-tlv/m-p/42167#M94</link>
      <description>Article ID: 12931 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
G-Series, firmware 6.03.00.0022 and higher&lt;BR /&gt;
D-Series, firmware 6.03.01.0008 and higher&lt;BR /&gt;
C5-Series, all firmware&lt;BR /&gt;
C3-Series, firmware 6.03.00.0022 and higher&lt;BR /&gt;
B5-Series, all firmware&lt;BR /&gt;
B3-Series, firmware 6.03.00.0022 and higher&lt;BR /&gt;
A4-Series, firmware 6.61.02.0007 and higher &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Goals&lt;/B&gt;&lt;BR /&gt;
One of the new features cited in version 6.03 &lt;A href="http://extranet.enterasys.com/downloads/" target="_blank" rel="nofollow noreferrer noopener"&gt;release notes&lt;/A&gt;, in the '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;What's New in 6.03&lt;/PRE&gt;&lt;/DIV&gt;' section, is a new TLV (Type/Length/Value) option enhancement to LLDP-MED (&lt;A href="http://bit.ly/1cjCGTD" target="_blank" rel="nofollow noreferrer noopener"&gt;7573&lt;/A&gt;&lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;BR /&gt;
&lt;B&gt;&lt;/B&gt;&lt;PRE&gt;&lt;B&gt;LLDP-MED Network-Policy TLV&lt;/B&gt;&lt;/PRE&gt; &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;reduces deployment costs of VoIP deployments by enabling standards-based provisioning of VoIP phones. The switches can be configured to assign VLAN, QoS, rate-limiting, and others operational parameters for LLDP-MED enabled VoIP phones. When combined with Enterasys Policy at the edge, this is a powerful, low cost solution for deploying convergent networks.&lt;/PRE&gt;&lt;/DIV&gt; &lt;BR /&gt;
&lt;BR /&gt;
This document discusses the concept of configuring to use the new feature, including a sample configuration. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
The LLDP-MED Network-Policy TLV feature may be used to communicate some combination of VLAN, Priority, and/or DSCP value to an LLDP-MED-compliant IP Phone:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set lldp port network-policy voice state enable tag tagged vid&lt;/PRE&gt;&lt;/DIV&gt; &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;vlan&lt;/I&gt;&lt;/PRE&gt;&amp;gt; &lt;BR /&gt;
   &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;cos&lt;/PRE&gt;&lt;/DIV&gt; &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;priority&lt;/I&gt;&lt;/PRE&gt;&amp;gt; &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;dscp&lt;/PRE&gt;&lt;/DIV&gt; &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;dscp&lt;/I&gt;&lt;/PRE&gt;&amp;gt; &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;ports&lt;/I&gt;&lt;/PRE&gt;&amp;gt;&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set lldp port tx-tlv med-pol sys-name port-desc&lt;/PRE&gt;&lt;/DIV&gt;  &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;ports&lt;/I&gt;&lt;/PRE&gt;&amp;gt;&lt;BR /&gt;
&lt;BR /&gt;
Note: If just activating the above-stated tx-tlv advertisements does not have the desired effect, then consider activating &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;all&lt;/PRE&gt;&lt;/DIV&gt; advertisement ('&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set lldp port tx-tlv all&lt;/PRE&gt;&lt;/DIV&gt;  &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;ports&lt;/I&gt;&lt;/PRE&gt;&amp;gt;').&lt;BR /&gt;
&lt;BR /&gt;
Recognizing that an IP Phone typically transmits its traffic VLAN-tagged while its attached PC's traffic is transmitted untagged, the phone would accept and utilize those same values in its VLAN Tag (VLAN, Priority) and IP Header (DSCP)(&lt;A href="http://bit.ly/1rOVKny" target="_blank" rel="nofollow noreferrer noopener"&gt;5811&lt;/A&gt;). &lt;BR /&gt;
&lt;BR /&gt;
On the switch one might then configure Policy or DiffServ (&lt;A href="http://bit.ly/18F0WPL" target="_blank" rel="nofollow noreferrer noopener"&gt;5848&lt;/A&gt;) to interpret any incoming (probably DSCP) value to yield a Policy Role or DiffServ action. Since VLAN and Priority are directly assignable using Policy, it would make sense to advertise the VLAN and Priority via LLDP-MED only in the absence of Policy. However, this is totally up to the user, based on the network design. &lt;BR /&gt;
&lt;BR /&gt;
Here, LLDP-MED would replace the possible use of CiscoDP to communicate a "VVID" (Voice VLAN ID) to the phone (&lt;A href="http://bit.ly/JI2puL" target="_blank" rel="nofollow noreferrer noopener"&gt;5831&lt;/A&gt;). With CiscoDP, if the design calls for the phone to use a Priority or DSCP value, this requires phone configuration. &lt;BR /&gt;
&lt;BR /&gt;
For more background regarding the LLDP command set, please refer to the &lt;A href="http://extranet.enterasys.com/downloads/" target="_blank" rel="nofollow noreferrer noopener"&gt;Configuration Guide&lt;/A&gt; for your product and firmware line.</description>
      <pubDate>Wed, 01 Jan 2014 02:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/g-d-c-b-a-series-f-w-6-03-use-of-the-lldp-med-network-policy-tlv/m-p/42167#M94</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2014-01-01T02:57:00Z</dc:date>
    </item>
  </channel>
</rss>

