Downloads |
Table Of Contents
Low Latency Queueing for Frame Relay
IP Cisco Express Forwarding Switching
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Configuring Class Policy in the Policy Map
Configuring Class Policy for a Low Latency Queueing Priority Queue
Configuring Class Policy Using a Specified Bandwidth and WRED Packet Drop
Configuring the Class-Default Class Policy
Attaching the Service Policy and Enabling Low Latency Queueing
for Frame RelayVerifying Configuration of Policy Maps and Their Classes
Monitoring and Maintaining Low Latency Queueing
for Frame RelayLow Latency Queueing for Frame Relay Configuration Example
Low Latency Queueing for Frame Relay
This document describes the Low Latency Queueing for Frame Relay feature. It includes information about the benefits of this new feature, supported platforms, related documents, and more.
This document includes the following sections:
•
Supported Standards, MIBs, and RFCs
•
Feature Overview
Low Latency Queueing for Frame Relay is a new feature that provides a strict priority queue (PQ) for voice traffic and weighted fair queues for other classes of traffic. Before the release of this feature, low latency queueing was available at the interface and ATM virtual circuit (VC) levels. It is now available at the Frame Relay VC level when Frame Relay traffic shaping is configured.
Low Latency Queueing, also called priority queueing/class-based weighted fair queueing (PQ/CBWFQ), is a superset of and more flexible than previous Frame Relay Quality of Service offerings, in particular Real-Time Transport Protocol (RTP) prioritization and priority queueing/weighted fair queueing (PQ/WFQ).
With RTP prioritization and PQ/WFQ, traffic that matches a specified User Datagram Protocol (UDP)/RTP port range is considered high priority and allocated to the PQ. With Low Latency Queueing for Frame Relay, you set up classes of traffic according to protocol, interface, or access lists, and then define policy maps to establish how the classes are handled in the priority queue and weighted fair queues.
Queues are set up on a per-permanent virtual circuit (PVC) basis: each PVC has a PQ and an assigned number of fair queues. The fair queues are assigned weights proportional to the bandwidth requirements of each class; a class requiring twice the bandwidth of another will have half the weight. Oversubscription of the bandwidth is not permitted. The command line interface (CLI) will reject a change of configuration that would cause the total bandwidth to be exceeded. This functionality differs from that of WFQ, in which flows are assigned a weight based on IP precedence. WFQ allows higher precedence traffic to obtain proportionately more of the bandwidth, but the more flows there are, the less bandwidth is available to each flow.
The PQ is policed to ensure that the fair queues are not starved of bandwidth. When you configure the PQ, you specify in kbps the maximum amount of bandwidth available to that queue. Packets that exceed that maximum are dropped. There is no policing of the fair queues.
Low Latency Queueing for Frame Relay is configured using a combination of class-map, policy-map and Frame Relay map-class commands. The class-map command defines traffic classes according to protocol, interface, or access list. The policy-map command defines how each class is treated in the queueing system according to bandwidth, priority, queue limit, or Weighted Random Early Detection (WRED). The service-policy output map-class command attaches a policy-map to a Frame Relay VC.
Policies not directly related to low latency queueing—for example, traffic shaping, setting IP precedence, and policing—are not supported by the class-map and policy-map commands for Frame Relay VCs. You must use other configuration mechanisms, such as map-class commands, to configure these policies.
Low Latency Queueing for Frame Relay can be used in conjunction with the features listed in the following sections:
•
RTP Prioritization
RTP prioritization provides a strict priority queueing scheme for voice traffic. Voice traffic is identified by its RTP port numbers and classified into a priority queue configured by the frame-relay ip rtp priority map-class command. You classify traffic as voice by specifying an RTP port number range. If traffic matches the specified range, it is classified as voice and queued in the low latency queueing PQ, as well as the interface priority queue. If traffic does not fall within the specified RTP port range, it is classified by the service policy of the low latency queueing scheme.
The ip rtp priority command is available in both interface configuration mode and map-class frame-relay configuration mode. Only the frame relay ip rtp priority map-class configuration command is supported in this feature.
Voice over Frame Relay
Voice over Frame Relay (VoFR) uses the low latency queueing PQ rather than its own priority queueing mechanism. The frame-relay voice bandwidth map-class command configures the total bandwidth available for VoFR traffic. The visible bandwidth made available to the other queues will be the minimum commited information rate (CIR) less the voice bandwidth.
The frame-relay voice bandwidth map-class command also configures a call admission control function, which ensures that there is sufficient VoFR bandwidth remaining before allowing a call. There is no policing of the voice traffic once the call has been established.
For VoFR with no data, all voice and call control packets are queued in the low latency queueing PQ. For VoFR with data, a VoFR PVC may carry both voice and data packets in different subchannels. VoFR data packets are fragmented and interleaved with voice packets to ensure good latency bounds for voice packets as well as scalability for voice and data traffic.
Note that when VoFR is enabled, there is no need to configure a priority class map for voice. The only VoFR commands to be used with Low Latency Queueing for Frame Relay are the frame-relay voice bandwidth map-class configuration command and the vofr data interface-dlci configuration command.
Note
Frame Relay Fragmentation
The purpose of Frame Relay fragmentation (FRF.12) is to support voice and data packets on lower-speed links without causing excessive delay to the voice packets. Large data packets are fragmented and interleaved with the voice packets.
When FRF.12 is configured with low latency queueing, small packets classified for the PQ pass through unfragmented onto both the low latency queueing PQ and the high priority interface queue. Large packets destined for PQ are shaped and fragmented when dequeued.
Use the frame-relay fragment and service-policy map-class configuration commands to enable low latency queueing with FRF.12 .
IP Cisco Express Forwarding Switching
IP Cisco express forwarding (CEF) switching is not affected by low latency queueing functionality.
Benefits
Strict Priority Service
Strict priority queueing improves quality of service by allowing delay-sensitive traffic, such as voice, to be pulled from the queue and sent before other classes of traffic.
Flexibility
Low Latency Queueing for Frame Relay allows you to define classes of traffic according to protocol, interface, or access lists. You can then assign characteristics to those classes, including priority, bandwidth, queue limit, and WRED.
Restrictions
Only the following class-map and policy-map commands are supported:
•
•
Related Features and Technologies
The following features and technologies are related to low latency queueing for Frame Relay:
•
•
•
•
•
Related Documents
The following documents provide information related to low latency queueing for Frame Relay:
•
•
•
•
Supported Platforms
The Low Latency Queueing for Frame Relay feature runs on the following platforms:
•
•
•
•
•
•
•
•
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature.
For descriptions of supported MIBs and how to use MIBs, see the Cisco MIB web site on Cisco Connection Online (CCO) at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites
The following tasks must be completed before Low Latency Queueing for Frame Relay can be enabled:
•
•
•
Configuration Tasks
See the following sections for configuration tasks for the Low Latency Queueing for Frame Relay feature. Each task in the list is identified as either optional or required.
•
•
•
•
Defining Class Maps
To create a class map containing match criteria against which a packet is checked to determine if it belongs to a class, begin with the class-map command in global configuration mode.
For more details about defining class maps, see the Cisco IOS Quality of Service Solutions Configuration Guide.
Configuring Class Policy in the Policy Map
To configure a policy map and create class policies that make up the service policy, begin with the policy-map command to specify the policy map name. Then use one or more of the following commands to configure the policy for a standard class or the default class:
•
•
•
•
For each class that you define, you can use one or more of the commands listed above to configure the class policy. For example, you might specify bandwidth for one class and both bandwidth and queue limit for another class.
The default class of the policy map (commonly known as the class-default class) is the class to which traffic is directed if that traffic does not satisfy the match criteria of the other classes defined in the policy map.
You can configure class policies for as many classes as are defined on the router, up to the maximum of 64. However, the total amount of bandwidth allocated for all classes in a policy map must not exceed the minimum CIR configured for the VC less any bandwidth reserved by the frame-relay voice bandwidth and frame-relay ip rtp priority commands. If the minimum CIR is not configured, it defaults to one half of the CIR. If all of the bandwidth is not allocated, the remaining bandwidth is allocated proportionally among the classes on the basis of their configured bandwidth.
To configure class policies in a policy map, perform the tasks in the following sections:
•
•
•
Configuring Class Policy for a Low Latency Queueing Priority Queue
To configure a policy map and give priority to a class within the policy map, begin with the policy-map command in global configuration mode.
Configuring Class Policy Using a Specified Bandwidth and WRED Packet Drop
To configure a policy map and create class policies that make up the service policy, begin with the policy map command in global configuration mode.
To configure policy for more than one class in the same policy map, repeat Steps 2 through 4.
Configuring the Class-Default Class Policy
The class-default class is used to classify traffic that does not fall into one of the defined classes. Even though the class-default class is predefined when you create the policy map, you still have to configure it. If a default class is not configured, then traffic that does not match any of the configured classes is given "best-effort" treatment, which means that the network will deliver the traffic if it can, without any assurance of reliability, delay prevention, or throughput.
To configure a policy map and the class-default class, begin with the policy-map command in global configuration mode.
For more details about configuring class policy in the policy map, see the Cisco IOS Quality of Service Solutions Configuration Guide.
Attaching the Service Policy and Enabling Low Latency Queueing
for Frame RelayTo attach a service policy to the output interface and enable Low Latency Queueing for Frame Relay, use the following map-class configuration command. When Low Latency Queueing is enabled, all classes configured as part of the service policy map are installed in the fair queueing system.
Router(config-map-class)# service-policy output policy-map
Attaches the specified service policy map to the output interface and enables Low Latency Queueing for Frame Relay.
Verifying Configuration of Policy Maps and Their Classes
To display the contents of a specific policy map or all policy maps configured on an interface, use one of the following commands in global configuration mode:
Monitoring and Maintaining Low Latency Queueing
for Frame RelayFor a list of commands that can be used to monitor Low Latency Queueing for Frame Relay, see the previous section, "Verifying Configuration of Policy Maps and Their Classes."
Configuration Examples
This section provides a configuration example for Low Latency Queueing for Frame Relay configuration.
Low Latency Queueing for Frame Relay Configuration Example
The following example shows how to configure a PVC shaped to a 64K CIR with fragmentation. The shaping queue is configured with a class for voice, two data classes for IP precedence traffic, and a default class for best-effort traffic. WRED is used as the drop policy on one of the data classes.
The following commands define class maps and the match criteria for the class maps:
!class-map voicematch access-group 101!class-map immediate-datamatch access-group 102!class-map priority-datamatch access-group 103!access-list 101 permit udp any any range 16384 32767access-list 102 permit ip any any precedence immediateaccess-list 103 permit ip any any precedence priorityThe following commands create and define a policy map called "mypolicy":
!policy-map mypolicyclass voicepriority 16class immediate-databandwidth 32random-detectclass priority-databandwidth 16class class-defaultfair-queue 64queue-limit 20The following commands enable Frame Relay fragmentation and attach the policy map to DLCI 100:
!interface Serial1/0.1 point-to-pointframe-relay interface-dlci 100class fragment!map-class frame-relay fragmentframe-relay cir 64000frame-relay mincir 64000frame-relay bc 640frame-relay fragment 50service-policy output mypolicyCommand Reference
This section documents modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command reference publications.
service-policy
To attach a policy map to an input interface or virtual circuit (VC), or an output interface or VC to be used as the service policy for that interface or VC, use the service-policy global configuration command. To remove a service policy from an input or output interface or input or output VC, use the no form of this command.
service-policy {input | output} policy-map
no service-policy {input | output}
Syntax Description
Defaults
No service policy is specified.
Command Modes
Global configuration
VC submode (for a standalone VC)
Bundle-vc configuration (for ATM VC bundle members)
Map-class configuration (for Frame Relay VCs)
Command History
12.0(5)T
This command was introduced.
12.1(2)T
This command was modified to enable low latency queueing on Frame Relay VCs.
Usage Guidelines
You can attach a single policy map to one or more interfaces or one or more VCs to specify the service policy for those interfaces or VCs.
Currently a service policy specifies class-based weighted fair queueing (CBWFQ). The class policies that make up the policy map are then applied to packets that satisfy the class map match criteria for the class.
To enable Low Latency Queueing for Frame Relay (PQ/CBWFQ), you must first enable Frame Relay traffic shaping on the interface using the frame-relay traffic-shaping command in interface configuration mode. You will then attach an output service policy to the Frame Relay VC using the service-policy command in map-class configuration mode.
For a policy map to be successfully attached to an interface or ATM VC, the aggregate of the configured minimum bandwidths of the classes that make up the policy map must be less than or equal to 75 percent of the interface bandwidth or the bandwidth allocated to the VC. For a Frame Relay VC, the total amount of bandwidth allocated must not exceed the minimum CIR configured for the VC less any bandwidth reserved by the frame-relay voice bandwidth and frame-relay ip rtp priority map-class commands. If not configured, the minimum CIR defaults to half of the CIR.
Configuring CBWFQ on a physical interface is possible only if the interface is in the default queueing mode. Serial interfaces at E1 (2.048 Mbps) and below use WFQ by default; other interfaces use FIFO by default. Enabling CBWFQ on a physical interface overrides the default interface queueing method. Enabling CBWFQ on an ATM PVC does not override the default queueing method.
Attaching a service policy and enabling CBWFQ on an interface renders ineffective any commands related to fancy queueing such as commands pertaining to fair queueing, custom queueing, priority queueing, and Weighted Random Early Detection (WRED). You can configure these features only after you remove the policy map from the interface.
You can modify a policy map attached to an interface or a VC, changing the bandwidth of any of the classes that make up the map. Bandwidth changes that you make to an attached policy map are effective only if the aggregate of the bandwidth amounts for all classes that make up the policy map, including the modified class bandwidth, is less than or equal to 75 percent of the interface bandwidth or the VC bandwidth. If the new aggregate bandwidth amount exceeds 75 percent of the interface bandwidth or VC bandwidth, the policy map is not modified.
Examples
The following exampleshow how to attache the service policy map called "policy9" to DLCI 100 on output interface Serial1 and enables Low Latency Queueing for Frame Relay:
interface Serial1/0.1 point-to-pointframe-relay interface-dlci 100class fragment!map-class frame-relay fragmentservice-policy output policy9The following example illustrates attaching the service policy map called "policy9" to the input interface Serial1:
interface Serial1service-policy input policy9The following example illustrates attaching the service policy map called "policy9" to the input permanent virtual circuit (PVC) called "cisco":
pvc cisco 0/34 service-policy input policy9vbr-nt 5000 3000 500 precedence 4-7The following example illustrates attaching the policy called "policy9" to the output interface serial1 to specify the service policy for the interface and enable CBWFQ on it:
interface serial1service-policy output policy9The following example illustrates attaching the service policy map called "policy9" to the output PVC called "cisco":
pvc cisco 0/5 service-policy output policy9 vbr-nt 4000 2000 500 precedence 2-3Related Commands
show frame-relay pvc
To display statistics about permanent virtual circuits (PVCs) for Frame Relay interfaces, use the show frame-relay pvc command in privileged EXEC mode.
show frame-relay pvc [interface interface ][dlci]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to monitor the PPP link control protocol (LCP) state as being open with an "up" state, or closed with a "down" state.
When "vofr" or "vofr cisco" has been configured on the PVC, and a voice bandwidth has been allocated to the class associated with this PVC, configured voice bandwidth and used voice bandwidth are also displayed.
Statistics Reporting
To obtain statistics about PVCs on all Frame Relay interfaces, use this command with no arguments.
To obtain statistics about a PVC that include policy-map configuration, use this command with the DLCI argument.
Per-VC counters are not incremented at all when either autonomous or silicon switching engine (SSE) switching is configured; therefore, PVC values will be inaccurate if either switching method is used.
Traffic Shaping
Congestion control mechanisms are currently not supported, but the switch passes forward explicit congestion notification (FECN) bits, backward explicit congestion notification (BECN) bits, and discard eligible (DE) bits unchanged from entry to exit points in the network.
If a Local Management Interface (LMI) status report indicates that a PVC is not active, then it is marked as inactive. A PVC is marked as deleted if it is not listed in a periodic LMI status message.
Examples
The various displays in this section show sample output for a variety of PVCs. Some of the PVCs carry data only; some carry a combination of voice and data.
The following is sample output from the show frame-relay pvc command for a PVC shaped to a 64K CIR with fragmentation. A policy map is attached to the PVC and is configured with a priority class for voice, two data classes for IP precedence traffic, and a default class for best-effort traffic. WRED is used as the drop policy on one of the data classes:
ed2-36b# show frame-relay pvc 100PVC Statistics for interface Serial1/0 (Frame Relay DTE)DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE = Serial1/0.1input pkts 0 output pkts 0 in bytes 0out bytes 0 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0pvc create time 00:00:42, last time pvc status changed 00:00:42service policy mypolicyClass voiceWeighted Fair QueueingStrict PriorityOutput Queue: Conversation 72Bandwidth 16 (kbps) Packets Matched 0(pkts discards/bytes discards) 0/0Class immediate-dataWeighted Fair QueueingOutput Queue: Conversation 73Bandwidth 60 (%) Packets Matched 0(pkts discards/bytes discards/tail drops) 0/0/0mean queue depth: 0drops: class random tail min-th max-th mark-prob0 0 0 64 128 1/101 0 0 71 128 1/102 0 0 78 128 1/103 0 0 85 128 1/104 0 0 92 128 1/105 0 0 99 128 1/106 0 0 106 128 1/107 0 0 113 128 1/10rsvp 0 0 120 128 1/10Class priority-dataWeighted Fair QueueingOutput Queue: Conversation 74Bandwidth 40 (%) Packets Matched 0 Max Threshold 64 (packets)(pkts discards/bytes discards/tail drops) 0/0/0Class class-defaultWeighted Fair QueueingFlow Based Fair QueueingMaximum Number of Hashed Queues 64 Max Threshold 20 (packets)Output queue size 0/max total 600/drops 0fragment type end-to-end fragment size 50cir 64000 bc 640 be 0 limit 80 interval 10mincir 64000 byte increment 80 BECN response nofrags 0 bytes 0 frags delayed 0 bytes delayed 0shaping inactivetraffic shaping drops 0The following is sample output from the show frame-relay pvc command that shows the PVC statistics for serial interface 5 (slot 1 and DLCI 55 is up) during a PPP session over Frame Relay:
Router# show frame-relay pvc 55PVC Statistics for interface Serial5/1 (Frame Relay DTE)DLCI = 55, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial5/1.1input pkts 9 output pkts 16 in bytes 154out bytes 338 dropped pkts 6 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0pvc create time 00:35:11, last time pvc status changed 00:00:22Bound to Virtual-Access1 (up, cloned from Virtual-Template5)The following is sample output from the show frame-relay pvc command for a PVC carrying Voice over Frame Relay configured via the vofr cisco command. The frame-relay voice bandwidth command has been configured on the class associated with this PVC, as has fragmentation. The fragmentation employed is proprietary to Cisco.
A sample configuration for this scenario is shown first, followed by the output for the show frame-relay pvc command:
interface serial 0encapsulation frame-relayframe-relay traffic-shapingframe-relay interface-dlci 108vofr ciscoclass vofr-classmap-class frame-relay vofr-classframe-relay fragment 100frame-relay fair-queueframe-relay cir 64000frame-relay voice bandwidth 25000Router# show frame-relay pvc 108PVC Statistics for interface Serial0 (Frame Relay DTE)DLCI = 108, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0input pkts 1260 output pkts 1271 in bytes 95671out bytes 98604 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 1271 out bcast bytes 98604pvc create time 09:43:17, last time pvc status changed 09:43:17Service type VoFR-ciscoconfigured voice bandwidth 25000, used voice bandwidth 0voice reserved queues 24, 25fragment type VoFR-cisco fragment size 100cir 64000 bc 64000 be 0 limit 1000 interval 125mincir 32000 byte increment 1000 BECN response nopkts 2592 bytes 205140 pkts delayed 1296 bytes delayed 102570shaping inactiveshaping drops 0Current fair queue configuration:Discard Dynamic Reservedthreshold queue count queue count64 16 2Output queue size 0/max total 600/drops 0Note that the "fragment type" field in the show frame-relay pvc display can have the following entries:
•
•
•
Below is sample output from the show frame-relay pvc command for an application employing pure FRF.12 fragmentation. A sample configuration for this scenario is shown first, followed by the output for the show frame-relay pvc command:
interface serial 0encapsulation frame-relayframe-relay traffic-shapingframe-relay interface-dlci 110class fragmap-class frame-relay fragframe-relay fragment 100frame-relay fair-queueframe-relay cir 64000Router# show frame-relay pvc 110PVC Statistics for interface Serial0 (Frame Relay DTE)DLCI = 110, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0input pkts 0 output pkts 243 in bytes 0out bytes 7290 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 243 out bcast bytes 7290pvc create time 04:03:17, last time pvc status changed 04:03:18fragment type end-to-end fragment size 100cir 64000 bc 64000 be 0 limit 1000 interval 125mincir 32000 byte increment 1000 BECN response nopkts 486 bytes 14580 pkts delayed 243 bytes delayed 7290shaping inactiveshaping drops 0Current fair queue configuration:Discard Dynamic Reservedthreshold queue count queue count64 16 2Output queue size 0/max total 600/drops 0Note that when voice is not configured, voice bandwidth output is not displayed.
The following is sample output from the show frame-relay pvc command for multipoint subinterfaces carrying data only. The output displays both the subinterface number and the DLCI. This display is the same whether the PVC is configured for static or dynamic addressing. Note that neither fragmentation nor voice is configured on this PVC.
Router# show frame-relay pvcDLCI = 300, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.103input pkts 10 output pkts 7 in bytes 6222out bytes 6034 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0outbcast pkts 0 outbcast bytes 0pvc create time 0:13:11 last time pvc status changed 0:11:46DLCI = 400, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.104input pkts 20 output pkts 8 in bytes 5624out bytes 5222 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0outbcast pkts 0 outbcast bytes 0pvc create time 0:03:57 last time pvc status changed 0:03:48The following is sample output from the show frame-relay pvc command for a PVC carrying voice and data traffic, with a special queue specifically for voice traffic created using the frame-relay voice bandwidth command queue keyword:
Router# show frame-relay pvc interface serial 1 45PVC Statistics for interface Serial1 (Frame Relay DTE)DLCI = 45, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial1input pkts 85 output pkts 289 in bytes 1730out bytes 6580 dropped pkts 11 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0pvc create time 00:02:09, last time pvc status changed 00:02:09Service type VoFRconfigured voice bandwidth 25000, used voice bandwidth 22000fragment type VoFR fragment size 100cir 20000 bc 1000 be 0 limit 125 interval 50mincir 20000 byte increment 125 BECN response nofragments 290 bytes 6613 fragments delayed 1 bytes delayed 33shaping inactivetraffic shaping drops 0Voice Queueing Stats: 0/100/0 (size/max/dropped)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Current fair queue configuration:Discard Dynamic Reservedthreshold queue count queue count64 16 2Output queue size 0/max total 600/drops 0Table 1 provides a listing of the fields in these displays and a description of each field.
Related Commands
show policy-map interface
To display the configuration of all classes configured for all service policies on the specified interface or to display the classes for the service policy for a specific permanent virtual circuit (PVC) on the interface, use the show policy-map interface global configuration command.
show policy-map interface interface-name [vc [vpi/] vci ][dlci dlci]
Syntax Description
