Table of Contents

Configuring QoS for IP Telephony

QPM includes a predefined database for IP telephony QoS. These topics describe how to configure QoS for IP telephony in an AVVID (Architecture for voice, video, and integrated data) network using the QPM templates:

• Understanding QoS for IP Telephony
  
  
• Working with the QPM IP Telephony Templates
  
  
• QPM IP Telephony Template Reference
  
  

Understanding QoS for IP Telephony

In order to support an AVVID network, you need to maintain end-to-end Quality of Service for IP telephony traffic.

Voice quality is directly affected by packet loss, packet delay and delay variation. Packet loss causes voice clippings and skips. Packet delay can cause either voice quality degradation due to the end-to-end voice latency, or packet loss if the delay is variable. Because network congestion can occur at any time in any portion of the network—campus, branch office, or WAN—you must ensure end-to-end network quality for voice traffic.

End-to-end QoS configuration improves voice quality on AVVID networks by decreasing dropped voice packets during times of network congestion and by minimizing both the fixed and variable delays encountered in a given voice connection.

Figure 9-1 shows a typical IP telephony network model.

Table 9-1 lists the network points that require QoS configuration for IP telephony.

QPM supports the QoS methods required to configure IP telephony QoS for:

• High-speed campus domains
  
  
• Branch offices
  
  
• WAN implementations
  
  

To simplify the tasks of configuring QoS for IP telephony throughout the enterprise, QPM includes templates that contain predefined policies for each point in the IP telephony network.

Note   The IP telephony templates are based on the QoS configurations in the Cisco IP Telephony QoS Design Guide. For more information about these QoS configurations, and about designing a Cisco AVVID network, see the Cisco IP Telephony QoS Design Guide at http://www.cisco.com/univercd/cc/td/doc/product/voice/ip_tele/index.htm.

Related Topics

• Management of Voice and Other Real-Time Traffic
  
  
• Working with the QPM IP Telephony Templates
  
  

Working with the QPM IP Telephony Templates

The following topics describe the IP Telephony templates and how to use them:

• Understanding the QPM IP Telephony Templates
  
  
• Using the QPM IP Telephony Templates
  
  

Understanding the QPM IP Telephony Templates

QPM IP Telephony templates allow you to easily implement the end-to-end Quality of Service (QoS) that is required for successful deployment of IP telephony in an enterprise environment. QPM includes a special database that contains a template for each network point that needs QoS configuration for IP telephony, as shown in Figure 9-1.

Each template is a predefined device group with a set of QoS properties and policies for all points in the network that need QoS for IP telephony. To implement QoS for IP Telephony, you only need to add devices to the database, then add the appropriate interfaces to the device groups, and deploy the database.

Table 9-2 provides a summary of the templates included in the IP telephony database.

Note   For details of the policies and properties in each device group, see QPM IP Telephony Template Reference.

Using the QPM IP Telephony Templates

This section describes how to configure QoS for IP telephony using the QPM templates:

• Create a New IP Telephony Database
  
  
• Add Devices and Interfaces to IP Telephony Database
  
  
• Add Interfaces to Device Groups
  
  
• Deploy the Database from the Distribution Manager
  
  

Create a New IP Telephony Database

You create a new IP telephony database from the predefined IP Telephony Template database that is included with QPM. After you open the QPM IP Telephony database, you must save it with a new name because it is read-only.

Procedure

Step 1  
In the Policy Manager window, click the New IP Telephony Database button.

The IP_TELEPHONY_TEMPLATE database is displayed in the Tree View of the Policy Manager window.

Step 2   Choose File>Save As. The Save Database dialog box opens.

Step 3   Enter a name in the Database Name field. Enter a description in the Database Description field. Click OK.

Add Devices and Interfaces to IP Telephony Database

You must add or import all the devices and interfaces that require QoS configuration for IP telephony.

Note   Do not use the Upload function when adding devices to the IP telephony QoS database. This database changes specific QoS properties on certain devices, and these will be overwritten if you upload the current device configuration.

For information about adding and importing devices, see the following topics:

• Adding a Device
  
  
• Importing Devices from a Device Inventory
  
  

Add Interfaces to Device Groups

