<?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 Trunking port in ExtremeSwitching (Other)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-other/trunking-port/m-p/10301#M1329</link>
    <description>How do I create a trunk port on a extreme switch (X440)?&lt;BR /&gt;
The goal is to allow a PC to connect to the native vlan via a Cisco IP Phone while all VoIP traffic connects to the voice vlan. It is my experience that the IP phone and switch port needs to be set to trunking or auto negotiate trunking in order to separate the traffic and achieve separation of data from voice.&lt;BR /&gt;
&lt;BR /&gt;
I have all of my experience in Cisco IOS, and familiar with this syntax.&lt;BR /&gt;
&lt;BR /&gt;
Assign port to vlan&lt;BR /&gt;
hostname(config)# switch port access vlan [tag name]&lt;BR /&gt;
&lt;BR /&gt;
create trunk port&lt;BR /&gt;
hostname(config)# switchport mode trunk&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Thu, 17 Apr 2014 23:35:00 GMT</pubDate>
    <dc:creator>Theo</dc:creator>
    <dc:date>2014-04-17T23:35:00Z</dc:date>
    <item>
      <title>Trunking port</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/trunking-port/m-p/10301#M1329</link>
      <description>How do I create a trunk port on a extreme switch (X440)?&lt;BR /&gt;
The goal is to allow a PC to connect to the native vlan via a Cisco IP Phone while all VoIP traffic connects to the voice vlan. It is my experience that the IP phone and switch port needs to be set to trunking or auto negotiate trunking in order to separate the traffic and achieve separation of data from voice.&lt;BR /&gt;
&lt;BR /&gt;
I have all of my experience in Cisco IOS, and familiar with this syntax.&lt;BR /&gt;
&lt;BR /&gt;
Assign port to vlan&lt;BR /&gt;
hostname(config)# switch port access vlan [tag name]&lt;BR /&gt;
&lt;BR /&gt;
create trunk port&lt;BR /&gt;
hostname(config)# switchport mode trunk&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Apr 2014 23:35:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/trunking-port/m-p/10301#M1329</guid>
      <dc:creator>Theo</dc:creator>
      <dc:date>2014-04-17T23:35:00Z</dc:date>
    </item>
    <item>
      <title>RE: Trunking port</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/trunking-port/m-p/10302#M1330</link>
      <description>Hello Theo&lt;BR /&gt;
&lt;BR /&gt;
The way we create "trunk ports" is simply by adding the ports to the VLANs as tagged ports.&lt;BR /&gt;
&lt;BR /&gt;
For example if we have two VLANs data and Voice that need to be on the same port we would do the following&lt;BR /&gt;
&lt;BR /&gt;
Create vlan data&lt;BR /&gt;
create vlan voice&lt;BR /&gt;
config voice tag 100&lt;BR /&gt;
config data add port 1&lt;BR /&gt;
config voice add port 1 tagged&lt;BR /&gt;
&lt;BR /&gt;
If we had more VLANs we would just continue to add the port as a tagged port to each VLAN.&lt;BR /&gt;
&lt;BR /&gt;
Hope that helps&lt;BR /&gt;
Thanks&lt;BR /&gt;
P&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Apr 2014 01:58:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/trunking-port/m-p/10302#M1330</guid>
      <dc:creator>Paul_Russo</dc:creator>
      <dc:date>2014-04-18T01:58:00Z</dc:date>
    </item>
    <item>
      <title>RE: Trunking port</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/trunking-port/m-p/10303#M1331</link>
      <description>Paul,&lt;BR /&gt;
&lt;BR /&gt;
How would I roll back this change if needed?&lt;BR /&gt;
&lt;BR /&gt;
switch# configure "vlan-name" [delete] ports [1:1] tagged&lt;BR /&gt;
&lt;BR /&gt;
I appreciate the feedback, and I look forward to using the LegacyCLI so that I can become more proficient with the XOS.&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
Theo</description>
      <pubDate>Wed, 23 Apr 2014 00:39:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/trunking-port/m-p/10303#M1331</guid>
      <dc:creator>Theo</dc:creator>
      <dc:date>2014-04-23T00:39:00Z</dc:date>
    </item>
    <item>
      <title>RE: Trunking port</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/trunking-port/m-p/10304#M1332</link>
      <description>Hey Theo&lt;BR /&gt;
&lt;BR /&gt;
Yes that is it.  Definitely use the legacy CLI it is not perfect but the training mode will help you understand the XOS CLI much better.&lt;BR /&gt;
&lt;BR /&gt;
Please continue to ask questions as I am sure there are others who have the same thoughts.&lt;BR /&gt;
&lt;BR /&gt;
P&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Apr 2014 01:32:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/trunking-port/m-p/10304#M1332</guid>
      <dc:creator>Paul_Russo</dc:creator>
      <dc:date>2014-04-23T01:32:00Z</dc:date>
    </item>
    <item>
      <title>RE: Trunking port</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/trunking-port/m-p/10305#M1333</link>
      <description>EXOS CLI is easy compare to any other vendor. 99% of the commands start with enable, configure, disable etc.</description>
      <pubDate>Wed, 23 Apr 2014 06:59:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/trunking-port/m-p/10305#M1333</guid>
      <dc:creator>Sumit_Tokle</dc:creator>
      <dc:date>2014-04-23T06:59:00Z</dc:date>
    </item>
  </channel>
</rss>

