FTOS Configuration Guide for the C-Series - Force10 Networks

Honoring the incoming dot1p value
On the C-Series, if you know traffic originating from the phone is tagged with a dot1p value of 5, you
might make the associated queue a strict priority queue, as shown in Figure 460; on the C-Series, FTOS
maps dot1p priority 5 to queue 2.
Figure 460 Honoring the Dot1P Value on Incoming Voice Traffic
Force10#sh run int gi 6/10
!
interface GigabitEthernet 6/10
description "IP Phone X"
no ip address
portmode hybrid
switchport
service-class dynamic dot1p
power inline auto
no shutdown
Force10#sh run | grep strict-priority
strict-priority unicast 2
Classifying VOIP traffic and applying QoS policies
Avoid congestion and give precedence to voice and signaling traffic by classifying traffic based on subnet
and using strict priority and bandwidth weights on egress, as outlined in the steps below.
Figure 461 depicts the topology and shows the configuration for a C-Series. The steps are the same on an
S-Series. Figure 462 on page 653 is a screenshot showing some of the steps and the resulting
running-config.
Figure 461 Classifying VOIP Traffic and Applying QoS Policies for an Office VOIP Deployment
PC
PC data
IP Phone X
Force10#sh run int gi 6/10
!
interface GigabitEthernet 6/10
description "IP Phone X”
no ip address
portmode hybrid
switchport
service-policy input phone-pc
power inline auto
no shutdown
VLAN 300: Voice Signaling
VLAN 200: Voice
VLAN 100: Data
6/10
LLDP-MED advertisements
Force10#sh run lldp
protocol lldp
advertise med
advertise med voice 200 6 46
advertise med voice-signaling 300 5 28
no disable
C-Series
Force10#sh run int gi 6/2
!
interface GigabitEthernet 6/2
description "Uplink to E1200"
no ip address
switchport
service-policy output BW
no shutdown
FTOS Configuration Guide, version 7.7.1.0 651
6/2
queue 2, bandwidth weight 64
queue 3, strict priority
queue 1, bandwidth weight 8
E-Series