Table Of Contents
Attaching Service Policies
Interfaces Supporting QoS Service Policies
Attaching ATM QoS Service Policies
Feature History for ATM QoS
ATM QoS Inheritance
service-policy Command
Syntax Description
service-policy Command History
service-policy Command Modes
Usage Guidelines for the service-policy Command
Restrictions and Limitations for Attaching ATM Service Policies
Attaching ATM QoS Service Policies to ATM Interfaces, Subinterfaces, and PVCs
Attaching QoS Service Policies to an ATM Interface
Attaching QoS Service Policies to an ATM Point-to-Point Subinterface
Attaching QoS Service Policies to an ATM PVC
Attaching QoS Service Policies to an ATM PVC Range and an ATM PVC in a Range
Attaching Frame Relay QoS Service Policies
Feature History for Frame Relay QoS
Frame Relay QoS Inheritance
map-class frame-relay Command
Syntax Description
map-class frame-relay Command History
Usage Guidelines for the map-class frame-relay Command
Restrictions and Limitations for Frame Relay QoS Service Policies
Creating and Attaching QoS Policies to Frame Relay Interfaces, Subinterfaces, and Data-Link Connection Identifiers
Attaching a QoS Service Policy to a Frame Relay Interface or Point-to-Point Subinterface
Attaching a QoS Service Policy to a Frame Relay DLCI
Attaching Virtual LAN QoS Service Policies
Feature History for VLAN QoS
VLAN QoS Inheritance
Restrictions and Limitations for Attaching QoS Services to VLAN Subinterfaces
Attaching QoS Policies to VLAN Interfaces and Subinterfaces
Attaching QoS Service Policies to Physical Interfaces with VLAN Subinterfaces
Attaching QoS Service Policies to VLAN Subinterfaces
Attaching Virtual Access Interface QoS Service Policies
Feature History for VAI QoS
VAI QoS Inheritance
Restrictions and Limitations for Attaching QoS Services to a VAI
Attaching QoS Policies to VAIs Using Virtual Template Interfaces
Applying a QoS Service Policy to a Virtual Template Interface
Applying a Virtual Template Interface to a BBA Group
Attaching a BBA Group to an Interface or Subinterface for PPPoE Sessions
Attaching Layer 2 Access Concentrator QoS Service Policies
Feature History for LAC QoS
LAC QoS Inheritance
Restrictions and Limitations for Attaching LAC QoS
Attaching QoS Policies to LAC ATM Virtual Circuits
Applying QoS on Layer 2 Tunnel Packets
Verifying and Monitoring QoS Service Policies
Verification Example for QoS Service Policies
Related Documentation
Attaching Service Policies
This chapter describes how to attach QoS service policies. After you create a QoS service policy, the next step is to attach the policy to an interface or virtual circuit (VC). By doing this, the router knows which service policy to apply to the packets arriving at or leaving the router. An interface can have different service policies for inbound and outbound packets.
This chapter includes the following topics:
•
Interfaces Supporting QoS Service Policies
•Attaching ATM QoS Service Policies
•Attaching Frame Relay QoS Service Policies
•Attaching Virtual LAN QoS Service Policies
•Attaching Virtual Access Interface QoS Service Policies
•Attaching Layer 2 Access Concentrator QoS Service Policies
•Applying QoS on Layer 2 Tunnel Packets
•Verifying and Monitoring QoS Service Policies
•Related Documentation
Interfaces Supporting QoS Service Policies
You can attach QoS service policies to:
•Physical interfaces
•Multilink Point-to-Point Protocol (MLPPP) and Multilink Frame Relay (MFR) interfaces
•ATM unspecified bit rate (UBR) permanent virtual circuits (PVCs) and point-to-point subinterfaces
•ATM shaped (peak cell rate is specified) UBR PVCs and point-to-point subinterfaces
•ATM constant bit rate (CBR) PVCs and point-to-point subinterfaces
•ATM variable bit rate (VBR) PVCs and point-to-point subinterfaces
•Label-controlled Asynchronous Transfer Mode (LC-ATM) subinterfaces
•Frame Relay PVCs, point-to-point subinterfaces, and map classes
•Ethernet virtual local area networks (VLANs)
•IP tunnel interfaces
•Virtual access interfaces
Each interface, subinterface, or PVC can have no more than two policy maps attached: one for inbound traffic and one for outbound traffic. The router does not require that the inbound and outbound policies be the same; you can attach different input and output policies.
Attaching ATM QoS Service Policies
You can attach a QoS service policy to an ATM interface, point-to-point subinterface, or PVC using the service-policy command.
This section describes the following topics:
•Feature History for ATM QoS
•ATM QoS Inheritance
•service-policy Command
•Restrictions and Limitations for Attaching ATM Service Policies
•Attaching ATM QoS Service Policies to ATM Interfaces, Subinterfaces, and PVCs
Feature History for ATM QoS
Cisco IOS Release
|
Description
|
Required PRE
|
12.0(17)SL
|
The attachment of ATM QoS service policies feature was introduced on the router.
|
PRE1
|
12.2(15)BX
|
This feature was introduced on the PRE2.
|
PRE2
|
12.3(7)XI2
|
This feature was modified to allow you to attach ATM QoS service policies to a range of PVCs and to a specific PVC within the PVC range.
|
PRE2
|
12.2(28)SB
|
This feature was integrated in Cisco IOS Release 12.2(28)SB for the PRE2.
|
PRE2
|
12.2(31)SB2
|
This feature was introduced on the PRE3.
|
PRE2
PRE3
|
ATM QoS Inheritance
The following describes how ATM traffic inherits QoS policies:
•For all releases earlier than Cisco IOS Release 12.3(7)XI2, if you attach a service policy only to the physical interface, the aggregate of all unspecified bit rate (UBR) PVCs is subject to the physical interface's service policy.
For Cisco IOS Release 12.3(7)XI2 and later releases, if you attach a service policy only to the physical interface, the aggregate of all unshaped UBR PVCs is subject to the physical interface's service policy. In Cisco IOS Release 12.3(7)XI2 and later releases, the router treats shaped UBR PVCs like variable bit rate (VBR) and constant bit rate (CBR) PVCs.
•If you attach a service policy only to individual PVCs and not to the physical interface, only the individual PVC is subject to its attached service policy.
•If you attach service policies to both the physical interface and individual PVCs, the aggregate of all UBR PVCs that do not have a service policy is subject to the physical interface's service policy. All PVCs that do have a service policy are individually subject to their attached service policies.
The router can operate in one of two ATM queuing modes: atm pxf queuing or no atm pxf queuing. The router supports:
•Unshaped UBR and nonreal-time VBR (VBR-nrt) PVCs when you configure the atm pxf queuing command on the ATM interfaces
•Unshaped UBR, shaped UBR, and VBR-nrt PVCs when you configure the no atm pxf queuing command on the ATM interfaces
For more information about ATM service classes, see the "ATM Service Categories" section on page 3-13.
The router allocates bandwidth to VBR, CBR, and shaped UBR PVCs before allocating bandwidth to unshaped UBR PVCs. As a result, a diminished amount of bandwidth is available to allocate to unshaped UBR PVCs. To override this behavior, create an hierarchical policy with the bandwidth specified and attach the policy to the ATM port or physical interface. For more information, see Chapter 13, "Defining QoS for Multiple Policy Levels."
service-policy Command
To attach a policy map that the router can use to apply QoS services to inbound and outbound packets, use the service-policy command in interface or map class configuration mode. Use the no form of the command to remove a service policy. This command has no default value or behavior.
service-policy {input | output} policy-map-name
no service-policy {input | output} policy-map-name
Syntax Description
input
|
Indicates to apply the QoS policy to inbound packets.
|
output
|
Indicates to apply the QoS policy to outbound packets.
|
policy-map-name
|
The name of the policy map (created using the policy-map command) you want to attach. The policy-map-name can be a maximum of 40 alphanumeric characters.
|
service-policy Command History
Cisco IOS Release
|
Description
|
12.0(17)SL
|
This command was introduced on the PRE1.
|
12.2(15)BX
|
This command was introduced on the PRE2.
|
12.3(7)XI2
|
This command was enhanced on the PRE2 to allow you to attach a policy map to a range of PVCs, and to a specific PVC within the PVC range.
|
12.2(28)SB
|
This command was integrated in Cisco IOS Release 12.2(28)SB for the PRE2.
|
12.2(31)SB2
|
This command was introduced on the PRE3.
|
service-policy Command Modes
You can configure this command in the following configuration modes:
•Bundle-VC (for ATM VC bundle members)
•Interface
•Map-class (for Frame Relay VCs)
•PVC-in-range (for ATM VCs)
•PVC range (for ATM VCs)
•VC submode (for a standalone VC)
Usage Guidelines for the service-policy Command
The service-policy {input | output} policy-map-name command is used to attach a service policy to an interface.
The service-policy policy-map-name command is used to create hierarchical service policies in policy-map class configuration mode. Do not specify input or output when using the service-policy command in an hierarchical policy.
In Cisco IOS Release 12.2(33)SB and later releases, the router no longer accepts the abbreviated form (ser) of the service-policy command. Instead, you must spell out the command name service- before the router accepts the command.
For example, when attaching a policy map the following error message appears when you attempt to use the abbreviated form of the service-policy command:
Router(config)# interface gigabit1/1/0
Router(config-if)# ser out ?
When you enter the command as service-, the router accepts the command as shown in the following example:
Router(config-if)# service- ?
input Assign policy-map to the input of an interface
output Assign policy-map to the output of an interface
type Configure CPL Service Policy
In releases earlier than Cisco IOS Release 12.2(33)SB, the router accepts the abbreviated form of the service-policy command. For example, the router accepts the following commands:
Router(config)# interface gigabit1/1/0
Router(config-if)# ser out test
Restrictions and Limitations for Attaching ATM Service Policies
•On ATM line cards, you can apply a policy map to the physical interface, point-to-point subinterfaces, and to individual PVCs. The router does not support applying QoS service policies to point-to-multipoint subinterfaces. However, you can apply service policies to VCs that are on multipoint interfaces.
•The policy map you assign to a PVC takes precedence over the policy map you assign to the main interface.
•You must first configure the atm pxf queuing command on the interface and then attach the policy map.
Note Do not change the queuing mode while VCs are configured on the interface. To change the mode, first delete the VCs and then change the mode. Changing the mode while VCs are configured can produce undesired results, and the change does not take effect until the router reloads.
•For a policy map to be successfully attached to an interface or ATM VC, the aggregate of the configured minimum bandwidths of the policy map classes is limited to the speed of the interface, unless you use the atm over-subscription-factor command to oversubscribe the interface.
•The router does not support a service policy based on queuing for unshaped UBR PVCs.
Attaching ATM QoS Service Policies to ATM Interfaces, Subinterfaces, and PVCs
You can attach a QoS service policy to ATM interfaces, point-to-point subinterfaces, or PVCs.
To attach an ATM QoS service policy, perform one of the following configuration tasks:
•Attaching QoS Service Policies to an ATM Interface
•Attaching QoS Service Policies to an ATM Point-to-Point Subinterface
•Attaching QoS Service Policies to an ATM PVC
•Attaching QoS Service Policies to an ATM PVC Range and an ATM PVC in a Range
Attaching QoS Service Policies to an ATM Interface
To attach a QoS service policy to an ATM interface, enter the following commands beginning in interface configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# interface atm
slot/module/port
|
Specifies the interface to which you want to attach the QoS service policy and enters interface configuration mode.
|
Step 2
|
Router(config-if)# service-policy {input
| output} policy-map-name
|
Attaches the service policy you specify to the interface.
input indicates to apply the service policy to inbound traffic on the interface.
output indicates to apply the service policy to outbound traffic on the interface.
Note For QoS policies containing the bandwidth, priority, random-detect, queue-limit, and shape commands, you must specify the output keyword. If you use these commands with the input keyword, the router ignores the commands.
policy-map-name is the name of the policy map you want to attach to the subinterface.
Note The router applies the service policy to the ATM interface and to all PVCs configured on the interface that do not have their own QoS policy applied.
|
Configuration Example for Attaching QoS Service Policies to an ATM Interface
Example 4-1 shows how to attach the QoS service policy named myQoS to inbound traffic arriving at ATM interface 1/0/0. The router applies the service policy to all of the PVCs configured on the interface.
Example 4-1 Attaching a QoS Policy to an ATM Interface
Router(config)# interface atm 1/0/0
Router(config-if)# service-policy input myQoS
Attaching QoS Service Policies to an ATM Point-to-Point Subinterface
To attach a QoS service policy to an ATM point-to-point subinterface, enter the following commands beginning in interface configuration mode:
Note The router does not support QoS service policies on ATM point-to-multipoint subinterfaces. However, you can apply service policies to VCs that are configured on multipoint interfaces.
| |
Command
|
Purpose
|
Step 1
|
Router(config)# interface atm
slot/module/port
|
Specifies the ATM interface and enters interface configuration mode.
|
Step 2
|
Router(config-if)# atm pxf queuing
|
Specifies the interface mode. In this mode, the interface operates in low VC count. The router operates in atm pxf queuing mode by default. You do not need to specify this mode unless the router is currently configured for no atm pxf queuing.
Note This is the required interface operating mode for QoS service policies that include queuing actions.
|
Step 3
|
Router(config-if)# interface atm
slot/module/port.subinterface
point-to-point
|
Specifies the point-to-point subinterface and enters subinterface configuration mode.
|
Step 4
|
Router(config-subif)# service-policy
{input | output} policy-map-name
|
Attaches the service policy you specify to the ATM subinterface.
input indicates to apply the service policy to inbound traffic on the interface.
output indicates to apply the service policy to outbound traffic on the interface.
Note For QoS policies containing the bandwidth, priority, random-detect, queue-limit, and shape commands, you must specify the output keyword. If you use these commands with the input keyword, the router ignores the commands.
policy-map-name is the name of the policy map you want to attach to the subinterface.
Note The router applies the service policy to the ATM subinterface and to all PVCs configured on the subinterface that does not have its own QoS policy applied.
|
Configuration Example for Attaching QoS Service Policies to an ATM Point-to-Point Subinterface
Example 4-2 attaches a QoS service policy named myQoS to ATM point-to-point subinterface 3/0/0.1 for inbound traffic.
Example 4-2 Attaching a QoS Service Policy to an ATM Point-to-Point Subinterface
Router(config)# interface atm 3/0/0
Router(config-if)# atm pxf queuing
Router(config-if)# interface atm 3/0/0.1 point-to-point
Router(config-subif)# service-policy input myQoS
Attaching QoS Service Policies to an ATM PVC
To attach a QoS service policy to an individual ATM PVC, enter the following commands beginning in interface configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# interface atm
slot/module/port
|
Specifies the ATM interface and enters interface configuration mode.
|
Step 2
|
Router(config-if)# atm pxf queuing
|
Specifies the interface mode. In this mode, the interface operates in low VC count. The router operates in atm pxf queuing mode by default. You do not need to specify this mode unless the router is currently configured for no atm pxf queuing.
Note This is the required interface operating mode for QoS service policies that include queuing actions.
|
Step 3
|
Router(config-if)# interface atm
slot/module/port.subinterface
point-to-point
|
Specifies the point-to-point subinterface and enters subinterface configuration mode.
|
Step 4
|
Router(config-subif)# pvc [name] vpi/vci
|
Creates an ATM permanent virtual circuit (PVC) and enters ATM VC configuration mode.
name is the name used to identify the PVC.
vpi is the virtual path identifier.
vci is the virtual circuit identifier.
|
Step 5
|
Router(config-if-atm-vc)# service-policy
[input | output] policy-map-name
|
Attaches the service policy you specify to the specified ATM PVC.
input indicates to apply the service policy to inbound traffic on the interface.
output indicates to apply the service policy to outbound traffic on the interface.
Note For QoS policies containing the bandwidth, priority, random-detect, queue-limit, and shape commands, you must specify the output keyword. If you use these commands with the input keyword, the router ignores the commands.
policy-map-name is the name of the policy map you want to attach to the subinterface.
Note The router applies the service policy to only the individual ATM PVC that you specify.
|
Configuration Example for Attaching QoS Service Policies to an ATM PVC
Example 4-3 shows how to attach a QoS service policy named bronze to PVC 0/101 on the ATM subinterface 3/0/0.1 for inbound traffic.
Example 4-3 Attaching a QoS Service Policy to an ATM PVC
Router(config)# interface atm 3/0/0
Router(config-if)# atm pxf queuing
Router(config)# interface atm 3/0/0.1
Router(config-subif)# pvc 0/101
Router(config-if-atm-vc)# service-policy input bronze
Attaching QoS Service Policies to an ATM PVC Range and an ATM PVC in a Range
To attach a QoS service policy to a range of ATM PVCs or to a specific ATM PVC in a range of PVCs, enter the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# interface atm
slot/module/port
|
Specifies the ATM interface and enters interface configuration mode.
|
Step 2
|
Router(config-if)# range [range-name] pvc
start-vpi/start-vci end-vpi/end-vci
|
Defines a range of ATM permanent virtual circuits (PVCs). Enters ATM range configuration mode.
(Optional) range-name is the name of the range. The range-name can be a maximum of 15 characters.
start-vpi/ specifies the beginning value for a range of virtual path identifiers (VPIs). The slash is required. If you do not provide a VPI value or the slash, the default value of 0 is used. Valid values for VPI are from 0 to 255.
start-vci specifies the beginning value for a range of virtual channel identifiers (VCIs). Valid values are from 32 to 65535.
end-vpi/ specifies the end value for a range of virtual path identifiers (VPIs). The slash is required. If you do not provide a VPI value or the slash, the start-vpi value is used by default. Valid values for VPI are from 0 to 255.
end-vci specifies the end value for a range of virtual channel identifiers (VCIs). Valid values are from 32 to 65535.
|
Step 3
|
Router(config-if-atm-range)#
service-policy [input | output]
policy-map-name
|
Attaches the service policy you specify to the specified ATM PVC range.
input indicates to apply the service policy to inbound traffic on the interface.
output indicates to apply the service policy to outbound traffic on the interface.
Note For QoS policies containing the bandwidth, priority, random-detect, queue-limit, and shape commands, you must specify the output keyword. If you use these commands with the input keyword, the router ignores the commands.
policy-map-name is the name of the policy map you want to attach to the subinterface.
Note The router applies the service policy to only the PVCs within the PVC range.
|
Step 4
|
Router(config-if-atm-range)# pvc-in-range
[pvc-name] vpi/vci
|
Configures an individual PVC within a PVC range. Enters ATM range PVC configuration mode.
(Optional) pvc-name is the name given to the PVC. The PVC name can have a maximum of 15 characters.
vpi/ is the virtual path identifier (VPI) for this PVC. The slash is required. If you do not specify a VPI value or the slash, the default value of 0 is used. Valid VPI values are from 0 to 255.
vci is the virtual circuit identifier (VCI) for this PVC. Valid values are from 32 to 2047.
|
Step 5
|
Router(config-if-atm-range-pvc)#
service-policy [input | output]
policy-map-name
|
Attaches the service policy you specify to the specified PVC within the ATM PVC range.
input indicates to apply the service policy to inbound traffic on the interface.
output indicates to apply the service policy to outbound traffic on the interface.
Note For QoS policies containing the bandwidth, priority, random-detect, queue-limit, and shape commands, you must specify the output keyword. If you use these commands with the input keyword, the router ignores the commands.
policy-map-name is the name of the policy map you want to attach to the subinterface.
Note The router applies the service policy to only the individual ATM PVC within the PVC range.
|
Configuration Example for Attaching QoS Service Policies to an ATM PVC
Example 4-4 shows how to attach policy maps to a range of ATM PVCs and to a specific PVC within a PVC range. In the example, the service policy named voice is attached to the range of ATM PVCs 1/32 to 1/34. The router applies the service policy to all of the PVCs within the PVC range. The service policy named data is attached to PVC 1/33 within the PVC range. The router applies the service policy to only PVC 1/33.
Example 4-4 Attaching Policy Maps to ATM PVC Ranges and PVCs in PVC Ranges
Router(config)# interface atm 2/0/0
Router(config-if)# range pvc 1/32 1/34
Router(config-if-atm-range)# service-policy input voice
Router(config-if-atm-range)# pvc-in-range 1/33
Router(config-if-atm-range-vc)# service-policy input data
Attaching Frame Relay QoS Service Policies
You can attach QoS service policies to Frame Relay interfaces, PVCs on subinterfaces, data-link connection identifiers (DLCIs), and map classes using the map-class frame-relay and service-policy commands. You can apply a map class to an interface or subinterface.
This section includes the following topics:
•Feature History for Frame Relay QoS
•Frame Relay QoS Inheritance
•map-class frame-relay Command
•Restrictions and Limitations for Frame Relay QoS Service Policies
•Creating and Attaching QoS Policies to Frame Relay Interfaces, Subinterfaces, and Data-Link Connection Identifiers
Feature History for Frame Relay QoS
Cisco IOS Release
|
Description
|
Required PRE
|
12.0(23)SX
|
The attachment of Frame Relay QoS service policies feature was introduced on the router.
|
PRE1
|
12.0(25)S
|
This feature was integrated into Cisco IOS Release 12.0(25)S.
|
PRE1
|
Frame Relay QoS Inheritance
On Frame Relay interfaces, you can attach a service policy to the physical interface, an individual PVC, or to both the physical interface and one or more PVCs. The following describes how Frame Relay traffic inherits QoS policies:
•If you attach a service policy only to the physical interface, the aggregate of all PVCs is subject to the physical interface's service policy.
•If you attach a service policy only to individual PVCs and not to the physical interface, only the individual PVC is subject to its attached service policy.
•If you attach service policies to both the physical interface and individual PVCs, the aggregate of all PVCs that do not have a service policy is subject to the physical interface's service policy. All PVCs that do have a service policy are individually subject to their attached service policies.
•If you attach a service policy to a Frame Relay point-to-point subinterface (either directly or using a map class), the router applies the QoS service policy to the aggregate of all of the DLCIs configured on the subinterface.
•If you attach a service policy to an individual DLCI (either directly or using a map class), the router only applies the QoS service policy to the individual DLCI.
map-class frame-relay Command
To attach a QoS service policy to a Frame Relay interface, PVC on a subinterface, DLCI, or map class, use the map-class frame-relay command in global configuration mode. To remove a map class, use the no form of the command. This command has no default behavior.
map-class frame-relay map-class-name
no map-class frame-relay map-class-name
Syntax Description
map-class-name
|
The name of the map class. The map-class-name can be a maximum of 40 alphanumeric characters.
|
map-class frame-relay Command History
Cisco IOS Release
|
Description
|
12.0(23)SX
|
This command was introduced on the PRE1.
|
12.0(25)S
|
This command was integrated into Cisco IOS Release 12.0(25)S.
|
Usage Guidelines for the map-class frame-relay Command
You can attach a QoS service policy to a Frame Relay map class using the service-policy command. For more information, see the "service-policy Command" section.
You can apply a map class to a Frame Relay interface and subinterface.
Restrictions and Limitations for Frame Relay QoS Service Policies
•Do not configure Frame Relay services using both the modular QoS command-line interface (MQC) and the Frame Relay legacy commands.
•For Cisco IOS Release 12.0(22)S and later releases, use the MQC to configure QoS services for Frame Relay interfaces.
•For all releases earlier than Cisco IOS Release 12.0(22)S, use the Frame Relay commands to configure Frame Relay QoS services. For more information, see Appendix A, "Configuring Frame Relay QoS Using Frame Relay Legacy Commands."
•The router has no preset scaling limit for Frame Relay QoS services. You can apply any number of Frame Relay QoS services.
•The router does not support attaching QoS service policies to Frame Relay point-to-multipoint subinterfaces.
•You cannot attach a policy map and a map class to the same subinterface. For Cisco IOS Release 12.0(22)S and later releases, use the MQC to create and attach a policy map as described in this chapter. For all releases earlier than Cisco IOS Release 12.0(22)S, use the Frame Relay legacy commands to create and attach a Frame Relay QoS policy as described in Appendix A, "Configuring Frame Relay QoS Using Frame Relay Legacy Commands."
•Output QoS policies that contain queuing actions must be nested service policies.
Creating and Attaching QoS Policies to Frame Relay Interfaces, Subinterfaces, and Data-Link Connection Identifiers
To create a Frame Relay QoS service policy, use the modular QoS CLI (MQC) elements called class maps and policy maps. For more information, see the "Classifying Traffic Using a Class Map" section on page 2-11 and the "Creating a Policy Map" section on page 3-18.
After you create the policy map, you can attach it to a Frame Relay interface, point-to-point subinterface, data-link connection identifier (DLCI), or map class. You can apply a map class to an interface or subinterface.
Note The router does not support attaching a QoS service policy to a Frame Relay point-to-multipoint subinterface. You can attach a QoS service policy to either a Frame Relay subinterface, a Frame Relay DLCI, but not to both.
To attach a QoS service policy to a Frame Relay link, perform any of the following tasks:
•Attaching a QoS Service Policy to a Frame Relay Interface or Point-to-Point Subinterface
•Attaching a QoS Service Policy to a Frame Relay DLCI
Attaching a QoS Service Policy to a Frame Relay Interface or Point-to-Point Subinterface
To attach a QoS policy to a Frame Relay interface or point-to-point subinterface, perform either of the following tasks:
•Attaching a QoS Policy Directly to a Frame Relay Interface or Point-to-Point Subinterface
•Attaching a QoS Service Policy to a Frame Relay Interface or Point-to-Point Subinterface Using a Map Class
Note You cannot attach a QoS policy to the same Frame Relay interface or subinterface by using both the MQC and a map class. For releases earlier than Cisco IOS Release 12.0(22)S, use the Frame Relay commands to attach QoS policies (see Appendix A, "Configuring Frame Relay QoS Using Frame Relay Legacy Commands"). For Cisco IOS Release 12.0(22)S and later releases, use the MQC.
Attaching a QoS Policy Directly to a Frame Relay Interface or Point-to-Point Subinterface
To attach a QoS policy directly to a Frame Relay interface or point-to-point subinterface, enter the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# interface type
slot/subslot/port.subinterface
|
Specifies the interface or subinterface to which you want to attach the QoS service policy. Enters interface or subinterface configuration mode.
|
Step 2
|
Router(config-if)# service-policy {input
| output} policy-map-name
|
Applies the service policy you specify to the interface or subinterface.
input indicates to apply the service policy to the inbound traffic on the interface.
output indicates to apply the service policy to the outbound traffic on the interface.
Note For QoS policies containing the bandwidth, priority, random-detect, queue-limit, and shape commands, you must specify the output keyword. The router ignores these commands when you use them with the input keyword.
policy-map-name is the name of the policy map you want to attach to the interface.
Note The router applies the service policy to the aggregate of all of the data link connection identifies (DLCIs) configured on the interface or subinterface.
|
Configuration Examples for Attaching QoS Policies Directly to a Frame Relay Interface or Point-to-Point Subinterface
Example 4-5 shows how to attach the service policy named mypolicy2 to serial subinterface 1/0/0.1 in the inbound direction.
Example 4-5 Attaching a QoS Policy Directly to a Frame Relay Point-to-Point Subinterface
Router(config)# interface serial 1/0/0.1 point-to-point
Router(config-if)# service-policy input mypolicy2
Example 4-6 shows how to attach the service policy named silver to serial interface 4/0/0 in the inbound direction.
Example 4-6 Attaching a QoS Policy Directly to a Frame Relay Interface
Router(config)# interface serial 4/0/0
Router(config-if)# service-policy input silver
Attaching a QoS Service Policy to a Frame Relay Interface or Point-to-Point Subinterface Using a Map Class
To attach a QoS service policy to a Frame Relay interface or point-to-point subinterface using a Frame Relay map class, enter the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# map-class frame-relay
map-class-name
|
Specifies a map class and enters map-class configuration mode.
map-class-name identifies the map class.
|
Step 2
|
Router(config-map-c)# service-policy
[input | output] policy-map-name
|
Applies the service policy you specify to the map class.
input indicates to apply the service policy to the inbound traffic on the interface.
output indicates to apply the service policy to the outbound traffic on the interface.
Note For QoS policies containing the bandwidth, priority, random-detect, queue-limit, and shape commands, you must specify the output keyword. The router ignores these commands when you use them with the input keyword.
policy-map-name is the name of the policy map.
|
Step 3
|
Router(config-map-c)# exit
|
Exits map-class configuration mode.
|
Step 4
|
Router(config)# interface type
slot/subslot/port.subinterface
[point-to-point]
|
Specifies the interface or subinterface to which you want to attach the map class. Enters interface or subinterface configuration mode.
|
Step 5
|
Router(config-if)# frame-relay class name
|
Associates a map class with a Frame Relay subinterface.
name is the name of the map class you want to associate with the interface.
Note The router applies the service policy configured in the map class to the aggregate of all of the data link connection identifies (DLCIs) on the interface or subinterface.
|
Configuration Examples for Attaching a QoS Policy to a Frame Relay Interface or Point-to-Point Subinterface Using a Map Class
Example 4-7 shows how to configure a policy map named policy1 within a Frame Relay map class named VCs_slow and attach the map class to serial subinterface 1/0/0.1.
Example 4-7 Configuring a QoS Service Policy on a Frame Relay Subinterface Using a Map Class
Router(config)# map-class frame-relay VCs_slow
Router(config-map-c)# service-policy policy1
Router(config-map-c)# exit
Router(config)# interface serial 1/0/0.1 point-to-point
Router(config-if)# frame-relay class VCs-slow
Example 4-8 shows how to configure a policy map named bronze within a Frame Relay map class named slow-VCs and attach the map class to serial interface 2/0/0.
Example 4-8 Configuring a QoS Service Policy on a Frame Relay Interface Using a Map Class
Router(config)# map-class frame-relay slow-VCs
Router(config-map-c)# service-policy bronze
Router(config-map-c)# exit
Router(config)# interface serial 2/0/0
Router(config-if)# frame-relay class slow-VCs
Attaching a QoS Service Policy to a Frame Relay DLCI
To attach a QoS service policy to a Frame Relay DLCI, perform one of the following tasks:
•Attaching a QoS Service Policy Directly to a Frame Relay DLCI
•Attaching a QoS Service Policy to a Frame Relay DLCI Using a Map Class
Note You cannot attach a QoS policy to the same Frame Relay interface or subinterface by using both the MQC and a map class. For releases earlier than Cisco IOS Release 12.0(22)S, use the Frame Relay commands to attach QoS policies (see Appendix A, "Configuring Frame Relay QoS Using Frame Relay Legacy Commands"). For Cisco IOS Release 12.0(22)S and later releases, use the MQC.
Attaching a QoS Service Policy Directly to a Frame Relay DLCI
You can attach a QoS service policy to a Frame Relay DLCI that is configured on an interface or subinterface.
To attach a QoS service policy directly to a Frame Relay DLCI, enter the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# interface type
slot/subslot/port.subinterface
[point-to-point]
|
Specifies the interface or subinterface. Enters interface or subinterface configuration mode.
|
Step 2
|
Router(config-if)# frame-relay
interface-dlci dlci
|
Assigns a data link connection identifier (DLCI) to the Frame Relay interface or subinterface. Enters Frame Relay DLCI configuration mode.
dlci is a number that identifies the data link connection on the interface or subinterface.
|
Step 3
|
Router(config-fr-dlci)# service-policy
[input | output] policy-map-name
|
Attaches the service policy you specify to the individual DLCI.
input indicates to apply the service policy to inbound traffic on the interface.
output indicates to apply the service policy to outbound traffic on the interface.
Note For QoS policies containing the bandwidth, priority, random-detect, queue-limit, and shape commands, you must specify the output keyword. If you use these commands with the input keyword, the router ignores the commands.
policy-map-name is the name of the policy map.
Note The router applies the service policy only to the individual DLCI.
|
Configuration Examples for Attaching a QoS Service Policy Directly to a Frame Relay DLCI
Example 4-9 shows how to attach the service policy named user_policy to the data link connection identifier (DLCI) 100 on serial subinterface 1/0/0.1 for outbound packets.
Example 4-9 Attaching a QoS Service Policy Directly to a DLCI Configured on a Subinterface
Router(config)# interface serial 1/0/0.1 point-to-point
Router(config-if)# frame-relay interface-dlci 100
Router(config-fr-dlci)# service-policy output user_policy
Example 4-10 shows how to attach the service policy named voice to DLCI 201 on serial interface 4/0/0 for outbound packets.
Example 4-10 Attaching a QoS Service Policy Directly to a DLCI Configured on an Interface
Router(config)# interface serial 4/0/0
Router(config-if)# frame-relay interface-dlci 201
Router(config-fr-dlci)# service-policy output voice
Attaching a QoS Service Policy to a Frame Relay DLCI Using a Map Class
You can attach a map class with a QoS policy to a Frame Relay DLCI that is configured on an interface or subinterface.
To attach a QoS service policy to a Frame Relay DLCI using a map class, enter the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# map-class frame-relay
map-class-name
|
Specifies a map class and enters map-class configuration mode.
map-class-name identifies the map class.
|
Step 2
|
Router(config-map-c)# service-policy
[input | output] policy-map-name
|
Applies the service policy you specify to the map class.
input indicates to apply the service policy to inbound traffic on the interface.
output indicates to apply the service policy to outbound traffic on the interface.
Note For QoS policies containing the bandwidth, priority, random-detect, queue-limit, and shape commands, you must specify the output keyword. If you use these commands with the input keyword, the router ignores the commands.
policy-map-name is the name of the policy map.
|
Step 3
|
Router(config-map-c)# exit
|
Exits map-class configuration mode.
|
Step 4
|
Router(config)# interface type
slot/module/port.subinterface
[point-to-point]
|
Specifies an interface or subinterface. Enters interface or subinterface configuration mode.
|
Step 5
|
Router(config-if)# frame-relay
interface-dlci dlci
|
Assigns a data link connection identifier (DLCI) to the Frame Relay interface or subinterface. Enters Frame Relay DLCI configuration mode.
dlci is a number that identifies the data link connection on the interface or subinterface.
|
Step 6
|
Router(config-fr-dlci)# |
