-
Cisco 7600 Series Ethernet Services Plus (ES+) and Ethernet Services Plus T (ES+T) Line Card Configuration Guide
-
Preface
-
Overview of the Cisco 7600 Series Ethernet Services 40G Line Card
-
Configuring the Cisco 7600 Series Ethernet Services 40G Line Card
-
Configuring High Availability Features
-
Configuring Layer 1 and Layer 2 Features
-
Configuring Multicast Features
-
Configuring MPLS Features
-
Configuring QoS Features
-
Troubleshooting the Cisco 7600 Series Ethernet Service + Line Card
-
Upgrading Field-Programmable Devices
-
Configuring IPoDWDM
-
Configuring Automatic Laser Shutdown
-
Network Clocking on Cisco 7600 Series Ethernet Services Plus Line Cards
-
Configuring Layer 3 and Layer 4 Features
-
Table Of Contents
Configuring QoS Features Using MQC
Restrictions and Usage Guidelines
Restrictions and Usage Guidelines
Attaching a QoS Traffic Policy to an Interface
Attaching a QoS Traffic Policy for an Input Interface
Attaching a QoS Traffic Policy to an Output Interface
Restrictions and Usage Guidelines
Restrictions and Usage Guidelines
Configuring QoS Queue Scheduling
Restrictions and Usage Guidelines
WRED Aggregate and Non-Aggregate Mode
Restrictions and Usage Guidelines
Configuring Bandwidth and CBWFQ
Restrictions and Usage Guidelines
Restrictions and Usage Guidelines
Configuring Bandwidth Remaining Ratio (BRR)
Restrictions and Usage Guidelines
Configuring PFC QoS on a Cisco 7600 Series Ethernet Services Plus Line Card
PFC QoS on a Cisco 7600 Series Ethernet Services Plus Line Card Configuration Guidelines
Restrictions and Usage Guidelines
QoS on Port-Channel Member-Link
Supported Egress QoS Configurations
Restrictions and Usage Guidelines
QoS on Port-Channel Member-LinkConfiguration Examples
IPv6 - Hop by Hop Rate Limiter
Restrictions and Usage Guidelines
Configuring IPv6 - Hop by Hop Rate Limiter
QoS: Service Group Support on Cisco 7600
Restrictions and Usage Guidelines
Configuring Flexible Service Mapping Based on CoS and Ethertype
Restrictions and Usage Guidelines
Configuring QoS
This chapter provides information about configuring Quality of Service (QoS) on the Cisco 7600 Series Ethernet Services Plus (ES+) and Ethernet Services Plus T (ES+T) line card on the Cisco 7600 series router.
Note
QoS on the Cisco 7600 Series Ethernet Services Plus line cards uses Layer 2 frame size.
Note
For more information about the commands in this chapter, see the Cisco IOS Release 12.2 SR Command References at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122sr/cr/index.htm.
Before referring to any other QoS documentation for the platform or in the Cisco IOS software, use this chapter to determine Cisco 7600 Series Cisco 7600 Series ES+ line card-specific QoS feature support and configuration guidelines.
Note
For additional details about QoS concepts and features in Cisco IOS Release 12.2, you can refer to the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2SR, at http://www.cisco.com/en/US/docs/ios/qos/configuration/guide/12_2sr/qos_12_2sr_book.html.
This chapter includes the following sections:
•
•
•
•
•
•
•
Supported Interfaces
The Cisco 7600 Series ES+ line cards support QoS on the following interfaces:
•
•
•
•
•
•
•
•
Note
•
•
•
QoS Functions
The following sections describe ingress and egress QoS functions.
Ingress QoS Functions
The following paragraphs describe ingress QoS support on the Cisco 7600 Series ES+ line card.
Ingress Trust
Trust is a port assignment instructing the port to trust (leave) existing priorities as they are on incoming frames or to rewrite the priorities back to zero.
A packet can arrive at an interface with a priority value already present in the packets header. The router needs to determine if the priority setting was set by a valid application or network device according to pre defined rules or if it was set by a user hoping to get better service.
The router has to decide whether to honor the priority value or change it to another value. How the router makes this determination is by using the port "trust" setting.
The main Layer 3 interface and the Layer 3 subinterface always trust Differentiated Services Code Point (DSCP) by default. For switchport interfaces and service instances, the port is untrusted and EARL QoS is ignored.
To change the ingress type of service (ToS), use marking. For information on marking, see the "Configuring Marking" section.
Ingress Queue Scheduling
The Cisco 7600 Series ES+ line card supports ingress queue scheduling. For information on configuring ingress scheduling, see the "Configuring QoS Queue Scheduling" section.
Ingress Classification
Classification entails using a traffic descriptor to categorize a packet within a specific group to define that packet and make it accessible for QoS handling on the network. Using packet classification, you can partition network traffic into multiple priority levels or classes of service.
Traffic is classified to determine whether it should be:
•
•
The Cisco 7600 Series ES+ line card supports ingress classification. For information on configuring classification, see the "Configuring Classification" section.
Ingress Policing
Policing provides a means to limit the amount of bandwidth that traffic traveling through a given port, or a collection of ports in a VLAN, can use. Policing works by defining an amount of data that the router is willing to send or receive in kilobytes per second.
When policing is configured, it limits the flow of data through the router by dropping or marking down the QoS value traffic that is out-of-profiles. Policing allows the router to limit the rate of specific types to a level lower than what they might get otherwise based only the interface bandwidth.
The Cisco 7600 Series ES+ line card supports ingress policing. For information on configuring policing, see the "Configuring Policing" section.
Ingress Marking
After it has been classified, traffic can be marked. Marking is a way to selectively modify the classification bits in a packet to identify traffic within the network. Other interfaces can then match traffic based on the markings.
The Cisco 7600 Series ES+ line card supports ingress marking. For information on configuring marking, see the "Configuring Marking" section.
Ingress Bandwidth and CBWFQ
Ingress bandwidth allows you to specify or modify the bandwidth allocated for a class belonging to a policy-.map. Class-based weighted fair queueing (CBWFQ) extends the standard WFQ functionality to provide support for user-defined traffic classes. Ingress bandwidth and CBWFQ are supported on on main Layer 3 interface, Layer 3 subinterface, and service instances.
The Cisco 7600 Series ES+ line card supports ingress bandwidth and CBWFQ. For information, see the "Configuring Bandwidth and CBWFQ" section.
LLQ (Ingress Priority)
Low-Latency Queuing (LLQ) allows you to allocate bandwidth to the class maps in the policy map.
The Cisco 7600 Series ES+ line card supports LLQ. For information, see the "Configuring LLQ" section.
Ingress Shaping
The Cisco 7600 Series ES+ line card supports ingress shaping. The shape average command is supported in flat/H-QoS policy-maps in ingress on main Layer 3 interface, Layer 3 subinterface, and service instances. For more information, see the "Configuring Shaping" section.
Note
Egress QoS Functions
The following sections describe QoS functions on the Cisco 7600 Series ES+ line card egress ports.
Egress Classification
Classification entails using a traffic descriptor to categorize a packet within a specific group to define that packet and make it accessible for QoS handling on the network. Using packet classification, you can partition network traffic into multiple priority levels or classes of service.
Traffic is classified to determine whether it should be:
•
•
The Cisco 7600 Series ES+ line card supports egress classification. For information on configuring classification, see the "Configuring Classification" section.
Egress Policing
The Cisco 7600 Series ES+ line card supports egress port policing.
Egress Marking
After traffic has been classified, the router can mark it. You use marking to selectively modify the classification bits in the packet to differentiate packets based on the designated markings.
The Cisco 7600 Series ES+ line card supports egress port marking. For information on configuring marking, see the "Configuring Marking" section.
Egress Shaping
Traffic shaping allows you to control the traffic going out an interface in order to match its flow to the speed of the remote target interface and to ensure that the traffic conforms to policies contracted for it. You can use shaping to meet downstream requirements, thereby eliminating bottlenecks in topologies with data-rate mismatches.
The Cisco 7600 Series ES+ line card supports shaping on egress port, subinterfaces, and service instances. For information on configuring shaping, see the "Configuring Shaping" section.
Egress Queue Scheduling
The egress line card uses congestion avoidance to help prevent congestion and keep its buffers from overflowing.
The Cisco 7600 Series ES+ line card supports Class-based Weighted Fair Queuing (CBWFQ), Low Latency Queueing (LLQ), and Weighted Random Early Detection (WRED). For information on configuring egress scheduling, see the "Configuring QoS Queue Scheduling" section.
Configuring QoS Features Using MQC
The Modular QoS CLI (MQC) is a CLI structure that allows users to create traffic policies and attach these policies to interfaces. A traffic policy contains a traffic class and one or more QoS features. A traffic class is used to select traffic, while the QoS features in the traffic policy determine how to treat the classified traffic.
To configure QoS features using the Modular QoS CLI on the Cisco 7600 Series ES+ line card, complete the following basic steps:
Step 1
Step 2
Step 3
For a complete discussion about MQC, refer to the "Modular Quality of Service Command-Line Interface Overview" section of the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.3 publication at:
http://www.cisco.com/en/US/docs/ios/12_3/featlist/qos_vcg.html
Configuring Classification
Use the QoS classification features to select your network traffic and categorize it into classes for further QoS processing based on matching certain criteria. The default class, named "class-default," is the class to which any traffic that does not match any of the selection criteria in the configured class maps is directed.
Restrictions and Usage Guidelines
Table 7-1 provides information about which QoS classification features are supported for the Cisco 7600 Series ES+ line card on the Cisco 7600 series router. For more information about most of the commands documented in this table, refer to the Cisco IOS Quality of Service Solutions Command Reference.
Table 7-1 QoS Classification Feature Support
Match on access list (ACL) number (match access-group command)
Input and output for the following interfaces:
•
•
•
•
•
•
Match on Class of Service (CoS) (match cos command)
Input and output for the following interfaces:
•
•
•
•
•
•
•
•
Match on inner CoS (match cos inner command)
Input and output for the following interfaces:
•
•
Match on input VLAN (match input vlan command)
Output for the following interfaces:
•
Note
Match on IP DSCP (match ip dscp command)
Input and output for the following interfaces:
•
•
•
•
•
•
•
Match on IP precedence (match ip precedence command)
Input and output for the following interfaces:
•
•
•
•
•
•
•
Match on MPLS experimental (EXP) bit (match mpls experimental command)
Input and output for the following interfaces:
•
•
•
•
•
•
Match on VLAN
(match vlan command—Matches the outer VLAN of a Layer 2 IEEE 802.1Q frame)
Input and output for the following interfaces:
•
•
•
•
•
•
Match on VLAN Inner
(match vlan inner command—Matches the innermost VLAN of the 802.1Q tag in the Layer 2 frame)
Input and output for the following interfaces:
•
•
•
•
Match on source-address MAC
match source-address mac command—Matches the source MAC address.
Input and output for the following interfaces:
•
•
•
1 Only classified based on source MAC address using Layer 2 ACL.
2 To match subinterface/EVC traffic and policy map applied on the main interface.
3 Cisco 7600 Series ES+ line cards support classification on SVI only for EoMPLS and VPLS.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Step 1
enable
Example:Router# enableEnables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
class-map [match-all | match-any] class-map-name
Example:Router(config)# class-map match-all acl9 (id 1049)
Creates a traffic class, where:
•
•
•
Note
Step 4
match type
Example:Router(config-cmap)# match ip precedence 5
Specifies the matching criterion to be applied to the traffic, where type represents one of the forms of the match command supported by the Cisco 7600 Series ES+ line card as shown in Table 7-1.
Note
Examples
This example shows how to configure a class map named ipp5, and enter a match statement for IP precedence 5:
Router# enableRouter# configure terminalRouter(config)# class-map ipp5Router(config-cmap)# match ip precedence 5Router(config-cmap)#This is an example of configuring class matching on multiple match statements.
Router# enableRouter# configure terminalRouter(config)# class-map match-any many (id 1047)Router(config-cmap)# match ip precedence 3Router(config-cmap)# match access-group 100Router(config-cmap)# match mpls experimental 5This is an example of configuring class matching on named ACLS.
Router# enableRouter# configure terminalRouter(config)# class-map match-all acl9 (id 1049)Router(config-cmap)# match access-group name rockThis example shows a logical AND operation in a child policy with match vlan and class-default in a parent.
Router# enableRouter# configure terminalRouter(config)# class-map match-all childANDRouter(config-cmap)# match vlan inner 2-3Router(config-cmap)# match cos inner 5 6Router(config)# policy-map testchildANDRouter(config-pmap)# class childANDRouter(config-pmap-c)# shape average 100000000Router(config)# policy-map parentANDRouter(config-pmap)# class vlan12Router(config-pmap-c)# shape average 500000000Router(config-pmap-c)# service-policy testchildAND
This example shows how to display class-map information for a specific class map using the show class-map command:
Router# show class-map ipp5Class Map match-all ipp5 (id 1)Match ip precedence 5
This example shows how to display class map information matching on extended ACLs using the show class-map command.
Router# show class-map acl5Class Map match-all acl5 (id 1042)Match access-group 102This example shows how to verify classification on a VLAN in the parent class of a H-QoS policy.
head# show policy-map matchPolicy Map matchClass vlan11shape average 2000000 8000 8000service-policy match4Class vlan12shape average 2000000 8000 8000service-policy match4Class vlansshape average 500000000 2000000 2000000service-policy match2Configuring Policing
The Cisco 7600 Series ES+ line cards support the following features:
•
•
•
–
–
–
–
•
–
•
•
•
•
•
•
Policing is supported at the input and output for the following interfaces:
•
•
•
•
•
•
•
Micro-flow policing is supported at the input for the following interfaces:
•
•
•
Restrictions and Usage Guidelines
When configuring policing, follow these restrictions and usage guidelines:
•
•
•
Note
•
•
•
–
–
•
•
•
–
–
–
Table 7-2 provides information about which policing features are supported for the Cisco 7600 Series ES+ line card on the Cisco 7600 series routers.
SUMMARY STEPS
1.
2.
3.
4.
5.
or
police cir percent % conform-action action exceed-action action
or
police cir bps value pir bps value conform-action action exceed-action action violate-action action
or
police cir percent % pir percent % conform-action action exceed-action action violate-action action
DETAILED STEPS
Step 1
enable
Example:Router# enableEnables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
policy-map policy-map-name
Example:Router(config)# policy-map policy-map-test
Creates or modifies a traffic policy and enters policy map configuration mode, where:
•
Step 4
class {class-name | class-default}
Example:Router (config-pmap)# class acgroup2
Specifies the name of the traffic class to which this policy applies and enters policy-map class configuration mode, where:
•
•
Step 5
police bps-value conform-action action exceed-action action
Example:Router(config-pmap-c)# police 5000000 conform-action drop exceed-action set-dscp-transmit
Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm, where:
•
•
Or
police cir percent % conform-action action exceed-action action
Example:Router(config-pmap-c)# police cir percent 20 conform-action transmit exceed-action set-prec-transmit 1
Configures traffic policing on the basis of a percentage of bandwidth available on an interface, where:
•
•
•
•
Or
police cir bps-value pir bps-value conform-action action exceed-action action violate-action action
Example:Router(config-pmap-c)# police cir 1000000 pir 2000000 conform-action set-cos-transmit 3 exceed-action set-cos-transmit 1 violate-action drop
Configures traffic policing using two rates, the CIR and the peak information rate (PIR), where:
•
•
•
•
Or
police cir percent % pir percent % conform-action action exceed-action action violate-action action
Example:Router(config-pmap-c)# police cir percent 20 pir percent 40 conform-action transmit exceed-action set-prec-transmit 1 violate-action drop
Configures traffic policing using two rates, the CIR and the PIR, where:
•
•
•
•
•
Examples
In the following example, all actions are configured in separate lines.
Router# (config)# policy-map ABCRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# police 10000000 8000 8000Router(config-pmap-c-police)# conform-action set-cos-transmit 2Router(config-pmap-c-police)# exceed-action set-cos-transmit 1Router(config-pmap-c-police)# endRouter#Router# show policy-map ABCPolicy Map ABCClass class-defaultpolice cir 10000000 bc 8000 be 8000conform-action set-cos-transmit 2exceed-action set-cos-transmit 1Router#This example configures a 1 rate 2-color policer:
Router(config)# policy-map 1r2cRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# police 2000000Router(config-pmap-c-police)# conform-action transmitRouter(config-pmap-c-police)# exceed-action dropRouter(config-pmap-c-police)# endRouter# show policy-map 1r2cPolicy Map 1r2cClass class-defaultpolice cir 2000000 bc 62500conform-action transmitexceed-action dropRouter#This example configures a 1 rate 2-color policer with percent:
Router(config)# policy-map 1r2c_percentRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# police cir percent 20Router(config-pmap-c-police)# conform-action set-cos-transmit 0Router(config-pmap-c-police)# exceed-action dropRouter(config-pmap-c-police)# endRouter#Router# show policy-map 1r2c_percentPolicy Map 1r2c_percentClass class-defaultpolice cir percent 20conform-action set-cos-transmit 0exceed-action dropRouter#This example configures a 2 rate 3-color policer:
Router(config)# policy-map 2r3cRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# police cir 2000000 pir 3000000Router(config-pmap-c-police)# conform-action set-prec-transmit 3Router(config-pmap-c-police)# exceed-action set-prec-transmit 2Router(config-pmap-c-police)# violate-action set-prec-transmit 1Router(config-pmap-c-police)# endRouter#Router# show policy-map 2r3cPolicy Map 2r3cClass class-defaultpolice cir 2000000 bc 62500 pir 3000000 be 93750conform-action set-prec-transmit 3exceed-action set-prec-transmit 2violate-action set-prec-transmit 1Router#This example configures a 2 rate 3-color policer with percent:
Router(config)# policy-map 2r3c_percentRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# police cir percent 10 pir percent 20Router(config-pmap-c-police)# conform-action transmitRouter(config-pmap-c-police)# exceed-action set-cos-transmit 0Router(config-pmap-c-police)# violate-action dropRouter(config-pmap-c-police)# endRouter#Router# show policy-map 2r3c_percentPolicy Map 2r3c_percentClass class-defaultpolice cir percent 10 pir percent 20conform-action transmitexceed-action set-cos-transmit 0violate-action dropRouter#This example configures a single rate two color policer in class-default with a CIR of 64 Kbps, a conform action of transmit and an exceed action of drop with as small a Bc as possible:
Router# enableRouter# configure terminalRouter(config)# policy-map policeRouter(config-pmap)# class test8Router(config-pmap-c)# police 64000 2000This example configures a single rate two color policer in class-default and a child policy with policing:
Router# enableRouter# configure terminalRouter(config)# policy-map police5Router(config-pmap)# class test18Router(config-pmap-c)# service policy child-levelRouter(config-pmap-c)# police cir 64000 50The following example shows a 2R3C configuration in a class and policy map:
Router# enableRouter# configure terminalRouter(config)# policy-map testRouter(config-pmap)# class cos2Router(config-pmap-c)# police 1000000 pir 2000000 conform-action set-cos-transmit 3 exceed-action set-cos-transmit 1 violate-action drop
The following example configures a dual rate three color policer in class-default with a CIR of 64 Kbps, and PIR doubled the CIR rate, a conform action of transmit, and an exceed action mark dscp af11 and violate mark dscp cs1 with default setting on Bc.
Router# enableRouter# configure terminalRouter(config)# policy-Map qos_testRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# police cir 64000 bc 2000 pir 128000 be 2000 conform-action transmit exceed-action set-dscp-transmit af11 violate-action set-dscp-transmit cs1The following example configures a dual rate three color policer in class-default.
Router# enableRouter# configure terminalRouter(config)# policy-map testRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# police cir percent 20 pir percent 40 conform-action transmit exceed-action set-prec-transmit 1 violate-action dropVerification
Use the following commands to verify policing:
This example shows how to display policing statistics using the show policy-map interface command in the EXEC mode.
Router# show policy-map interfaceTenGigabitEthernet3/1service-policy output: xclass-map: a (match-all)0 packets, 0 bytes5 minute rate 0 bpsmatch: ip precedence 0police:1000000 bps, 10000 limit, 10000 extended limitconformed 0 packets, 0 bytes; action: transmitexceeded 0 packets, 0 bytes; action: dropconformed 0 bps, exceed 0 bps, violate 0 bps
This is another example of displaying policing statistics using the show policy-map interface command; in this case the statistics are for a one rate 2 color per EVC policer.
Router# show policy-map interface ten 4/1 service instance 1
TenGigabitEthernet4/1: EFP 1
Service-policy input: evc_ingress
Counters last updated 00:00:00 ago
Class-map: class-default (match-any)
72077 packets, 36903424 bytes
5 minute offered rate 981000 bps, drop rate 440000 bps
Match: any
police:
cir 10000000 bps, bc 8000 bytes
conformed 87426 packets, 44762112 bytes; actions:
transmit
exceeded 85974 packets, 44018688 bytes; actions:
drop
conformed 556000 bps, exceed 448000 bps
Attaching a QoS Traffic Policy to an Interface
Before a traffic policy can be enabled for a class of traffic, it must be configured on an interface. A traffic policy also can be attached to Ethernet subinterfaces, main interfaces, and service instances.
Traffic policies can be applied for traffic coming into an interface (input), and for traffic leaving that interface (output).
Attaching a QoS Traffic Policy for an Input Interface
When you attach a traffic policy to an input interface, the policy is applied to traffic coming into that interface. To attach a traffic policy for an input interface, use the following command beginning in interface configuration mode:
Attaching a QoS Traffic Policy to an Output Interface
When you attach a traffic policy to an output interface, the policy is applied to traffic leaving that interface. To attach a traffic policy to an output interface, use the following command beginning in interface configuration mode:
Configuring Marking
After you have created your traffic classes, you can configure traffic policies to configure marking features to apply certain actions to the selected traffic in those classes.
In most cases, the purpose of a packet mark is identification. After a packet is marked, downstream devices identify traffic based on the marking and categorize the traffic according to network needs. This categorization occurs when the match commands in the traffic class are configured to identify the packets by the mark (for example, match ip precedence, match ip dscp, match cos, and so on). The traffic policy using this traffic class can then set the appropriate QoS features for the marked traffic.
In some cases, the markings can be used for purposes besides identification. Distributed WRED, for instance, can use the IP precedence, IP DSCP, or MPLS EXP values to detect and drop packets.
Restrictions and Usage Guidelines
When configuring class-based marking on an Cisco 7600 Series ES+ line card, follow these restrictions and usage guidelines:
•
•
•
•
•
Table 7-3 provides information about which QoS class-based marking features are supported for the Cisco 7600 Series ES+ line card on the Cisco 7600 series router.
Table 7-3 QoS Class-Based Marking Feature Support
Set IP DSCP
(set ip dscp command—Marks the IP differentiated services code point (DSCP) in the type of service (ToS) byte with a value from 0 to 63.)
Input and output for the following interfaces:
•
•
•
•
•
•
Set IP precedence
(set ip precedence command—Marks the precedence value in the IP header with a value from 0 to 7.)
Input and output for the following interfaces:
•
•
•
•
•
•
Set Layer 2 IEEE 802.1Q CoS
(set cos command—Marks the CoS value from 0 to 7 in an 802.1Q tagged frame.)
Input and output for the following interfaces:
•
•
•
•
•
•
•
Set Layer 2 802.1Q CoS
(set cos-inner command—Marks the inner CoS field from 0 to 7 in a bridged frame.)
Input and output for the following interfaces:
•
•
•
Set Layer 2 802.1Q CoS
(set cos-inner cos command—Copies out CoS to inner CoS.)
Input and output for the following interfaces:
•
•
•
Set Layer 2 802.1Q CoS
(set cos cos-inner command)
Input and output for the following interfaces:
•
•
•
Set MPLS experimental (EXP) bit on label imposition
(set mpls experimental imposition command)
Input for the following interfaces:
•
•
•
•
•
Set MPLS EXP topmost
(set mpls experimental topmost command)
Input and output for the following interfaces:
•
•
•
1 To match subinterface/EVC traffic and policy map applied on the main interface.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS:
Step 1
enable
Example:Router# enableEnables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
policy-map policy-map-name
Example:Router(config)# policy-map policymap3
Creates or modifies a traffic policy and enters policy map configuration mode, where:
•
Step 4
class {class-name | class-default}
Example:Router(config-pmap)# class class1
Specifies the name of the traffic class to which this policy applies and enters policy-map class configuration mode, where:
•
•
Step 5
set type
Example:Router(config-pmap-c)# set ip precedence2
Specifies the marking action to be applied to the traffic, where type represents one of the forms of the set command supported by the Cisco 7600 Series ES+ line card as shown in Table 7-3.
Examples
This example shows the creation of a service policy called policy1. This service policy is associated to a previously defined classification policy through the use of the class command. This example assumes that a classification policy called class1 was previously configured.
Router# enableRouter# configure terminalRouter(config)# policy-map policy1Router(config-pmap)# class class1Router(config-pmap-c)# set ip precedence 1This example configures marking to set the imposed MPLS EXP bits to 1:
Router# enableRouter# configure terminalRouter(config)# policy-map testRouter(config-pmap)# class testRouter(config-pmap-c)# set mpls experimental imposition 1This example configures marking to set the inner cos value:
Router# enableRouter# configure terminalRouter(config)# policy-map testRouter(config-pmap)# class testRouter(config-pmap-c)# set cos inner 1This example configures marking to set the imposed MPLS EXP bits to 1:
Router# enableRouter# configure terminalRouter(config)# policy-map testRouter(config-pmap)# class testRouter(config-pmap-c)# set mpls experimental topmost 1Verification
Use the following commands to verify marking:
For more detailed information about configuring class-based marking features, refer to the Class-Based Marking document located at the following URL:
http://www.cisco.com/en/US/docs/ios/12_1t/12_1t5/feature/guide/cbpmark2.html
Configuring Shaping
This section describes information for configuring QoS traffic policies for shaping traffic. Shaping is the process of delaying packets in queues to make them conform to a specified profile.
Restrictions and Usage Guidelines
When configuring shaping on an Cisco 7600 Series ES+ line card, follow these restrictions and usage guidelines:
•
•
•
•
•
•
•
–
–
•
–
•
–
–
–
–
•
For more detailed information about configuring congestion management features, refer to the Cisco IOS Quality of Service Solutions Configuration Guide document corresponding to your Cisco IOS software release.
Table 7-4 provides information about which QoS traffic shaping features are supported for the Cisco 7600 Series ES+ line card on the Cisco 7600 series router.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Examples
This example shows traffic shaping on a main interface; traffic leaving interface gi1/1 is shaped at the rate of 10 Mbps:
Router# enableRouter# configure terminalRouter(config)# class-map class-interface-allRouter(config-cmap)# match ip precedence 2Router(config-cmap)# exitRouter(config)# policy-map dts-interface-all-actionRouter(config-pmap)# class class-interface-allRouter(config-pmap-c)# shape average 10000000Router(config-pmap-c)# exitRouter(config)# interface gi1/1Router(config-if)# service-policy output dts-interface-all-action
This is an example of an output shaping policy on a switchport interface that matches on a CoS value queuing defined in the classes.
Router# enableRouter# configure terminalRouter(config)# policy-map switchport-cos-policyRouter(config-pmap)# class cos1Router(config-pmap-c)# shape ave 100000000Now the policy is applied in the egress direction on the main switchport.
Router# enableRouter# configure terminalRouter(config)# interface TenGigabitEthernet9/1Router(config-if)# switchportRouter(config-if)# switchport access vlan 2000Router(config-if)# switchport mode accessRouter(config-if)# service-policy output switchport-cos-policyIn this example, shape is applied at the parent level of an HQoS policy-map.
Router# enableRouter# configure terminalRouter(config)# policy-map child2Router(config-pmap)# class prec5Router(config-pmap-c)# shape average 100000000Router(config)# policy-map pcdRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 300000000Router(config-if)# service-policy child2This example configures a shaping policy in default-class with WRED:
Router# enableRouter# configure terminalRouter(config)# policy Map qos_testRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape ave 100MbpsRouter(config-pmap-c)# random-detect dscp-based aggregateVerification
Use the following commands to verify traffic shaping:
Configuring QoS Queue Scheduling
This section describes Cisco 7600 Series ES+ line card-specific information for configuring QoS queue scheduling.
Restrictions and Usage Guidelines
When configuring queueing features on an Cisco 7600 Series ES+ line card, follow these restrictions and usage guidelines:
•
–
–
–
•
•
•
•
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
For more detailed information about configuring congestion management features, refer to the Cisco IOS Quality of Service Solutions Configuration Guide document corresponding to your Cisco IOS software release.
Configuring WRED
Weighted RED (WRED) generally drops packets selectively based on IP precedence. Packets with a higher IP precedence are less likely to be dropped than packets with a lower precedence. WRED is supported on the output of the following interfaces:
•
•
•
•
•
•
WRED Aggregate and Non-Aggregate Mode
WRED Aggregate mode and Non-Aggregate modes define how the hardware resources are internally used to provide the WRED behavior. On an ES+linecard, there are 8 WRED curves. In a WRED Non-Aggregate mode, a single CoS value maps to one WRED curve and in a WRED Aggregate mode, multiple dscp values are mapped to one WRED curve.
For more information on this, see https://www.cisco.com/en/US/docs/ios/qos/command/reference/qos_q1.html#wp1053666
The set of subclass (DSCP precedence) values defined on a random-detect dscp (aggregate) CLI will be aggregated into a single hardware WRED resource. The statistics for these subclasses will also be aggregated.
Restrictions and Usage Guidelines
When configuring WRED on Cisco 7600 Series ES+ line cards, follow these restrictions and usage guidelines:
•
–
–
–
•
–
–
–
•
•
•
•
•
•
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Examples
This is an example of a WRED configuration.
Router# enableRouter# configure terminalRouter(config)# policy-map wredtestRouter(config-pmap)# class cos5Router(config-pmap-c)# shape average 200000000Router(config-pmap-c)# random-detect dscp-based aggregateRouter(config-pmap-c)# random-detect dscp values 0 min 100 max 200 mark-prob 1Router(config-pmap-c)# random-detect dscp values 1 min 300 max 500 mark-prob 1Router(config-pmap-c)# random-detect dscp values 2 min 600 max 900 mark-prob 1The following example configures a class-map which matches IPP=1, 3, 5 and 7, and configures a WRED policy that is applied to the egress interface:
Router# enableRouter# configure terminalRouter(config)# policy-map wredRouter(config-pmap)# class IPP1Router(config-pmap-c)# shape average 100000000Router(config-pmap-c)# random-detect precedence-basedRouter(config-pmap)# class IPP3Router(config-pmap-c)# shape average 100000000Router(config-pmap-c)# random-detect precedence-basedRouter(config-pmap)# class IPP5Router(config-pmap-c)# shape average 100000000Router(config-pmap-c)# random-detect precedence-basedRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 100000000Router(config-pmap-c)# random-detect precedence-basedThe following example show the output of the show policy map interface command (transmit packets are not displayed).
Router# enableRouter# configure terminalRouter# show policy-map int gig 11/1 service instance 1GigabitEthernet11/1: EFP 1Service-policy output: temp_parentCounters last updated 00:00:00 agoClass-map: class-default (match-any)139358 packets, 71351296 bytes5 minute offered rate 1745000 bps, drop rate 283000 bpsMatch: anyQueueingqueue limit 2048 packets(queue depth/total drops/no-buffer drops) 0/104062/0(pkts output/bytes output) 35296/18071552shape (average) cir 10000000, bc 40000, be 40000target shape rate 10000000Service-policy : tempCounters last updated 00:00:00 agoClass-map: class-default (match-any)139358 packets, 71351296 bytes5 minute offered rate 1745000 bps, drop rate 1304000 bpsMatch: anyqueue limit 2048 packets(queue depth/total drops/no-buffer drops) 0/104062/0(pkts output/bytes output) 35296/18071552Exp-weight-constant: 9 (1/512)Mean queue depth: 0 packetsclass Random drop Tail drop Minimum Maximum Markpkts/bytes pkts/bytes thresh thresh probConfiguring Bandwidth and CBWFQ
Class-based weighted fair queueing (CBWFQ) extends the standard WFQ functionality to provide support for user-defined traffic classes. For CBWFQ, you define traffic classes based on match criteria including protocols and access control lists (ACLs).
Bandwidth is supported on the output of the following interfaces:
•
•
•
•
•
•
Note
Restrictions and Usage Guidelines
When configuring Bandwidth and CBWFQ on Cisco 7600 Series ES+ line cards, follow these restrictions and usage guidelines:
•
•
•
•
•
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Examples
This example shows a service policy called policy1 that specifies the amount of bandwidth to allocate for traffic classes 1 and 2:
Router# enableRouter# configure terminalRouter(config)# class-map class1 Router(config-cmap)# match ip dscp 30Router(config-cmap)# exitRouter(config)# class-map class2 Router(config-cmap)# match ip dscp 10Router(config-cmap)# exit
Router(config)# policy-map policy1Router(config-pmap)# class class1Router(config-pmap-c)# bandwidth 30000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config-pmap)# class class2Router(config-pmap-c)# bandwidth 20000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)#
Router(config)# interface gigabit ethernet 2/1 Router(config-if)# service-policy output policy1Router(config-if)# exitThe following example configures a QoS policy with multiple user class with rate guarantee setting using the bandwidth command.
Router(config)# policy-map policy1Router(config)# Class c1Router(config-pmap-c)# Bandwidth percent 1%Router(config-pmap)# Class c2Router(config-pmap-c)# Bandwidth percent 10%Router(config-pmap)# Class c3Router(config-pmap-c)# Bandwidth percent 88%Router(config-pmap)# Class class-defaultRouter(config-pmap-c)# Bandwidth 1%The following example configures a QoS policy with multiple user class with rate guarantee setting:
Router# enableRouter# configure terminalRouter(config)# Policy Map parent_policyRouter(config-pmap)# class-defaultRouter(config-pmap-c)# shape average 20000000Router(config-pmap-c)# bandwidth remaining ratio 5Router(config-pmap-c)# service-policy child_policyRouter(config)# policy-map child_policyRouter(config-pmap)# class videoRouter(config-pmap-c)# priorityRouter(config-pmap-c)# police 10000000Router(config-pmap)# class criticalRouter(config-pmap-c)# bandwidth remaining percent 80Router(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining percent 20Use the following commands to verify CBWFQ:
Configuring LLQ
Low-Latency Queuing (LLQ) uses the priority command to allocate bandwidth to the class maps in the policy map.
LLQ is supported on the output of the following interfaces:
•
•
•
•
•
•
Restrictions and Usage Guidelines
When configuring LLQ on Cisco 7600 Series ES+ line cards, follow these restrictions and usage guidelines:
•
–
–
–
–
–
–
•
–
–
–
–
–
–
SUMMARY STEPS
1.
2.
3.
4.
5.
or
police cir percent % conform-action action exceed-action action
or
police cir bps-value pir bps-value conform-action action exceed-action action violate-action action
or
police cir percent % pir percent % conform-action action exceed-action action violate-action action
6.
or
priority level
DETAILED STEPS
Step 1
enable
Example:Router# enableEnables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
policy-map policy-name
Example:Router(config)# policy-map silver
Specifies the name of the policy map to configure.
Step 4
class {class-name | class-default}
Example:Router(config-pmap)# class classcos0Specifies the name of a predefined class included in the service policy.
Step 5
police bps-value conform-action action exceed-action action
Example:Router(config-pmap-c)# police 5000000 conform-action set-dscp-transmit 0 exceed-action drop
Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm, where:
•
•
Or
police cir percent % conform-action action exceed-action action
Example:Router(config-pmap-c)# police cir percent 20 conform-action transmit exceed-action set-prec-transmit 1
Configures traffic policing on the basis of a percentage of bandwidth available on an interface, where:
•
•
•
•
Or
police cir bps-value pir bps-value conform-action action exceed-action action violate-action action
Example:Router(config-pmap-c)# police cir 1000000 pir 2000000 conform-action set-cos-transmit 3 exceed-action set-cos-transmit 1 violate-action drop
Configures traffic policing using two rates, the CIR and the PIR, where:
•
•
•
•
Or
police cir percent % pir percent % conform-action action exceed-action action violate-action action
Example:Router(config-pmap-c)# police cir percent 20 pir percent 40 conform-action transmit exceed-action set-prec-transmit 1 violate-action drop
Configures traffic policing using two rates, the CIR and the PIR, where:
•
•
•
•
•
Step 6
priority
Example:Router(config-pmap-c)# priorityGives strict priority to a class of traffic belonging to the policy map.
Or
priority level
Example:Router(config-pmap-c)# priority level 1
Gives priority level to a class of traffic belonging to the policy map.
Examples
The following example configures an output LLQ policy on a switchport interface that matches on a CoS value queuing defined in the classes.
Router# enableRouter# configure terminalRouter(config)# policy map switchport-llq-policyRouter(config-pmap)# class cos0Router(config-pmap-c)# police 500000000Router(config-pmap-c)# priorityNow the policy is applied to the interface.
Router# enableRouter# configure terminalRouter(config)# interface TenGigabitEthernet9/1Router(config-if)# switchportRouter(config-if)# switchport access vlan 2000Router(config-if)# switchport mode accessRouter(config-if)# service-policy output switchport-llq-policyThe following example configures a simple LLQ QoS policy on a class c1 with strict priority setting.
Router# enableRouter# configure terminalRouter(config)# Policy Map qos_llqRouter(config-pmap)# Class c1Router(config-pmap-c)# police 500000000Router(config-pmap-c)# priorityThe following example configures an LLQ policy with multiple priority classes with a smallest percent value and default burst value for testing:
Router# enableRouter# configure terminalRouter(config-pmap)# Class-map VoiceRouter(config-pmap-c)# police cir percent 10Router(config-pmap-c)# PriorityRouter(config-pmap)# Class-map VideoRouter(config-pmap-c)# Police cir percent 20Router(config-pmap-c)# PriorityRouter(config-pmap)# Class-defaultConfiguring DBUS CoS Queing
This feature allows you to configure which DBUS CoS values are mapped to the high-priority queue. The hw-module slot slot queue priority switch-fpga output cos values|none command is used on the Routing Processor (RP) to configure the priority values. You can change the priority by changing the CoS values. The system allows you to configure eight class-of-service values . The default CoS values are 5,6, and 7.
Configuring Bandwidth Remaining Ratio (BRR)
Bandwidth Remaining Ratio (BRR) specifies the ratio that bandwidth is split between users when the link is congested (oversubscribed). This feature allows the link rate to be prorated out to logical interfaces such as EVCs and L3 subinterfaces. This feature is needed by the user since it provides the ability to oversubscribe the shape rate so logical interfaces can utilize unused bandwidth of other logical interfaces.
BRR is implemented on logical interfaces using hierarchical policy-maps.
Restrictions and Usage Guidelines
When configuring BRR on the Cisco 7600 Series ES+ line card, follow these restrictions and usage guidelines:
•
•
•
•
•
•
•
•
•
•
–
–
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Examples
In the following configuration, three policy-maps are applied in egress on three service instances. If gold, silver, and bronze service instances send their full quota of 300, 300, and 100 Mbps of priority traffic, then because PRP/service propagtion is ON, the remaining (1 Gbps - 700 Mbps) 300 Mbps of link bandwidth is shared between users in the ratio 1 : 2 : 3 where:
User A gets : 1 / (1+2+3) * 300 Mbps = 50 Mbps of non-LLQ traffic
User B gets : 2 / (1+2+3) * 300 Mbps = 100 Mbps of non-LLQ traffic
User C gets : 3 / (1+2+3) * 300 Mbps = 150 Mbps of non-LLQ traffic
Router# enableRouter# configure terminalRouter(config)# policy-map data_gold_child_outRouter(config-pmap)# class videoRouter(config-pmap-c)# priorityRouter(config-pmap-c)# police 300000000Router(config-pmap-c)# set cos 4Router(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 300000000Router(config-pmap-c)# set cos 3Router(config)# policy-map data_gold_parent_outRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 500000000Router(config-pmap-c)# bandwidth remaining ratio 3Router(config-pmap-c)# service-policy data_gold_child_outRouter(config)# policy-map data_silver_child_outRouter(config-pmap)# class videoRouter(config-pmap-c)# priorityRouter(config-pmap-c)# police 300000000Router(config-pmap-c)# set cos 4Router(config-pmap)# class gamingRouter(config-pmap-c)# bandwidth remaining ratio 2Router(config-pmap-c)# set cos 2Router(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining ratio 1Router(config-pmap-c)# set cos 1Router(config)# policy-map data_silver_parent_outRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 500000000Router(config-pmap-c)# bandwidth remaining ratio 2Router(config-pmap-c)# service-policy data_silver_child_outRouter(config)# policy-map data_bronze_child_outRouter(config-pmap)# class videoRouter(config-pmap-c)# priorityRouter(config-pmap-c)# police 100000000Router(config-pmap-c)# set cos 4Router(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 300000000Router(config-pmap-c)# set cos 1Router(config)# policy-map data_bronze_parent_outRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 500000000Router(config-pmap-c)# bandwidth remaining ratio 1Router(config-pmap-c)# service-policy data_bronze_child_outConfiguring PFC QoS on a Cisco 7600 Series Ethernet Services Plus Line Card
The Cisco 7600 Series ES+ line card supports most of the same QoS features as those supported by the Policy Feature Card (PFC) on the Cisco 7600 series routers.
This section describes those QoS features that have Cisco 7600 Series ES+ line card-specific configuration guidelines. After you review the Cisco 7600 Series ES+ line card-specific guidelines described in this document, then refer to the Cisco 7600 Series Router Cisco IOS Software Configuration Guide, Release 12.2SR located at the following URL:
http://www.cisco.com/en/US/docs/routers/7600/ios/12.2SR/configuration/guide/qos.html
PFC QoS on a Cisco 7600 Series Ethernet Services Plus Line Card Configuration Guidelines
The Cisco 7600 Series ES+ line card supports Policy Feature Card (PFC) QoS for SVI interfaces only in the case of ingress cos-to-exp marking.
Configuring Hierarchical QoS
The Cisco 7600 Series ES+ line cards support hierarchical QoS (H-QoS) that you configure using Cisco Modular QoS CLI (MQC). The following H-QoS capabilities are supported:
•
•
•
Note
•
•
•
•
•
•
•
•
•
–
–
–
–
•
–
–
–
–
–
–
In IOS hierarchical levels are represented as follows and current support is up to five levels:
•
•
•
•
•
A policy map with two levels has three levels of hierarchy when attached on the main interface, and four levels of hierarchy when attached on a subinterface.
A policy map with three levels has four levels of hierarchy when attached on the main interface, and five levels of hierarchy when attached on a subinterface.
On the ingress, three level H-QOS is supported (port, parent, child).
Table 7-5 provides information about supported H-QoS features.
Examples
This example configures the child policy to allocate different percentages of bandwidth by class:
!Router# enableRouter# configure terminalRouter(config)# policy-map childRouter(config-pmap)# class User-ARouter(config-pmap-c)# bandwidth percent 40Router(config-pmap-c)# exitRouter(config-pmap)# class User-BRouter(config-pmap-c)# bandwidth percent 60Router(config-pmap-c)# exitRouter(config-pmap)# exit!This example applies the parent service policy to an output subinterface:
!Router# enableRouter# configure terminalRouter(config)# interface TenGigabitEthernet 2/1.1Router(config-if-srv)# encapsulation dot1q 11Router(config-if)# service-policy output parentThis example shows how to configure a 2 level H-QoS policy on a main interface:
Router(config)# policy-map child_1Router(config-pmap)# class prec1Router(config-pmap-c)# priority level 1Router(config-pmap)# class prec2Router(config-pmap-c)# priority level 1 2Router(config-pmap)# class class-defaultRouter(config-pmap-c)# Police 100kbps!Router(config)# policy-map HQoS_parentRouter(config-pmap)# class class-defaultouter(config-pmap-c)# shape average 100000000Router(config-pmap-c)# service-policy child_1This example shows how to configure a 2 level H-QoS policy on an EVC interface:
Router(config)# policy-map child_1Router(config-pmap)# class cos1Router(config-pmap-c)# priority level 1Router(config-pmap)# class cos 2Router(config-pmap-c)# priority 2Router(config-pmap)# class class-defaultRouter(config-pmap-c)# Police 100kbps!Router(config)# policy-map HQoS_parentRouter(config-pmap)# class class-defaultouter(config-pmap-c)# shape average 100000000Router(config-pmap-c)# service-policy child_1This example configures an ingress 3-level H-QOS policy on a main-interface:
Router(config)# policy-map child_1Router(config-pmap)# class prec123Router(config-pmap-c)# random-detect precedence basedRouter(config-pmap)# class prec456Router(config-pmap-c)# shape average 10MRouter(config-pmap)# class class-default!Router(config)# policy-map HQoS_parentRouter(config-pmap)# class ACL_c1Router(config-pmap-c)# Police 100kbpsRouter(config-pmap-c)# priority 1Router(config-pmap-c)# service policy child_1Router(config-pmap)# class ACL_c2Router(config-pmap-c)# Police 100kbpsRouter(config-pmap-c)# priority level 2Router(config-pmap-c)# service policy child_2Router(config-pmap)# class class-defaultRouter(config-pmap-c)# Police 100kbpsRouter(config-pmap-c)# service policy child_3!Router(config)# policy-map HQos_grandparentRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape 100000000Router(config-pmap-c)# service-policy HQoS_parentThis example configures an egress 3 level H-QOS policy on a main-interface:
Router(config)# policy-map child_1Router(config-pmap)# class prec123Router(config-pmap-c)# random-detect precedence basedRouter(config-pmap)# class prec456Router(config-pmap-c)# shape average 10MRouter(config-pmap)# class class-default!Router(config)# policy-map HQoS_parentRouter(config-pmap)# class ACL_c1Router(config-pmap-c)# Police 100kbpsRouter(config-pmap-c)# priority level 1Router(config-pmap-c)# service policy child_1Router(config-pmap)# class ACL_c2Router(config-pmap-c)# Police 100kbpsRouter(config-pmap-c)# priority level 2Router(config-pmap-c)# service policy child_2Router(config-pmap)# class class-defaultRouter(config-pmap-c)# service policy child_3!Router(config)# policy-map HQos_grandparentRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape 100000000Router(config-pmap-c)# service-policy HQoS_parent!EVCS QoS Support
Ethernet Virtual Connection Services (EVCS) uses the concepts of service instances and EVCs (Ethernet virtual circuits). A service instance is the instantiation of an EVC on a given port on a given router. An EVC is an end-to-end representation of a single instance of a Layer 2 service being offered by a provider to a customer. It embodies the different parameters on which the service is being offered.
EVC QoS works with the following EVC combinations:
•
•
•
•
•
•
•
•
•
For information on how to configure EVC QoS, refer to the following sections to see how service instances and port channel service instances are handled:
•
Restrictions and Usage Guidelines
When configuring QoS with EVCS on the Cisco 7600 Series ES+ line card, follow these restrictions and usage guidelines:
•
•
•
•
•
•
•
•
•
•
–
–
–
–
–
•
EVC Configuration Examples
This example shows ingress QOS on scalable EoMPLS.
Router# enableRouter# configure terminalRouter(config)# interface GE 1/2Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 100Router(config-if-srv)# rewrite ingress tag pop 1 symmetricRouter(config-if)# xconnect 2.2.2.2 100 pw-class vlan-xconnectRouter(config-pmap-c)# service-policy input mark-it-inRouter(config)# policy-map mark-it-inRouter(config-pmap)# class cos0Router(config-pmap-c)# policeRouter(config-pmap-c)# set mpls exp imposition 5In this example of a single tag VLAN configuration, because the encapsulation dot1q 10 is already classified, only the inner VLAN and CoS values are configured.
Router# enableRouter# configure terminalRouter(config)# interface GE 1/2Router(config-if)# service instance 1Router(config-if-srv)# encapsulation dot1q 10 second-dot1q anyRouter(config-if-srv)# rewrite ingress tag pop 1 symmetricRouter(config-if-srv)# bridge domain 200Router(config-pmap-c)# service-policy input mark-it-inRouter(config)# policy-map mark-it-inRouter(config-pmap)# class innervlan20Router(config-pmap-c)# police 100000000Router(config-pmap-c)# set cos 0Router(config-pmap-c)# set cos-inner 0This is an example of a single tag VLAN connect ingress policy.
Router# enableRouter# configure terminalRouter(config)# interface GigabitEthernet1/1Router(config-if)# service instance 100 ethernetRouter(config-if-srv)# encapsulation dot1q 10 second-dot1q anyRouter(config-if-srv)# rewrite ingress tag pop 1 symmetricRouter(config-pmap-c)# service-policy in mark-it-inRouter(config)# interface GigabitEthernet 1/2Router(config-if)# service instance 101 ethernetRouter(config-if-srv)# encapsulation dot1q 11 second-dot1q anyRouter(config-if-srv)# rewrite ingress tag pop 1 symmetricRouter(config-pmap-c)# service-policy in mark-it-inRouter(config-if-srv)# connect EVC1 GigabitEthernet 1/1 100 GigabitEthernet 1/2 101Router(config)# policy-map mark-it-inRouter(config-pmap)# class vlaninner20cosinner5Router(config-pmap-c)# set cos 0This is an example of an egress double tag VLAN connect hierarchical configuration.Router# enableRouter# configure terminalRouter(config)# interface GigabitEthernet 1/1Router(config-if)# service instance 100 ethernetRouter(config-if-srv)# encapsulation dot1q 10 second-dot1q 20Router(config-if-srv)# rewrite ingress tag pop 2 symmetricRouter(config-pmap-c)# service-policy out parent-out-100Router(config)# interface GigabitEthernet 1/2Router(config-if)# service instance 101 ethernetRouter(config-if-srv)# encapsulation dot1q 11 second-dot1q 21Router(config-if-srv)# rewrite ingress tag pop 2 symmetricRouter(config-pmap-c)# service-policy out parent-out-101Router(config-if-srv)# connect EVC1 GigabitEthernet 1/1 100 GigabitEthernet 1/2 101Router(config)# policy-map child-out-100Router(config-pmap)# class cos5Router(config-pmap-c)# bandwidth percent 10Router(config-pmap-c)# set cos 0Router(config-pmap-c)# set cos-inner 0Router(config)# policy-map parent-out-100Router(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 10000000Router(config-pmap-c)# service-policy child-out-100Router(config)# policy-map child-out-101Router(config-pmap)# class cos0Router(config-pmap-c)# bandwidth percent 10Router(config-pmap-c)# set cos 5Router(config-pmap-c)# set cos-inner 5Router(config)# policy-map parent-out-101Router(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 10000000Router(config-pmap-c)# service-policy child-out-101This is an example of an egress double tag VLAN connect flat configuration.Router# enableRouter# configure terminalRouter(config)# policy-map flat-100Router(config-pmap)# class cos5Router(config-pmap-c)# shape average 10000000Router(config-pmap-c)# set cos 0Router(config-pmap-c)# set cos-inner 0Router(config-pmap)# class class-default <-- required classRouter(config-pmap-c)# shape average 10000000 <-- required queuing actionRouter(config-pmap-c)# set cos 6Router(config)# policy-map flat-101Router(config-pmap)# class cos0Router(config-pmap-c)# shape average 10000000Router(config-pmap-c)# set cos 5Router(config-pmap-c)# set cos-inner 5Router(config-pmap)# class class-default <-- required classRouter(config-pmap-c)# shape average 10000000 <-- required queuing actionRouter(config-pmap-c)# set cos 4QoS on Port-Channel Member-Link
The QoS on Port-Channel Member-Link feature provides support for service-policies on the following:
•
When a policy map attached to a port-channel main interface, ingress or egress traffic coming from any member link should be subjected to port-channel main interface QoS. When a policy map attached to member link interface, ingress or egress traffic from that member link should be subject to either QoS attached to EVC or subinterface configured under port-channel or QoS attached to member link.
Supported Egress QoS Configurations
Table 7-6 lists the QoS configurations supported on ingress and egress.
Restrictions and Usage Guidelines
When configuring the QoS on Port-Channel Member-Link feature on the Cisco 7600 Series ES+ line card, follow these restrictions and usage guidelines:
•
•
If the port-channel subinterface or port-channel service instance has its own policy, traffic is subjected to the policy applied on that port-channel subinterface or port-channel service instance.
It is not recommended to configure member link policy on the ingress if there is a micro-flow policing policy configured on the port-channel main interface or port-channel subinterface. If a member link policy and a micro-flow policing policy exist together, traffic is subjected to both policies, first by the member link policy on the Trident and then the micro-flow policing policy on the PFC.
Having Layer 3 port-channel member links with user defined classes in the parent introduces an additional queuing hierarchy. The member link policy will use half of the interface bandwidth and the remaining policies (port channel service instance policies) will get the remaining half of the interface bandwidth.
To protect and guarantee the port channel service instance bandwidth, the member link policy should have a grand-parent class-default with shape configured to restrict the maximum interface bandwidth given to non port-channel service instance traffic (if there is more than one class at the parent level in the member link policy).
QoS on Port-Channel Member-LinkConfiguration Examples
The following example illustrates one way of configuring the service-policy under a router port-channel Layer 3 member link.
Router# enableRouter# configure terminalRouter(config)# interface Port-channel 1Router(config-if)# ip addressRouter(config-if)# mpls ipRouter(config)# interface gi1/0Router(config-if)# channel-group 1Router(config-if)# service-policy output port-qosRouter(config)# interface gi1/1Router(config-if)# channel-group 1Router(config-if)# service-policy output port-qosThe following example includes a bandwidth remaining ratio:
Router# enableRouter# configure terminalRouter(config)# policy-map port-qosRouter(config-pmap)# class cos0 >>>match on cos 0Router(config-pmap-c)# police cir 100000000Router(config-pmap-c)# priorityRouter(config-pmap)# class cos1Router(config-pmap-c)# bandwidth remaining ratio 2Router(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining ratio 1The following are four examples of Layer 3 service policies:
Router# enableRouter# configure terminalRouter(config)# policy-map port-qosRouter(config-pmap)# class prec1 >>>match on ip prec 1Router(config-pmap-c)# police cir 100000000Router(config-pmap-c)# priorityRouter(config-pmap)# class prec2Router(config-pmap-c)# bandwidth 100000Router(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 100000000Router(config-pmap-c)# random-detect aggregateRouter(config-pmap-c)# random-detect precedence values 3 minimum-thresh 40 maximum-thresh 60 mark-prob 1Router(config-pmap-c)# random-detect precedence values 4 minimum-thresh 70 maximum-thresh 90 mark-prob 1Router(config-pmap-c)# random-detect precedence values 5 minimum-thresh 100 maximum-thresh 120 mark-prob 1:
Router# enableRouter# configure terminalRouter(config)# policy-map port-qosRouter(config-pmap)# class exp1 >>>match on exp 1Router(config-pmap-c)# police cir 100000000Router(config-pmap-c)# priorityRouter(config-pmap)# class exp2Router(config-pmap-c)# bandwidth 100000Router(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 100000000Router# enableRouter# configure terminalRouter(config)# policy-map port-qosRouter(config-pmap)# class ip-exp1 >>>match on ip prec1, or exp 1Router(config-pmap-c)# police cir 100000000Router(config-pmap-c)# priorityRouter(config-pmap)# class ip-exp22Router(config-pmap-c)# bandwidth 100000Router(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 100000000Router# enableRouter# configure terminalRouter(config)# policy-map port-qosRouter(config-pmap)# class exp1 >>>match on exp 1Router(config-pmap-c)# police cir 100000000Router(config-pmap-c)# priorityRouter(config-pmap)# class exp2Router(config-pmap-c)# bandwidth remaining ratio 5Router(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining ratio 2The folowing example shows the flat service-policies that can be configured under member-links:
Router# enableRouter# configure terminalRouter(config)# policy-map port-qosRouter(config-pmap)# class vlan11 >>>match on vlan 11Router(config-pmap-c)# police cir 100000000Router(config-pmap-c)# priorityRouter(config-pmap)# class vlan12Router(config-pmap-c)# bandwidth 100000Router(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 100000000.
The following examples shows the H-QoS policy that can be configured under member-links:
Router# enableRouter# configure terminalRouter(config)# policy-map childRouter(config-pmap)# class prec0 >>>match on prec 0Router(config-pmap-c)# police cir 100000000Router(config-pmap-c)# priorityRouter(config-pmap)# class prec1Router(config-pmap-c)# bandwidth 100000Router(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 100000000Router(config)# policy-map parentRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 300000000Router(config-pmap-c)# shape average 300000000Router(config-if)# service-policy child
Note
Router# enableRouter# configure terminalRouter(config)# policy-map childRouter(config-pmap)# class cos0 >>>match on cos 0Router(config-pmap-c)# police cir 100000000Router(config-pmap-c)# priorityRouter(config-pmap)# class cos1Router(config-pmap-c)# bandwidth 100000Router(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 100000000Router(config)# policy-map parentRouter(config-pmap)# class vlan11Router(config-pmap-c)# shape average 300000000Router(config-if)# service-policy childRouter(config-pmap)# class vlan12Router(config-pmap-c)# shape average 300000000Router(config-if)# service-policy childRouter(config-pmap)# class class-defaultThe following examples show service-policy combination on various interfaces.
The first example shows an egress service-policy attached to a port-channel member-link. There is no service-policy on the port-channel service instance.
Router# enableRouter# configure terminalRouter(config)# interface Port-channel 1Router(config-if)# ip addressRouter(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 100Router(config-if-srv)# bridge-domain 200Router(config-if)# service instance 2 ethernetRouter(config-if-srv)# encapsulation dot1q 101Router(config-if-srv)# bridge-domain 200interface gi1/0Router(config-if)# channel-group 1Router(config-if)# service-policy output port-qosRouter(config)# interface gi1/1Router(config-if)# channel-group 1Router(config-if)# service-policy output port-qosIn the next example, an egress service-policy is attached toa port-channel member-link. An egress and an ingress service-policy are applied on the port-channel service instance.
Router# enableRouter# configure terminalRouter(config)# interface Port-channel 1Router(config-if)# ip addressRouter(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 100Router(config-if-srv)# bridge-domain 200Router(config-if)# service-policy output evc-egressRouter(config-if)# service-policy input evc-ingressRouter(config-if)# service instance 2 ethernetRouter(config-if-srv)# encapsulation dot1q 101Router(config-if-srv)# bridge-domain 200Router(config-if)# service-policy output evc-egressRouter(config-if)# service-policy input evc-ingressRouter(config)# interface gi1/0Router(config-if)# channel-group 1Router(config-if)# service-policy output port-qosRouter(config)# interface gi1/1Router(config-if)# channel-group 1Router(config-if)# service-policy output port-qosIn the following example, an egress service-policy is attached to a port-channel member-link. An egress and an ingress service-policy are applied on the port-channel service instance. An ingress service-policy is applied on the port-channel subinterface.
Router# enableRouter# configure terminalRouter(config)# interface Port-channel 1Router(config-if)# ip addressRouter(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 100Router(config-if-srv)# bridge-domain 200Router(config-if)# service-policy output evc-egressRouter(config-if)# service-policy input evc-ingressRouter(config-if)# service instance 2 ethernetRouter(config-if-srv)# encapsulation dot1q 101Router(config-if-srv)# bridge-domain 200Router(config-if)# service-policy output evc-egressRouter(config-if)# service-policy input evc-ingressRouter(config)# interface Port-channel 1.1Router(config-if-srv)# encapsulation dot1q 1000Router(config-if)# service-policy input subint-ingressRouter(config)# interface gi1/0Router(config-if)# channel-group 1Router(config-if)# service-policy output port-qosRouter(config)# interface gi1/1Router(config-if)# channel-group 1Router(config-if)# service-policy output port-qosIPv6 - Hop by Hop Rate Limiter
The IPv6 Hop-by-Hop (HBH) extension header is part of the original specification of the IPv6 protocol (RFC 2460). It is identified by header type 0 and when present, this extension header must always be the first extension header (EH) to follow the main header. Because a node must process any received packet that has an HBH extension header, forwarding of packets containing the HBH header can represent or be used as a security threat.
The IPv6 - Hop by Hop Rate Limiter feature provides protection from Denial of Service (DoS) attacks by allowing you to rate limit IPv6 HBH packets.
Restrictions and Usage Guidelines
When rate limiting IPv6 HBH packets on the Cisco 7600 Series ES+ line card, follow these restrictions and usage guidelines:
•
–
–
–
–
•
•
•
Configuring IPv6 - Hop by Hop Rate Limiter
To connect to a specific line card for the purpose of executing the test platform police set command or the test platform police get command, use the attach command in privileged EXEC mode.
You can then set the IPv6 internal police rate by using the test platform police set command in privileged EXEC mode from the line card console:
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Example
This example shows how to set the rate.
Console# attach 3
Trying Switch ...
Entering CONSOLE for Switch
Type "^C^C^C" to end this session
osr3-dfc3#
Router-dfc3# enable
Router-dfc3# test platform police ipv6 set 1234
You can then obtain IPv6 internal police rate by using the test platform police get command in privileged EXEC mode from the line card console:
Router-dfc3# test platform police ipv6 getIPv6 with HBH header is policed at 100000 kbps
QoS: Service Group Support on Cisco 7600
A service group is a logical entity that allows you to add the capability to group existing different interface types (service instance, sub-interface, ISG session) and apply features on this aggregate logical entity. You can use a service group to apply QoS policy on a aggregate basis for a number of services encompassed under the service group.
You can create a service group for each subscriber. An ingress policing and an egress hierarchical (H-QoS) policy can be configured at the group level. A number of service instances are added as members of the group. Consequently, the group service policies are applied to the members. The aggregate policy on this group should co-exist with the existing policies on the individual members.
The members of these service groups can be EFPs only.
In addition other restrictions imposed by other modules QoS requires that due to the current hardware design. Also the membership is rejected if there is conflict between a member level policy and the group level policy.
You can create service group only on EVCs; service groups cannot be created on sessions and sub-interfaces.
Restrictions and Usage Guidelines
When configuring EVC Group 7600 Support, follow these restrictions and guidelines:
•
–
–
–
–
–
–
–
–
–
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Summary Steps
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Examples
This example configures a service group and configures an output service policy.
Router(config)# service-group 1Router(config-service-group)# service-policy output p<1-3>Router(config)# service-group 2Router(config-service-group)# service-policy output p<4-6>This example creates an EFP member with and/or without service-policy add it to the newly created service-group and configure a 3-level service policy.
Router(config)# interface gigabitethernet 1/1Router(config-if)# service instance 101 ethernetRouter(config-if-srv)# group 1Router(config-service-group)# service-policy output p4 | p5Verification
Use the following commands to verify operation.
Configuring Flexible Service Mapping Based on CoS and Ethertype
The Flexible Serivce Mapping based on CoS and Etherytpe feature enhances the current capability of mapping packets to service instance by allowing you to use CoS and Ethertypes to classify traffic into different service instances, thereby consuming a lesser number of VLANs on the module.
This feature adds the following capabilities for mapping to service instances:
•
•
•
•
–
–
–
•
•
•
•
Restrictions and Usage Guidelines
When configuring Flexible Service Mapping based on CoS and Ethertype, follow these restrictions and guidelines:
•
•
•
•
•
•
•
•
•
•
Summary Steps
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Supported Configurations
The following are the supported Ethertype and CoS configurations:
•
Router(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q vlan_id etype etype string•
Router(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q vlan id second-dot1q vlan id etype etype string•
Router(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 10 etype ipv4Router(config-if-srv)# exitRouter(config-if)# service instance 2 ethernetRouter(config-if-srv)# encapsulation dot1q 10 etype ipv6Router(config-if-srv)# exitRouter(config-if)# service instance 3 ethernetRouter(config-if-srv)# encapsulation dot1q 10 etype pppoe-all•
Router(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 11-15 etype ipv4Router(config-if-srv)# exitRouter(config-if)# service instance 2 ethernetRouter(config-if-srv)# encapsulation dot1q 11-15 etype ipv6Router(config-if-srv)# exitRouter(config-if)# service instance 3 ethernetRouter(config-if-srv)# encapsulation dot1q 11-15 etype pppoe-all•
Router(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 10 second-dot1q 1001 etype ipv4Router(config-if-srv)# exitRouter(config-if)# service instance 2 ethernetRouter(config-if-srv)# encapsulation dot1q 10 second-dot1q 1001 etype ipv6Router(config-if-srv)# exitRouter(config-if)# service instance 3 ethernetRouter(config-if-srv)# encapsulation dot1q 10 second-dot1q 1001 etype pppoe-all•
Router(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 10 second-dot1q 11-15 etype ipv4Router(config-if-srv)# exitRouter(config-if-srv)# encapsulation dot1q 10 second-dot1q 11-15 etype ipv6Router(config-if-srv)# exitRouter(config-if-srv)# encapsulation dot1q 10 second-dot1q 11-15 etype pppoe-all•
Router(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q single vlan_id cos single cos valueRouter(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q single vlan_id cos list/range of cos valuesRouter(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q list/range of vlan ids cos single cos value•
Router(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q single vlan _id second-dot1q single vlan id cos single cos valueRouter(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q single vlan_id second-dot1q single vlan_id cos list/range of cos_valuesRouter(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q single vlan_id second-dot1q list/range of vlan_ids cos single cos_valueRouter(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q single vlan_id cos single cos_value second-dot1q single vlan_idRouter(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q single vlan_id cos list/range of cos_values second-dot1q single vlan idRouter(config)# interface gigabitethernet 1/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q single vlan_id cos single cos_value second-dot1q list/range of vlan_idsExamples
The following example displays EVCs with encap dot1q and CoS under bridge-domain.
Router# conf tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface gigabitethernet 3/1Router(config-if)# no shutRouter(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 100 cos 5Router(config-if-srv)# bridge-domain 202Router(config-if-srv)# interface gigabitethernet 3/2Router(config-if)# no shutRouter(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 100 cos 5Router(config-if-srv)# bridge-domain 202Router(config-if-srv)# endRouter#Router#Router# show bridge-domain 202Bridge-domain 202 (2 ports in all)State: UP Mac learning: EnabledGigabitEthernet3/1 service instance 1GigabitEthernet3/2 service instance 1The following example shows EVC with encap dot1q and ethertype ipv4 with bridge-domain.
Router(config)# interface gigabitethernet 3/1Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 100 etype ipv4Router(config-if-srv)# bridge-domain 202Router(config-if-srv)# interface gigabitethernet 3/2Router(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 100 etype ipv4Router(config-if-srv)# bridge-domain 202Router(config-if-srv)#Router(config-if-srv)# endRouter#Router#Router# show bridge-domain 202Bridge-domain 202 (2 ports in all)State: UP Mac learning: EnabledGigabitEthernet3/1 service instance 1GigabitEthernet3/2 service instance 1The following is an example of local connect.
Router(config)# interface TenGigabitEthernet2/3Router(config-if)# no ip addressRouter(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 2 second-dot1q 2-3 cos 5Router(config)# interface TenGigabitEthernet2/4Router(config-if)# no ip addressRouter(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 2 second-dot1q 2-3 cos 5Router(config-if-srv)# connect local1 te2/3 1 te2/4 1The following is an example of xconnect.
Router(config)# interface TenGigabitEthernet2/3Router(config-if)# no ip addressRouter(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 2 second-dot1q 2-3 cos 5Router(config-if-srv)# xconnect 75.1.1.5 10000 encapsulation mpls!Router(config-if-srv)# endThe peer side router configuration is below:
Router(config)# interface GigabitEthernet3/0/14Router(config-if)# no ip addressRouter(config-if)# service instance 1 ethernetRouter(config-if-srv)# encapsulation dot1q 2 second-dot1q 2-3 cos 5Router(config-if-srv)# xconnect 75.1.1.1 10000 encapsulation mpls!Router(config-if-srv)# endVerification
Use the following commands to verify operation.
