Feedback
Contents
- Frame Relay PVC Interface Priority Queueing
- Finding Feature Information
- Feature Overview
- Benefits
- Restrictions
- Related Features and Technologies
- Related Documents
- Supported Platforms
- Supported Standards and MIBs and RFCs
- Prerequisites
- Configuration Tasks
- Configuring PVC Priority in a Map Class
- Enabling FR PIPQ and Setting Queue Limits
- Assigning a Map Class to a PVC
- Verifying FR PIPQ
- Monitoring and Maintaining FR PIPQ
- Configuration Examples
- FR PIPQ Configuration Example
- Glossary
Frame Relay PVC Interface Priority Queueing
The Frame Relay PVC Interface Priority Queueing feature provides an interface-level priority queueing scheme in which prioritization is based on destination permanent virtual circuit (PVC) rather than packet contents.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Feature Overview
The FR PIPQ feature provides an interface-level priority queueing scheme in which prioritization is based on destination permanent virtual circuit (PVC) rather than packet contents. For example, FR PIPQ allows you to configure a PVC transporting voice traffic to have absolute priority over a PVC transporting signalling traffic, and a PVC transporting signalling traffic to have absolute priority over a PVC transporting data.
FR PIPQ provides four levels of priority: high, medium, normal, and low. The Frame Relay packet is examined at the interface for the data-link connection identifier (DLCI) value. The packet is then sent to the correct priority queue based on the priority level configured for that DLCI.
You assign priority to a PVC within a Frame Relay map class. All PVCs using or inheriting that map class will be classed according to the configured priority. If a PVC does not have a map class associated with it, or if the map class associated with it does not have priority explicitly configured, then the packets on that PVC will be queued on the default "normal" priority queue.
If you do not enable FR PIPQ on the interface using the frame-relay interface-queue prioritycommand in interface configuration mode, configuring PVC priority within a map class will not be effective. At this time you have the option to also set the size (in maximum number of packets) of the four priority queues.
FR PIPQ works with or without Frame Relay traffic shaping (FRTS) and FRF.12. The interface-level priority queueing takes the place of the FIFO queueing or dual FIFO queueing normally used by FRTS and FRF.12. PVC priority assigned within FR PIPQ takes precedence over FRF.12 priority, which means that all packets destined for the same PVC will be queued on the same interface queue whether they were fragmented or not.
 Note | Although high priority PVCs most likely will transport only small packets of voice traffic, you may want to configure FRF.12 on these PVCs anyway to guard against any unexpectedly large packets. |
