Attaching A Traffic Policy To Multiple Subinterfaces; Prerequisites; Restrictions - Cisco ASR 9000 Series Configuration Manual

Aggregation services router modular quality of service
Hide thumbs Also See for ASR 9000 Series:
Table of Contents

Advertisement

How to Configure Modular QoS Packet Classification on Cisco ASR 9000 Series Routers
Command or Action
Step 4
end
or
commit
Example:
RP/0/RSP0/CPU0:router(config-if)# end
or
RP/0/RSP0/CPU0:router(config-if)# commit
Step 5
show policy-map interface type instance [input
| output]
Example:
RP/0/RSP0/CPU0:router# show policy-map
interface gigabitethernet 0/1/0/9

Attaching a Traffic Policy to Multiple Subinterfaces

After the traffic class and traffic policy are created, you can optionally use the service-policy (interface)
configuration command to attach a traffic policy to multiple subinterfaces, and to specify the direction
in which the policy should be applied (either on packets coming into or leaving the subinterface).
Note
A shared policy can include a combination of Level 2 and Level 3 interfaces.
For additional commands that can be entered in policy map class configuration mode, see the
Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Command Reference.

Prerequisites

A traffic class and traffic policy must be created before attaching a traffic policy to a subinterface.

Restrictions

Shared policy instance is not supported on bundle subinterfaces or bundle EFPs.
Shared policy instance across multiple physical interfaces is not supported.
Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide
QC-20
Configuring Modular Quality of Service Packet Classification on Cisco ASR 9000 Series Routers
D r a f t — C i s c o C o n f i d e n t i a l
Purpose
Saves configuration changes.
When you issue the end command, the system prompts
you to commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
Entering yes saves configuration changes to the
running configuration file, exits the configuration
session, and returns the router to EXEC mode.
Entering no exits the configuration session and
returns the router to EXEC mode without
committing the configuration changes.
Entering cancel leaves the router in the current
configuration session without exiting or
committing the configuration changes.
Use the commit command to save the configuration
changes to the running configuration file and remain within
the configuration session.
(Optional) Displays policy configuration information for all
classes configured for all service policies on the specified
interface.
OL-17239-01

Advertisement

Table of Contents
loading

Table of Contents