3 Replies Latest reply on Oct 7, 2014 9:04 AM by levi

    Setting up native VLANs

    opl3sa New Member

      Hi All,


      I'm looking for some help related to about 6 adtran switches I purchased for a new Comcast VOIP system.

      We just recently rewired our building to ensure a 1:1 ratio of network drops to phones and computers.  That is to say we plan on daisy chaining the phones to the computers.

      I bought 3 1234p (POE) adtran switches and 3 1238p (POE) switches.


      I'm only vaguely familiar with the concept of VLANs.

      The idea I had (and it was supported by Comcast's IP telephony engineering team, although they don't actually program the switches themselves) was to set up 2 VLANs, where VLAN1 would be the native VLAN (for the computers) and VLAN5 would be for the phones.

      I've created the VLAN5, and assigned it an interface of

      VLAN1 is set as "default" (does that mean native?) and sits at assigned interface


      I envisioned a scenario where I configure the phones (Which will be polycom 335s) for VLAN5 and daisy chain them to the computers, which would then operate on the native VLAN (VLAN1)


      Am I missing something conceptually?  And if not, what are some of the commands I need to be instituting for this network?



        • Re: Setting up native VLANs
          cj! Beta_User

          Hi Ryan:


          VLAN is a Layer 2 feature that basically emulates physically separate networks over a common physical medium.  Think of two switches, each with devices connected to switchports, but the two switches are not connected to each other.  In that sense, you would have two discreet networks; hosts on switch A cannot communicate with hosts on switch B.  VLAN in its most basic implementation might be configuring a 1234 so that ports 1-12 provide access to VLAN 1, while ports 13-24 access VLAN 5.  Hosts in ports 1-12 cannot communicate with hosts in 13-24.  In other words, VLANs provide a way to segregate traffic in a way similar to separate switches.


          When you share one cable from desk to switch, the devices at each end (switchport and phone) must create an 802.1Q VLAN trunk.  This way, two or more VLANs can traverse one physical link.  The switch normally considers VLAN 1 default, which means untagged Ethernet frames.  Traffic to/from the PC will be untagged.  The phone will add a "VLAN 5" tag to its own Ethernet frames and the switch will forward that traffic in VLAN 5.


          There are various ways to achieve this design, but I normally prefer to:


          • Choose one or more switchports where the PBX and other voice 'main equipment' will connect; hard-set them to VLAN 5 (untagged, native).



          interface switchport 0/24

            description PBX

            no shutdown

            switchport access vlan 5



          • Assuming your Polycom phones support the feature, configure LLDP-MED on other switchports where phones will connect.  This will automatically configure your phones to be aware of VLAN 5 and use it for voice traffic, as well as setup an 802.1Q VLAN trunk to allow the PC to pass through untagged.  You can probably configure each phone's VLAN assignment manually, but who wants to do that?



          interface switchport 0/1

            description Voice

            spanning-tree edgeport

            no shutdown

            switchport voice vlan 5 dscp 46



          Repeat for each phone-facing switchport, or use command interface range switchport 0/1-24 and then enter the common parameters to configure a range all at once.


          • Configure uplink ports between switches (typically gigabit) for VLAN trunking (all of them).



          interface gigabit-switchport 0/1

            description Uplink

            no shutdown

            switchport mode trunk



          Some reading material:


          The difference between VLANs and VLAN interfaces


          Configuring Link-Layer Discovery Protocol (LLDP) and LLDP-Media Endpoint Discovery (LLDP-MED) in AOS


          Configuring InterVLAN Routing in AOS - Quick Configuration Guide




            • Re: Setting up native VLANs
              jwable Frequent Visitor


                  Chris did an excellent job explaining the VLANs very good explanation Chris.  I wanted to touch on a couple of other things to be aware from the voice side.  First you have to do one of two things either directly on each phone you have to manually configure the voice VLAN or you have to add to the DHCP server the specific option the phones need in order to get their VLAN ID and configuration server setting.  Second big issue is where is the routing occurring for the phones?  If it and DHCP are being handled by a device Comcast puts on site then from the switch side you do not need to do any routing so turn it off on the switch, and VLAN 5 would have no IP address, also make sure you do no ip route.  Only IP address on the switch should be the management IP address of the switch itself on whatever the management VLAN is which I will assume VLAN 1 based on the configs.  If it is a completely hosted system and you are handling DHCP for both networks and routing from the private network then there would be some additional design needed to be done but that would be on a router not at the switch level.


              John Wable

              1 of 1 people found this helpful
            • Re: Setting up native VLANs



              I went ahead and flagged the "Correct Answer" on this post to make it more visible and help other members of the community find solutions more easily. If you don't feel like the answer I marked was correct, feel free to come back to this post and unmark it, and select another in its place, with the applicable buttons.