After you have added the devices and interfaces to the IP telephony database, you add interfaces to the appropriate predefined device groups. See Table 9-2 for a summary of the device groups in the IP telephony database. For details of the policies and properties in each device group, see QPM IP Telephony Template Reference.

For details about how to add interfaces to a device group, see the Procedure.

Campus Configuration

• Add all IP phone ports on Catalyst 3500XL and Catalyst 2900XL switches to the Acc3500=>IP-Phones device group.
  
  
• Add all IP phone ports on Catalyst 6000 switches with PFC cards to the Acc6000=>IP-Phones device group.
  
  
• Add the voice VLAN for IP phones to the AccDist6K-VoiceVLAN device group.
  
  
• Add all ports connected to Cisco SoftPhones to the Acc6000=>SoftPhones device group.
  
  
• Add all ports connected to Cisco CallManagers, H.323 gateways, and MGPC gateways to the Acc6000=>VoIPControl device group.
  
  
• Add the uplink ports on Catalyst 6000 access switches that are connected to distribution or core switches, to the Acc6000_GE=>Dist device group.
  
  
• Add the downlink ports on Catalyst 6000 distribution and core switches that are connected to Catalyst 6000 access switches (with PFC) to the Dist=>Acc6K-PFC device group.
  
  
• Add the downlink ports on Catalyst 6000 distribution and core switches, with Supervisor IOS, that are connected to Catalyst 6000 access switches (with PFC) to the Dist(IOS)=>6K-PFC device group.
  
  
• Add the downlink ports on Catalyst 6000 distribution and core switches that are connected to layer 2 QoS-aware access switches to the Dist=>AccNon6KPFC device group.
  
  
• Add the downlink ports on Catalyst 6000 distribution and core switches, with Supervisor IOS, that are connected to layer 2 QoS-aware access switches to the Dist(IOS)=>Non6KPFC device group.
  
  
• Add the voice VLAN on Catalyst 6000 distribution switches with Supervisor IOS to the Dist(IOS)-VoiceVLAN device group.
  
  
• Add the ethernet ports on Catalyst 6000 distribution and core switches that are connected to the WAN router to the Dist=>RouterWAN device group.
  
  
• Add the gigabit ethernet ports on Catalyst 6000 distribution and core switches that are connected to the WAN router to the Dist_GE=>RouterWAN device group.
  
  
• Add the ports on Catalyst 6000 distribution and core switches, with Supervisor IOS, that are connected to the WAN router to the Dist(IOS)=>RouterWAN device group.
  
  

Remote Site Configuration

• Add the IP phone ports on Catalyst 3500XL and Catalyst 2900XL switches to the Acc3500=>IP-Phones device group.
  
  
• Add the router interface that is connected to the access switch to the RouterWAN=>Non6KPFC device group.
  
  

WAN Configuration

• Add low-speed Multilink PPP (MLP) WAN interfaces to the WAN-MLP-Slow(<768K) device group.
  
  
• Add high-speed Multilink PPP (MLP) WAN interfaces to the WAN-MLP-High(>768K) device group, or add the high-speed serial interfaces to the WAN-PPP-High(>768K) device group.
  
  
• Add the main Frame Relay interface to the WAN-FR-Interface device group.
  
  
• Add Frame Relay DLCI subinterfaces to the following device groups according to the interface speed:
  
  
• • WAN-FR-64K-DLCI
    
    
  • WAN-FR-128K-DLCI
    
    
  • WAN-FR-256K-DLCI
    
    
  • WAN-FR-512K-DLCI
    
    
  • WAN-FR-768K-DLCI
    
    
  • WAN-FR-1.5M-DLCI
    
    
• Add ATM WAN interfaces to the WAN-ATM-VirtualTempl device group.
  
  

Procedure

Step 1   Select the device group to which you want to add interfaces.

Step 2   Choose Devices>Device Group>Add/Remove Members. The Add/Remove Members dialog box opens.

Step 3   Select the interfaces you want to add from the Available Interfaces list, and click >>. The selected interfaces are added to the Group Members list.

Step 4   Click OK.

Deploy the Database from the Distribution Manager

