Data and Voice VLAN 2

By certskills June 10, 2016 09:05

Ready to prepare some access switches to support IP phones? This latest config labs sets up the problem for that specific task. And yes, voice VLANs are another one of the topics now explicitly listed in the new ICND1 100-105 and CCNA R&S 200-125 exam topics.


There is an ongoing VoIP deployment happening. Each access port current connects to a PC on a user’s desk. All those PCs are currently in VLAN 20. The migration will instead connect a new IP phone to the cable, and then connect that same PC to a port on the bottom of the phone. That change will happen for all the access ports shown in the figure.

Your job is to look at the existing configuration on the access ports, and then add the required configuration to support the migration to having both a phone and a PC at the end of each access link. The specific rules for this lab are:

  • All phones will be in the same VLAN: new Voice VLAN 30
  • Do not change the current data VLAN used by each PC
  • Make use of the interface range command to reduce typing
  • Assumptions:
    • All device interfaces shown in the lab are up and working
    • The path from the existing PCs to the existing router (as default gateway) is working, but the router is not shown in the figure
    • Trunking is configured and operational between the switches
    • All switches use VTP transparent mode
    • VLANs 10, 20, and 30 already exist and are enabled on all four switches



Figure 1: Original Topology without IP Phones

Figure 2: New Topology with IP Phones


Initial Configuration

Examples 1, 2, 3 and 4 show the beginning configuration state of Dist1, Dist2, Access1 and Access2.

Example 1: Dist1 Config


Example 2: Dist2 Config


Example 3: Access1 Config


Example 4: Access2 Config


Answer on Paper, or Maybe Test in Lab

Next, write your answer on paper. Or if you have some real gear, or other tools, configure the lab with those tools.

To test your solution if you happen to try it with VIRL or real gear, the easiest way to verify the configuration is to use the show interfaces interface switchport command on the access switches using the interfaces connected to the PC and IP Phone; this will list the configured data and voice VLAN.


Do this Lab with Cisco’s VIRL

You can do these labs on paper and still get a lot out of the lab. As an extra help, we have added files for the Virtual Internet Routing Lab (VIRL) software as well. The .VIRL file found here is a file that when used with VIRL will load a lab topology similar to this lab’s topology, with the initial configuration shown in the lab as well. This section lists any differences between the lab exercise and the .VIRL file’s topology and configuration.

Download this lab’s VIRL file!

All interfaces in topology match the lab figure.

Network Device Info:

The switches used in the lab are Cisco IOS layer 2 switches. Note that if you happen to have a layer 3 switch, to use the initial configurations as shown in this lab, issue the no ip routing command on the switch. This command will disable the routing of IPv4 packets, making the layer 3 switch act only as a layer 2 switch.

Also, when using VIRL, the IOS layer 2 switch image supports both the older ISL and the preferred 802.1Q VLAN trunking protocols. As a result, to make VLAN trunks work, add the switchport trunk encapsulation dot1q command on each interface that should trunk, in addition to the initial configuration shown in this lab.

(The .VIRL file that you can download already has these commands added to the switch configurations.)

Host device info:

This lab includes four server hosts in the positions of PC1, PC2, PC11, and PC12 in the figure for this lab. It does not include any simulated IP phones. The PCs use the IP addresses listed in this table, pre-configured in VIRL. The information is not required in lab but may be useful to you.


Device IP Address User/password
PC1 cisco/cisco
PC2 cisco/cisco
PC11 cisco/cisco
PC12 cisco/cisco



Handy Host Commands:

To see PC IP address: ifconfig eth1

Ping example: ping -c 4

Trace example: tracepath

To connect to another node within the topology: telnet

Answers: RIPv2 Options 1
Answers: Data and Voice VLAN 2
By certskills June 10, 2016 09:05
Write a comment


  1. RN May 19, 19:16

    Hi Wendell,

    Notice the typo in the configuration of Access2.

    (“hostname Access1” instead “hostname Access2”

    Reply to this comment
View comments

Write a comment

Comment; Identify w/ Social Media or Email


Subscribe to our mailing list and get interesting stuff and updates to your email inbox.

Thank you for subscribing.

Something went wrong.