Benefits
FR PIPQ provides four levels of PVC priority: high, medium, normal, and low. This method of queueing ensures that time/delay-sensitive traffic such as voice has absolute priority over signalling traffic, and that signalling traffic has absolute priority over data traffic, providing different PVCs are used for the different types of traffic.
Restrictions
The following restrictions apply to FR PIPQ:
- FR PIPQ is not supported on loopback or tunnel interfaces, or interfaces that explicitly disallow priority queueing.
- FR PIPQ is not supported with hardware compression.
- FR PIPQ cannot be enabled on an interface that is already configured with queueing other than FIFO queueing. FR PIPQ can be enabled if WFQ is configured, as long as WFQ is the default interface queueing method.
Supported Platforms
- Cisco 1000 series
- Cisco 1400 series
- Cisco 1600
- Cisco 1700
- Cisco 1750
- Cisco 2500
- Cisco 2600
- Cisco 3600
- Cisco 3810
- Cisco 4500
- Cisco 4700
- Cisco 7200
- Cisco 7500 (in nondistributed mode)
Supported Standards and MIBs and RFCs
Prerequisites
- PVCs should be configured to carry a single type of traffic.
- The network should be configured with adequate call admission control to prevent starvation of any of the priority queues.
Configuration Tasks
- Configuring PVC Priority in a Map Class
- Enabling FR PIPQ and Setting Queue Limits
- Assigning a Map Class to a PVC
- Verifying FR PIPQ
Configuring PVC Priority in a Map Class
To configure PVC priority within a map class, use the following commands beginning in global configuration mode:
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
Step 1 |
Router(config)# map-class frame-relay map-class-name |
Specifies a Frame Relay map class. |
Step 2 |
Router(config-map-class)# frame-relay interface-queue priority {high | medium| normal | low} |
Assigns a PVC priority level to a Frame Relay map class. |
Enabling FR PIPQ and Setting Queue Limits
To enable FR PIPQ and set the priority queue sizes, use the following commands beginning in global configuration mode:
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
Step 1 |
Router(config)# interface type number [name-tag] |
Configures an interface type and enters interface configuration mode. |
Step 2 |
Router(config-if)# encapsulation frame-relay[cisco | ietf] |
Enables Frame Relay encapsulation. |
Step 3 |
Router(config-if)# frame-relay interface-queue priority [high-limit medium-limit normal-limit low-limit] |
Enables FR PIPQ and sets the priority queue limits. |
Assigning a Map Class to a PVC
To assign a map class to a specific PVC, use the following commands beginning in interface configuration mode:
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
Step 1 |
Router(config-if)# frame-relay interface-dlci dlci |
Specifies a single PVC on a Frame Relay interface. |
Step 2 |
Router(config-fr-dlci)# class map-class-name |
Associates a map class with a specified PVC. |
Verifying FR PIPQ
To verify the configuration of FR PIPQ, use one or more of the following commands in privileged EXEC mode:
|
Command |
Purpose |
|---|---|
Router# show frame-relay pvc [interface interface][dlci] |
Displays statistics about PVCs for Frame Relay interfaces. |
Router# show interfaces [type number][first][last] |
Displays the statistical information specific to a serial interface. |
Router# show queueing [custom | fair | priority | random-detect [interface atm_subinterface [vc [[vpi/] vci]]]] |
Lists all or selected configured queueing strategies. |
Monitoring and Maintaining FR PIPQ
To monitor and maintain FR PIPQ, use one or more of the following commands in privileged EXEC mode:
|
Command |
Purpose |
|---|---|
Router# debug priority
|
Debugs priority output queueing. |
Router# show frame-relay pvc [interface interface][dlci] |
Displays statistics about PVCs for Frame Relay interfaces. |
Router# show interfaces [type number][first][last] |
Displays the statistical information specific to a serial interface. |
Router# show queue interface-name interface-number [vc [vpi/] vci][queue-number] |
Displays the contents of packets inside a queue for a particular interface or VC. |
Router# show queueing [custom | fair | priority | random-detect [interface atm_subinterface [vc [[vpi/] vci]]]] |
Lists all or selected configured queueing strategies. |
Configuration Examples
FR PIPQ Configuration Example
This example shows the configuration of four PVCs on serial interface 0. DLCI 100 is assigned high priority, DLCI 200 is assigned medium priority, DLCI 300 is assigned normal priority, and DLCI 400 is assigned low priority.
The following commands configure Frame Relay map classes with PVC priority levels:
Router(config)# map-class frame-relay HI Router(config-map-class)# frame-relay interface-queue priority high Router(config-map-class)# exit Router(config)# map-class frame-relay MED Router(config-map-class)# frame-relay interface-queue priority medium Router(config-map-class)# exit Router(config)# map-class frame-relay NORM Router(config-map-class)# frame-relay interface-queue priority normal Router(config-map-class)# exit Router(config)# map-class frame-relay LOW Router(config-map-class)# frame-relay interface-queue priority low Router(config-map-class)# exit
The following commands enable Frame Relay encapsulation and FR PIPQ on serial interface 0. The sizes of the priority queues are set at a maximum of 20 packets for the high priority queue, 40 for the medium priority queue, 60 for the normal priority queue, and 80 for the low priority queue.
Router(config)# interface Serial0 Router(config-if)# encapsulation frame-relay Router(config-if)# frame-relay interface-queue priority 20 40 60 80
The following commands assign priority to four PVCs by associating the DLCIs with the configured map classes:
Router(config-if)# frame-relay interface-dlci 100 Router(config-fr-dlci)# class HI Router(config-fr-dlci)# exit Router(config-if)# frame-relay interface-dlci 200 Router(config-fr-dlci)# class MED Router(config-fr-dlci)# exit Router(config-if)# frame-relay interface-dlci 300 Router(config-fr-dlci)# class NORM Router(config-fr-dlci)# exit Router(config-if)# frame-relay interface-dlci 400 Router(config-fr-dlci)# class LOW Router(config-fr-dlci)# exit
Glossary
DLCI --data-link connection identifier. Value that specifies a permanent virtual circuit (PVC) or switched virtual circuit (SVC) in a Frame Relay network.
FIFO queueing -- First-in, first-out queueing. FIFO involves buffering and forwarding of packets in the order of arrival. FIFO embodies no concept of priority or classes of traffic. There is only one queue, and all packets are treated equally. Packets are sent out an interface in the order in which they arrive.
Frame Relay traffic shaping --See FRTS.
FRF.12 --The FRF.12 Implementation Agreement was developed to allow long data frames to be fragmented into smaller pieces and interleaved with real-time frames. In this way, real-time voice and nonreal-time data frames can be carried together on lower-speed links without causing excessive delay to the real-time traffic.
FRTS --Frame Relay traffic shaping. FRTS uses queues on a Frame Relay network to limit surges that can cause congestion. Data is buffered and then sent into the network in regulated amounts to ensure that the traffic will fit within the promised traffic envelope for the particular connection.
PIPQ --Permanent virtual circuit (PVC) interface priority queueing. An interface-level priority queueing scheme in which prioritization is based on destination PVC rather than packet contents.
quality of service --Measure of performance for a transmission system that reflects its transmission quality and service availability.
VoFR --Voice over Frame Relay. Enables a router to carry voice traffic over a Frame Relay network. When voice traffic is sent over Frame Relay, the voice traffic is segmented and encapsulated for transit across the Frame Relay network using FRF.12 encapsulation.
Voice over Frame Relay --See VoFR.
WFQ --weighted fair queueing. Congestion management algorithm that identifies conversations (in the form of traffic streams), separates packets that belong to each conversation, and ensures that capacity is shared fairly among these individual conversations. WFQ is an automatic way of stabilizing network behavior during congestion and results in increased performance and reduced retransmission.
WRED --Weighted Random Early Detection. Combines IP Precedence and standard Random Early Detection (RED) to allow for preferential handling of voice traffic under congestion conditions without exacerbating the congestion. WRED uses and interprets IP Precedence to give priority to voice traffic over data traffic, dropping only data packets.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.