After you have added all the required interfaces to the relevant device groups, you can deploy the IP telephony database from the Distribution Manager.

Note   You can preview the CLI commands that will be downloaded to the devices, using the Devices>View Commands option in the Distribution Manager. See Viewing the Configuration Commands for a Device for details.

Procedure

Step 1   To open the Distribution Manager from the Policy Manager, choose Tools>Distribution Manager.

Step 2   Distribute the policies. See "Distributing Policies to Network Devices" for more information.

QPM IP Telephony Template Reference

The QPM IP telephony templates are based on the Cisco IP Telephony QoS Design Guide. This template reference describes the QoS properties and policies in each of the templates.

In general, the CLI commands generated by the templates on deployment are compliant with those defined in the QoS Design Guide. You can preview the CLI commands that will be generated on deployment, using the Devices>View Commands menu option in the Distribution Manager. See Viewing the Configuration Commands for a Device for details.

Note   The QPM IP telephony templates configure only QoS. Other commands, such as power settings and voice VLANs, are not supported by QPM, and should be configured first through CLI or other applications.

The template reference is organized according to the network points that require QoS configuration for IP telephony:

• IP Phone Ports
  
  
• SoftPhone Ports
  
  
• CallManager and Voice Gateway Ready Ports
  
  
• Uplink Ports (from Access to Distribution or Core)
  
  
• Downlink Ports (from Distribution or Core to Access Layer Catalyst 6000)
  
  
• Downlink Ports (from Distribution or Core to Access Layer Catalyst 3500 or Catalyst 4000)
  
  
• Interface from Distribution or Core Switch to WAN Router
  
  
• Per Device Scheduling
  
  
• Point-to-Point WAN Interfaces
  
  
• Frame Relay WAN Interfaces
  
  
• ATM WAN Links
  
  
• Interface from Branch Office Router to Layer 2 Switch
  
  

IP Phone Ports

When connected by a single cable, the IP phone is the edge of the managed network. An integral part of the Cisco network design architecture has always been the classification, or coloring, of traffic as close to the edge of the network as possible. As such, the IP phone can and should classify traffic flows.

By default, Cisco IP phones mark all VoIP traffic with CoS=5 and DSCP=46. However, it is critical to make sure that the PC connected to the access port of the IP phone is not also classifying traffic. The recommended method for ensuring this is to extend the trust boundary of the Ethernet switch to the IP phone and not beyond, meaning the IP phone will re-classify all traffic coming from the PC with CoS=0. The switch port is set to trust the CoS value and copy it to the DSCP field according to the CoS to DSCP mapping table. To overcome a configuration limitation on the line card ASIC, the switch port is also configured to trust the IP phones. VLAN-based QoS configuration is used to trust all CoS classification on the IP phone ports in the voice VLAN. The VLAN-based configuration is deployed to all ports in the VLAN that have been added to QPM.

Acc6000=>IP-Phones

This template is for IP phone ports on Catalyst 6000 switches with CatOS 5.5 and higher.

The following device group properties are configured for this template:

• Model: Catalyst 6000
  
  
• Mapped Software Version: 5.5
  
  
• Group Contains Interfaces, Type: ethernet, Card Type: Non-VIP
  
  
• QoS Property: 2Q2T/1P2Q2T
  
  
• Trust State: Trust CoS, Trust-ext: Untrusted, QoS Style: VLAN Based
  
  

The following QoS policies are configured for this template:

• Trust-ext untrusted
  
  
• Trust CoS
  
  

AccDist6K-VoiceVLAN

