Voice VLAN Configuration for QoS in IP Telephony

1. The Need for Voice VLANs

In modern enterprise networks, data, voice, and video traffic all share the same infrastructure. While this is efficient, it creates a problem: what happens when a large file download competes for bandwidth with a CEO's conference call? The file download can tolerate a bit of delay, but the voice call will quickly become choppy and unusable.

To solve this, we must separate and prioritize traffic. The first step is to place voice traffic into its own dedicated VLAN, known as a voice VLAN.

IP phones are often deployed in a "daisy-chain" fashion, where a user's PC connects to a port on the phone, and the phone connects to a single port on the switch. This saves on cabling and switch ports but means both voice and data traffic must traverse the same link.

As the video explained, the IP phone essentially acts as a mini-switch. This setup leads to a unique traffic flow:

• Data Traffic: Frames from the PC pass through the phone to the switch. These are standard, untagged Ethernet frames.
• Voice Traffic: Frames generated by the IP phone itself are tagged with the voice VLAN ID before being sent to the switch.

2. The "Multi-VLAN Access Port"

This architecture requires a special switch port configuration. Although it carries traffic for two different VLANs (one tagged, one untagged), the port is not a trunk port. It's configured as an access port with an additional command to specify the voice VLAN.

The configuration looks like this:

• switchport mode access
• switchport access vlan 10 (This is the data VLAN for the PC)
• switchport voice vlan 50 (This is the voice VLAN for the phone)

When configured this way, the switch port operates as follows:

• It accepts untagged frames and places them into the access VLAN (VLAN 10).
• It accepts frames tagged with the voice VLAN ID (VLAN 50) and places them into the voice VLAN.
• The switch uses Cisco Discovery Protocol (CDP) to inform the IP phone which VLAN ID it should use for tagging its voice traffic.

3. From Separation to Prioritization: Quality of Service (QoS)

Simply separating voice traffic into its own VLAN isn't enough to guarantee call quality. We also need to instruct the network hardware to give this traffic preferential treatment. This is where Quality of Service (QoS) comes in.

Voice traffic is highly sensitive to three main factors:

• Delay: The time it takes for a packet to travel from source to destination. High delay makes a conversation unnatural. (Recommended: < 150 ms one-way)
• Jitter: The variation in delay between packets. High jitter results in choppy, distorted audio. (Recommended: < 30 ms)
• Loss: The percentage of packets that are dropped and never arrive. Even small amounts of packet loss can degrade call quality. (Recommended: < 1%)

To meet these strict requirements, we need a way to mark voice packets as "important" and configure our switches to act on those markings.

4. Marking and Trusting Voice Traffic

Cisco IP phones automatically mark the traffic they generate to signal its priority. They use two primary methods:

1. Layer 2 Marking (CoS): The phone sets the 3-bit Priority Code Point (PCP) field in the 802.1Q tag to a specific value. This is known as the Class of Service (CoS).
2. Layer 3 Marking (DSCP): The phone sets the 6-bit Differentiated Services Code Point (DSCP) field in the IP header.

The switch, however, won't act on these markings unless it's configured to trust them. This creates a "trust boundary." We trust the markings from a corporate IP phone, but we might not trust markings from a user's PC, as they could be maliciously altered to give their data traffic unfair priority.

5. Configuration and Verification

Now, let's put all the pieces together. To properly configure a switch port for a Cisco IP phone and ensure QoS, we need to perform these steps.

Here is a summary of a complete manual configuration:

1. Enable QoS Globally: This is a prerequisite on many Catalyst switch platforms.

   Switch(config)# mls qos
   

2. Configure the Interface:

   Switch(config)# interface GigabitEthernet1/0/1
   Switch(config-if)# switchport mode access
   Switch(config-if)# switchport access vlan 100      ! Data VLAN
   Switch(config-if)# switchport voice vlan 110      ! Voice VLAN
   Switch(config-if)# mls qos trust cos              ! Trust the Layer 2 CoS marking
   Switch(config-if)# spanning-tree portfast         ! Recommended, though often enabled automatically
   

   Note: On newer platforms, you might see trust device cisco-phone. This command provides conditional trust, instructing the port to only trust markings if CDP detects that the connected device is a Cisco IP phone.

3. Verification:
   The primary command to verify your configuration is show interfaces <interface-id> switchport.

   Switch# show interfaces gigabitethernet1/0/1 switchport
   Name: Gi1/0/1
   Switchport: Enabled
   Administrative Mode: static access
   Operational Mode: static access
   Administrative Trunking Encapsulation: dot1q
   Operational Trunking Encapsulation: native
   Negotiation of Trunking: Off
   Access Mode VLAN: 100 (Data)
   Trunking Native Mode VLAN: 1 (default)
   Voice VLAN: 110 (Voice)
   [...]
   

   Notice that the operational mode is static access, and both the Access VLAN and Voice VLAN are listed.

Switch(config)# mls qos

Switch(config)# interface FastEthernet0/24
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 20
Switch(config-if)# switchport voice vlan 30
Switch(config-if)# mls qos trust cos
Switch(config-if)# end

6. AutoQoS: The Simplified Approach

Configuring QoS can become very complex. To simplify deployment for common scenarios like VoIP, Cisco created AutoQoS. This is a set of macros that automatically generates and applies a best-practice QoS configuration based on the type of device connected to the port.

While AutoQoS is a powerful tool for rapid deployment, it's essential for a CCNP candidate to understand the manual steps it automates. This knowledge is crucial for customization and advanced troubleshooting when the automatic configuration isn't sufficient.

Conclusion

In this lesson, we bridged the gap between basic VLAN switching and Quality of Service. We saw how the special voice VLAN configuration allows a single access port to securely handle both untagged data and tagged voice traffic, enabling the prioritization that real-time applications demand.

Key Takeaways:

• Voice VLANs are used to segregate IP telephony traffic from data traffic for security and QoS management.
• A switch port connected to an IP phone and a PC operates in access mode but is configured with both a data VLAN (switchport access vlan) and a voice VLAN (switchport voice vlan).
• The switch receives untagged data frames for the access VLAN and tagged voice frames for the voice VLAN.
• To enable prioritization, the switch must be configured to trust the Layer 2 CoS markings sent by the IP phone using the mls qos trust cos command.
• AutoQoS provides a simplified macro (auto qos voip) to apply a robust, best-practice QoS configuration to a port.

Preview of the Next Lesson:

We will continue our exploration of advanced VLAN technologies by looking at another method of Layer 2 segmentation. In the next lesson, we will learn how to configure and verify private VLANs to provide Layer 2 isolation between hosts within the same subnet, a powerful tool for security in multi-tenant environments.