30-56
Cisco ME 3400 EthernetAccess Switch SoftwareConfiguration Guide
78-17058-01
Chapter30 Co nf iguring QoS
Configuration Examples for Policy Maps
Configuration Examples for Policy Maps
This section includes configuration examples for configuring QoS policies on the Cisco ME switch,
including configuration limitations and restrictions. The sections are broken into different configurati ons
actions that a customer might do. Each section provides the exact sequence of steps that you must follow
for successful configuration or modification.
These sections are included:
•QoS Configuration for Customer A, page 30-56
•QoS Configuration for Customer B, page 30-58
•Modifying Output Policies and Adding or Deleting Classification Criteria, page 30-5 9
•Modifying Output Policies and Changing Queuing or Scheduling Parameters, page 30-60
•Modifying Output Policies and Adding or Deleting Configured Actions , pa ge 30 -60
•Modifying Output Policies and Adding or Deleting a Class, page 3 0-61

QoS Configuration for Customer A

This section provides examples of the initial configuration and activation of QoS policies for a customer
switch. Input and output QoS service policies are configured based on the requirements and attached to
relevant ports.
In the initial configuration for Customer A, Fast Ethernet ports 1 through 24 are user network interfaces
(UNIs) and are disabled by default. Gigabit Ethernet ports 1 and 2 are networ k n ode i nterfa ce s (N NIs)
and are enabled by default.
This is the overall sequence for initial configuration:
•Configure classes and policies.
•Shut down all active ports.
•Attach policies to ports to be activated.
•Take the ports out of shut-down state.
•Leave unused ports shut down.
Note these restrictions for configuring output policies:
•You can define up to three classes in the output policy map.
•The defined classes must be the same as other output policy maps.
•The number of defined classes in each output policy map must be same.
•You must assign an action to each class; that is, there can be no empty class.
•Each class configuration must be based on the classification/marking done in the input policy-map.