This template is for the voice VLAN on Catalyst 6000 switches with CatOS 5.5 and higher. This template is required to configure specific policies because the QoS style on the IP phone ports is set to VLAN based, which means that only the VLAN-based policies (not the individual port's policies) will be deployed to the ports on the VLAN.

The following device group properties are configured for this template:

• Model: Catalyst 6000
  
  
• Mapped Software Version: 5.5
  
  
• Group contains interfaces, Type: propVirtual, Card Type: Non-VIP
  
  
• QoS Property: 2Q2T/1P2Q2T
  
  

The following QoS policies are configured for this template:

• Trust CoS for all IP traffic.
  
  
• Color Skinny traffic
  
  

Acc3500=>IP-Phones

This template is for IP phone ports on Catalyst 3500XL and 2900XL switches with IOS 12.0E and higher.

The following device group properties are configured for this template:

• Model: Cat3500_Family
  
  
• Mapped Software Version: 12.0
  
  
• Group contains interfaces, Type: ethernet, Card Type: Non-VIP
  
  
• QoS Property: Do not Change
  
  

The following QoS policies are configured for this template:

• Trust-ext Untrusted
  
  

SoftPhone Ports

The Cisco SoftPhone application marks voice traffic only at the Layer 3 IP header. This means that the access switch to which it is connected must be Layer 3 aware in order to prioritize voice traffic before the first uplink to the distribution layer. This limits the choice of wiring closet switches with multiple queues to the Catalyst 6000 with a PFC installed.

Acc6000=>SoftPhones

This template is for SoftPhone ports on Catalyst 6000 switches with CatOS 5.5 and higher, and with a PFC installed.

The following device group properties are configured for this template:

• Model: Cat6000
  
  
• Mapped Software Version: 5.5
  
  
• Group contains interfaces, Type: ethernet, Card Type: Non-VIP
  
  
• QoS Property: 2Q2T/1P2Q2T
  
  
• Trust State: Untrusted, Trust-ext: None, QoS Style: Port Based
  
  

The following QoS policies are configured for this template:

• Color voice traffic DSCP=46
  
  
• Color SoftPhone control traffic DSCP=26
  
  

CallManager and Voice Gateway Ready Ports

In networks with high traffic loads, timely transmission of control traffic is critical to ensure a positive user experience with VoIP, for example, maintaining Delay to Dial-Tone (DTT) time at acceptable levels. When a Cisco IP Phone goes off hook, it uses Skinny Station Protocol to communicate with Cisco CallManager. Cisco CallManager then instructs the Cisco IP Phone to play dial-tone. If this Skinny Client Protocol management and control traffic is dropped or delayed within the network, the user experience is adversely affected. This same logic applies to all signaling traffic for gateways and phones.

To ensure that this control and management traffic is marked as important (but not as important as the actual RTP stream), Access Control Lists (ACLs) are used to classify these streams on Catalyst 6000 switches that are enabled for Layer 3 and Layer 4.

Acc6000=>VoIPControl

This template is for CallManager and Voice Gateway ready ports on Catalyst 6000 switches with CatOS 5.5 and higher.

The following device group properties are configured for this template:

• Model: Cat6000
  
  
• Mapped Software Version: 5.5
  
  
• Group contains interfaces, Type: ethernet, Card Type: Non-VIP
  
  
• QoS Property: 2Q2T/1P2Q2T
  
  
• Trust State: Untrusted, Trust-ext: None, QoS Style: Port Based
  
  

The following QoS policies are configured for this template:

• Color all control traffic port ranges:
  
  
• • Skinny—TCP destination ports 2000-2002
    
    
  • H.323 (H.225)—TCP destination port 1720
    
    
  • H.323 (H.245)—TCP destination ports 11xxx
    
    
  • MGCP—UDP destination port 2427
    
    
  • CTI—TCP destination port 2748
    
    

  ---

  Note   To mark packets destined to CallManager and packets originating from CallManager, the policy also filters all the above ports as source ports.

  ---

Uplink Ports (from Access to Distribution or Core)

After QoS configuration of the access interfaces, QoS must be configured throughout the LAN.

These templates are for uplink ports on a Catalyst 6000 access switch to the distribution or core switch.

Acc6000_GE=>Dist

This template is for access ports on a Catalyst 6000 with CatOS 5.5 and higher, and with a PFC installed.

The following device group properties are configured for this template:

• Model: Cat6000
  
  
• Mapped Software Version: 5.5
  
  
• Group contains interfaces, Type: gigabitEthernet, Card Type: Non-VIP
  
  
• QoS Property: 2Q2T/1P2Q2T
  
  
• Trust State: Trust CoS, Trust-ext: None, QoS Style: Port Based
  
  

The following QoS policies are configured for this template:

• Trust CoS from distribution layer
  
  

Downlink Ports (from Distribution or Core to Access Layer Catalyst 6000)

These templates are for downlink ports on a Catalyst 6000 distribution or core switch to the access layer Catalyst 6000 switch with a PFC installed.

Because classification is set on the access switch, a switch can trust traffic from a neighboring switch. The level of trust depends on the neighboring switch's capabilities. For switches with layer 3 capabilities, trust layer 3 is sufficient.

Dist=>Acc6K-PFC

This template is for distribution or core switch ports on a Catalyst 6000 with CatOS 5.5 and higher, and with a PFC installed.

The following device group properties are configured for this template:

• Model: Catalyst 6000
  
  
• Mapped Software Version: 5.5
  
  
• Group contains interfaces, Type: gigabitEthernet, Card Type: Non-VIP
  
  
• QoS Property: 2Q2T/1P2Q2T
  
  
• Trust State: Trust CoS, Trust-ext: None, QoS Style: Port Based
  
  

The following QoS policies are configured for this template:

• Trust CoS from access layer
  
  

Dist(IOS)=>6K-PFC

This template is for distribution or core switch ports on a Catalyst 6000 with Supervisor IOS 12.1(6)E.

The following device group properties are configured for this template:

• Model: Catalyst 6000 with Supervisor IOS
  
  
• Mapped Software Version: 12.1(6)E
  
  
• Group contains interfaces, Type: Any, Card Type: Non-VIP
  
  
• QoS Property: 1P2Q2T
  
  

---

Note   There is currently no corresponding template for 2Q2T interfaces.

---

The following QoS policies are configured for this template:

• Trust CoS from access layer
  
  
• Set queuing—Place all CoS=3 (VoIP control) traffic into the second transmit queue, with a low drop threshold. Place all CoS=5 (VoIP RTP Bearer) traffic into priority queue in 1p2q2t.
  
  

Downlink Ports (from Distribution or Core to Access Layer Catalyst 3500 or Catalyst 4000)

These templates are for downlink ports on a Catalyst 6000 distribution or core switch to Layer 2 QoS-aware access switches, such as Catalyst 3500 or Catalyst 4000.

Because classification is set on the access switch, a switch can trust traffic from a neighboring switch. The level of trust depends on the neighboring switch's capabilities. For switches with layer 2 capabilities, trust of layer 2 is required with the addition of layer 3 and 4 classification statements.

Dist=>AccNon6KPFC

This template is for distribution or core switch ports on a Catalyst 6000 with CatOS 5.5 and higher, and with a PFC installed.

The following device group properties are configured for this template:

• Model: Catalyst 6000
  
  
• Mapped Software Version: 5.5
  
  
• Group contains interfaces, Type: gigabitEthernet, Card Type: Non-VIP
  
  
• QoS Property: 2Q2T/1P2Q2T
  
  
• Trust State: Trust CoS, Trust-ext: None, QoS Style: VLAN Based
  
  

The following QoS policies are configured for this template:

• Trust CoS for all IP traffic
  
  

---

Note   Because the QoS style in this template is VLAN based, you should also use the AccDist6K-VoiceVLAN template described in AccDist6K-VoiceV LAN.

---

Dist(IOS)=>Non6KPFC

This template is for distribution or core switch ports on a Catalyst 6000 with Supervisor IOS 12.1(6)E.

The following device group properties are configured for this template:

• Model: Catalyst 6000 with Supervisor IOS
  
  
• Mapped Software Version: 12.1(6)E
  
  
• Group contains interfaces, Type: Any, Card Type: Non-VIP
  
  
• QoS Property: 1P2Q2T
  
  
• QoS style: VLAN based
  
  

---

Note   There is currently no corresponding template for 2Q2T interfaces.

---

The following QoS policies are configured for this template:

• Trust CoS
  
  
• Set queuing—Place all CoS=3 (VoIP control) traffic into the second transmit queue, with a low drop threshold. Place all CoS=5 (VoIP RTP Bearer) traffic into priority queue in 1p2q2t.
  
  

Dist(IOS)-VoiceVLAN

This template is for the voice VLAN on Catalyst switches with Supervisor IOS 12.1(6)E. This template is required to configure specific policies because the QoS style on the ports is set to VLAN based.

The following device group properties are configured for this template:

• Model: Catalyst 6000 with Supervisor IOS
  
  
• Mapped Software Version: 12.1(6)E
  
  
• Group contains interfaces, Type: propVirtual, Card Type: Non-VIP
  
  
• QoS Property: 2Q2T/1P2Q2T
  
  

The following QoS policies are configured for this template:

• Color Skinny traffic DSCP=26
  
  
• Trust CoS for all IP traffic
  
  

Interface from Distribution or Core Switch to WAN Router

These templates are for the interfaces from the distribution and core switches to the WAN router.

Dist=>RouterWAN

This template is for the ethernet interfaces to the WAN router from a Catalyst 6000 with CatOS 5.5 or higher.

The following device group properties are configured for this template:

• Model: Cat6000
  
  
• Mapped Software Version: 5.5
  
  
• Group contains interfaces, Type: Ethernet, Card Type: Non-VIP
  
  
• QoS Property: 2Q2T/1P2Q2T
  
  
• Trust State: Untrusted, Trust-ext: None, QoS Style: Port Based
  
  

The following QoS policies are configured for this template:

• Trust DSCP for any IP traffic
  
  

Dist_GE=>RouterWAN

This template is for the gigabit ethernet interfaces to the WAN router from a Catalyst 6000 with CatOS 5.5 or higher.

The following device group properties are configured for this template:

• Model: Cat6000
  
  
• Mapped Software Version: 5.5
  
  
• Group contains interfaces, Type: gigabit ethernet, Card Type: Non-VIP
  
  
• QoS Property: 2Q2T/1P2Q2T
  
  
• Trust State: Trust DSCP, Trust-ext: None, QoS Style: Port Based
  
  

The following QoS policies are configured for this template:

• Trust DSCP
  
  

Dist(IOS)=>RouterWAN

The following device group properties are configured for this template:

• Model: Catalyst 6000 with Supervisor IOS
  
  
• Mapped Software Version: 12.1(6)E
  
  
• Group contains interfaces, Type: Any, Card Type: Non-VIP
  
  
• QoS Property: 1P2Q2T, QoS style: Port based
  
  

---

Note   There is currently no corresponding template for 2Q2T interfaces.

---

The following QoS policies are configured for this template:

• Trust DSCP
  
  
• Set queuing—Place all CoS=3 (VoIP control) traffic into the second transmit queue, with a low drop threshold. Place all CoS=5 (VoIP RTP Bearer) traffic into priority queue in 1p2q2t.
  
  

Per Device Scheduling

Certain QoS properties required for IP telephony QoS are configured on a device basis, and therefore cannot be included in the QoS templates. These QoS properties, which include the scheduling QoS properties and the CoS to DSCP mapping for Catalyst switches, are set automatically by QPM when the device is added to the IP Telephony QoS database.

Catalyst 6000

The following QoS properties are set for the Catalyst 6000:

• Place all CoS=3 (VoIP control) traffic into the second transmit queue, with a low drop threshold.
  
  
• All CoS=5 (VoIP RTP Bearer) traffic is automatically placed into priority queue in 1p2q2t and on the second queue in 2q2t (this is the default).
  
  
• Mapping the CoS and IPP values to appropriate DSCP values (IPP=3 to DSCP=26, IPP=5 to DSCP=46).
  
  

Catalyst 6000 with Supervisor IOS

The following QoS properties are set for the Catalyst 6000 with Supervisor IOS.

• Mapping the CoS and IPP values to appropriate DSCP values (CoS=3 or IPP=3 to DSCP=26, CoS=5 or IPP=5 to DSCP=46).
  
  

---

Note   On the Catalyst 6000 with Supervisor IOS the scheduling is configured per interface and not per device.

---

Point-to-Point WAN Interfaces

Link speed in the WAN is much slower than in the LAN, therefore QoS configuration for WAN links is most important to prevent delay.

The templates for Point-to-Point (PPP) and Multilink PPP (MLP) WAN interfaces use the following QoS techniques:

• Link Fragmentation and Interleaving (LFI)— LFI ensures that voice packets are not blocked behind large data packets (such as file transfers) by fragmenting these large packets and interleaving voice packets between the fragments.
  
  
• Low Latency Queuing (LLQ)—LLQ allows delay-sensitive data such as voice to be de-queued and sent first (before packets in other queues are de-queued), giving delay-sensitive data preferential treatment over other traffic. The relatively small size of voice packets makes it possible to use a strict priority queue for voice without degrading network quality for the remaining traffic. It is also using CBWFQ to ensure bandwidth for VoIP control traffic. The traffic classification will be according to DSCP value.
  
  
• Compressed Real Time Protocol (CRTP)—CRTP reduces unnecessary bandwidth consumption by compressing header size from 40 bytes to 5 bytes. The benefits of using CRTP for voice are apparent when considering that the payload for a VoIP packet is only 20 bytes.
  
  

WAN-MLP-Slow(<=768k)

This template is for low-speed Multilink PPP (MLP) WAN links (<= 768kbs) running IOS 12.1(3)T and later.

The following QoS properties are set:

• Model: IOS_Family
  
  
• Mapped Software Version: 12.1
  
  
• Group contains interfaces, Type: ppp, Card Type: Non-VIP
  
  
• QoS Property: Class Based QoS
  
  
• CRTP Enabled
  
  
• LFI Enabled: Fragment Delay=10
  
  

The following QoS policies are configured for this template:

• Set queuing for voice traffic—Bandwidth=40%, LLQ enabled
  
  
• Set queuing for control traffic—Drop mechanism is TAIL, Bandwidth=10%
  
  
• Set queuing for class-default—Drop mechanism is TAIL, queuing is WFQ
  
  

WAN-MLP-High(>768k)

This template is for high-speed Multilink PPP (MLP) WAN links (> 768kbs) running IOS 12.1(3)T and later. It uses the same QoS techniques as in the low-speed point-to-point template, but without LFI.

The following QoS properties are set:

• Model: IOS_Family
  
  
• Mapped Software Version: 12.1
  
  
• Group contains interfaces, Type: ppp, Card Type: Non-VIP
  
  
• QoS Property: Class Based QoS
  
  
• CRTP Enabled
  
  

The following QoS policies are configured for this template:

• Set queuing for voice traffic—Bandwidth=40%, LLQ enabled
  
  
• Set queuing for control traffic—Drop mechanism is TAIL, Bandwidth=10%
  
  
• Set queuing for class-default—Drop mechanism is TAIL, queuing is WFQ
  
  

WAN-PPP-High(>768k)

This template is for high-speed PPP WAN links without Multilink (> 768kbs) running IOS 12.1(3)T and later. It uses the same configuration as for the WAN-MLP-High(>768k) template except for the interface type, which is defined as propPointToPointSerial.

Frame Relay WAN Interfaces

The templates for Frame Relay WAN interfaces use the following QoS techniques:

• Frame Relay Traffic Shaping (FRTS)—FRTS minimizes packet loss by throttling back packets as they are forwarded into the Frame Relay cloud, based on congestion indicators. The values for FRTS are configured as Rate=(CIR-Flags&CRC overhead), BC=1000, BE=0, MINCIR=Rate.
  
  
• Frame Relay Fragmentation (FRF)—FRF ensures that voice packets are not blocked behind large data packets (such as file transfers) by fragmenting these large packets and interleaving voice packets between the fragments.
  
  
• Low Latency Queuing (LLQ). For more information, see Point-to-Point WAN Interfaces.
  
  
• Compressed Real Time Protocol (CRTP). For more information, see Point-to-Point WAN Interfaces.
  
  

WAN-FR-Interface

This template is for a main, Frame Relay interface that has DLCI interfaces for voice traffic, running IOS 12.1(3)T and later. (There are separate templates for the DLCI subinterfaces.)

The following QoS properties are set:

• Model: IOS_Family
  
  
• Mapped Software Version: 12.2
  
  
• Group contains interfaces, Type: frame-relay, Card Type: Non-VIP
  
  
• QoS Property: Class Based QoS
  
  
• FRTS Enabled
  
  

Low-Speed Frame Relay Links

This set of templates is for low-speed Frame Relay subinterfaces. The QoS configuration for these subinterfaces use FRTS with CIR, and because a different configuration is required for each speed, there are five templates: WAN-FR-64K-DLCI, WAN-FR-128K-DLCI, WAN-FR-256K-DLCI, WAN-FR-512K-DLCI and WAN-FR-768K-DLCI.

When you use these templates, you should also use the WAN-FR-Interface described in WAN-FR-Interface for the main interfaces.

The following information is for the WAN-FR-256K-DLCI template.

The following QoS properties are set:

• Model: IOS_Family
  
  
• Mapped Software Version: 12.2
  
  
• Group Contains Subinterfaces, Type: frame-relay, Card Type: Non-VIP
  
  
• QoS Property: Class Based QoS
  
  
• FRTS Enabled: Configure on DLCI, Rate=253, Burst Size=1, Exceed Burst Size=0, Minimum Rate=253,
  
  
• CRTP Enabled,
  
  

The following QoS policies are configured for this template:

• Set queuing for voice traffic—Bandwidth=40%, LLQ enabled
  
  
• Set queuing for control traffic—Drop mechanism is TAIL, Bandwidth=10%
  
  
• Set queuing for class-default—Drop mechanism is TAIL, queuing is WFQ
  
  

WAN-FR-1.5M-DLCI

This template is for high-speed (> 768kbs) Frame Relay subinterfaces running IOS 12.1(3)T and later. It uses the same QoS techniques as in the low-speed Frame Relay templates, but without FRF.

When you use this template, you should also use the WAN-FR-Interface described in WAN-FR-Interface for the main interfaces.

The following QoS properties are set:

• Model: IOS_Family
  
  
• Mapped Software Version: 12.2
  
  
• Group Contains Subinterfaces, Type: frame-relay, Card Type: Non-VIP
  
  
• QoS Property: Class Based QoS
  
  
• FRTS Enabled: Configure on DLCI, Rate=1500, Burst Size=1, Exceed Burst Size=0, Minimum Rate=1500
  
  
• CRTP Enabled
  
  

The following QoS policies are configured for this template:

• Set queuing for voice traffic—Bandwidth=40%, LLQ enabled
  
  
• Set queuing for control traffic—Drop mechanism is TAIL, Bandwidth=5%
  
  

ATM WAN Links

This template implements QoS over ATM using one PVC with CBWFQ and LLQ.

WAN-ATM-VirtualTempl

This template implements QoS over ATM using a virtual template.

The following QoS properties are set:

• Model: IOS_Family
  
  
• Mapped Software Version: 12.2
  
  
• Group Contains Interfaces, Type: ppp, Card Type: Non-VIP
  
  
• QoS Property: Class Based QoS
  
  
• LFI Enabled: Fragment Delay=10
  
  

The following QoS policies are configured for this template:

• Set queuing for voice traffic—Bandwidth=40%, LLQ enabled
  
  
• Set queuing for control traffic—Drop mechanism is TAIL, Bandwidth=5%
  
  
• Set queuing for class-default—Drop mechanism is TAIL, queuing is WFQ
  
  

---

Note   This template does not configure the TX-ring buffer size. You must adjust the TX-ring buffer size using CLI commands. See the Cisco IP Telephony QoS Design Guide for more details at http://www.cisco.com/univercd/cc/td/doc/product/voice/ip_tele//index.htm.

---

Interface from Branch Office Router to Layer 2 Switch

The traditional branch office design for up to 100 users consists of a branch router and an Ethernet switch. The router handles all IP routing and WAN connectivity.

RouterWAN=>Non6KPFC

This template is for the interfaces on a router running IOS 12.2 or higher, to a layer 2 switch.

The following QoS properties are set:

• Model: IOS_Family
  
  
• Mapped Software Version: 12.2
  
  
• Group Contains Interfaces, Type: Any, Card Type: Non-VIP
  
  
• QoS Property: Class Based QoS
  
  

The following QoS policies are configured for this template:

• Color control traffic DSCP=26.
  
  
• Filter voice traffic and leave the color as set by the IP phone at IP Precedence=5.