Cisco ASR 9000 Series Service Configuration Manual page 41

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

Advertisement

Configuring Modular QoS Service Packet Classification and Marking on Cisco ASR 9000 Series Routers
Command or Action
Step 3
service-policy {input | output} policy - map
[shared-policy-instance instance-name ]
Example:
RP/0/RSP0/CPU0:router(config-if)#
service-policy output policy1
shared-policy-instance Customer1
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 shared-policy-instance
instance-name [input | output] location
rack/slot/module
Example:
RP/0/RSP0/CPU0:router# show policy-map
shared-policy-instance Customer1 location
0/1/0/7.1
Attaching a Shared Policy Instance to Bundle Interfaces or EFP Bundles
After the traffic class and traffic policy are created, you can optionally use the service-policy (interface)
configuration command to attach a shared policy instance to bundle interfaces and to bundle EFPs, and
to specify the direction in which the policy should be applied (either on packets coming into or leaving
the subinterface).
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 shared policy instance to bundle
interfaces or EFP bundles.
OL-23108-02
How to Configure Modular QoS Packet Classification and Marking on Cisco ASR 9000 Series Routers
Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide
Purpose
Attaches a policy map to an input or output subinterface to
be used as the service policy for that subinterface.
In this example, the traffic policy evaluates all traffic
leaving that interface.
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 statistics for the policy on the specified
shared policy instance subinterface.
QC-27

Advertisement

Table of Contents
loading

Table of Contents