Quality of Service

This chapter describes the EOS Quality of Service (QoS) implementation, including configuration instructions and command descriptions. Topics covered by this chapter include the following:

Quality of Service Conceptual Overview

QoS processes apply to traffic that flows through Ethernet ports and control planes. These processes can modify data fields (CoS or DSCP) or assign data streams to traffic classes for prioritized handling. Transmission queues are configurable for individual Ethernet ports to shape traffic based on its traffic class. Many switches also support traffic policies that apply to data that is filtered by access control lists.

The following sections describe QoS features:

Identifying the Switch Platform

QoS configuration varies significantly by switch platform. A list of Arista switch model numbers and their corresponding switch platforms (chipsets) can be found in the Chipset Mapping for QoS.

On some switches, the platform can also be determined by entering platform ? in the CLI.

 

Example

This command shows that the example switch is running on the Trident platform. 
switch(config)# platform ?
  trident  Trident chip
switch(config)#

 

QoS Data Fields and Traffic Classes

Quality of Service (QoS) defines a method of differentiating data streams to provide varying levels of service to the different streams.

Criteria determining a packet’s priority level include packet field contents and the port where data packets are received. QoS settings are translated into traffic classes, which are then used by switches to manage all traffic flows. Traffic flow management varies with each switch platform.

QoS Data Fields

Quality of service decisions are based on the contents of the following packet fields:
  • CoS (three bits): Class of service (CoS) is a 3-bit field in Ethernet frame headers using VLAN tagging. The field specifies a priority value between zero and seven. Class of service operates at Layer 2.

     

  • DSCP (six bits): Differentiated Service Code Point (DSCP) is a 6-bit field in the Type Of Service (TOS) field of IP packet headers.

     

Port Settings – Trust Mode and Traffic Class

Ethernet and port channel interfaces support three QoS trust modes:
  • CoS Trust: Ports use inbound packet CoS field contents to derive the traffic class.

     

  • DSCP Trust: Ports use inbound packets DSCP field contents to derive the traffic class.

     

  • Untrusted: Ports use their default values to derive the traffic class, ignoring packet contents.

     

The default mode setting is CoS trust for switched ports and DSCP trust for routed ports.

Ports are associated with default CoS, DSCP, and traffic class settings; defaults vary by platform.

These sections describe procedures for configuring port settings:

Rewriting CoS and DSCP

CoS Rewrite

Switches can rewrite the CoS field for outbound tagged packets. The new CoS value is configurable, and is derived from a data stream’s traffic class as specified by the traffic class-to-CoS rewrite map. CoS rewrite is disabled on all the traffic received on CoS trusted ports.

On Arad, Jericho, FM6000, Trident and Tomahawk, Trident II, and Helix platform switches, CoS rewrite can be enabled or disabled on DSCP trusted ports and untrusted ports.
  • CoS rewrite is globally enabled by default for packets received on untrusted ports and DSCP trusted ports if at least one port is explicitly configured in DSCP trust or untrusted mode.

     

  • CoS rewrite is globally disabled by default for packets received on untrusted ports and DSCP trusted ports if there are no ports explicitly configured in DSCP trust or untrusted mode.

     

On Petra platform switches, CoS rewrite is always enabled on DSCP trusted ports and untrusted ports.

DSCP Rewrite

Switches can rewrite the DSCP field for outbound IP packets. On FM6000, Trident and Tomahawk, Trident II, and Helix platform switches, DSCP rewrite is disabled by default on all ports and always disabled for traffic received on DSCP trusted ports. On Petra, Arad, and Jericho platform switches, DSCP rewrite is always disabled.

FM6000, Trident and Tomahawk, Trident II, and Helix platform switches provide a command that enables or disables DSCP rewrite for packets received on CoS trusted ports and untrusted ports. The new DSCP value is configurable, based on the data stream’s traffic class, as specified by the traffic class-to-DSCP rewrite map.

These sections describe procedures for rewriting CoS and DSCP fields:

Traffic Classes

Data stream distribution is based on their traffic classes. Data stream management varies by switch platform. Traffic classes are derived from these data stream, inbound port, and switch attributes:
  • CoS field contents.
  • DSCP field contents.
  • Inbound port trust setting.
  • CoS default setting (Arad, Jericho, FM6000, Trident and Tomahawk, Trident II, and Helix platform switches).
  • DSCP default setting (Arad, Jericho, FM6000, Trident and Tomahawk, and Trident II platform switches).
  • Traffic class default setting (Petra platform switches).

     

When a port is configured to derive a data stream’s traffic class from the CoS or DSCP value associated with the stream, the traffic class is determined from a conversion map.
  • A CoS-to-traffic class map derives a traffic class from a CoS value.
  • A DSCP-to-traffic class map derives a traffic class from a DSCP value.

     

Map entries are configurable through CLI commands. Default maps determine the traffic class value when CLI map entry commands are not configured. Default maps vary by switch platform.

These sections describe traffic class configuration procedures:

Transmit Queues and Port Shaping

Transmit queues are logical partitions of an Ethernet port’s egress bandwidth. Data streams are assigned to queues based on their traffic class, then sent as scheduled by port and transmit settings. Support varies by switch platform. A queue’s label determines its priority: queues with the suffix 0 have the lowest priority.

Parameters that determine transmission schedules include:
  • Traffic class-to-transmit queue mapping determines the transmit queue for transmitting data streams based on traffic class. The set of available transmit maps vary by switch platforms:
    • Arad, Jericho, FM6000, Trident II, and Helix platforms: one map for all unicast and multicast traffic.
    • Trident and Tomahawk platform: one map for unicast traffic and one map for multicast traffic.
    • Petra platform: one map for unicast traffic. Queue shaping is not available for multicast traffic.

       

  • Port shaping specifies a port’s maximum egress bandwidth.
  • Queue shaping specifies a transmit queue’s maximum egress bandwidth, and implementation varies by platform.
    • Trident and Tomahawk platform: queue shaping is configurable separately for unicast and multicast queues.
    • Trident II platform: queue shaping is configurable for transmit queues. Port shaping and queue shaping are supported only in store-and-forward switching mode.
    • Petra platform: queue shaping is not available for multicast traffic.
    • Helix platform: queue shaping is configurable for transmit queues.
    • FM6000 platform: switches do not support simultaneous port shaping and queue shaping. Enabling port shaping on an FM6000 switch disables queue shaping, regardless of the previous configuration.

       

  • Guaranteed bandwidth guarantees the allocation of a specified bandwidth for a transmit queue. Guaranteed bandwidth is supported only on Trident II platforms.

     

  • Queue priority specifies the priority at which a transmit queue is serviced. The switch defines two queue priority types:
    • Strict priority queues are serviced in the order of their priority rank - subject to each queue’s configured maximum bandwidth. Data is not handled for a queue until all queues with higher priority are emptied or their transmission limit is reached. These queues typically carry low latency real time traffic and require highest available priority.
    • Round robin queues are serviced simultaneously subject to assigned bandwidth percentage and configured maximum bandwidth. All round robin queues have lower priority than strict priority queues. Round robin queues can be starved by strict priority queues.

       

  • Queue scheduling determines how packets from different transmit queues are serviced to be sent out on the port.

     

  • Queue bandwidth allocation specifies the time slice (percentage) assigned to a round robin queue, relative to all other round robin queues.

     

These sections describe transmit queue and port shaping configuration procedures:

Explicit Congestion Notification (ECN)

Explicit Congestion Notification (ECN) is an IP and TCP extension that facilitates end-to-end network congestion notification without dropping packets. ECN recognizes early congestion and sets flags that signal affected hosts. Trident and Tomahawk, Trident II, and Helix platform switches extend ECN support to non-TCP packets.

ECN usage requires that it is supported and enabled by both endpoints. Although only unicast flows are modified by ECN markers, the multicast, broadcast, and unmarked unicast flows can affect network congestion and influence the indication of unicast packet congestion.

ECN Conceptual Overview

The ECN field in the IP header (bits 6 and 7 in the IPv4 TOS or IPv6 traffic class octet) advertises ECN capabilities:
  • 00: Router does not support ECN.
  • 10: Router supports ECN.
  • 01: Router supports ECN.
  • 11: Congestion encountered.

     

Networks typically signal congestion by dropping packets. After an ECN-capable host negotiates ECN, it signals impending congestion by marking the IP header of packets encountering the congestion instead of dropping the packets. The recipient echoes the congestion indication back to the sender, which reduces its transmission rate as if it had detected a dropped packet.

Switches support ECN for unicast queues through Weighted Random Early Detection (WRED), an Active Queue Management (AQM) algorithm that extends Random Early Detection (RED) to define multiple thresholds for an individual queue. WRED determines congestion by comparing average queue size with queue thresholds. Average queue size depends on the previous average and current queue size:
  • average queue size = (old_avg * (1-2^(-weight))) + (current_queue_size * 2^(-weight))
  • where weight is the exponential weight factor used for averaging the queue size.
  • Packets are marked based on WRED as follows:

     

  • If average queue size is below the minimum threshold, packets are queued as in normal operation without ECN.
  • If average queue size is greater than the maximum threshold, packets are marked for congestion.
  • If average queue size is between minimum and maximum queue threshold, packets are either queued or marked. The proportion of packets that are marked increases linearly from 0% at the minimum threshold to 100% at the maximum threshold.

     

Treatment of packets marked as not ECN capable varies by platform.

These sections describe ECN configuration procedures:

ACL Policing

ACL policing monitors the ingress data rates for a particular class of traffic and performs the action configured when the traffic exceeds the user configured value. Therefore, it allows the user to control ingress bandwidth based on packet classification. The incoming traffic is metered and marked by the policing, and based on the metering results the actions are performed.

ACL policing uses a token bucket shaping algorithm for packet transmission. Packets are eligible for transmission when token count is positive, and when token count is negative the next packet will have to wait until the token count turns positive again. The tokens are renewed at 96ns time interval (Tc). The tokens are collected in the policer bucket up to a max burst size of 16KB, and any traffic beyond this shape rate and burst size is buffered in the shared memory. The packets are dropped if there is a memory overflow.

 

Note: The policer bucket is refilled at a sweeper period of 0.333 millisecond. This is applicable for all the platforms.

 

For example, let us assume that shaping is not enabled, and the link is at 10 Gbps, that is 1.25 bytes/nsec. In such case a each refill cycle will add tokens worth 120 bytes. For a shape rate of 500 Mbps, each refill cycle will add 6 bytes. And for 64 byte worth of tokens we need around 11 refill cycles = 1us. A 64 byte packet coming immediately after a jumbo frame will have to wait longer compared to a jumbo frame coming after 64 byte packet.

Token size depends on the interface speed, following the last example:
  • For 10 Gbps, each refill cycle will add tokens worth 120 bytes.
  • For 1 Gbps, each refill cycle will add tokens worth 12 bytes.

     

At lower shaping rates (less than 10 Mbps), granularity and rounding errors may alter the actual shaping rate by 20% from the specified rate, and the rounding errors are much less at higher speeds. For example, At 100 Mbps you will see 98.9Mbps configured in hardware. User can use the show qos interfaces command to verify the interface speed.

The policing uses three types of traffic metering and coloring mechanisms.
  • Single Rate Two Color Marker
  • Single Rate Three Color Marker
  • Two Rate Three Color Marker

     

Single Rate Two Color Marker

It meters the packet stream and marks packets based on committed burst size (bc) and excess burst size (be).

Single Rate Three Color Marker

It meters the packet stream and marks packets based on single rate committed information rate (cir), and committed burst size (bc) and excess burst size (be). The packets are marked in green if it does not exceed the set burst size, and marked in yellow if it does exceed the burst size but not the excess burst size, and marked red otherwise. The packets are marked in two color modes.
  • Color-blind Mode: In color-blind mode the incoming packet color is ignored.
  • Color-aware Mode: In color-aware mode it is assumed that incoming packet is colored by preceding entity. And, in color-aware mode, a packet never get better than it was. If the input color of the packet is green, it can be marked as green, yellow, or red. But if the input color is yellow, then it can be marked only yellow or red.

     

Two Rate Three Color Marker

It meters the packet stream and marks its packets based on two rates, peak information rate (pir) and committed information rate (cir), and associated burst sizes (bc and be).The packet is marked red if rate exceeds ‘pir’, and yellow if it exceeds ‘cir’ but not 'pir' and marked green if rate is lower than 'cir'. The two rate mode is configured by setting four parameters pir, cir, bc, and be.

The ACL policing is supported on platforms specified in the table below.

Table 1. ACL Policing Support Matrix

Platform Supported

ACL Policing

ACL Policing on LAG Interface

Trident

Yes

Yes

Trident II

Yes

Yes

Trident+

Yes

Yes

FM6000

Yes

Yes

Arad

Yes

Only Per-Port

Jericho

Yes

Yes

Helix

Yes

Yes

XP

Yes

Yes

Trident 3

Yes

Yes

Tomahawk

Yes

Yes

Tomahawk 2

Yes

Yes

Tofino

No

No

 

Configuring ACL Policing

The policer is applied to the class inside the policy map. Policy maps can contain one or more policy map classes, each with different match criteria and policers. The following is the default behavior on conditions and available policing actions:
  • Police command creates a per-interface policer. If you attach per-interface policers to multiple ingress ports, each one polices the matched traffic on each ingress port separately. Per interface statistics gathered for conformed/allowed traffic and exceeded/dropped traffic.

     

  • When there is no policer configured within a class, all traffic is transmitted without any policing. If there are any actions configured, the configured actions are applied.
    • conform-action (green): transmit (default).
    • exceed-action (yellow): drop (default).
    • violate-action (red): drop (default).

       

  • The policer bucket is refilled at a sweeper period of 0.333 milliseconds, and the tokens in the policer bucket are renewed at 96ns time interval (Tc). This is applicable for all the platforms.

     

Steps to Configure ACL Policing

These commands set the CIR, burst size, and creates a class and applies the policing to the policy map:
  1. Create a policy map.
  2. Create a class-map.
  3. Apply the policer to the policy map created.

 

Examples
  • These commands configure the ACL policing for a policy map. 
    switch# configure terminal
switch(config)# policy-map [type qos] policy-name
switch(config-pmap)# class { class-name }
switch(config-pmap-c)# [no] police cir cir [{bps|kbps|mbps}] bc 
committed-burst-size [{bytes|kbytes|mbytes}]

     

  • These commands configure ACL policing in single-rate, two-color mode. 
    switch(config)# class-map type qos match-any class1   
switch(config-cmap-class1)# match ip access-group acl1    
switch(config-cmap-class1)# exit    

switch(config)# policy-map type quality-of-service policy1    
switch(config-pmap)# class class1     
switch(config-pmap-c)# police cir 512000 bc 96000     
switch(config-pmap-c)# exit     
switch(config-pmap)#

     

Displaying ACL Policing Information

 

Examples
  • This command shows the contents of all policy maps on the switch. 
    switch(config)# show policy-map 
Service-policy p

 Class-map: c (match-any)
    Match: ip access-group name a
       police rate 1000 mbps burst-size 100 bytes
 Class-map: class-default (match-any)
Service-policy p
 Class-map: c (match-any)
    Match: ip access-group name a
       police rate 1000 mbps burst-size 100 bytes
 Class-map: class-default (match-any)

     

  • This command shows the interface-specific police counters for interface Ethernet 1. 
    switch(config)# show policy-map interface Ethernet 1 input counters
Service-policy input: policy1
Hardware programming status: Successful

Class-map: class1 (match-any) Match: ip access-group name acl1
Police cir 512000 bps bc 96000 bytes Conformed 4351 packets, 1857386 bytes
Conformed 2536 packets, 3384260 bytes

Class-map: class-default (match-any) matched packets: 0

     

  • This command shows the counters associated with the policy map called p1. 
    switch(config)# show policy-map type qos p1 input counters
Service-policy input: p1 Class-map: c1 (match-any)
Match: ip access-group name a1
Police cir 512000 bps bc 96000 bytes Interface: Ethernet1
Conformed 4351 packets, 1857386 bytes
Exceeded 2536 packets, 3384260 bytes
Interface: Ethernet2
Conformed 2351 packets, 957386 bytes
Exceeded 1536 packets, 1384260 bytes
Class-map: class-default (match-any)
Matched packets : 3229

     

  • This command shows the QoS policy map for interface Ethernet 1. 
    switch(config)# show policy-map interface Ethernet 1 input type qos
Interface: Ethernet 1 Service-policy input: policy1
Hardware programming status: Successful Class-map: class1 (match-any)
Match: ip access-group name acl1
Police cir 512000 bps bc 9000 bytes
Class-map: class2 (match-any)
Match: ip access-group name acl2 set dscp 2
Class-map: class3 (match-any) Match: ip access-group name acl3
Police cir 1280000 bps bc 9000 bytes
Class-map: class-default (match-any)

     

Quality of Service (QoS) Profiles

QoS profiles are sets of QoS configuration instructions defined and applied at the interface level. A QoS profile serves the traffic better by reducing disorder in the running configuration. QoS profiles can modify all interface-level QoS configurations, and are supported on fabric, Ethernet, and port-channel interfaces. Control-plane policies cannot be applied using QoS profiles. Because configuration can be applied through QoS profiles or directly at the interface level, multiple configurations can be applied to the same interface. In such cases, QoS configurations with non-default values, whether configured through the CLI at the interface level or through a QoS profile, are given priority. In the case of multiple non-default values being configured, the interface-level CLI configuration is given priority.

Policy maps incorporating traffic resolution commands can also be applied by a QoS profile. If two policy maps are applied to the same interface (one through a QoS profile and another directly to the CLI).

Policy maps cannot be used on fabric interfaces. If a QoS profile which includes a policy map is applied to a fabric interface, a warning message will be displayed and the policy map will not be applied to the interface, but any additional supported configurations in the QoS profile will be applied. On SVIs and subinterfaces, QoS profiles are not supported, so policy maps must be applied directly through the CLI for these interfaces.

 

Note: For tx-queue configuration, conflicts between QoS profiles and configuration entered via the CLI are resolved at the tx-queue level and not at the tx-queue attribute level. If any non-default configuration has been entered for the tx-queue through the CLI, all tx-queue configuration included in the QoS profile is ignored.

 

IPv6 Flow Label Matches for QoS

Certain packets may include a flow label in their IPv6 headers when the source requests special handling by routers, such as for a media stream or other “real-time” service, among others. A flow consists of packets which share a single flow label, which is preserved throughout their passage from source to destination.

QoS policy map rules can match IPv6 traffic based on their flow labels. This requires a special TCAM profile (qos-match-ipv6-flow-label). These rules require either an exact match, using the “eq” operator, or both a label and a mask.

QoS Configuration: Platform-Independent Features

Creating QoS Profiles

QoS profiles are created by using the qos profile command. This also places the switch in QoS profile configuration mode, where the QoS parameters applied to interfaces are configured. To delete a QoS profile from the running configuration, use the no form of the command.

 

Example

This command creates a QoS profile named Test-Profile and places the switch in QoS profile configuration mode for the profile. 
switch(config)# qos profile Test-Profile 
switch(config-qos-profile-Test-Profile)#

 

Configuring QoS Profiles

The parameters that a QoS profile applies to interfaces are configured in QoS profile configuration mode by issuing the same QoS configuration commands that are available in interface configuration mode. QoS profile configuration mode is a group change mode, and changes made in the mode are not saved until the mode is exited. To abandon all changes made while in the mode, use the abort command.

 

Example

These commands enter QoS profile configuration mode for a QoS profile named Test Profile, configure the CoS value and transmit queue, and save the changes to the profile. 
switch(config)# qos profile Test-Profile
switch(config-qos-profile-Test-Profile)# qos cos 3
switch(config-qos-profile-Test-Profile)# priority-flow-control on
switch(config-qos-profile-Test-Profile)# exit
switch(config)#

 

These commands enter QoS profile configuration mode for a QoS profile named Latency, configure the maximum latency value for VOQ tail-drop threshold, and save the changes to the profile. The latency value can be specified to a maximum of 50 ms. Both milliseconds and microseconds may be used. 
switch(config)# qos profile Latency
switch(config-qos-profile-Latency)# tx-queue 3
switch(config-qos-profile-Latency)# latency maximum <1-50000> microseconds
switch(config-qos-profile-Latency)# latency maximum <1-50> milliseconds
switch(config-qos-profile-Latency)# exit
switch(config)#

 

Attaching Policy-Map to a QoS Profile

The qos profile command places the switch in QoS profile configuration mode. The profile applies the QoS configurations to Ethernet and Port-Channel, and even to the Fabric interfaces, if it exists. A profile specifies the policy-map and other QoS supported configurations. The policy-map is then attached to the QoS profile using service-policy command.

Profiles are created in QoS-profile configuration mode, then applied to an interface in interface configuration mode.

 

Examples
  • This command places the switch in QoS profile configuration mode, the policy-map is then attached to the profile using service-policy command in this mode. 
    switch(config)# qos profile TP
switch(config-qos-profile-TP)#

     

  • This command applies the policy-map to the QoS profile. 
    switch(config-qos-profile-TP)# service-policy type qos input PM-1

     

Applying a QoS profile on an Interface

The service-profile command applies a QoS profile to the configuration mode interface.

 

Example

This command applies the QoS profile TP to interface ethernet 13. 
switch(config)# interface ethernet 13
switch(config-if-Et13)# service-profile TP

 

Displaying the QoS Profile Information

The show qos profile command displays information about the QoS profiles configured and their parameters. To display the attribute of a specific profile, add the name of the profile. To display a list of configured QoS profiles and the interfaces on which they are configured, add the summary keyword.

 

Examples
  • This command displays the configured profiles and their configuration. 
    switch# show qos profile
qos profile p
 qos cos 1
no priority-flow-control pause watchdog
priority-flow-control priority 1 no-drop
priority-flow-control priority 2 no-drop
qos profile p2
qos cos 3
priority-flow-control priority 0 no-drop

     

  • This command displays the contents of a specific profile. 
    switch# show qos profile p2
qos profile p2
qos cos 3
priority-flow-control priority 0 no-drop

     

  • This command displays the interfaces on which each profile is applied. 
    switch# show qos profile summary
Qos Profile: p
Configured on: Et13,7
Fabric
Po12
Qos Profile: p2
Configured on: Et56

     

QoS Configuration: Arad Platform Switches

Implementing QoS on an Arad platform switch consists of configuring port trust settings, default port settings, default traffic classes, conversion maps, and transmit queues.

 

Note: QoS traffic policy is supported on Trident and Tomahawk, Trident II, FM6000, Arad, and Jericho.

 

CoS and DSCP Port Settings – Arad Platform Switches

Port Settings – Trust Mode and Traffic Class describes port trust and default port CoS and DSCP values.

Configuring Port Trust Settings

The qos trust command configures the QoS port trust mode for the configuration mode interface. Trust enabled ports use packet CoS or DSCP values to classify traffic. The port-trust default for switched ports is CoS. The port-trust default for routed ports is DSCP.
  • qos trust cos specifies CoS as the port’s port-trust mode.

     

  • qos trust dscp specifies DSCP as the port’s port-trust mode.

     

  • no qos trust specifies untrusted as the port’s port-trust mode.

     

The show qos interfaces trust command displays the trust mode of specified interfaces.

 

Example

These commands configure and display the following trust modes:
  • Ethernet 3/5/1: dscp
  • Ethernet 3/5/2: untrusted
  • Ethernet 3/5/3: cos
  • Ethernet 3/5/4: default as a switched port
  • Ethernet 3/6/1: default as a routed port 
    switch(config)# interface ethernet 3/5/1
switch(config-if-Et3/5/1)# qos trust dscp
switch(config-if-Et3/5/1)# interface ethernet 3/5/2
switch(config-if-Et3/5/2)# no qos trust
switch(config-if-Et3/5/2)# interface ethernet 3/5/3
switch(config-if-Et3/5/3)# qos trust cos
switch(config-if-Et3/5/3)# interface ethernet 3/5/4
switch(config-if-Et3/5/4)# switchport
switch(config-if-Et3/5/4)# default qos trust
switch(config-if-Et3/5/4)# interface ethernet 3/6/1
switch(config-if-Et3/6/1)# no switchport
switch(config-if-Et3/6/1)# default qos trust
switch(config-if-Et3/6/1) #show qos interface ethernet 3/5/1 - 3/6/1 trust
Port                                       Trust Mode
                               Operational           Configured
---------------------------------------------------------------
Ethernet3/5/1                  DSCP                  DSCP
Ethernet3/5/2                  UNTRUSTED             UNTRUSTED
Ethernet3/5/3                  COS                   COS
Ethernet3/5/4                  COS                   DEFAULT
Ethernet3/6/1                  DSCP                  DEFAULT

switch(config-if-Et3/6/1)#

     

Configuring Default Port Settings

Default CoS and DSCP values are assigned to each Ethernet and port channel interface. These commands specify the configuration mode interface commands specify the port’s default CoS and DSCP values.
  • qos cos configures a port’s default CoS value.
  • qos dscp configures a port’s default DSCP value.

 

Example

These commands configure default CoS (4) and DSCP (44) values on Ethernet interface 3/6/2.


switch(config)# interface ethernet 3/6/2
switch(config-if-Et3/6/2)# qos cos 4
switch(config-if-Et3/6/2)# qos dscp 44
switch(config-if-Et3/6/2)# show active
interface Ethernet3/6/2
   qos cos 4
   qos dscp 44
switch(config-if-Et3/6/2)# show qos interfaces ethernet 3/6/2
Ethernet3/6/2:
   Trust Mode: COS
   Default COS: 4
   Default DSCP: 44

switch(config-if-Et3/6/2)#

 

Traffic Class Derivations – Arad Platform Switches

Traffic Classes describes traffic classes.

Traffic Class Derivation Source

The following table displays the source for deriving a data stream’s traffic class.
Table 2. Traffic Class Derivation Source: Arad Platform Switches
  Untrusted CoS Trusted DSCP Trusted
Untagged Non-IP Default CoS (port) Default CoS (port) Default DSCP (port)
Untagged IP Default CoS (port) Default CoS (port) DSCP (packet)
Tagged Non-IP Default CoS (port) CoS (packet) Default DSCP (port)
Tagged IP Default CoS (port) CoS (packet) DSCP (packet)

 

CoS and DSCP Port Settings – Arad Platform Switches describes the default CoS and DSCP settings for each port.

Mapping CoS to Traffic Class

The qos map cos command assigns a traffic class to a list of CoS values. Multiple commands create a complete CoS to traffic class map. The switch uses this map to assign a traffic class to data packets on the basis of the packet’s CoS field or the chip upon which it is received.

 

Example

This command assigns the traffic class of 5 to the classes of service 1, 3, 5, and 7. 
switch(config)# qos map cos 1 3 5 7 to traffic-class 5
switch(config)# show qos maps
   Number of Traffic Classes supported: 8


   Cos-tc map:
     cos:  0  1  2  3  4  5  6  7
     ----------------------------
     tc:   1  5  2  5  4  5  6  5


switch(config)#

 

The following table displays the default CoS to Traffic Class map on Arad platform switches.

Table 3. Default CoS to Traffic Class Map: Arad Platform Switches
Inbound CoS Untagged 0 1 2 3 4 5 6 7
Traffic Class Derived: use default CoS as inbound 1 0 2 3 4 5 6 7

Mapping DSCP to Traffic Class

The qos map dscp command assigns a traffic class to a set of DSCP values. Multiple commands create a complete DSCP to traffic class map. The switch uses this map to assign a traffic class to data packets on the basis of the packet’s DSCP field or the chip upon which it is received.

 

Example

This command assigns the traffic class of 0 to DSCP values of 12, 24, 41, and 44-47. 
switch(config)# qos map dscp 12 24 41 44 45 46 47 to traffic-class 0
switch(config)# show qos maps
   Number of Traffic Classes supported: 8

   Dscp-tc map:
     d1 :  d2 0  1  2  3  4  5  6  7  8  9
     --------------------------------------
      0 :     1  1  1  1  1  1  1  1  0  0
      1 :     0  0  0  0  0  0  2  2  2  2
      2 :     2  2  2  2  0  3  3  3  3  3
      3 :     3  3  4  4  4  4  4  4  4  4
      4 :     5  0  5  5  0  0  0  0  6  6
      5 :     6  6  6  6  6  6  7  7  7  7
      6 :     7  7  7  7

switch(config)#

 

The following table displays the default DSCP to traffic class map on Arad platform switches.

Table 4. Default DSCP to Traffic Class Map: Arad Platform Switches
Inbound DSCP 0-7 8-15 16-23 24-31 32-39 40-47 48-55 56-63
Traffic Class 1 0 2 3 4 5 6 7

 

CoS Rewrite – Arad Platform Switches

Rewriting CoS and DSCP describes the CoS rewrite functions.

Traffic Class to CoS Rewrite Map

The CoS rewrite value is configurable and based on a data stream’s traffic class, as specified by the traffic class-CoS rewrite map. The qos map traffic-class to cos command assigns a CoS rewrite value to a list of traffic classes. Multiple commands create the complete traffic class–CoS rewrite map.

 

Example

This command assigns the CoS of two to traffic classes 1, 3, and 5. 
switch(config)# qos map traffic-class 1 3 5 to cos 2
switch(config)# show qos map
   Number of Traffic Classes supported: 8

   Tc-cos map:
     tc:   0  1  2  3  4  5  6  7
     ----------------------------
     cos:  1  2  2  2  4  2  6  7

switch(config)#

 

The following table displays the default Traffic Class to CoS rewrite value map on Arad platform switches.

Table 5. Default Traffic Class to CoS Rewrite Value Map: Arad Platform Switches

Traffic Class

 0 1 2 3 4 5 6 7

CoS Rewrite Value

 1 0 2 3 4 5 6 7

 

Traffic Class to DSCP Rewrite Map

DSCP rewrite is always disabled on Arad platform switches.

Transmit Queues and Port Shaping – Arad Platform Switches

Transmit Queues and Port Shaping describes transmit queues and port shaping.

Arad platform switches provide 16 physical queues for each egress port: eight unicast and eight multicast queues. Data is scheduled to the physical queues based on transmit queue assignments.

Multicast queue capacity that remains after multicast traffic is serviced is available for unicast traffic of a corresponding priority. Similarly, unicast queue capacity that remains after unicast traffic is serviced is available for overflow multicast traffic. Under conditions of unicast and multicast congestion, egress traffic is evenly split between unicast and multicast traffic.

A data stream’s traffic class determines the transmit queue it uses. The switch defines a single traffic class–transmit queue map for unicast and multicast traffic on all Ethernet and port channel interfaces. The show qos maps command displays the traffic class–transmit queue map.

The following tabledisplays the default traffic class to transmit queue map on Arad platform switches.

Table 6. Default Traffic Class to Transmit Queue Map: Arad Platform Switches
Traffic Class 0 1 2 3 4 5 6 7
Transmit Queue 0 1 2 3 4 5 6 7

 

Transmit queue parameters are configured in tx-queue configuration command mode, which is entered from interface-ethernet configuration mode.

Mapping Traffic Classes to a Transmit Queue

The qos map traffic-class to tx-queue command assigns traffic classes to a transmit queue. Multiple commands complete the traffic class-transmit queue map. Traffic class 7 and transmit queue 7 are always mapped to each other. This association is not editable.

 

Example

These commands assign traffic classes of 1, 3, and 5 to transmit queue 1, traffic classes 2, 4, and 6 to transmit queue 2, and traffic class 0 to transmit queue 0, then display the resultant map. 
switch(config)# qos map traffic-class 1 3 5 to tx-queue 1
switch(config)# qos map traffic-class 2 4 6 to tx-queue 2
switch(config)# qos map traffic-class 0 to tx-queue 0
switch(config)# show qos maps
   Number of Traffic Classes supported: 8
   Number of Transmit Queues supported: 8

   Tc - tx-queue map:
     tc:        0  1  2  3  4  5  6  7
     ---------------------------------
     tx-queue:  0  1  2  1  2  1  2  7

switch(config)#

 

Entering Tx-Queue Configuration Mode

The tx-queue (Arad/Jericho) command places the switch in tx-queue configuration mode to configure a transmit queue on the configuration mode interface. Tx-queue 7 is not configurable. The show qos interfaces displays the transmit queue configuration for a specified port.

 

Example

This command enters Tx-queue configuration mode for transmit queue 4 of interface Ethernet 3/3/3. 
switch(config)# interface ethernet 3/3/3
switch(config-if-Et3/3/3)# tx-queue 4
switch(config-if-Et3/3/3-txq-4)#

 

Configuring the Shape Rate – Port and Transmit Queues

A port’s shape rate specifies its maximum outbound traffic bandwidth. A transmit queue’s shape rate specifies the queue’s maximum outbound bandwidth. Shape rate commands specify data rates in kbps.
Examples
  • This command configures a port shape rate of 5 Gbps on interface Ethernet 3/5/1. 
    switch(config)# interface ethernet 3/5/1
switch(config-if-Et3/5/1)# shape rate 5000000
switch(config-if-Et3/5/1)# show qos interfaces ethernet 3/5/1 
Ethernet3/5/1:

   Port shaping rate: 5000012 / 5000000 kbps

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D

switch(config-if-Et3/5/1)#

     

  • These commands configure a shape rate of 1 Gbps on transmit queues 3 and 4 of interface Ethernet 3/4/1. 
    switch(config)# interface ethernet 3/4/1
switch(config-if-Et3/4/1)# tx-queue 4
switch(config-if-Et3/4/1-txq-4)# shape rate 1000000 kbps
switch(config-if-Et3/4/1-txq-4)# tx-queue 3
switch(config-if-Et3/4/1-txq-3)# shape rate 1000000 kbps
switch(config-if-Et3/4/1-txq-3)# show qos interface ethernet 3/4/1
Ethernet3/4/1:

   Port shaping rate: disabled

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D
   6      - / -        - / -    (  -  )    SP / SP    D
   5      - / -        - / -    (  -  )    SP / SP    D
   4      - / -      999 / 1000 ( Mbps )   SP / SP    D
   3      - / -      999 / 1000 ( Mbps )   SP / SP    D
   2      - / -        - / -    (  -  )    SP / SP    D
   1      - / -        - / -    (  -  )    SP / SP    D
   0      - / -        - / -    (  -  )    SP / SP    D

switch(config-if-Et3/4/1-txq-3)#

     

Configuring Queue Priority

The priority (Arad/Jericho) command configures a transmit queue’s priority type:
  • The priority strict command configures the queue as a strict priority queue.
  • The no priority command configures the queue as a round robin queue.

     

A queue’s configuration as round robin also applies to all lower priority queues regardless of other configuration statements.

The bandwidth percent (Arad/Jericho) command configures a round robin queue’s bandwidth share. The cumulative operational bandwidth of all round robin queues is always less than or equal to 100%. If the cumulative configured bandwidth is greater than 100%, each port’s operational bandwidth is its configured bandwidth divided by the cumulative configured bandwidth.

 

Examples
  • These commands configure queues 0 through 3 (interface Ethernet 3/5/1) as round robin, then allocate bandwidth for three queues at 30% and one queue at 10%.
    The no priority statement for queue 3 also configures queues 0, 1, and 2 as round robin queues. Removing this statement reverts the other queues to strict priority type unless running-config contains a no priority statement for one of these queues. 
    switch(config)# interface ethernet 3/5/1
switch(config-if-Et3/5/1)# tx-queue 3
switch(config-if-Et3/5/1-txq-3)# no priority
switch(config-if-Et3/5/1-txq-3)# bandwidth percent 10
switch(config-if-Et3/5/1-txq-3)# tx-queue 2
switch(config-if-Et3/5/1-txq-2)# bandwidth percent 30
switch(config-if-Et3/5/1-txq-2)# tx-queue 1
switch(config-if-Et3/5/1-txq-1)# bandwidth percent 30
switch(config-if-Et3/5/1-txq-1)# tx-queue 0
switch(config-if-Et3/5/1-txq-0)# bandwidth percent 30
switch(config-if-Et3/5/1-txq-0)# show qos interfaces ethernet 3/5/1
Ethernet3/5/1:

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D
   6      - / -        - / -    (  -  )    SP / SP    D
   5      - / -        - / -    (  -  )    SP / SP    D
   4      - / -        - / -    (  -  )    SP / SP    D
   3     10 / 10       - / -    (  -  )    RR / RR    D
   2     30 / 30       - / -    (  -  )    RR / SP    D
   1     30 / 30       - / -    (  -  )    RR / SP    D
   0     30 / 30       - / -    (  -  )    RR / SP    D

switch(config-if-Et3/5/1-txq-0)#

     

  • Changing the bandwidth percentage for queue 3 to 30 changes the operational bandwidth of each queue to its configured bandwidth divided by 120% (10%+20%+30%+60%). 
    switch(config-if-Et3/5/1-txq-0)# tx-queue 3
switch(config-if-Et3/5/1-txq-3)# bandwidth percent 30
switch(config-if-Et3/5/1-txq-3)# show qos interfaces ethernet 3/5/1
Ethernet3/5/1:

   Port shaping rate: disabled

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D
   6      - / -        - / -    (  -  )    SP / SP    D
   5      - / -        - / -    (  -  )    SP / SP    D
   4      - / -        - / -    (  -  )    SP / SP    D
   3     24 / 30       - / -    (  -  )    RR / RR    D
   2     24 / 30       - / -    (  -  )    RR / SP    D
   1     24 / 30       - / -    (  -  )    RR / SP    D
   0     24 / 30       - / -    (  -  )    RR / SP    D

Note: Values are displayed as Operational/Configured

switch(config-if-Et3/5/1-txq-3)#

     

ECN Configuration – Arad Platform Switches

Explicit Congestion Notification (ECN) describes Explicit Congestion Notification (ECN).

ECN is independently configurable on all egress queues of each Ethernet interface. ECN settings for Port-Channels are applied on each of the channel’s member Ethernet interfaces. Average queue length is tracked for transmit queues. When it reaches maximum threshold, all subsequent packets are marked.

Although the switch does not limit the number of queues that can be configured for ECN, hardware table limitations restrict the number of queues that can simultaneously implement ECN.

The random-detect ecn (Arad/Jericho) command enables ECN marking for the configuration mode unicast transmit queue and specifies threshold queue sizes.

 

Example

These commands enable ECN marking of unicast packets from unicast transmit queue 4 of interface Ethernet 3/5/1, setting thresholds at 128 kbytes and 1280 kbytes. 
switch(config)# interface ethernet 3/5/1
switch(config-if-Et3/5/1)# tx-queue 4
switch(config-if-Et3/5/1-txq-4)# random-detect ecn minimum-threshold 128 kbytes maximum-threshold 1280 kbyte 
switch(config-if-Et3/5/1-txq-4)# show active
interface Ethernet3/5/1
   tx-queue 4
      random-detect ecn minimum-threshold 128 kbytes maximum-threshold 1280 kbytes
switch(config-if-Et3/5/1-txq-4)#

 

ACL Policing – Arad Platform Switches

ACL Policing describes ACL policing.

Implementing ACL policing consists of configuring the following:
  • policy-map settings.
  • class-name.
  • committed information rate (CIR) the data speed committed to any given circuit regardless of the number of users.
  • burst size the maximum burst size in bytes the network commits to moving under normal conditions.

     

The default unit for the metering rate CIR is bits per second; the default unit for the burst size is bytes.

The policer is applied to the class inside the policy map. Policy maps can contain one or more policy map classes, each with different match criteria and policer.

Default behavior and available policing actions are as follows:
  • Policy map can be applied on multiple interfaces. Interfaces on the same chip will share the policer. (Applicable for Arad only.)
  • If there is no policer configured within a class, all traffic is transmitted without any policing.
  • If there are any actions configured, the configured actions are applied:
    • Conform-action (green): transmit (default).
    • Violate-action (red): drop (default).

       

Example

These commands configure ACL policing in single-rate, two-color mode. 
switch(config)# class-map type qos match-any class1
switch(config-cmap-class1)# match ip access-group acl1
switch(config-cmap-class1)# exit
switch(config)# policy-map type quality-of-service policy1
switch(config-policy1)# class class1
switch(config-policy1-class1)# police cir 512000 bc 96000
switch(config-policy1-class1)# exit
switch(config-policy1)# exit
switch(config)#

 

Displaying ACL Policing Information

Examples

  • This command shows the contents of all policy maps on the switch. 
    switch(config)# show policy-map
Service-policy policy1

Class-map: class1 (match-any)
Match: ip access-group name acl1
Police cir 512000 bps bc 96000 bytes

Class-map: class-default (match-any)
switch(config)#

     

  • This command shows the interface-specific police counters for interface Ethernet 1. 
    switch(config)# show policy-map interface Ethernet 1 input counters
Service-policy input: policy1
Hardware programming status: Successful

Class-map: class1 (match-any) Match: ip access-group name acl1
Police cir 512000 bps bc 96000 bytes Conformed 4351 packets, 1857386 bytes
Conformed 2536 packets, 3384260 bytes

Class-map: class-default (match-any) matched packets: 0

switch(config)#

     

  • This command shows the counters associated with the policy map called p1. 
    switch(config)# show policy-map type qos p1 input counters
Service-policy input: p1 Class-map: c1 (match-any)
Match: ip access-group name a1
Police cir 512000 bps bc 96000 bytes Interface: Ethernet1
Conformed 4351 packets, 1857386 bytes
Exceeded 2536 packets, 3384260 bytes
Interface: Ethernet2
Conformed 2351 packets, 957386 bytes
Exceeded 1536 packets, 1384260 bytes
Class-map: class-default (match-any)
Matched packets : 3229

switch(config)#

     

  • This command shows the QoS policy map for interface Ethernet 1. 
    switch(config)# show policy-map interface Ethernet 1 input type qos
Interface: Ethernet 1 Service-policy input: policy1
Hardware programming status: Successful Class-map: class1 (match-any)
Match: ip access-group name acl1
Police cir 512000 bps bc 9000 bytes
Class-map: class2 (match-any)
Match: ip access-group name acl2 set dscp 2
Class-map: class3 (match-any) Match: ip access-group name acl3
Police cir 1280000 bps bc 9000 bytes
Class-map: class-default (match-any)

switch(config)#

     

QoS Configuration: Jericho Platform Switches

Implementing QoS on an Jericho platform switch consists of configuring port trust settings, default port settings, default traffic classes, conversion maps, and transmit queues.

CoS and DSCP Port Settings – Jericho Platform Switches

Port Settings – Trust Mode and Traffic Class describes port trust and default port CoS and DSCP values.

Configuring Port Trust Settings

The qos trust command configures the QoS port trust mode for the configuration mode interface. Trust enabled ports use packet CoS or DSCP values to classify traffic. The port-trust default for switched ports is CoS. The port-trust default for routed ports is DSCP.
  • qos trust cos specifies CoS as the port’s port-trust mode.

     

  • qos trust dscp specifies DSCP as the port’s port-trust mode.

     

  • no qos trust specifies untrusted as the port’s port-trust mode.

     

The show qos interfaces trust command displays the trust mode of specified interfaces.

 

Example

These commands configure and display the following trust modes:
  • Ethernet 3/5/2: untrusted.
  • Ethernet 3/5/3: cos.
  • Ethernet 3/5/4: default as a switched port.
  • Ethernet 3/6/1: default as a routed port.
switch(config)# interface ethernet 3/5/1
switch(config-if-Et3/5/1)# qos trust dscp
switch(config-if-Et3/5/1)# interface ethernet 3/5/2
switch(config-if-Et3/5/2)# no qos trust
switch(config-if-Et3/5/2)# interface ethernet 3/5/3
switch(config-if-Et3/5/3)# qos trust cos
switch(config-if-Et3/5/3)# interface ethernet 3/5/4
switch(config-if-Et3/5/4)# switchport
switch(config-if-Et3/5/4)# default qos trust
switch(config-if-Et3/5/4)# interface ethernet 3/6/1
switch(config-if-Et3/6/1)# no switchport
switch(config-if-Et3/6/1)# default qos trust
switch(config-if-Et3/6/1)# show qos interface ethernet 3/5/1 - 3/6/1 trust
Port                                       Trust Mode
                               Operational           Configured
---------------------------------------------------------------
Ethernet3/5/1                  DSCP                  DSCP
Ethernet3/5/2                  UNTRUSTED             UNTRUSTED
Ethernet3/5/3                  COS                   COS
Ethernet3/5/4                  COS                   DEFAULT
Ethernet3/6/1                  DSCP                  DEFAULT

switch(config-if-Et3/6/1)#

 

Configuring Default Port Settings

Default CoS and DSCP values are assigned to each Ethernet and port channel interface. These commands specify the configuration mode interface commands specify the port’s default CoS and DSCP values.
  • qos cos configures a port’s default CoS value.

     

  • qos dscp configures a port’s default DSCP value.

 

Example

These commands configure default CoS (4) and DSCP (44) values on interface Ethernet 3/6/2. 
switch(config)# interface ethernet 3/6/2
switch(config-if-Et3/6/2)# qos cos 4
switch(config-if-Et3/6/2)# qos dscp 44
switch(config-if-Et3/6/2)# show active
interface Ethernet3/6/2
   qos cos 4
   qos dscp 44
switch(config-if-Et3/6/2)# show qos interfaces ethernet 3/6/2
Ethernet3/6/2:
   Trust Mode: COS
   Default COS: 4
   Default DSCP: 44

switch(config-if-Et3/6/2)#

 

Traffic Class Derivations – Jericho Platform Switches

Traffic Classes describes traffic classes.

Traffic Class Derivation Source

The following table displays the source for deriving a data stream’s traffic class on Jericho platform switches.

Table 7. Traffic Class Derivation Source: Jericho Platform Switches
  Untrusted CoS Trusted DSCP Trusted
Untagged Non-IP Default CoS (port) Default CoS (port) Default DSCP (port)
Untagged IP Default CoS (port) Default CoS (port) DSCP (packet)
Tagged Non-IP Default CoS (port) CoS (packet) Default DSCP (port)
Tagged IP Default CoS (port) CoS (packet) DSCP (packet)

 

CoS and DSCP Port Settings – Arad Platform Switches describes the default CoS and DSCP settings for each port.

Mapping CoS to Traffic Class

The qos map cos command assigns a traffic class to a list of CoS values. Multiple commands create a complete CoS to traffic class map. The switch uses this map to assign a traffic class to data packets on the basis of the packet’s CoS field or the chip upon which it is received.

 

Example

This command assigns the traffic class of 5 to the classes of service 1, 3, 5, and 7. 
switch(config)# qos map cos 1 3 5 7 to traffic-class 5
switch(config)# show qos maps
   Number of Traffic Classes supported: 8

   Cos-tc map:
     cos:  0  1  2  3  4  5  6  7
     ----------------------------
     tc:   1  5  2  5  4  5  6  5

switch(config)#

 

The following table displays the default CoS to Traffic Class map on Jericho platform switches.

Table 8. Default CoS to Traffic Class Map: Jericho Platform Switches
Inbound CoS Untagged 0 1 2 3 4 5 6 7
Traffic Class Derived: use default CoS as inbound 1 0 2 3 4 5 6 7

 

Mapping DSCP to Traffic Class

The qos map dscp command assigns a traffic class to a set of DSCP values. Multiple commands create a complete DSCP to traffic class map. The switch uses this map to assign a traffic class to data packets on the basis of the packet’s DSCP field or the chip upon which it is received.

 

Example

This command assigns the traffic class of 0 to DSCP values of 12, 24, 41, and 44-47. 
switch(config)# qos map dscp 12 24 41 44 45 46 47 to traffic-class 0
switch(config)# show qos maps
   Number of Traffic Classes supported: 8


   Dscp-tc map:
     d1 :  d2 0  1  2  3  4  5  6  7  8  9
     --------------------------------------
      0 :     1  1  1  1  1  1  1  1  0  0
      1 :     0  0  0  0  0  0  2  2  2  2
      2 :     2  2  2  2  0  3  3  3  3  3
      3 :     3  3  4  4  4  4  4  4  4  4
      4 :     5  0  5  5  0  0  0  0  6  6
      5 :     6  6  6  6  6  6  7  7  7  7
      6 :     7  7  7  7


switch(config)#

 

The following table displays the default DSCP to traffic class map on Jericho platform switches.

Table 9. Default DSCP to Traffic Class Map: Jericho Platform Switches
Inbound DSCP 0-7 8-15 16-23 24-31 32-39 40-47 48-55 56-63
Traffic Class 1 0 2 3 4 5 6 7

 

CoS Rewrite – Jericho Platform Switches

Rewriting CoS and DSCP describes the CoS rewrite functions.

Traffic Class to CoS Rewrite Map

The CoS rewrite value is configurable and based on a data stream’s traffic class, as specified by the traffic class-CoS rewrite map. The qos map traffic-class to cos command assigns a CoS rewrite value to a list of traffic classes. Multiple commands create the complete traffic class–CoS rewrite map.

 

Example

This command assigns the CoS of two to traffic classes 1, 3, and 5. 
switch(config)# qos map traffic-class 1 3 5 to cos 2
switch(config)# show qos map
   Number of Traffic Classes supported: 8

   Tc-cos map:
     tc:   0  1  2  3  4  5  6  7
     ----------------------------
     cos:  1  2  2  2  4  2  6  7

switch(config)#

 

The following table displays the default Traffic Class to CoS rewrite value map on Jericho platform switches.

Table 10. Default Traffic Class to CoS Rewrite Value Map: Jericho Platform Switches

Traffic Class

 0 1 2 3 4 5 6 7

CoS Rewrite Value

 1 0 2 3 4 5 6 7

 

Traffic Class to DSCP Rewrite Map

DSCP rewrite is always disabled on Jericho platform switches.

Transmit Queues and Port Shaping – Jericho Platform Switches

Transmit Queues and Port Shaping describes transmit queues and port shaping.

Jericho platform switches provide 16 physical queues for each egress port: eight unicast and eight multicast queues. Data is scheduled to the physical queues based on transmit queue assignments.

Multicast queue capacity that remains after multicast traffic is serviced is available for unicast traffic of a corresponding priority. Similarly, unicast queue capacity that remains after unicast traffic is serviced is available for overflow multicast traffic. Under conditions of unicast and multicast congestion, egress traffic is evenly split between unicast and multicast traffic.

A data stream’s traffic class determines the transmit queue it uses. The switch defines a single traffic class–transmit queue map for unicast and multicast traffic on all Ethernet and port channel interfaces. The show qos maps command displays the traffic class–transmit queue map.

The following table displays the default traffic class to transmit queue map on Jericho platform switches.

Table 11. Default Traffic Class to Transmit Queue Map: Jericho Platform Switches
Traffic Class 0 1 2 3 4 5 6 7
Transmit Queue 0 1 2 3 4 5 6 7

 

Transmit queue parameters are configured in tx-queue configuration command mode, which is entered from interface-ethernet configuration mode.

Mapping Traffic Classes to a Transmit Queue

The qos map traffic-class to tx-queue command assigns traffic classes to a transmit queue. Multiple commands complete the traffic class-transmit queue map. Traffic class 7 and transmit queue 7 are always mapped to each other. This association is not editable.

 

Example

These commands assign traffic classes of 1, 3, and 5 to transmit queue 1, traffic classes 2, 4, and 6 to transmit queue 2, and traffic class 0 to transmit queue 0, then display the resultant map. 
switch(config)# qos map traffic-class 1 3 5 to tx-queue 1
switch(config)# qos map traffic-class 2 4 6 to tx-queue 2
switch(config)# qos map traffic-class 0 to tx-queue 0
switch(config)# show qos maps
   Number of Traffic Classes supported: 8
   Number of Transmit Queues supported: 8


   Tc - tx-queue map:
     tc:        0  1  2  3  4  5  6  7
     ---------------------------------
     tx-queue:  0  1  2  1  2  1  2  7

switch(config)#

 

Entering Tx-Queue Configuration Mode

The tx-queue (Arad/Jericho) command places the switch in tx-queue configuration mode to configure a transmit queue on the configuration mode interface. Tx-queue 7 is not configurable. The show qos interfaces displays the transmit queue configuration for a specified port.

 

Example

This command enters Tx-queue configuration mode for transmit queue 4 of interface ethernet 3/3/3. 
switch(config)# interface ethernet 3/3/3
switch(config-if-Et3/3/3)# tx-queue 4
switch(config-if-Et3/3/3-txq-4)#

 

Configuring the Shape Rate – Port and Transmit Queues

A port’s shape rate specifies its maximum outbound traffic bandwidth. A transmit queue’s shape rate specifies the queue’s maximum outbound bandwidth. Shape rate commands specify data rates in kbps.

 

Examples
  • This command configures a port shape rate of 5 Gbps on interface ethernet 3/5/1. 
    switch(config)# interface ethernet 3/5/1
switch(config-if-Et3/5/1)# shape rate 5000000
switch(config-if-Et3/5/1)# show qos interfaces ethernet 3/5/1
Ethernet3/5/1:

   Port shaping rate: 5000012 / 5000000 kbps

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D

switch(config-if-Et3/5/1)#

     

  • These commands configure a shape rate of 1 Gbps on transmit queues 3 and 4 on interface ethernet 3/4/1. 
    switch(config)# interface ethernet 3/4/1
switch(config-if-Et3/4/1)# tx-queue 4
switch(config-if-Et3/4/1-txq-4)# shape rate 1000000 kbps
switch(config-if-Et3/4/1-txq-4)# tx-queue 3
switch(config-if-Et3/4/1-txq-3)# shape rate 1000000 kbps
switch(config-if-Et3/4/1-txq-3)# show qos interface ethernet 3/4/1
Ethernet3/4/1:

   Port shaping rate: disabled

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D
   6      - / -        - / -    (  -  )    SP / SP    D
   5      - / -        - / -    (  -  )    SP / SP    D
   4      - / -      999 / 1000 ( Mbps )   SP / SP    D
   3      - / -      999 / 1000 ( Mbps )   SP / SP    D
   2      - / -        - / -    (  -  )    SP / SP    D
   1      - / -        - / -    (  -  )    SP / SP    D
   0      - / -        - / -    (  -  )    SP / SP    D

switch(config-if-Et3/4/1-txq-3)#

     

Configuring Queue Priority

The priority (Arad/Jericho) command configures a transmit queue’s priority type:
  • The priority strict command configures the queue as a strict priority queue.

     

  • The no priority command configures the queue as a round robin queue.

     

A queue’s configuration as round robin also applies to all lower priority queues regardless of other configuration statements.

The bandwidth percent (Arad/Jericho) command configures a round robin queue’s bandwidth share. The cumulative operational bandwidth of all round robin queues is always less than or equal to 100%. If the cumulative configured bandwidth is greater than 100%, each port’s operational bandwidth is its configured bandwidth divided by the cumulative configured bandwidth.

 

Examples
  • These commands configure queues 0 through 3 (interface ethernet 3/5/1) as round robin, then allocate bandwidth for three queues at 30% and one queue at 10%.
    The no priority statement for queue 3 also configures queues 0, 1, and 2 as round robin queues. Removing this statement reverts the other queues to strict priority type unless running-config contains a no priority statement for one of these queues. 
    switch(config)# interface ethernet 3/5/1
switch(config-if-Et3/5/1)# tx-queue 3
switch(config-if-Et3/5/1-txq-3)# no priority
switch(config-if-Et3/5/1-txq-3)# bandwidth percent 10
switch(config-if-Et3/5/1-txq-3)# tx-queue 2
switch(config-if-Et3/5/1-txq-2)# bandwidth percent 30
switch(config-if-Et3/5/1-txq-2)# tx-queue 1
switch(config-if-Et3/5/1-txq-1)# bandwidth percent 30
switch(config-if-Et3/5/1-txq-1)# tx-queue 0
switch(config-if-Et3/5/1-txq-0)# bandwidth percent 30
switch(config-if-Et3/5/1-txq-0)# show qos interfaces ethernet 3/5/1
Ethernet3/5/1:

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D
   6      - / -        - / -    (  -  )    SP / SP    D
   5      - / -        - / -    (  -  )    SP / SP    D
   4      - / -        - / -    (  -  )    SP / SP    D
   3     10 / 10       - / -    (  -  )    RR / RR    D
   2     30 / 30       - / -    (  -  )    RR / SP    D
   1     30 / 30       - / -    (  -  )    RR / SP    D
   0     30 / 30       - / -    (  -  )    RR / SP    D

switch(config-if-Et3/5/1-txq-0)#

     

  • Changing the bandwidth percentage for queue 3 to 30 changes the operational bandwidth of each queue to its configured bandwidth divided by 120% (10%+20%+30%+60%). 
    switch(config-if-Et3/5/1-txq-0)# tx-queue 3
switch(config-if-Et3/5/1-txq-3)# bandwidth percent 30
switch(config-if-Et3/5/1-txq-3)# show qos interfaces ethernet 3/5/1
Ethernet3/5/1:

   Port shaping rate: disabled

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D
   6      - / -        - / -    (  -  )    SP / SP    D
   5      - / -        - / -    (  -  )    SP / SP    D
   4      - / -        - / -    (  -  )    SP / SP    D
   3     24 / 30       - / -    (  -  )    RR / RR    D
   2     24 / 30       - / -    (  -  )    RR / SP    D
   1     24 / 30       - / -    (  -  )    RR / SP    D
   0     24 / 30       - / -    (  -  )    RR / SP    D

Note: Values are displayed as Operational/Configured

switch(config-if-Et3/5/1-txq-3)#

     

ACL Policing – Jericho Platform Switches

ACL Policing describes ACL policing.

Implementing ACL policing consists of configuring the following:
  • policy-map settings.

     

  • class-name.

     

  • committed information rate (CIR)     the data speed committed to any given circuit regardless of the number of users.

     

  • burst size     the maximum burst size in bytes the network commits to moving under normal conditions.

     

The default unit for the metering rate CIR is bits per second; the default unit for the burst size is bytes.

The policer is applied to the class inside the policy map. Policy maps can contain one or more policy map classes, each with different match criteria and policer.

Default behavior and available policing actions are as follows:
  • Policy map can be applied on multiple interfaces. Interfaces on the same chip will share the policer. (Applicable for Arad and Jericho only.)

     

  • If there is no policer configured within a class, all traffic is transmitted without any policing.

     

  • If there are any actions configured, the configured actions are applied:
    • Conform-action (green): transmit (default).
    • Violate-action (red): drop (default).

       

Example

These commands configure ACL policing in single-rate, two-color mode. 
switch(config)# class-map type qos match-any class1
switch(config-cmap-class1)# match ip access-group acl1
switch(config-cmap-class1)# exit
switch(config)# policy-map type quality-of-service policy1
switch(config-policy1)# class class1
switch(config-policy1-class1)# police cir 512000 bc 96000
switch(config-policy1-class1)# exit
switch(config-policy1)# exit
switch(config)#

 

Displaying ACL Policing Information

Examples

  • This command shows the contents of all policy maps on the switch. 
    switch(config)# show policy-map
Service-policy policy1

Class-map: class1 (match-any)
Match: ip access-group name acl1
Police cir 512000 bps bc 96000 bytes

Class-map: class-default (match-any)
switch(config)#

     

  • This command shows the interface-specific police counters for interface ethernet 1. 
    switch(config)# show policy-map interface Ethernet 1 input counters
Service-policy input: policy1
Hardware programming status: Successful

Class-map: class1 (match-any) Match: ip access-group name acl1
Police cir 512000 bps bc 96000 bytes Conformed 4351 packets, 1857386 bytes
Conformed 2536 packets, 3384260 bytes

Class-map: class-default (match-any) matched packets: 0

switch(config)#

     

  • This command shows the counters associated with the policy map called p1. 
    switch(config)# show policy-map type qos p1 input counters
Service-policy input: p1 Class-map: c1 (match-any)
Match: ip access-group name a1
Police cir 512000 bps bc 96000 bytes Interface: Ethernet1
Conformed 4351 packets, 1857386 bytes
Exceeded 2536 packets, 3384260 bytes
Interface: Ethernet2
Conformed 2351 packets, 957386 bytes
Exceeded 1536 packets, 1384260 bytes
Class-map: class-default (match-any)
Matched packets : 3229

switch(config)#

     

  • This command shows the QoS policy map for interface ethernet 1. 
    switch(config)# show policy-map interface Ethernet 1 input type qos
Interface: Ethernet 1 Service-policy input: policy1
Hardware programming status: Successful Class-map: class1 (match-any)
Match: ip access-group name acl1
Police cir 512000 bps bc 9000 bytes
Class-map: class2 (match-any)
Match: ip access-group name acl2 set dscp 2
Class-map: class3 (match-any) Match: ip access-group name acl3
Police cir 1280000 bps bc 9000 bytes
Class-map: class-default (match-any)

switch(config)#

     

QoS Configuration: FM6000 Platform Switches

Implementing QoS on an FM6000 platform switch consists of configuring port trust settings, default port settings, default traffic classes, conversion maps, and transmit queues.

CoS and DSCP Port Settings – FM6000 Platform Switches

Port Settings – Trust Mode and Traffic Class describes port trust and default port CoS and DSCP values.

Configuring Port Trust Settings

The qos trust command configures the QoS port trust mode for the configuration mode interface. Trust enabled ports use packet CoS or DSCP values to classify traffic. The port-trust default for switched ports is cos. The port-trust default for routed ports is dscp.
  • qos trust cos specifies cos as the port’s port-trust mode.

     

  • qos trust dscp specifies dscp as the port’s port-trust mode.

     

  • no qos trust specifies untrusted as the port’s port-trust mode.

     

The show qos interfaces trust command displays the trust mode of specified interfaces.

 

Example

These commands configure and display the following trust modes:
  • Ethernet 15: dscp.
  • Ethernet 16: untrusted.
  • Ethernet 17: cos.
  • Ethernet 18: default as a switched port.
  • Ethernet 19: default as a routed port. 
    switch(config)# interface ethernet 15
switch(config-if-Et15)# qos trust dscp
switch(config-if-Et15)# interface ethernet 16
switch(config-if-Et16)# no qos trust
switch(config-if-Et16)# interface ethernet 17
switch(config-if-Et17)# qos trust cos
switch(config-if-Et17)# interface ethernet 18
switch(config-if-Et18)# switchport
switch(config-if-Et18)# default qos trust
switch(config-if-Et19)# interface ethernet 19
switch(config-if-Et19)# no switchport
switch(config-if-Et19)# default qos trust
switch(config-if-Et19)# show qos interface ethernet 15 - 19 trust
Port                                       Trust Mode
                               Operational           Configured
---------------------------------------------------------------
Ethernet15                     DSCP                  DSCP
Ethernet16                     UNTRUSTED             UNTRUSTED
Ethernet17                     COS                   COS
Ethernet18                     COS                   DEFAULT
Ethernet19                     DSCP                  DEFAULT

switch(config-if-Et19)#

     

Configuring Default Port Settings

Default CoS and DSCP settings are assigned to individual port channel and Ethernet interfaces. These configuration mode interface commands specify the port’s default CoS and DSCP values.
  • qos cos configures a port’s default CoS value.

     

  • qos dscp configures a port’s default DSCP value.

     

Example

These commands configure default CoS (4) and DSCP (44) settings on interface ethernet 19. 
switch(config)# interface ethernet 19
switch(config-if-Et19)# qos cos 4
switch(config-if-Et19)# qos dscp 44
switch(config-if-Et19)# show active
interface Ethernet19
   qos cos 4
   qos dscp 44
switch(config-if-Et19)# show qos interfaces ethernet 19
Ethernet19:
   Trust Mode: COS
   Default COS: 4
   Default DSCP: 44

switch(config-if-Et19)#

 

Traffic Class Derivations – FM6000 Platform Switches

Traffic Classes describes traffic classes.

Traffic Class Derivation Source

The following table displays the source for deriving a data stream’s traffic class.

Table 12. Traffic Class Derivation Source: FM6000 Platform Switches
  Untrusted CoS Trusted DSCP Trusted
Untagged Non-IP Default CoS (port) Default CoS (port) Default DSCP (port)
Untagged IP Default CoS (port) Default CoS (port) DSCP (packet)
Tagged Non-IP Default CoS (port) CoS (packet) Default DSCP (port)
Tagged IP Default CoS (port) CoS (packet) DSCP (packet)

 

CoS and DSCP Port Settings – FM6000 Platform Switches describes the default CoS and DSCP settings for each port.

Mapping CoS to Traffic Class

The qos map cos command assigns a traffic class to a list of CoS settings. Multiple commands create a complete CoS to traffic class map. The switch uses this map to assign a traffic class to data packets on the basis of the packet’s CoS field or the port upon which it is received.

 

Example

This command assigns the traffic class of 5 to the classes of service 1, 3, 5, and 7. 
switch(config)# qos map cos 1 3 5 7 to traffic-class 5
switch(config)# show qos maps
   Number of Traffic Classes supported: 8
   Number of Transmit Queues supported: 8


   Cos-tc map:
     cos:  0  1  2  3  4  5  6  7
     ----------------------------
     tc:   1  5  2  5  4  5  6  5


switch(config)#

 

The following table displays the default CoS to Traffic Class map on FM6000 platform switches.
Table 13. Default CoS to Traffic Class Map: FM6000 Platform Switches
Inbound CoS Untagged 0 1 2 3 4 5 6 7
Traffic Class Derived: use default CoS as inbound CoS 1 0 2 3 4 5 6 7

 

Mapping DSCP to Traffic Class

The qos map dscp command assigns a traffic class to a set of DSCP values. Multiple commands create a complete DSCP to traffic class map. The switch uses this map to assign a traffic class to data packets on the basis of the packet’s DSCP field or the chip upon which it is received.

 

Example

This command assigns the traffic class of three to the DSCP values of 12, 13, 25, and 37. 
switch(config)# qos map dscp 12 13 25 37 to traffic-class 3
switch(config)# show qos map
   Number of Traffic Classes supported: 8

   Dscp-tc map:
     d1 :  d2 0  1  2  3  4  5  6  7  8  9
     --------------------------------------
      0 :     1  1  1  1  1  1  1  1  0  0
      1 :     0  0  3  3  0  0  2  2  2  2
      2 :     2  2  2  2  3  3  3  3  3  3
      3 :     3  3  4  4  4  4  4  3  4  4
      4 :     5  5  5  5  5  5  5  5  6  6
      5 :     6  6  6  6  6  6  7  7  7  7
      6 :     7  7  7  7

switch(config)#

 

The following displays the default DSCP to Traffic Class map on FM6000 platform switches.
Table 14. Default DSCP to Traffic Class Map: FM6000 Platform Switches
Inbound DSCP 0-7 8-15 16-23 24-31 32-39 40-47 48-55 56-63
Traffic Class 1 0 2 3 4 5 6 7

CoS and DSCP Rewrite – FM6000 Platform Switches

Rewriting CoS and DSCP describes the CoS and DSCP rewrite functions.

Traffic Class to CoS Rewrite Map

The CoS rewrite value is configurable and based on a data stream’s traffic class, as specified by the traffic class-CoS rewrite map. The qos map traffic-class to cos command assigns a CoS rewrite value to a list of traffic classes. Multiple commands create the complete traffic class–CoS rewrite map.

 

Example

This command assigns the CoS rewrite value of two to traffic classes 1, 3, and 5. 
switch(config)# qos map traffic-class 1 3 5 to cos 2
switch(config)# show qos map
   Number of Traffic Classes supported: 8

   Tc - tx-queue map:
     tc:        0  1  2  3  4  5  6  7
     ---------------------------------
     tx-queue:  0  1  2  3  4  5  6  7

switch(config)#

 

The following table displays the default traffic class–CoS rewrite map on FM6000 platform switches.
Table 15. Default Traffic Class to CoS Rewrite Map: FM6000 Platform Switches

Traffic Class

0

1

2

3

4

5

6

7

CoS Rewrite Value

1

0

2

3

4

5

6

7

 

Traffic Class to DSCP Rewrite Map

The DSCP rewrite value is configurable and based on a data stream’s traffic class, as specified by the traffic class-DSCP rewrite map. The qos map traffic-class to dscp command assigns a DSCP rewrite value to a list of traffic classes. Multiple commands create the complete traffic class-DSCP rewrite map.

 

Example

This command assigns the DSCP rewrite value of 37 to traffic classes 2, 4, and 6. 
switch(config)# qos map traffic-class 2 4 6 to dscp 37
switch(config)# show qos map
   Number of Traffic Classes supported: 8

   Tc-dscp map:
     tc:    0  1  2  3  4  5  6  7
     -----------------------------
     dscp:  8  0 37 24 37 40 37 56

switch(config)#

 

The following table displays the default traffic class–DSCP rewrite map on on FM6000 platform switches.

Table 16. Default Traffic Class to DSCP Rewrite Map: FM6000 Platform Switches
Traffic Class 0 1 2 3 4 5 6 7
DSCP Rewrite Value 8 0 16 24 32 40 48 56

 

Transmit Queues and Port Shaping – FM6000 Platform Switches

Transmit Queues and Port Shaping describes transmit queues and port shaping.

A data stream’s traffic class determines the transmit queue it uses. The switch defines a single traffic class-transmit queue map for all Ethernet and port channel interfaces and is used for unicast and multicast traffic. The show qos maps command displays the traffic class to transmit queue map.

The following table displays the default traffic class to transmit queue map on FM6000 platform switches.

Table 17. Default Traffic Class to Transmit Queue Map: FM6000 Platform Switches
Traffic Class 0 1 2 3 4 5 6 7
Transmit Queue 0 1 2 3 4 5 6 7

 

Mapping Traffic Classes to a Transmit Queue

The qos map traffic-class to tx-queue command assigns traffic classes to a transmit queue. Multiple commands create the complete map.

 

Example

These commands assign traffic classes of 1, 3, and 5 to transmit queue 1, traffic classes 2, 4, and 6 to transmit queue 2, and traffic class 0 to transmit queue 0, then display the resultant map. 
switch(config)# qos map traffic-class 1 3 5 to tx-queue 1
switch(config)# qos map traffic-class 2 4 6 to tx-queue 2
switch(config)# qos map traffic-class 0 to tx-queue 0
switch(config)# show qos maps
   Number of Traffic Classes supported: 8
   Number of Transmit Queues supported: 8


   Tc - tx-queue map:
     tc:        0  1  2  3  4  5  6  7
     ---------------------------------
     tx-queue:  0  1  2  1  2  1  2  7

switch(config)#

 

Entering TX-Queue Configuration Mode

Transmit queues are configurable on Ethernet ports and port channels. Queue parameters are configured in tx-queue configuration command mode, which is entered from interface ethernet configuration mode. The tx-queue (FM6000) command places the switch in tx-queue configuration mode. The show qos interfaces displays the transmit queue configuration for a specified port.

 

Example

This command enters tx-queue configuration mode for transmit queue 3 of interface Ethernet 5. 
switch(config)# interface ethernet 5
switch(config-if-Et5)# tx-queue 3   
switch(config-if-Et5-txq-3)#

 

Configuring the Shape Rate – Port and Transmit Queues

A port’s shape rate specifies its maximum outbound traffic bandwidth. A transmit queue’s shape rate specifies the queue’s maximum outbound bandwidth. Shape rate commands specify data rates in kbps.

 

Note: Enabling port shaping on an FM6000 interface disables queue shaping internally. Disabling port shaping restores queue shaping as specified in running-config.

 

Example

These commands configure a shape rate of 5 Gbs on interface Ethernet 3, then configure the shape rate for the following transmit queues:
    • transmit queues 0, 1, and 2: 500 Mbps.

    • transmit queues 3, 4, and 5: 400 Mbps.

      switch(config)# interface ethernet 3
switch(config-if-Et3)# shape rate 5000000
switch(config-if-Et3)# tx-queue 0
switch(config-if-Et3-txq-0)# shape rate 500000
switch(config-if-Et3-txq-0)# tx-queue 1
switch(config-if-Et3-txq-1)# shape rate 500000
switch(config-if-Et3-txq-1)# tx-queue 3
switch(config-if-Et3-txq-3)# shape rate 400000
switch(config-if-Et3-txq-3)# tx-queue 4
switch(config-if-Et3-txq-4)# shape rate 400000
switch(config-if-Et3-txq-4)# tx-queue 5
switch(config-if-Et3-txq-5)# shape rate 400000
switch(config-if-Et3-txq-5)# exit
switch(config-if-Et3)# show qos interface ethernet 3
Ethernet3:

   Port shaping rate: 5000000Kbps

   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
   -----------------------------------------------
          7         N/A     disabled        strict
          6         N/A     disabled        strict
          5         N/A       400000        strict
          4         N/A       400000        strict
          3         N/A       400000        strict
          2         N/A     disabled        strict
          1         N/A       500000        strict
          0         N/A       500000        strict

switch(config-if-Et3)#

       

Configuring Queue Priority

Queue priority rank is denoted by the queue number; transmit queues with higher numbers have higher priority. The priority (FM6000) command configures a transmit queue’s priority type:
  • priority strict configures the queue as a strict priority queue.

     

  • no priority configures the queue as a round robin queue.

     

A queue’s configuration as round robin also applies to all lower priority queues regardless of other configuration statements.

The bandwidth percent (FM6000) command configures a round robin queue’s bandwidth share. The cumulative operational bandwidth of all round robin queues is always less than or equal to 100%. If the cumulative configured bandwidth is greater than 100%, each port’s operational bandwidth is its configured bandwidth divided by the cumulative configured bandwidth.

 

Examples
  • These commands configure transmit queue 3 (on interface Ethernet 19) as a round robin queue, then allocates 10%, 20%, 30%, and 40% bandwidth to queues 0 through 3.
    The no priority statement for queue 3 also configures queues 0, 1, and 2 as round robin queues. Removing this statement reverts the other queues to strict priority type unless running-config contains a no priority statement for one of these queues. 
    switch(config)# interface ethernet 19
switch(config-if-Et19)# tx-queue 3
switch(config-if-Et19-txq-3)# no priority
switch(config-if-Et19-txq-3)# bandwidth percent 40
switch(config-if-Et19-txq-3)# tx-queue 2
switch(config-if-Et19-txq-2)# bandwidth percent 30
switch(config-if-Et19-txq-2)# tx-queue 1
switch(config-if-Et19-txq-1)# bandwidth percent 20
switch(config-if-Et19-txq-1)# tx-queue 0
switch(config-if-Et19-txq-0)# bandwidth percent 10
switch(config-if-Et19-txq-0)# show qos interface ethernet 19
Ethernet19:

   Port shaping rate: disabled

   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
   -----------------------------------------------
          7         N/A     disabled        strict
          6         N/A     disabled        strict
          5         N/A     disabled        strict
          4         N/A     disabled        strict
          3          40     disabled   round-robin
          2          30     disabled   round-robin
          1          20     disabled   round-robin
          0          10     disabled   round-robin

switch(config-if-Et19-txq-0)#

     

  • Changing the bandwidth percentage for queue 3 to 60 changes the operational bandwidth of each queue to its configured bandwidth divided by 120% (10%+20%+30%+60%). 
    switch(config-if-Et19-txq-0) #tx-queue 3
switch(config-if-Et19-txq-3)# bandwidth percent 60
switch(config-if-Et19-txq-3)# show qos interface ethernet 19
Ethernet19:

   Port shaping rate: disabled

   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
   -----------------------------------------------
          7         N/A     disabled        strict
          6         N/A     disabled        strict
          5         N/A     disabled        strict
          4         N/A     disabled        strict
          3          49     disabled   round-robin
          2          24     disabled   round-robin
          1          16     disabled   round-robin
          0           8     disabled   round-robin

switch(config-if-Et19-txq-3)#

     

QoS Configuration: Petra Platform Switches

Implementing QoS on a Petra platform switch consists of configuring port trust settings, default port settings, default traffic classes, conversion maps, and transmit queues.

CoS and DSCP Port Settings – Petra Platform Switches

Port Settings – Trust Mode and Traffic Class describes port trust and default port CoS and DSCP values.

Configuring Port Trust Settings

The qos trust command configures the QoS port trust mode for the configuration mode interface. Trust enabled ports use packet CoS or DSCP values to classify traffic. The port-trust default for switched ports is cos. The port-trust default for routed ports is dscp.
  • qos trust cos specifies cos as the port’s port-trust mode.

     

  • qos trust dscp specifies dscp as the port’s port-trust mode.

     

  • no qos trust specifies untrusted as the port’s port-trust mode.

     

The show qos interfaces trust command displays the trust mode of specified interfaces.

Example

These commands configure and display the following trust modes:
  • Ethernet 3/25: dscp.
  • Ethernet 3/26: untrusted.
  • Ethernet 3/27: cos.
  • Ethernet 3/28: default as a switched port.
  • Ethernet 3/29: default as a routed port. 
    switch(config)# interface ethernet 3/25
switch(config-if-Et3/25)# qos trust dscp
switch(config-if-Et3/25)# interface ethernet 3/26
switch(config-if-Et3/26)# no qos trust
switch(config-if-Et3/26)# interface ethernet 3/27
switch(config-if-Et3/27)# qos trust cos
switch(config-if-Et3/27)# interface ethernet 3/28
switch(config-if-Et3/28)# switchport
switch(config-if-Et3/28)# default qos trust
switch(config-if-Et3/28)# interface ethernet 3/29
switch(config-if-Et3/29)# no switchport
switch(config-if-Et3/29)# default qos trust
switch(config-if-Et3/29)# show qos interface ethernet 3/25 - 3/29 trust
Port                                       Trust Mode
                               Operational           Configured
---------------------------------------------------------------
Ethernet3/25                   DSCP                  DSCP
Ethernet3/26                   UNTRUSTED             UNTRUSTED
Ethernet3/27                   COS                   COS
Ethernet3/28                   COS                   DEFAULT
Ethernet3/29                   DSCP                  DEFAULT

switch(config-if-Et3/29)#

     

Configuring Default Port Settings

Port channel and Ethernet interfaces are not assigned default CoS or DSCP settings.

Traffic Class Derivations – Petra Platform Switches

Traffic Classes describes traffic classes.

Traffic Class Derivation Source

The following table displays the source for deriving a data stream’s default traffic class.

Table 18. Traffic Class Derivation Source: Petra Platform Switches
  Untrusted CoS Trusted DSCP Trusted
Untagged Non-IP Default TC (chip) Default TC (chip) Default TC (chip)
Untagged IP Default TC (chip) Default TC (chip) DSCP (packet)
Tagged Non-I Default TC (chip) CoS (packet) Default TC (chip)
Tagged IP Default TC (chip) CoS (packet) DSCP (packet)

 

Configuring Default Traffic Class

Petra platform switches assign a default traffic class to the set of Ethernet interfaces controlled by individual PetraA chips. Default traffic class values are configurable for each PetraA chip, not individual interfaces.

The platform petraA traffic-class command specifies the default traffic class used by all ports controlled by a specified chip. The show platform petraA traffic-class command displays traffic class assignments.

 

Examples
  • This command configures the default traffic class to five for the ports 32-39 on linecard 3 (7500 Series). 
    switch(config)# platform petraA petra3/4 traffic-class 5
switch(config)# show platform petraA module 3 traffic-class
Petra3/0 traffic-class: 1
Petra3/1 traffic-class: 1
Petra3/2 traffic-class: 1
Petra3/3 traffic-class: 1
Petra3/4 traffic-class: 5
Petra3/5 traffic-class: 1
switch(config)#

     

  • This command configures the default traffic class to three for all ports on linecard 6 (7500 Series). 
    switch(config)# platform petraA module 6 traffic-class 6
switch(config)# show platform petraA module 6 traffic-class
Petra6/0 traffic-class: 6
Petra6/1 traffic-class: 6
Petra6/2 traffic-class: 6
Petra6/3 traffic-class: 6
Petra6/4 traffic-class: 6
Petra6/5 traffic-class: 6
switch(config)#

     

Mapping CoS to Traffic Class

The qos map cos command assigns a traffic class to a list of CoS settings. Multiple commands create a complete CoS–traffic class map. The switch uses this map to assign a traffic class to data packets on the basis of the packet’s CoS field or the port upon which it is received.

 

Example

This command assigns traffic class 4 to the classes of service 1, 3, 5, and 7. 
switch(config)# qos map cos 1 3 5 7 to traffic-class 4
switch(config)# show qos maps
   Number of Traffic Classes supported: 8

   Cos-tc map:
     cos:  0  1  2  3  4  5  6  7
     ----------------------------
     tc:   1  4  2  4  4  4  6  4

switch(config)#

 

The following table displays the default CoS to traffic class map on Petra platform switches.

Table 19. Default CoS to Traffic Class Map: Petra Platform Switches
Inbound CoS untagged 0 1 2 3 4 5 6 7
Traffic Class Derived: use default CoS as inbound CoS 1 0 2 3 4 5 6 7

 

Mapping DSCP to Traffic Class

The qos map dscp command assigns a traffic class to a set of DSCP values. Multiple commands create a complete DSCP to traffic class map. The switch uses this map to assign a traffic class to data packets on the basis of the packet’s DSCP field or the chip upon which it is received.

Example

This command assigns traffic class 3 to the DSCP values of 12, 13, 25, and 37. 
switch(config)# qos map dscp 12 13 14 25 48 to traffic-class 3
switch(config)# show qos maps
   Number of Traffic Classes supported: 8

   Dscp-tc map:
     d1 :  d2 0  1  2  3  4  5  6  7  8  9
     --------------------------------------
      0 :     1  1  1  1  1  1  1  1  0  0
      1 :     0  0  3  3  3  0  2  2  2  2
      2 :     2  2  2  2  3  3  3  3  3  3
      3 :     3  3  4  4  4  4  4  4  4  4
      4 :     5  5  5  5  5  5  5  5  3  6
      5 :     6  6  6  6  6  6  7  7  7  7
      6 :     7  7  7  7

switch(config)#

 

The following table displays the default DSCP to Traffic Class map on Petra platform switches.

Table 20. Default DSCP to Traffic Class Map: Petra Platform Switches
Inbound DSCP 0-7 8-15 16-23 24-31 32-39 40-47 48-55 56-63
Traffic Class 1 0 2 3 4 5 6 7

 

CoS Rewrite – Petra Platform Switches

Rewriting CoS and DSCP describes the CoS rewrite function.

Traffic Class to CoS Rewrite Map

The CoS rewrite value is configurable and based on a data stream’s traffic class, as specified by the traffic class-CoS rewrite map. The qos map traffic-class to cos command assigns a CoS rewrite value to a list of traffic classes. Multiple commands create the complete traffic class-CoS rewrite map.

 

Example

This command assigns the CoS of two to traffic classes 1, 3, and 5. 
switch(config)# qos map traffic-class 1 3 5 to cos 2
switch(config)# show qos map
   Number of Traffic Classes supported: 8

   Tc-cos map:
     tc:   0  1  2  3  4  5  6  7
     ----------------------------
     cos:  1  2  2  2  4  2  6  7

switch(config)#

 

The following table displays the default Traffic Class to CoS rewrite value map on Petra platform switches.

Table 21. Default Traffic Class to CoS Rewrite Value Map: Petra Platform Switches
Traffic Class 0 1 2 3 4 5 6 7
CoS Rewrite Value 1 0 2 3 4 5 6 7

 

Traffic Class to DSCP Rewrite Map

DSCP rewrite is always disabled on Petra platform switches.

Transmit Queues and Port Shaping – Petra Platform Switches

Transmit Queues and Port Shaping describes transmit queues and port shaping.

Petra platform switches provide four physical queues for each egress port: Unicast High, Unicast Low, Multicast High, and Multicast Low. Data is scheduled for the high or low queue based on its priority as defined by its transmit queue assignment (unicast traffic) or traffic class (multicast traffic), as shown in the table below. A Petra transmit queue is a data structure that defines scheduling of unicast traffic among physical egress queues.

Table 22. Traffic Distribution to Egress Port Queues
  High Priority Queue Low Priority Queue
Unicast Traffic Transmit Queues 5 – 7 Transmit Queues 0 – 4
Multicast Traffic Traffic Classes 5 – 7 Traffic Classes 0 – 4

 

Multicast queue capacity that is available after multicast traffic is serviced is used for unicast traffic of a corresponding priority. Similarly, unicast queue capacity that is available after unicast traffic is serviced is used for overflow multicast traffic. Under conditions of unicast and multicast congestion, egress traffic is evenly split between unicast and multicast traffic.

Unicast Transmit Queues and Port Shaping describes unicast transmit queues and shaping. Multicast Egress Scheduling describes multicast priority and traffic classes.

Unicast Transmit Queues and Port Shaping

A data stream’s traffic class determines the transmit queue it uses. The switch defines a single traffic class–transmit queue map for unicast traffic on all Ethernet interfaces. The show qos maps command displays the traffic class–transmit queue map. The following table displays the default traffic class to transmit queue map on Petra platform switches.

Table 23. Default Traffic Class to Transmit Queue Map: Petra Platform Switches
Traffic Class 0 1 2 3 4 5 6 7
Transmit Queue 0 1 2 3 4 5 6 7

 

Transmit queue parameters are configured in tx-queue configuration command mode.

Mapping Traffic Classes to a Transmit Queue

The qos map traffic-class to tx-queue command assigns traffic classes to a transmit queue. Multiple commands complete the traffic class-transmit queue map. Traffic class 7 and transmit queue 7 are always mapped to each other. This association is not editable.

 

Example

These commands assign traffic classes of 1, 3, and 5 to transmit queue 1, traffic classes 2, 4, and 6 to transmit queue 2, and traffic class 0 to transmit queue 0, then display the resultant map. 
switch(config)# qos map traffic-class 1 3 5 to tx-queue 1
switch(config)# qos map traffic-class 2 4 6 to tx-queue 2
switch(config)# qos map traffic-class 0 to tx-queue 0
switch(config)# show qos maps
   Number of Traffic Classes supported: 8
   Number of Transmit Queues supported: 8

   Tc - tx-queue map:
     tc:        0  1  2  3  4  5  6  7
     ---------------------------------
     tx-queue:  0  1  2  1  2  1  2  7

switch(config)#

 

Entering Tx-Queue Configuration Mode

The tx-queue (Petra) command places the switch in tx-queue configuration mode to configure a transmit queue on the configuration mode interface. Tx-queue 7not configurable. The show qos interfaces displays the transmit queue configuration for a specified port.

 

Example

This command enters tx-queue configuration mode for transmit queue 3 of interface ethernet 3/28. 
switch(config)# interface ethernet 3/28
switch(config-if-Et3/28)# tx-queue 3
switch(config-if-Et3/28-txq-3)#

 

Configuring the Shape Rate – Port and Transmit Queues
A port’s shape rate specifies its maximum outbound traffic bandwidth. A transmit queue’s shape rate specifies the queue’s maximum outbound bandwidth. Shape rate commands specify data rates in kbps.

 

Example

These commands configure a shape rate of 5 Gbs on interface Ethernet 3, then configure the shape rate for the following transmit queues:
  • transmit queues 0, 1, and 2: 500 Mbps.

     

  • transmit queues 3, 4, and 5: 400 Mbps.

    switch(config)# interface ethernet 3/28
switch(config-if-Et3/28)# shape rate 5000000
switch(config-if-Et3/28)# tx-queue 0
switch(config-if-Et3/28-txq-0)# shape rate 500000
switch(config-if-Et3/28-txq-0)# tx-queue 1
switch(config-if-Et3/28-txq-1)# shape rate 500000
switch(config-if-Et3/28-txq-1)# tx-queue 2
switch(config-if-Et3/28-txq-2)# shape rate 500000
switch(config-if-Et3/28-txq-5)# tx-queue 3
switch(config-if-Et3/28-txq-3)# shape rate 400000
switch(config-if-Et3/28-txq-3)# tx-queue 4
switch(config-if-Et3/28-txq-4)# shape rate 400000
switch(config-if-Et3/28-txq-4)# tx-queue 5
switch(config-if-Et3/28-txq-5)# shape rate 400000
switch(config-if-Et3/28-txq-5)# show qos interface ethernet 3/28
Ethernet3/28:

   Port shaping rate: 5000000Kbps

   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
   -----------------------------------------------
          7         N/A     disabled        strict
          6         N/A     disabled        strict
          5         N/A       400000        strict
          4         N/A       400000        strict
          3         N/A       400000        strict
          2         N/A       500000        strict
          1         N/A       500000        strict
          0         N/A       500000        strict

switch(config-if-Et3/28-txq-5)#

     

Configuring Queue Priority
The priority (Petra) command configures a transmit queue’s priority type:
  • The priority strict command configures the queue as a strict priority queue.

     

  • The no priority command configures the queue as a round robin queue.

     

A queue’s configuration as round robin also applies to all lower priority queues regardless of other configuration statements.

The bandwidth percent (Petra) command configures a round robin queue’s bandwidth share. The cumulative operational bandwidth of all round robin queues is always less than or equal to 100%. If the cumulative configured bandwidth is greater than 100%, each port’s operational bandwidth is its configured bandwidth divided by the cumulative configured bandwidth.

 

Examples
  • These commands configure transmit queue 3 (on interface Ethernet 3/28) as a round robin queue, then allocates 10%, 20%, 30%, and 40% bandwidth to queues 0 through 3.
    The no priority statement for queue 3 also configures queues 0, 1, and 2 as round robin queues. Removing this statement reverts the other queues to strict priority type unless running-config contains a no priority statement for one of these queues. 
    switch(config-if-Et3/28)# tx-queue 3
switch(config-if-Et3/28-txq-3)# no priority
switch(config-if-Et3/28-txq-3)# bandwidth percent 40
switch(config-if-Et3/28-txq-3)# tx-queue 2
switch(config-if-Et3/28-txq-2)# bandwidth percent 30
switch(config-if-Et3/28-txq-2)# tx-queue 1
switch(config-if-Et3/28-txq-1)# bandwidth percent 20
switch(config-if-Et3/28-txq-1)# tx-queue 0
switch(config-if-Et3/28-txq-0)# bandwidth percent 10
switch(config-if-Et3/28-txq-0)# show qos interface ethernet 3/28
Ethernet3/28:

   Port shaping rate: 5000000Kbps

   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
   -----------------------------------------------
          7         N/A     disabled        strict
          6         N/A     disabled        strict
          5         N/A       400000        strict
          4         N/A       400000        strict
          3          40       400000   round-robin
          2          30       500000   round-robin
          1          20       500000   round-robin
          0          10       500000   round-robin

switch(config-if-Et3/28-txq-0)#

     

  • Changing the bandwidth percentage for queue 3 to 60 changes the operational bandwidth of each queue to its configured bandwidth divided by 120% (10%+20%+30%+60%). 
    switch(config-if-Et3/28-txq-0)# tx-queue 3
switch(config-if-Et3/28-txq-3)# bandwidth percent 60
switch(config-if-Et3/28-txq-3)# show qos interface ethernet 3/28
Ethernet3/28:

   Port shaping rate: 5000000Kbps

   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
   -----------------------------------------------
          7         N/A     disabled        strict
          6         N/A     disabled        strict
          5         N/A       400000        strict
          4         N/A       400000        strict
          3          49       400000   round-robin
          2          24       500000   round-robin
          1          16       500000   round-robin
          0           8       500000   round-robin
switch(config-if-Et3/28-txq-3)#

     

Multicast Egress Scheduling

Multicast traffic is not affected by traffic class assignment or port shaping statements. Multicast traffic is assigned to port egress queues based on traffic class and uses strict priority to schedule egress between the high and low queues.

QoS Configuration: Trident and Tomahawk Platform Switches

Implementing QoS on a Trident and Tomahawk platform switch consists of configuring port trust settings, default port settings, default traffic classes, conversion maps, and transmit queues.

CoS and DSCP Port Settings – Trident and Tomahawk Platform Switches

Configuring Port Trust Settings

The qos trust command configures the QoS port trust mode for the configuration mode interface. Trust-enabled ports use packet CoS or DSCP values to classify traffic. The port-trust default for switched ports is CoS. The port-trust default for routed ports is DSCP.
  • qos trust cos specifies CoS as the port’s trust mode.

     

  • qos trust dscp specifies DSCP as the port’s trust mode.

     

  • no qos trust specifies untrusted as the port’s trust mode.

     

The show qos interfaces trust command displays the trust mode of specified interfaces.

 

Example

  • These commands configure and display the following trust modes:

    • Ethernet 15: dscp
    • Ethernet 16: untrusted
    • Ethernet 17: cos
    • Ethernet 18: default as a switched port
    • interface ethernet 19: default as a routed port 
      switch(config)# interface ethernet 15
switch(config-if-Et15)# qos trust dscp
switch(config-if-Et15)# interface ethernet 16
switch(config-if-Et16)# no qos trust
switch(config-if-Et16)# interface ethernet 17
switch(config-if-Et17)# qos trust cos
switch(config-if-Et17)# interface ethernet 18
switch(config-if-Et18)# switchport
switch(config-if-Et18)# default qos trust
switch(config-if-Et18)# interface ethernet 19
switch(config-if-Et19)# no switchport
switch(config-if-Et19)# default qos trust
switch(config-if-Et19)# show qos interface ethernet 15 - 19 trust
Port                                       Trust Mode
                               Operational           Configured
---------------------------------------------------------------
Ethernet15                     DSCP                  DSCP
Ethernet16                     UNTRUSTED             UNTRUSTED
Ethernet17                     COS                   COS
Ethernet18                     COS                   DEFAULT
Ethernet19                     DSCP                  DEFAULT

switch(config-if-Et19)#

       

Configuring Default Port Settings

Default CoS and DSCP settings are assigned to individual port channel and Ethernet interfaces. These configuration mode interface commands specify the port’s default CoS and DSCP values.
  • qos cos configures a port’s default CoS value.

     

  • qos dscp configures a port’s default DSCP value.

     

 

Example

These commands configure default CoS (4) and DSCP (44) values on interface ethernet 7. 
switch(config)# interface ethernet 7
switch(config-if-Et7)# qos cos 4
switch(config-if-Et7)# qos dscp 44
switch(config-if-Et7)# show active
interface Ethernet7
   qos cos 4
   qos dscp 44
switch(config-if-Et7)# show qos interfaces ethernet 7
Ethernet7:
   Trust Mode: COS
   Default COS: 4
   Default DSCP: 44

switch(config-if-Et7)#

 

Traffic Class Derivations – Trident and Tomahawk Platform Switches

Traffic Classes describes traffic classes.

Traffic Class Derivation Source

The following table displays the source for deriving a data stream’s traffic class.

Table 24. Traffic Class Derivation Source: Trident and Tomahawk Platform Switches
  Untrusted CoS Trusted DSCP Trusted
Untagged Non-IP Default CoS (port) Default CoS (port) Default DSCP (port)
Untagged IP Default CoS (port) Default CoS (port) DSCP (packet)
Tagged Non-IP Default CoS (port) CoS (packet) Default DSCP (port)
Tagged IP Default CoS (port) CoS (packet) DSCP (packet)

 

CoS and DSCP Port Settings – Trident and Tomahawk Platform Switches describes the default CoS and DSCP settings for each port.

Mapping CoS to Traffic Class

The qos map cos command assigns a traffic class to a list of CoS settings. Multiple commands create a complete CoS to traffic class map. The switch uses this map to assign a traffic class to data packets on the basis of the packet’s CoS field or the port upon which it is received.

 

Example

This command assigns the traffic class 5 to the classes of service 1, 3, 5, and 7. 
switch(config)# qos map cos 1 3 5 7 to traffic-class 5
switch(config)# show qos maps
   Number of Traffic Classes supported: 8

   Cos-tc map:
     cos:  0  1  2  3  4  5  6  7
     ----------------------------
     tc:   1  5  2  5  4  5  6  5

switch(config)#

 

The following table displays the default CoS–traffic class map on Trident and Tomahawk platform switches.

Table 25. Default CoS to Traffic Class Map: Trident II Platform Switches
Inboun CoS 0 1 2 3 4 5 6 7
Traffic Class 1 0 2 3 4 5 6 7

 

Mapping DSCP to Traffic Class

The qos map dscp command assigns a traffic class to a set of DSCP values. Multiple commands create a complete DSCP to traffic class map. The switch uses this map to assign a traffic class to data packets on the basis of the packet’s DSCP field or the chip upon which it is received.

 

Example

This command assigns the traffic class 0 to DSCP values of 12, 24, 41, and 44-47. 
switch(config)# qos map dscp 12 24 41 44 45 46 47 to traffic-class 0
switch(config)# show qos maps
   Number of Traffic Classes supported: 8

   Dscp-tc map:
     d1 :  d2 0  1  2  3  4  5  6  7  8  9
     --------------------------------------
      0 :     1  1  1  1  1  1  1  1  0  0
      1 :     0  0  0  0  0  0  2  2  2  2
      2 :     2  2  2  2  0  3  3  3  3  3
      3 :     3  3  4  4  4  4  4  4  4  4
      4 :     5  0  5  5  0  0  0  0  6  6
      5 :     6  6  6  6  6  6  7  7  7  7
      6 :     7  7  7  7

switch(config)#

 

The following table displays the default DSCP–traffic class map on Trident and Tomahawk platform switches.

Table 26. Default DSCP to Traffic Class Map: Trident and Tomahawk Platform Switches
Inbound DSCP 0-7 8-15 16-23 24-31 32-39 40-47 48-55 56-63
Traffic Class 1 0 2 3 4 5 6 7

 

CoS and DSCP Rewrite – Trident and Tomahawk Platform Switches

Rewriting CoS and DSCP describes the CoS and DSCP rewrite functions.

Traffic Class to CoS Rewrite Map

The CoS rewrite value is configurable and based on a data stream’s traffic class, as specified by the traffic class-CoS rewrite map. The qos map traffic-class to cos command assigns a CoS rewrite value to a list of traffic classes. Multiple commands create the complete traffic class–CoS rewrite map.

 

Example

This command assigns the CoS 2 to traffic classes 1, 3, and 5. 
switch(config)# qos map traffic-class 1 3 5 to cos 2
switch(config)# show qos map
   Number of Traffic Classes supported: 8

   Tc-cos map:
     tc:   0  1  2  3  4  5  6  7
     ----------------------------
     cos:  1  2  2  2  4  2  6  7

switch(config)#

 

The following table displays the default Traffic Class to CoS rewrite value map on Trident and Tomahawk platform switches.

Table 27. Default Traffic Class to CoS Rewrite Value Map: Trident and Tomahawk Platform Switches
Traffic Class 0 1 2 3 4 5 6 7
CoS Rewrite Value 1 0 2 3 4 5 6 7

 

Traffic Class to DSCP Rewrite Map

The DSCP rewrite value is configurable and based on a data stream’s traffic class, as specified by the traffic class-DSCP rewrite map. The qos map traffic-class to dscp command assigns a DSCP rewrite value to a list of traffic classes. Multiple commands create the complete traffic class-DSCP rewrite map.

 

Example

This command assigns the DSCP value of 29 to traffic classes 2, 4, and 6. 
switch(config)# qos map traffic-class 2 4 6 to dscp 29
switch(config)# show qos map
   Number of Traffic Classes supported: 8

   Tc-dscp map:
     tc:    0  1  2  3  4  5  6  7
     -----------------------------
     dscp:  8  0 29 24 29 40 29 56

switch(config)#

 

The following displays the default traffic class to DSCP rewrite map on Trident and Tomahawk platform switches.

Table 28. Traffic Class to DSCP Rewrite Value Map: Trident and Tomahawk Platform Switches

Traffic Class

0

1

2

3

4

5

6

7

DSCP

8

0

16

24

32

40

48

56

 

Transmit Queues and Port Shaping – Trident and Tomahawk Platform Switches

Transmit Queues and Port Shaping describes transmit queues and port shaping.

Trident and Tomahawk platform switches define 12 transmit queues: eight unicast (UC0 – UC7) and four multicast (MC0 – MC03). The traffic class–transmit queue maps are configured globally and apply to all Ethernet interfaces. The show qos maps command displays the traffic class–transmit queue maps.

The following table displays the default traffic class–transmit queue maps.

Table 29. Default Traffic Class to Transmit Queue Map: Trident and Tomahawk Platform Switches
Traffic Class 0 1 2 3 4 5 6 7
Unicast Transmit Queue 0 1 2 3 4 5 6 7
Multicast Transmit Queue 0 0 1 1 2 2 3 3

 

Mapping Traffic Classes to a Transmit Queue

These commands assign traffic classes to a transmit queue:

Multiple commands create the complete maps.

 

Example

These commands assign the following on interface ethernet 7:
  • traffic classes 1, 3, and 5 to unicast queue 1
  • traffic classes 2, 4, and 6 to unicast queue 5
  • traffic classes 1, 2, and 3 to multicast queue 1
  • traffic classes 4, 5, and 6 to multicast queue 3
  • traffic class 0 to unicast queue 0 and multicast queue 0 
    switch(config)# default interface ethernet 7
switch(config)# qos map traffic-class 1 3 5 to uc-tx-queue 1
switch(config)# qos map traffic-class 2 4 6 to uc-tx-queue 5
switch(config)# qos map traffic-class 1 2 3 to mc-tx-queue 1
switch(config)# qos map traffic-class 4 5 6 to mc-tx-queue 3
switch(config)# qos map traffic-class 0 to uc-tx-queue 0
switch(config)# qos map traffic-class 0 to mc-tx-queue 0
switch(config)# show qos maps
   Number of Traffic Classes supported: 8
   Number of Transmit Queues supported: 12

   Tc - uc-tx-queue map:
     tc:           0  1  2  3  4  5  6  7
     ------------------------------------
     uc-tx-queue:  0  1  5  1  5  1  5  7

   Tc - mc-tx-queue map:
     tc:           0  1  2  3  4  5  6  7
     ------------------------------------
     mc-tx-queue:  0  1  1  1  3  3  3  3

switch(config)#

     

Entering a Transmit Queue Configuration Mode

Transmit queues are configurable on individual Ethernet ports. Parameters for individual transmit queues are configured in one of two transmit queue configuration modes. Transmit queue modes are accessed from an interface-ethernet configuration mode.
  • uc-tx-queue places the switch in uc-tx-queue mode to configure a unicast transmit queue.

     

  • mc-tx-queue places the switch in mc-tx-queue mode to configure a multicast transmit queue.

     

The show qos interfaces displays the transmit queue configuration for a specified port.

 

Examples
  • This command enters the mode that configures unicast transmit queue 3 of interface ethernet 5. 
    switch(config)# interface ethernet 5
switch(config-if-Et5)# uc-tx-queue 3
switch(config-if-Et5-uc-txq-3)#

     

  • This command enters the mode to configure multicast transmit queue 3 of interface ethernet 5. 
    switch(config-if-Et5)# mc-tx-queue 2
switch(config-if-Et5-mc-txq-2)#

     

Configuring the Shape Rate – Port and Transmit Queues

A port’s shape rate specifies the port’s maximum outbound traffic bandwidth. A shape rate can also be configured for all transmit queues on each port. All shape rate commands use kbps to specify data rates.

 

Example

These commands configure a shape rate of 5 Gbs on interface Ethernet 7, then configure the shape rate for the following transmit queues:
  • unicast transmit queues 0 and 1: 500 Mbps.
  • unicast transmit queues 3 and 4: 400 Mbps.
  • multicast transmit queues 0 and 2: 300 Mbps. 
    switch(config)# interface ethernet 7
switch(config-if-Et7)# shape rate 5000000
switch(config-if-Et7)# uc-tx-queue 0
switch(config-if-Et7-uc-txq-0)# shape rate 500000
switch(config-if-Et7-uc-txq-0)# uc-tx-queue 1
switch(config-if-Et7-uc-txq-1)# shape rate 500000
switch(config-if-Et7-uc-txq-1)# uc-tx-queue 3
switch(config-if-Et7-uc-txq-3)# shape rate 400000
switch(config-if-Et7-uc-txq-3)# uc-tx-queue 5
switch(config-if-Et7-uc-txq-5)# shape rate 400000
switch(config-if-Et7-uc-txq-5)# mc-tx-queue 0
switch(config-if-Et7-mc-txq-0)# shape rate 300000
switch(config-if-Et7-mc-txq-0)# mc-tx-queue 2
switch(config-if-Et7-mc-txq-2)# shape rate 300000
switch(config-if-Et7-mc-txq-2)# exit
switch(config-if-Et7)# show qos interface ethernet 7
Ethernet7:

   Port shaping rate: 5000000Kbps

   Tx-Queue   Bandwidth    Shape Rate     Priority   Priority Group
              (percent)       (Kbps)
   ----------------------------------------------------------------
        UC7         N/A     disabled        strict                1
        UC6         N/A     disabled        strict                1
        MC3         N/A     disabled        strict                1
        UC5         N/A       400000        strict                0
        UC4         N/A     disabled        strict                0
        MC2         N/A       300000        strict                0
        UC3         N/A       400000        strict                0
        UC2         N/A     disabled        strict                0
        MC1         N/A     disabled        strict                0
        UC1         N/A       500000        strict                0
        UC0         N/A       500000        strict                0
        MC0         N/A       300000        strict                0

switch(config-if-Et7)#

     

Configuring Queue Priority

Trident and Tomahawk platform switch queues are categorized into two priority groups. Priority group 1 queues have priority over priority 0 queues. The following lists display the priority group queues in order from higher priority to lower priority.
  • Priority Group 1: UC7, UC6, MC3

     

  • Priority Group 0: UC5, UC4, MC2, UC3, UC2, MC1, UC1, UC0, MC0

     

The priority (Trident and Tomahawk) command configures a transmit queue’s priority type:
  • The priority strict command configures the queue as a strict priority queue.

     

  • The no priority command configures the queue as a round robin queue.

     

A queue’s configuration as round robin also applies to all lower priority queues regardless of other configuration statements.

The bandwidth percent (Trident and Tomahawk) command configures a round robin queue’s bandwidth share. The cumulative operational bandwidth of all round robin queues is always 100%. If the cumulative configured bandwidth is greater than 100%, each port’s operational bandwidth is its configured bandwidth divided by the cumulative configured bandwidth.

Priority Group 1 queues (UC7, UC6, MC3) are not configurable as round robin queues. The bandwidth percent command is not available for these queues.

 

Examples
  • These commands configure unicast transmit queue 3 as a round robin queue, then allocates 5%, 15%, 25%, 35%, 8%, and 12% bandwidth to unicast transmit queues 0 through 3 and multicast transmit queues 0 and 1, respectively.
    The no priority statement for queue 3 also configures priority for all lower priority queues. Removing the statement reverts the other queues to strict priority type unless running-config contains a no priority statement for one of these queues. 
    switch(config)# interface ethernet 7
switch(config-if-Et7)# uc-tx-queue 3
switch(config-if-Et7-uc-txq-3)# no priority
switch(config-if-Et7-uc-txq-3)# bandwidth percent 5
switch(config-if-Et7-uc-txq-3)# uc-tx-queue 2
switch(config-if-Et7-uc-txq-2)# bandwidth percent 15
switch(config-if-Et7-uc-txq-2)# uc-tx-queue 1
switch(config-if-Et7-uc-txq-1)# bandwidth percent 25
switch(config-if-Et7-uc-txq-1)# uc-tx-queue 0
switch(config-if-Et7-uc-txq-0)# bandwidth percent 35
switch(config-if-Et7-uc-txq-0)# mc-tx-queue 1
switch(config-if-Et7-mc-txq-1)# bandwidth percent 12
switch(config-if-Et7-mc-txq-1)# mc-tx-queue 0
switch(config-if-Et7-mc-txq-0)# bandwidth percent 8
switch(config-if-Et7-mc-txq-0)# show qos interface ethernet 7
Ethernet7:

   Port shaping rate: disabled

   Tx-Queue   Bandwidth    Shape Rate     Priority   Priority Group
              (percent)       (Kbps)
   ----------------------------------------------------------------
        UC7         N/A     disabled        strict                1
        UC6         N/A     disabled        strict                1
        MC3         N/A     disabled        strict                1
        UC5         N/A     disabled        strict                0
        UC4         N/A     disabled        strict                0
        MC2         N/A     disabled        strict                0
        UC3           5     disabled   round-robin                0
        UC2          15     disabled   round-robin                0
        MC1          12     disabled   round-robin                0
        UC1          25     disabled   round-robin                0
        UC0          35     disabled   round-robin                0
        MC0           8     disabled   round-robin                0

switch(config-if-Et7-mc-txq-0)#

     

  • Changing the bandwidth percentage for unicast queue 3 to 30 changes the operational bandwidth of each queue to its configured bandwidth divided by 125% (8%+12%+30%+15%+25%+35%). 
    switch(config-if-Et7-uc-txq-0)# uc-tx-queue 3
switch(config-if-Et7-uc-txq-3)# bandwidth percent 30
switch(config-if-Et7-uc-txq-3)# show qos interface ethernet 7
Ethernet7:

   Port shaping rate: disabled

   Tx-Queue   Bandwidth    Shape Rate     Priority   Priority Group
              (percent)       (Kbps)
   ----------------------------------------------------------------
        UC7         N/A     disabled        strict                1
        UC6         N/A     disabled        strict                1
        MC3         N/A     disabled        strict                1
        UC5         N/A     disabled        strict                0
        UC4         N/A     disabled        strict                0
        MC2         N/A     disabled        strict                0
        UC3          24     disabled   round-robin                0
        UC2          12     disabled   round-robin                0
        MC1           9     disabled   round-robin                0
        UC1          20     disabled   round-robin                0
        UC0          28     disabled   round-robin                0
        MC0           6     disabled   round-robin                0

switch(config-if-Et7-uc-txq-3)#

     

ECN Configuration – Trident and Tomahawk Platform Switches

ECN is independently configurable on all egress queues of each Ethernet interface. ECN settings for Port-Channels are applied on each of the channel’s member Ethernet interfaces. ECN is also globally configurable to mark packets from the shared pool used for dynamically allocating memory to the queues. Multicast packets contribute to the globally shared pool and can contribute to global level congestion that result in ECN marking of unicast packets queued after the multicast packets.

Average queue length is tracked for transmit queues and the global pool independently. When either entity reaches its maximum threshold, all subsequent packets are marked.

Although the switch does not limit the number of queues that can be configured for ECN, hardware table limitations restrict the number of queues (including the global shared pool) that can simultaneously implement ECN.

The qos random-detect ecn global-buffer (Trident and Tomahawk) command enables ECN marking for globally shared packet memory and specifies minimum and maximum queue threshold sizes.

 

Examples
  • This command enables ECN marking of unicast packets from the global data pool and sets the minimum and maximum thresholds at 20 and 500 segments. 
    switch(config)# qos random-detect ecn global-buffer minimum-threshold 20 segments 
maximum-threshold 500 segments
switch(config)#

     

  • This command disables ECN marking of unicast packets from the global data pool. 
    switch(config)# no qos random-detect ecn global-buffer
switch(config)#

     

    The random-detect ecn (Trident and Tomahawk) command enables ECN marking for the configuration mode unicast transmit queue and specifies threshold queue sizes.

     

  • These commands enable ECN marking of unicast packets from transmit queue 4 of interface Ethernet 15, setting thresholds at 10 and 100 segments. 
    switch(config)# interface ethernet 15
switch(config-if-Et15)# uc-tx-queue 4
switch(config-if-Et15-uc-txq-4)# random-detect ecn minimum-threshold 10 segments 
maximum-threshold 100 segments
switch(config-if-Et15-uc-txq-4)# show active
interface Ethernet15
   uc-tx-queue 4
      random-detect ecn minimum-threshold 10 segments maximum-threshold 100 
segments
switch(config-if-Et15-uc-txq-4)# exit
switch(config-if-Et15)#

     

  • This command disables ECN marking of unicast packets from transmit queue 4 of interface Ethernet 15. 
    switch(config-if-Et15-uc-txq-4)# no random-detect ecn
switch(config-if-Et15-uc-txq-4)# show active
interface Ethernet15
switch(config-if-Et15-uc-txq-4)# exit
switch(config-if-Et15)#

     

QoS Configuration: Trident II and Helix Platform Switches

Implementing QoS on a Trident platform switch consists of configuring port trust settings, default port settings, default traffic classes, conversion maps, and transmit queues.

CoS and DSCP Port Settings – Trident II and Helix Platform Switches

Configuring Port Trust Settings

The qos trust command configures the QoS port trust mode for the configuration mode interface. Trust enabled ports use packet CoS or DSCP values to classify traffic. The port-trust default for switched ports is cos. The port-trust default for routed ports is dscp.
  • qos trust cos specifies cos as the port’s port-trust mode.

     

  • qos trust dscp specifies dscp as the port’s port-trust mode.

     

  • no qos trust specifies untrusted as the port’s port-trust mode.

     

The show qos interfaces trust command displays the trust mode of specified interfaces.

 

Example

These commands configure and display the following trust modes:
  • Ethernet 7/1: dscp.
  • Ethernet 7/2: untrusted.
  • Ethernet 7/3: cos.
  • Ethernet 7/4: default as a switched port.
  • Ethernet 8/1: default as a routed port. 
    switch(config)# interface ethernet 7/1
switch(config-if-Et7/1)# qos trust dscp
switch(config-if-Et7/1)# interface ethernet 7/2
switch(config-if-Et7/2)# no qos trust
switch(config-if-Et7/2)# interface ethernet 7/3
switch(config-if-Et7/3)# qos trust cos
switch(config-if-Et7/3)# interface ethernet 7/4
switch(config-if-Et7/4)# switchport
switch(config-if-Et7/4)# default qos trust
switch(config-if-Et7/4)# interface ethernet 8/1
switch(config-if-Et8/1)# no switchport
switch(config-if-Et8/1)# default qos trust
switch(config-if-Et8/1)# show qos interface ethernet 7/1 - 8/1 trust

Port                                       Trust Mode
                               Operational           Configured
---------------------------------------------------------------
Ethernet7/1                    DSCP                  DSCP
Ethernet7/2                    UNTRUSTED             UNTRUSTED
Ethernet7/3                    COS                   COS
Ethernet7/4                    COS                   DEFAULT
Ethernet8/1                    DSCP                  DEFAULT

switch(config-if-Et8/1)#

     

Configuring Default Port Settings

Default CoS and DSCP settings are assigned to individual port channel and Ethernet interfaces. These configuration mode interface commands specify the port’s default CoS and DSCP values.
  • qos cos configures a port’s default CoS value.

     

  • qos dscp configures a port’s default DSCP value.

     

Example

These commands configure default CoS 4 and DSCP 44 values on interface ethernet 7/3. 
switch(config)# interface ethernet 7/3
switch(config-if-Et7/3)# qos cos 4
switch(config-if-Et7/3)# qos dscp 44
switch(config-if-Et7/3)# show active

interface Ethernet7/3
   qos cos 4
   qos dscp 44

switch(config-if-Et7/3)# show qos interfaces ethernet 7/3

Ethernet7/3:
   Trust Mode: COS
   Default COS: 4
   Default DSCP: 44

switch(config-if-Et7/3)#

 

Traffic Class Derivations – Trident II and Helix Platform Switches

Traffic Classes describes traffic classes.

 

Note: QoS traffic policy is supported on Trident II platform switches.

 

Traffic Class Derivation Source

The following table displays the source for deriving a data stream’s traffic class.

Table 30. Traffic Class Derivation Source: Trident II Platform Switches
  Untrusted CoS Trusted DSCP Trusted
Untagged Non-IP Default CoS (port) Default CoS (port) Default DSCP (port)
Untagged IP Default CoS (port) Default CoS (port) DSCP (packet)
Tagged Non-IP Default CoS (port) CoS (packet) Default DSCP (port)
Tagged IP Default CoS (port) CoS (packet) DSCP (packet)

 

CoS and DSCP Port Settings – Trident II and Helix Platform Switches describes the default CoS and DSCP settings for each port.

Mapping CoS to Traffic Class

The qos map cos command assigns a traffic class to a list of CoS settings. Multiple commands create a complete CoS to traffic class map. The switch uses this map to assign a traffic class to data packets on the basis of the packet’s CoS field or the port upon which it is received.

 

Example

This command assigns the traffic class 5 to the classes of service 1, 3, 5, and 7. 
switch(config)# qos map cos 1 3 5 7 to traffic-class 5
switch(config)# show qos maps
   Number of Traffic Classes supported: 8

   Cos-tc map:
     cos:  0  1  2  3  4  5  6  7
     ----------------------------
     tc:   1  5  2  5  4  5  6  5

switch(config)#

 

The following table displays the default CoS–traffic class map on Trident II platform switches.

Table 31. Default CoS to Traffic Class Map: Trident II Platform Switches
Inbound CoS 0 1 2 3 4 5 6 7
Traffic Class 1 0 2 3 4 5 6 7

 

Mapping DSCP to Traffic Class

The qos map dscp command assigns a traffic class to a set of DSCP values. Multiple commands create a complete DSCP to traffic class map. The switch uses this map to assign a traffic class to data packets on the basis of the packet’s DSCP field or the chip upon which it is received.

 

Example

This command assigns the traffic class 0 to DSCP values of 12, 24, 41, and 44-47. 
switch(config)# qos map dscp 12 24 41 44 45 46 47 to traffic-class 0
switch(config)# show qos maps                 
   Number of Traffic Classes supported: 8

   Dscp-tc map:
     d1 :  d2 0  1  2  3  4  5  6  7  8  9
     --------------------------------------
      0 :     1  1  1  1  1  1  1  1  0  0
      1 :     0  0  0  0  0  0  2  2  2  2
      2 :     2  2  2  2  0  3  3  3  3  3
      3 :     3  3  4  4  4  4  4  4  4  4
      4 :     5  0  5  5  0  0  0  0  6  6
      5 :     6  6  6  6  6  6  7  7  7  7
      6 :     7  7  7  7

switch(config)#

 

The following table displays the default DSCP–traffic class map on Trident II platform switches.

Table 32. Default DSCP to Traffic Class Map: Trident II Platform Switches
Inbound DSCP 0-7 8-15 16-23 24-31 32-39 40-47 48-55 56-63
Traffic Class 1 0 2 3 4 5 6 7

 

CoS and DSCP Rewrite – Trident II and Helix Platform Switches

Rewriting CoS and DSCP describes the CoS and DSCP rewrite functions.

Traffic Class to CoS Rewrite Map

The CoS rewrite value is configurable and based on a data stream’s traffic class, as specified by the traffic class-CoS rewrite map. The qos map traffic-class to cos command assigns a CoS rewrite value to a list of traffic classes. Multiple commands create the complete traffic class–CoS rewrite map.

 

Example

This command assigns the CoS of two to traffic classes 1, 3, and 5. 
switch(config)# qos map traffic-class 1 3 5 to cos 2
switch(config)#show qos map

   Number of Traffic Classes supported: 8

   Tc-cos map:
     tc:   0  1  2  3  4  5  6  7
     ----------------------------
     cos:  1  2  2  2  4  2  6  7

switch(config)#

 

The following tabledisplays the default Traffic Class to CoS rewrite value map on Trident II platform switches.

Table 33. Default Traffic Class to CoS Rewrite Value Map: Trident II Platform Switches
Traffic Class 0 1 2 3 4 5 6 7
CoS Rewrite Value 1 0 2 3 4 5

6

 7

 

Traffic Class to DSCP Rewrite Map

The DSCP rewrite value is configurable and based on a data stream’s traffic class, as specified by the traffic class-DSCP rewrite map. The qos map traffic-class to dscp command assigns a DSCP rewrite value to a list of traffic classes. Multiple commands create the complete traffic class-DSCP rewrite map.

 

Example

This command assigns the DSCP value of 29 to traffic classes 2, 4, and 6. 
switch(config)# qos map traffic-class 2 4 6 to dscp 29
switch(config)# show qos map

   Number of Traffic Classes supported: 8

   Tc-dscp map:
     tc:    0  1  2  3  4  5  6  7
     -----------------------------
     dscp:  8  0 29 24 29 40 29 56

switch(config)#

 

The following table displays the default traffic class to DSCP rewrite map on Trident II platform switches.

Table 34. Traffic Class to DSCP Rewrite Value Map: Trident II Platform Switches
Traffic Class 0 1 2 3 4 5 6 7
DSCP 8 0 16 24 32 40 48 56

 

Transmit Queues and Port Shaping – Trident II and Helix Platform Switches

Transmit Queues and Port Shaping describes transmit queues and port shaping.

A data stream’s traffic class determines the transmit queue it uses. The switch defines a single traffic class-transmit queue map for all Ethernet interfaces and is used for unicast and multicast traffic. The traffic class to transmit queue maps are configured globally and apply to all Ethernet and port channel interfaces. The show qos maps command displays the traffic class to transmit queue map.

Trident II platform switches have eight unicast (UC0 – UC7) and eight multicast (MC0 – MC7) queues. Each UCx-MCx queue set is combined into a single queue group (L1.x), which is exposed to the CLI through this command.

The following table displays the default traffic class to transmit queue maps.

Table 35. Default Traffic Class to Transmit Queue Map: Trident II Platform Switches
Traffic Class 0 1 2 3 4 5 6 7
Transmit Queue Group 0 1 2 3 4 5 6 7

 

Mapping Traffic Classes to a Transmit Queue

The qos map traffic-class to tx-queue command assigns traffic classes to a transmit queue. Multiple commands create the complete map.

 

Example

These commands assign traffic classes of 1, 3, and 5 to transmit queue 1, traffic classes 2, 4, and 6 to transmit queue 2, and traffic class 0 to transmit queue 0, then display the resultant map. 
switch(config)# qos map traffic-class 1 3 5 to tx-queue 1
switch(config)# qos map traffic-class 2 4 6 to tx-queue 2
switch(config)# qos map traffic-class 0 to tx-queue 0
switch(config)# show qos maps
   Number of Traffic Classes supported: 8
   Number of Transmit Queues supported: 8

   Tc - tx-queue map:
     tc:        0  1  2  3  4  5  6  7
     ---------------------------------
     tx-queue:  0  1  2  1  2  1  2  7

switch(config)#

 

Entering a Transmit Queue Configuration Mode

Transmit queues are configurable on Ethernet ports and port channels. Queue parameters are configured in tx-queue configuration command mode, which is entered from the appropriate interface configuration mode. The tx-queue (Trident II) command places the switch in tx-queue configuration mode. The show qos interfaces displays the transmit queue configuration for a specified port.

 

Example

This command enters tx-queue configuration mode for transmit queue 3 of interface ethernet 5. 
switch(config)# interface ethernet 5
switch(config-if-Et5)# tx-queue 3
switch(config-if-Et5-txq-3)#

 

Configuring the Shape Rate – Port and Transmit Queues

A port’s shape rate specifies the port’s maximum outbound traffic bandwidth. A shape rate can also be configured for all transmit queues on each port. All shape rate commands use kbps to specify data rates.

Example

These commands configure a shape rate of 5 Gbs on interface Ethernet 3, then configure the shape rate for the following transmit queues:
    • transmit queues 0, 1, and 2: 500 Mbps

    • transmit queues 3, 4, and 5: 400 Mbps

      switch(config)# interface ethernet 17/3
switch(config-if-Et17/3)# shape rate 5000000
switch(config-if-Et17/3)# tx-queue 0
switch(config-if-Et17/3-txq-0)# shape rate 500000
switch(config-if-Et17/3-txq-0)# tx-queue 1
switch(config-if-Et17/3-txq-1)# shape rate 500000
switch(config-if-Et17/3-txq-1)# tx-queue 3
switch(config-if-Et17/3-txq-3)# shape rate 400000
switch(config-if-Et17/3-txq-3)# tx-queue 4
switch(config-if-Et17/3-txq-4)# shape rate 400000
switch(config-if-Et17/3-txq-4)# tx-queue 5
switch(config-if-Et17/3-txq-5)# shape rate 400000
switch(config-if-Et17/3-txq-5)# exit
switch(config-if-Et17/3)# show qos interface ethernet 17/3
Ethernet17/3:

  Tx       Bandwidth                 Shape Rate        Priority
 Queue     Guaranteed (units)         (units)
   ------------------------------------------------------------
   7        - / -    (  -  )       - / -    (  -  )    SP / SP
   6        - / -    (  -  )       - / -    (  -  )    SP / SP
   5        - / -    (  -  )     400 / 400  ( Mbps )   SP / SP
   4        - / -    (  -  )     400 / 400  ( Mbps )   SP / SP
   3        - / -    (  -  )     400 / 400  ( Mbps )   SP / SP
   2        - / -    (  -  )       - / -    (  -  )    SP / SP
   1        - / -    (  -  )     500 / 500  ( Mbps )   SP / SP
   0        - / -    (  -  )     500 / 500  ( Mbps )   SP / SP

switch(config-if-Et17/3)#

       

Configuring Queue Priority

Queue priority rank is denoted by the queue number; transmit queues with higher numbers have higher priority. Trident II supports strict priority queues; round robin queues are not supported.

The bandwidth guaranteed (Trident II) command configures specifies the minimum bandwidth for outbound traffic on the transmit queue.

 

Example

These commands configure a minimum egress bandwidth of 1 Mbps for transmit queue 4 on interface ethernet 17/3. 
switch(config-if-Et17/3)# tx-queue 4
switch(config-if-Et17/3-txq-4)# show qos interface ethernet 17/3

  Tx       Bandwidth                 Shape Rate        Priority
 Queue     Guaranteed (units)         (units)
   ------------------------------------------------------------
   7        - / -    (  -  )       - / -    (  -  )    SP / SP
   6        - / -    (  -  )       - / -    (  -  )    SP / SP
   5        - / -    (  -  )     400 / 400  ( Mbps )   SP / SP
   4        1 / 1    ( Mbps )    400 / 400  ( Mbps )   SP / SP
   3        - / -    (  -  )     400 / 400  ( Mbps )   SP / SP
   2        - / -    (  -  )       - / -    (  -  )    SP / SP
   1        - / -    (  -  )     500 / 500  ( Mbps )   SP / SP
   0        - / -    (  -  )     500 / 500  ( Mbps )   SP / SP

switch(config-if-Et17/3-txq-4)#

 

Ingress Policing on LAG

Ingress policing on a port-channel polices the matched traffic from all member interfaces combined, i.e. it provides aggregate policing and statistics (DCS-7050X, DCS-7010T, DCS-7250X, and DCS-7300X series). When a per-interface policer is attached to a port-channel, one set of TCAM entries is created for all member interfaces. The associated interface bitmap is updated, and aggregate policing is performed on all member interfaces.

 

Examples
  • These commands configure a service-policy (with policer action) on LAG by creating the service-policy and applying the service-policy on a port-channel. 
    switch(config)# policy-map policy-1
switch(config-pmap-qos-policy-1)# class class-1
switch(config-pmap-c-qos-policy-1-class-1)# police cir 512000 bps bc 96000
switch(config-pmap-c-qos-policy-1-class-1)# exit
switch(config-pmap-qos-policy-1)# exit
switch(config)# interface Et 4 / 5 / 4
switch(config-if-Et4/5/4)# channel-group 2 mode active
switch(config-if-Et4/5/4)# exit
switch(config)# interface po2
switch(config-if-Po2)# service-policy type qos input policy-1
switch(config-if-Po2)# exit
switch(config)#

     

  • These commands configure ACL policing in single-rate, two-color mode. 
    switch(config)# class-map type qos match-any class1
switch(config-cmap-qos-class1)# match ip access-group acl1
switch(config-cmap-qos-class1)# exit
switch(config)# policy-map type quality-of-service policy1
switch(config-pmap-qos-policy1)# class class1
switch(config-pmap-c-qos-policy1-class1)# police cir 512000 bc 96000
switch(config-pmap-c-qos-policy1-class1)# exit
switch(config-pmap-qos-policy1)# exit
switch(config)# show policy-map
Service-policy policy1

  Class-map: class1 (match-any)
    Match: ip access-group name acl1
       police rate 512000 bps burst-size 96000 bytes

  Class-map: class-default (match-any)

switch(config)#

     

Fabric QoS -- – Trident II Platform Switches

EOS is optimized to support QoS configuration on the Fabric interfaces on 7250x and 7300 series switches. Configuring QoS on the Fabric interfaces in addition to front panel ports allows user to have end-to-end control and helps to manage traffic better over these switches. By default, tx queues are configured as strict priority on 7250X and 7300X series.

The following QoS configuration options are supported on Fabric interfaces on 7250x and 7300 series switches.
  • Guaranteed Bandwidth: In order to prevent queue starvation on fabric ports EOS supports minimum bandwidth configuration on per queue basis across all fabric ports.

     

  • Explicit Congestion Notification (ECN): EOS supports enabling ECN on a per queue basis across all fabric ports.

     

  • Priority Flow Control (PFC): Queue back-pressure propagates across the backplane such that flow control messages can be generated to the upstream devices. This is done by enabling PFC for the desired backplane traffic-classes.

     

  • Weight Round Robin (WRR): EOS supports configuring Weighted Round Robin (WRR) on a per queue basis across all fabric ports.

     

Configuring Fabric QoS on 7250X and 7300X Series

Fabric QoS is configured using a QoS profiles which is then applied on fabric interfaces on 7250x and 7300x series. Following are the steps to configure Fabric QoS.

  1. Use qos profile command to create a QoS profile.
     
  2. Use tx-queue (Trident II) command to configure a transmit queue on the configuration mode interface.
     
  3. Use bandwidth guaranteed (Trident II) command to specifie the minimum bandwidth for outbound traffic on the transmit queue.
     
  4. Use random-detect ecn (Trident) command to enable the ECN marking for the configuration mode unicast transmit queue and specifies threshold queue sizes.
     
  5. Use priority-flow-control priority command to configure the packet resolution setting on the configuration mode interface.
     
  6. Use interface fabric command to configure Fabric interface.
     
  7. Use service-profile command to apply the QoS profile to the Fabric interface.

     

    Examples
    • These commands create a QoS profile named fabricProfile with tx queue, bandwidth, ECN, PFC and DLB values defined in it and then the profile is attached to Fabric interface of the switch.

       

      Note: To support PFC on a particular priority, DLB is disabled for that priority.

       

      switch(config)# qos profile fabricProfile
switch(config-qos-profile-fabricProfile)# tx-queue 0
switch(config-qos-profile-fabricProfile-txq-0)# bandwidth guaranteed 10000 kbps
switch(config-qos-profile-fabricProfile-txq-0)# random-detect ecn 
minimum-threshold 10 mbytes maximum-threshold 10 mbytes
switch(config-qos-profile-fabricProfile)# priority-flow-control priority 1 
no-drop
switch(config-qos-profile-fabricProfile)# priority-flow-control priority 6 
no-drop dlb

       

    • Applying the QoS profile on interface fabric of the switch.
    switch# configure terminal
switch(config)# interface fabric
switch(config-if-fabric)# service-profile fabricProfile

     

Displaying Fabric QoS Information

These show commands display the configured Fabric QoS information on the switch.
  • show qos profile [profile Name]: Displays the list of QoS profiles configured on the switch.

     

  • show qos interfaces fabric: Displays the profile applied on the fabric interface on the switch.

     

Examples

  • This command displays the fabricProfile profile information. 
    switch# show qos profile fabricProfile
  qos profile fabricProfile
     priority-flow-control priority 1 no-drop
     priority-flow-control priority 6 no-drop dlb
     tx-queue 0
         bandwidth guaranteed 10000 kbps
         random-detect ecn minimum-threshold 10 mbytes maximum-threshold 10 mbytes

     

  • This command displays the profile applied on the fabric interface. 
    switch# show qos interfaces fabric
   qos profile fabricProfile

     

Support for Configuring Color Extended Communities

EOS Release 4.23.1F introduces the ability to configure the color extended community in route-map set clauses and in an extcommunity-list for inbound and outbound policy application.

Use the color extended community for per-destination steering into Segment-Routing Traffic-Engineered (SR-TE) policies. If the next-hop and color of a BGP route match a particular policy (composed of an endpoint and color), any traffic bound to the destination can be steered according to the policy instead of forwarded via an IGP path or tunnel.

This section describes support for configuring color extended communities, including configuration instructions and command descriptions. Topics covered by this section include:

Platform Compatibility

Configuring color extended communities is supported on all platforms.

Configuration

Use the following command for color extended community expressions:

 

color COLOR-VALUE [color-only (exact-match | (endpoint-match (any | null)))]

 

Use this command in route-maps and extcommunity-lists to apply inbound and outbound policy.

 
Configuring Color Extended Community in route-map mode
Command(config-route-map mode) [no | default] set extcommunity COLOR-EXPRESSION [additive | delete]
Action Adds a color extended community to be applied to routes affected by the route-map. Multiple set clauses can be applied to a single route-map to configure multiple colors for routes. Additive adds the extended communities to those received, while delete deletes any matching extended color communities. Negating the command removes the entry from the route-map.
Default

None
Example 
switch(config)# route-map foo
switch(config-route-map foo)# set extcommunity color 1
switch(config-route-map foo)# set extcommunity color 2 color-only exact-match
switch(config-route-map foo)# set extcommunity color 3 color-only endpoint-match null
switch(config-route-map foo)# set extcommunity color 4 color-only endpoint-match any

 

 

 
Configuring Color Extended Community in extcommunity-list
Command(config mode) 
[(no|default)] ip extcommunity-list WORD (permit|deny){COLOR-EXPRESSION}
Action Adds a color extended community to an extcommunity-list. Multiple color extended communities can be added to the list. Negating the command removes the corresponding color extended community from the list.
Default None
Example 
switch(config)# ip extcommunity-list foo permit color 1 color 2
switch(config)# ip extcommunity-list bar permit color 3 color-only endpoint-match null color 4 color-only endpoint-match any

 

Limitations

The color extended community is only supported in multi-agent mode. Enable Multi-agent mode via the following command:

 

service routing protocols mode multi-agent

 

ACL based QoS Configuration

ACL Based QoS (DCS-7160)

The IPv4 ACL based QoS is enabled on switches through policy-map configuration. The ACL based QoS can be configured on front panel ports, port-channel interfaces on DCS-7160 series switches.

ACL based QoS on SVIs

The ACL based QoS policy applied on SVIs modify the QoS parameters for SVI traffic (L3 VLAN) based on ACL classification. The ACL based QoS on Switched Virtual Interface (SVI) ports is supported on DCS-7500E, DCS-7280E, DCS-7010, DCS-7050, DCS-7050X, DCS-7250X, DCS-7300X, DCS-7020TR.

 

ACL Sharing on QoS

The ACLs applied on QoS shares the hardware resources (TCAM) when potentially large QoS policy-maps are applied to multiple SVIs. For ACL based QoS on SVIs in sharing mode we share TCAM for class-maps without policer action and replicate entries for policer class-maps. The ACL Sharing on QoS is supported only on selected platforms.

The QoS actions is applicable only to the routed traffic flowing through the members of the corresponding VLAN.

The steps to configure ACL based QoS is as follows:

  1. Create a access list using ip access-list command.
     
  2. Create a class map and attach it to the access list using class-map command.
     
  3. Create a policy and attach the class map to the policy created, using the policy-map command.
     
  4. Apply the policy to the interface using the service-policy input command.

     

    Examples

    • These command configure the access list acl1.

      switch(config)# ip access-list acl1
switch(config-acl-acl1)# permit ip 10.1.1.1/24 any
switch(config-acl-acl1)# exit

       

    • These commands configure the class map class1.

      switch(config)# class-map match-any class1
switch(config-cmap-qos-class1)# match ip access-group acl1
switch(config-cmap-qos-class1)# exit

       

    • These commands configure the policy map policy1.

      switch(config)# policy-map policy1 
switch(config-pmap-qos-policy1)# class class1
switch(config-pmap-c-qos-policy1-class1)# set dscp 20
switch(config-pmap-c-qos-policy1-class1)# set traffic-class 2
switch(config-pmap-c-qos-policy1-class1)# exit 
switch(config-pmap-c-qos-policy1)# exit

       

    • These commands apply the policy1 to the interface ethernet 1/1.

      switch(config)# interface Et1/1
switch(config-if-Et1/1)# service-policy input policy1 
switch(config-if-Et1/1)# exit

       

    • These commands configure a ACL based QoS on the SVI interface VLAN10.

      switch(config)# interface vlan 10
switch(config-if-Vl10)# service-policy [type qos] input policy1

       

    • This command enables the resource (hardware) sharing when a ACL based QoS is attached to VLAN interface. The no form of the command disables it.

      switch(config)# hardware access-list qos resource sharing vlan in

       

    • This command allows inbound broadcast IP packets with source IP address as one of the permitted hosts and denies the rest of the directed broadcast traffic.

      switch(config)# ip directed-broadcast
 switch(config-ip-directed-broadcast)# field-set ipv4 prefix ALLOWED1
 switch(config-ipdb-field-set-ipv4-prefix-ALLOWED)# 10.1.1.1/32 20.1.1.1/32 30.1.1.1/32
 switch(config-ipdb-field-set-ipv4-prefix-ALLOWED)# commit
 
 switch(config-ip-directed-broadcast)# field-set ipv4 prefix ALLOWED2
 switch(config-ipdb-field-set-ipv4-prefix-ALLOWED)# 10.2.1.1/32 20.2.1.1/32 30.2.1.1/32
 switch(config-ipdb-field-set-ipv4-prefix-ALLOWED)# commit

       

    Show Commands

    The following show commands display the status of policy-maps programmed on the interface, for more information on these commands refer Quality of Service Commands.
    • show policy-map [policy-name]: Displays the policy-map programming status.

       

    • show policy-map interface interface id: Displays the policy-map that is currently programmed on the interface.

       

    • show policy-map [policy-name] counters: Displays the policy-map traffic hits.

       

    • show platform xp qos tcam [hits]: Displays the TCAM entries programmed for each policy-map as well as the traffic hits. The hits option is used to see the TCAM entries with nonzero traffic hits.

       

    • show run | grep sharing: Displays if whether the ACL based QoS is enabled or disabled.

       

    • show platform trident tcam shared vlan interface-class-id: Displays what SVIs are currently sharing the QoS policy-map.

       

    • show platform trident tcam directed-broadcast: Displays the permitted hosts via field-set.

       

    • show platform trident tcam qos detail: Displays the list of all the SVIs that are sharing the TCAM entries.

       

Limitations

  • Maximum number of TCAM entries that can be programmed in hardware for all QoS policy-maps on the box is 1024.

     

  • Layer 4 port ranges are not supported for ACL based QoS. The ranges will be expanded into multiple TCAM rules and programmed in the hardware.

     

  • Configured policer rate should be above 1mbps and recommended burst value is 2000 bytes.

     

  • Policer action cannot be associated with policy-maps applied to Port-Channels.

     

The following are the limitations specific to DCS-7500E, DCS-7280E and DCS-7020TR:

The user cannot apply more than 31 QoS service policies per chip on L3 interfaces.
  • When different QoS service policies are applied to the SVI and its member interfaces, the behavior is indeterministic.

     

  • When QoS service policies are applied on SVIs with partial failures due to limited hardware resources, any event that triggers a forwarding agent restart will lead to indeterministic behavior.

     

  • When QoS service policies are applied on 2 SVIs, any event that triggers the VLAN membership change of a member interface may result in a policy-map programming failure. To change the VLAN membership, remove the interface from the first VLAN and then add it to the other.

     

  • Outgoing COS rewrite is not supported.

     

  • QoS policy-map counters are not supported.

     

The following are the limitations specific to DCS-7010, DCS-7050, DCS-7050X, DCS-7250X, DCS-7300X:
  • TCAM resources will not be shared for the same policy-map applied to multiple SVIs.

     

  • Policy-map applied to a SVI will result in TCAM allocation on all chips irrespective of whether the SVI members are present or not.

     

When QoS service policies are applied to both SVI and its member interfaces and packets hit both policies, the behavior is indeterministic.

Configuring IPv6 Flow Label Matches for QoS

In addition to criteria like COS and DSCP, QoS decisions can be based on the IPv6 flow labels of packets. To use IPv6 flow labels as a criterion for QoS decisions, use the permit command to create ACL rules to select packets based on their IPv6 flow labels using an exact match and an optional mask, and then apply the access list to a class map in a QoS policy map, which can then be applied to individual interfaces. This requires a TCAM profile which must be installed explicitly.

Install the QoS Flow Label TCAM Profile

Open the QoS flow label TCAM profile Web page at https://www.arista.com/en/support/toi/tcam-profile?pn=qos-match-ipv6-flow-label. Copy the entire contents of the file which starts with the following commands: 
hardware tcam
system profile qos-match-ipv6-flow-label

 

There are approximately 130 lines.

Paste this into the CLI of the switch. Each command in the file will be executed in turn when you paste the file contents. When the paste completes, if the cursor is at the end of the last command, type enter to execute it.

Confirm the QoS Flow Label TCAM Profile Installation

Configure the TCAM with the hardware tcam command, and use the system profile command to confirm that the “qos-match-ipv6-flow-label” profile has been installed. If the profile is installed, the ? operator will show “qos-match-ipv6-flow-label” as an available profile.

 

Example

The following commands confirm whether the “qos-match-ipv6-flow-label” profile is installed and available to be applied. 
switch(config)# hardware tcam
switch(config-tcam)# system profile qos-match?
WORD  qos-match-ipv6-flow-label

switch(config-tcam)# exit
switch(config)#

 

Apply the QoS Flow Label TCAM Profile

If the profile "qos-match-ipv6-flow-label" is listed, use the system profile command to apply it. Confirm that the profile has been successfully applied with the show hardware tcam profile command.

 

Example

The following commands apply the profile “qos-match-ipv6-flow-label” to the TCAM configuration, then confirm that the profile has been applied. The warning is normal, as the restart of forwarding agents is part of the procedure.

switch(config)# hardware tcam
switch(config-tcam)# system profile qos-match-ipv6-flow-label
!
WARNING!
Changing TCAM profile will cause forwarding agent(s) to exit and restart.
All traffic through the forwarding chip managed by the restarting
forwarding agent will be dropped.

Proceed [y/n] y
switch(config-tcam)# exit
switch(config)# show hardware tcam profile
                     Configuration            Status
FixedSystem          qos-match-ipv6-flow-label qos-match-ipv6-flow-label
switch(config)#

 

Create IPv6 ACL Rules

Configure an access list with the ipv6 access-list command. Then create rules with the permit ipv6 command.

 

Example

The following commands create an IPv6 ACL rule which matches the flow label 23 in the access list L1. 
switch(config)# ipv6 access-list L1
switch(config-ipv6-acl-L1)# permit ipv6 any any flow-label eq 23
switch(config-ipv6-acl-L1)# exit
switch(config)#

 

Add Access List to QoS Class Map

Configure a QoS class map with the class-map command. Then add an access list to the class map with the match command.

 

Example

The following commands create a QoS class map called C1, and then add the access list L1. 
switch(config)# class-map type qos match-any C1
switch(config-cmap-qos-C1)# match ipv6 access-group L1
switch(config-cmap-qos-C1)# exit
switch(config)#

 

Add Class Map to Policy Map

Configure a QoS policy map, creating it if necessary, with the policy-map command. Then add a class map to the policy map and define the traffic class.

 

Example

The following commands configure the QoS policy map P1 and add the class map C1, and then assign the class to traffic class 4. 
switch(config)# policy-map type quality-of-service P1
switch(config-pmap-quality-of-service-P1)# class C1
switch(config-pmap-c-quality-of-service-P1-C1)# set traffic-class 4
switch(config-pmap-c-quality-of-service-P1-C1)# exit
switch(config-pmap-quality-of-service-P1)# exit
switch(config)#

 

Configure An Interface with QoS Policy

Configure an interface with the interface command. Apply the QoS policy to the interface with the service-policy command.

 

Example

The following commands configure the Ethernet interface 1/1, and apply the QoS policy P1 to the interface. 
switch(config)# interface Ethernet 1/1
switch(config-if-Et1/1)# service-policy type qos input P1
switch(config-if-Et1/1)# exit
switch(config)#

 

Example

The following commands confirm that the policy map P1 has been programmed successfully. 
switch(config)# show policy-map P1
Service-policy input: P1
  Hardware programming status: Successful

  Class-map: C1 (match-any)
    Match: ipv6 access-group name L1
       set traffic-class 4

  Class-map: class-default (match-any)

switch(config)# show ipv6 access-lists L1
IPV6 Access List L1
        10 permit ipv6 any any flow-label eq 23
switch(config)#

 

Differentiated MMU Discard Counters

To count discarded packets through tagging, assign drop-precendes for a certain class of packets on platforms that support such tagging.

Configuring Differentiated MMU Discard Counters

The following steps configure the Differentiated MMU Discard Counters.
  1. Configure an IP access-lists to match traffic 
    switch(config)# ip access-list acl1
switch(config-acl-acl1)# permit 41 any any !!41 = 0x29 = IPv6

     

  2. Add the access-list to a class-map 
    switch(config)# class-map type qos match-any class1
switch(config-cmap-qos-class1)# match ip access-group acl1

     

  3. Add the class-map to a policy-map 
    switch(config)# policy-map type quality-of-service policy1
switch(config-pmap-quality-of-service-policy1)# class class1

     

  4. Add drop-precedence action to the policy-map 
    switch(config-pmap-c-quality-of-service-policy1-class1)# set drop-precedence 2

     

  5. Create qos profile with the policy map assigned 
    switch(config)# qos profile qos1
switch(config-qos-profile-qos1)# service-policy input policy1

     

  6. Apply the policy-map to the interface 
    switch(config)# int et3/1
switch(config-if-Et3/1)# service-profile qos1

     

Repeat step 6 on all interfaces that receive traffic to be counted. Packets are tagged on ingress. If the same packet gets dropped on egress as an MMU discard, the corresponding counter gets incremented.

Displaying Differentiated MMU Discard Counters

The show interface counters queue drop-precedence command displays the drop-precedence counters. Based on the above configuration, drop-precedence 2 counts IPv6 packets. 
switch# show interface counters queue drop-precedence
intf        0          1          2
Et1/1     100          0        200
Et1/2     200          0        300
…

 

txQueue Percentage-based Shaping

When you enable this feature using the qos tx-queue shape rate percent percentage adaptive command, QoS calculates the txQueue shape rate based the available bandwidth and not the link speed. For instance, if the interface has a link speed of 100Gbps, and the subinterface configured to 50%, then the subinterface has a link speed of 50Gbps.

Configuring txQueue Percentage-based Shaping

Use the following command to configure traffic for a 50Gps interface for adaptive shaping on interfaces.

switch(config)# qos tx-queue shape rate percentage adaptive
! Change will take effect only after switch reboot.

 

Reboot the switch.

Displaying txQueue Adaptive Information

Use the show qos tx-queue to display the status of the configuration. One of the following messages displays after entering the command:

 

No Configuration

switch# show qos tx-queue
Shape rate percent : Non-Adaptive

 

Configuration Successful After Switch Reboot

switch# show qos tx-queue
Shape rate percent : Adaptive

 

Configuration Successful but No Switch Reboot

switch# show qos tx-queue
Shape rate percent : Non-Adaptive (reboot required for Adaptive)

 

Configuring Round Robin Scheduling on Shaped Subinterfaces

To enable subinterface Round Robin scheduling on the switch, use the following command:

switch(config)#qos subinterface scheduling parent round-robin
! Change will only take effect after switch reboot.

To disable subinterface Round Robin scheduling on the switch, use the following command:

switch(config)#no qos subinterface scheduling parent round-robin
! Change will only take effect after switch reboot.

Displaying Round Robin Scheduling Information

When enabled, the command show platform sand subinterface capabilities displays the Round Robin scheduling information on the switch:

switch#show platform sand subinterface capabilities
SubInterface:
------------------
     
     Supported:     
     ----------
     Minimum port shape rate(kbps)                                : 1000
     Maximum port shape rate(kbps)                                : 400000000
     Number of voqs per subinterface when shaping is applied      : 4
     Traffic class to Voq mapping                                  
                TC0-1    : Voq0
                TC2-3    : Voq1
                TC4-5    : Voq2
                TC6-7    : Voq3
     Traffic class to scheduling mode                              
                TC0-1    : WRR( weight 1 )
                TC2-3    : WRR( weight 2 )
                TC4-5    : WRR( weight 3 )
                TC6-7    : SP
         ( Higher weight implies more credits )               
    Voq tail-drop threshold(MegaByte)                            : 12.500000
    Voq tail-drop threshold(Buffer Descriptor)                   : 12500
    Maximum number of subinterfaces with voq supported on the system: 512
    Maximum number of subinterfaces with voq supported per core   
                                             System Core 0  : 512
                                             System Core 1  : 512
    Scheduling between parent and shaped subinterfaces:          : Round Robin

Latency-based Explicit Congestion Notification

Explicit Congestion Notification (ECN) provides a mechanism of notifying about network traffic congestion without dropping packets. Notification occurs in two ways:

  • Queue Length ECN - Marks the ECN-capable Transport (ECT) packets when the average Virtual Output Queue (VOQ) length exceeds the configured ECN threshold value.
  • Latency-based ECN - Notifies the congestion by marking the ECT packets if the packets take longer than the configured threshold to dequeue from the VOQ.

Both types of notification result in the egress marking of the packet when experiencing the congestion beyond the configured threshold.

Configure ECN on a transmit queue of an interface, and only switches with front panel ports and port-channels support ECN.

Supported Platforms

  • DCS-7280R3 series
  • DCS-7500R3 series
  • DCS-7800R3 series
  • DCS-7130

Quality of Service Commands

QoS Data Field and Traffic Class Configuration Commands

QoS and ECN Display Commands

ECN Configuration Commands

Transmit Queue and Port Shaping Commands – Arad and Jericho Platforms

Transmit Queue and Port Shaping Commands – FM6000 Platform

Transmit Queue and Port Shaping Commands – Helix Platform

Transmit Queue and Port Shaping Commands – Petra Platform

Transmit Queue and Port Shaping Commands – Trident and Tomahawk Platform

Transmit Queue and Port Shaping Commands – Trident II Platform

bandwidth guaranteed (Helix)

The bandwidth guaranteed command specifies the minimum bandwidth for outbound traffic on the transmit queue. By default, no bandwidth is guaranteed to any transmit queue.

The no bandwidth guaranteed and default bandwidth guaranteed commands remove the minimum bandwidth guarantee on the transmit queue by deleting the corresponding bandwidth guaranteed command from running-config.

 

Command Mode

Tx-Queue Configuration

 

Command Syntax

bandwidth guaranteed rate DATA_MIN

no bandwidth guaranteed

default bandwidth guaranteed

 

Parameters

DATA_MIN Minimum bandwidth. Value range varies with data unit:
  • 8 to 40000000  8 to 40000000 kbytes per second.
  • 8 to 40000000 kbps  8 to 40000000 kbytes per second.
  • 1 to 60000000 pps  1 to 60000000 packets per second.

     

Related Command

tx-queue (Helix) places the switch in tx-queue configuration mode.

 

Example
These commands configure a minimum egress bandwidth of 1 Mbps for transmit queue 4 of interface ethernet 17/3. 
switch(config)# interface ethernet 17
switch(config-if-Et17)# tx-queue 4
switch(config-if-Et17-txq-4)# bandwidth guaranteed 1000 kbps
switch(config-if-Et17-txq-4)# show qos interfaces ethernet 17

Ethernet17/3:
   Trust Mode: COS
   Default COS: 0
   Default DSCP: 0

   Port shaping rate: disabled

  Tx       Bandwidth                 Shape Rate        Priority
 Queue     Guaranteed (units)         (units)
   ------------------------------------------------------------
   7        - / -    (  -  )       - / -    (  -  )    SP / SP
   6        - / -    (  -  )       - / -    (  -  )    SP / SP
   5        - / -    (  -  )       - / -    (  -  )    SP / SP
   4        1 / 1    ( Mbps )      - / -    (  -  )    SP / SP
   3        - / -    (  -  )       - / -    (  -  )    SP / SP
   2        - / -    (  -  )       - / -    (  -  )    SP / SP
   1        - / -    (  -  )       - / -    (  -  )    SP / SP
   0        - / -    (  -  )       - / -    (  -  )    SP / SP

Note: Values are displayed as Operational/Configured

switch(config-if-Et17-txq-4)#

bandwidth guaranteed (Trident II)

The bandwidth guaranteed command specifies the minimum bandwidth for outbound traffic on the transmit queue. By default, no bandwidth is guaranteed to any transmit queue.

The no bandwidth guaranteed and default bandwidth guaranteed commands remove the minimum bandwidth guarantee on the transmit queue by deleting the corresponding bandwidth guaranteed command from running-config.

 

Command Mode

Tx-Queue Configuration

 

Command Syntax

bandwidth guaranteed rate DATA_MIN

no bandwidth guaranteed

default bandwidth guaranteed

 

Parameters

DATA_MIN minimum bandwidth. Value range varies with data unit:
  • 8 to 40000000     kbytes per second.
  • 8 to 40000000 kbps    kbytes per second.
  • 1 to 60000000pps      packets per second.

     

Related Command

tx-queue (Trident II) places the switch in tx-queue configuration mode.

 

Example
These commands configure a minimum egress bandwidth of 1 Mbps for transmit queue 4 of interface ethernet 17/3. 
switch(config)# interface ethernet 17/3
switch(config-if-Et17/3)# tx-queue 4
switch(config-if-Et17/3-txq-4)# bandwidth guaranteed 1000 kbps
switch(config-if-Et17/3-txq-4)# show qos interfaces ethernet 17/3

Ethernet17/3:
   Trust Mode: COS
   Default COS: 0
   Default DSCP: 0

   Port shaping rate: disabled

  Tx       Bandwidth                 Shape Rate        Priority
 Queue     Guaranteed (units)         (units)
   ------------------------------------------------------------
   7        - / -    (  -  )       - / -    (  -  )    SP / SP
   6        - / -    (  -  )       - / -    (  -  )    SP / SP
   5        - / -    (  -  )       - / -    (  -  )    SP / SP
   4        1 / 1    ( Mbps )      - / -    (  -  )    SP / SP
   3        - / -    (  -  )       - / -    (  -  )    SP / SP
   2        - / -    (  -  )       - / -    (  -  )    SP / SP
   1        - / -    (  -  )       - / -    (  -  )    SP / SP
   0        - / -    (  -  )       - / -    (  -  )    SP / SP

Note: Values are displayed as Operational/Configured

switch(config-if-Et17/3-txq-4)#

bandwidth percent (Arad/Jericho)

The bandwidth percent command configures the bandwidth share of the transmit queue when configured for round robin priority. Bandwidth is allocated to all queues based on the cumulative configured bandwidth of all the port’s round robin queues.

The cumulative operational bandwidth of all round robin queues is always less than or equal to 100%. If the cumulative configured bandwidth is greater than 100%, each port’s operational bandwidth is its configured bandwidth divided by the cumulative configured bandwidth.

The no bandwidth percent and default bandwidth percent commands restore the default bandwidth share of the transmit queue by removing the corresponding bandwidth percent command from running-config.

 

Command Mode

Tx-Queue Configuration

 

Command Syntax

bandwidth percent proportion

no bandwidth percent

default bandwidth percent

 

Parameter

proportion Bandwidth percentage assigned to queues. Values range from 1 to 100.

 

Related Command

tx-queue (Arad/Jericho) places the switch in tx-queue configuration mode.

 

Examples
  • These commands configure queues 0 through 3 (interface ethernet 3/5/1) as round robin, then allocate bandwidth for three queues at 30% and one queue at 10%. 
    switch(config)# interface ethernet 3/5/1
switch(config-if-Et3/5/1)# tx-queue 3
switch(config-if-Et3/5/1-txq-3)# no priority
switch(config-if-Et3/5/1-txq-3)# bandwidth percent 10
switch(config-if-Et3/5/1-txq-3)# tx-queue 2
switch(config-if-Et3/5/1-txq-2)# bandwidth percent 30
switch(config-if-Et3/5/1-txq-2)# tx-queue 1
switch(config-if-Et3/5/1-txq-1)# bandwidth percent 30
switch(config-if-Et3/5/1-txq-1)# tx-queue 0
switch(config-if-Et3/5/1-txq-0)# bandwidth percent 30
switch(config-if-Et3/5/1-txq-0)# show qos interfaces ethernet 3/5/1

Ethernet3/5/1:

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D
   6      - / -        - / -    (  -  )    SP / SP    D
   5      - / -        - / -    (  -  )    SP / SP    D
   4      - / -        - / -    (  -  )    SP / SP    D
   3     10 / 10       - / -    (  -  )    RR / RR    D
   2     30 / 30       - / -    (  -  )    RR / SP    D
   1     30 / 30       - / -    (  -  )    RR / SP    D
   0     30 / 30       - / -    (  -  )    RR / SP    D

switch(config-if-Et3/5/1-txq-0)#

     

  • These commands re-configure the bandwidth share of the fourth queue at 30%. 
    switch(config-if-Et3/5/1-txq-0)# tx-queue 3
switch(config-if-Et3/5/1-txq-3)# bandwidth percent 30
switch(config-if-Et3/5/1-txq-3)# show qos interfaces ethernet 3/5/1

Ethernet3/5/1:

   Port shaping rate: disabled

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D
   6      - / -        - / -    (  -  )    SP / SP    D
   5      - / -        - / -    (  -  )    SP / SP    D
   4      - / -        - / -    (  -  )    SP / SP    D
   3     24 / 30       - / -    (  -  )    RR / RR    D
   2     24 / 30       - / -    (  -  )    RR / SP    D
   1     24 / 30       - / -    (  -  )    RR / SP    D
   0     24 / 30       - / -    (  -  )    RR / SP    D

Note: Values are displayed as Operational/Configured

switch(config-if-Et3/5/1-txq-3)#

     

  • These commands configure the bandwidth share of the fourth queue at 2%. 
    switch(config-if-Et3/5/1-txq-3)# bandwidth percent 2
switch(config-if-Et3/5/1-txq-3)# show qos interfaces ethernet 3/5/1

Ethernet3/5/1:

   Port shaping rate: disabled

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D
   6      - / -        - / -    (  -  )    SP / SP    D
   5      - / -        - / -    (  -  )    SP / SP    D
   4      - / -        - / -    (  -  )    SP / SP    D
   3      2 / 2        - / -    (  -  )    RR / RR    D
   2     30 / 30       - / -    (  -  )    RR / SP    D
   1     30 / 30       - / -    (  -  )    RR / SP    D
   0     30 / 30       - / -    (  -  )    RR / SP    D

Note: Values are displayed as Operational/Configured

switch(config-if-Et3/5/1-txq-3)#

bandwidth percent (FM6000)

The bandwidth percent command configures the bandwidth share of the transmit queue when configured for round robin priority. Bandwidth is allocated to all queues based on the cumulative configured bandwidth of all the port’s round robin queues.

The cumulative operational bandwidth of all round robin queues is always less than or equal to 100%. If the cumulative configured bandwidth is greater than 100%, each port’s operational bandwidth is its configured bandwidth divided by the cumulative configured bandwidth.

The no bandwidth percent and default bandwidth percent commands restore the default bandwidth share of the transmit queue by removing the corresponding bandwidth percent command running-config.

 

Command Mode

Tx-Queue Configuration

 

Command Syntax

bandwidth percent proportion

no bandwidth percent

default bandwidth percent

 

Parameter

proportion     Configured bandwidth percentage. Value ranges from 1 to 100. Default value is 0.

 

Related Command

tx-queue (FM6000) places the switch in tx-queue configuration mode.

 

Examples
  • These commands configure queues 0 through 3 (interface Ethernet 19) as round robin, then allocate bandwidth for three queues at 30% and one queue at 10%. 
    switch(config)# interface Ethernet 19
switch(config-if-Et19)# tx-queue 3
switch(config-if-Et19-txq-3)# no priority
switch(config-if-Et19-txq-3)# bandwidth percent 10
switch(config-if-Et19-txq-3)# tx-queue 2
switch(config-if-Et19-txq-2)# bandwidth percent 30
switch(config-if-Et19-txq-2)# tx-queue 1
switch(config-if-Et19-txq-1)# bandwidth percent 30
switch(config-if-Et19-txq-1)# tx-queue 0
switch(config-if-Et19-txq-0)# bandwidth percent 30
switch(config-if-Et19-txq-0)# show qos interface ethernet 19

Ethernet19:
   Trust Mode: COS
   Default COS: 0
   Default DSCP: 0

   Port shaping rate: disabled

 Tx    Bandwidth  Bandwidth          Shape Rate     Priority  ECN/WRED
 Queue (percent)  Guaranteed (units)  units)
 
-----------------------------------------------------------------------
  7     - / -      - / -     ( - )     - / -  ( - )  SP / SP    D
  6     - / -      - / -     ( - )     - / -  ( - )  SP / SP    D
  5     - / -      - / -     ( - )     - / -  ( - )  SP / SP    D
  4     - / -      - / -     ( - )     - / -  ( - )  SP / SP    D
  3    10 / 10     - / -     ( - )     - / -  ( - )  RR / RR    D
  2    30 / 30     - / -     ( - )     - / -  ( - )  RR / SP    D
  1    30 / 30     - / -     ( - )     - / -  ( - )  RR / SP    D
  0    30 / 30     - / -     ( - )     - / -  ( - )  RR / SP    D

Note: Values are displayed as Operational/Configured

Legend:
RR -> Round Robin
SP -> Strict Priority
 -  -> Not Applicable / Not Configured
ECN/WRED: L -> Queue Length ECN Enabled     W -> WRED Enabled     D -> Disabled

     

  • These commands re-configure the bandwidth share of transmit queue 3 at 30%. 
    cp118.14:04:20# config
cp118.14:04:23(config)# interface ethernet 19
cp118.14:04:47(config-if-Et19-txq-0)# tx-queue 3
cp118.14:04:59(config-if-Et19-txq-3)# bandwidth percent 30
cp118.14:05:16(config-if-Et19-txq-3)# show qos interface ethernet 19

Ethernet19:
   Trust Mode: COS
   Default COS: 0
   Default DSCP: 0

   Port shaping rate: disabled

 Tx   Bandwidth   Bandwidth          Shape Rate      Priority  ECN/WRED
Queue (percent)   Guaranteed (units)  (units)
 
------------------------------------------------------------------------
  7     - / -      - / -     ( - )     - / -  ( - )   SP / SP    D
  6     - / -      - / -     ( - )     - / -  ( - )   SP / SP    D
  5     - / -      - / -     ( - )     - / -  ( - )   SP / SP    D
  4     - / -      - / -     ( - )     - / -  ( - )   SP / SP    D
  3    24 / 30     - / -     ( - )     - / -  ( - )   RR / RR    D
  2    24 / 30     - / -     ( - )     - / -  ( - )   RR / SP    D
  1    24 / 30     - / -     ( - )     - / -  ( - )   RR / SP    D
  0    24 / 30     - / -     ( - )     - / -  ( - )   RR / SP    D

Note: Values are displayed as Operational/Configured

Legend:
RR -> Round Robin
SP -> Strict Priority
 -  -> Not Applicable / Not Configured
ECN/WRED: L -> Queue Length ECN Enabled     W -> WRED Enabled     D -> Disabled

     

  • These commands re-configure the bandwidth share of transmit queue 3 at 2%. 
    cp118.14:09:37(config-if-Et19-txq-3)# bandwidth percent 2
cp118.14:12:56(config-if-Et19-txq-3)# show qos interface ethernet 19

Ethernet19:
   Trust Mode: COS
   Default COS: 0
   Default DSCP: 0

   Port shaping rate: disabled

 Tx   Bandwidth  Bandwidth           Shape Rate    Priority  ECN/WRED
Queue (percent)  Guaranteed (units)  (units)
 
----------------------------------------------------------------------
  7     - / -      - / -     ( - )   - / -  ( - )   SP / SP   D
  6     - / -      - / -     ( - )   - / -  ( - )   SP / SP   D
  5     - / -      - / -     ( - )   - / -  ( - )   SP / SP   D
  4     - / -      - / -     ( - )   - / -  ( - )   SP / SP   D
  3     2 / 2      - / -     ( - )   - / -  ( - )   RR / RR   D
  2    30 / 30     - / -     ( - )   - / -  ( - )   RR / SP   D
  1    30 / 30     - / -     ( - )   - / -  ( - )   RR / SP   D
  0    30 / 30     - / -     ( - )   - / -  ( - )   RR / SP   D

Note: Values are displayed as Operational/Configured

Legend:
RR -> Round Robin
SP -> Strict Priority
 -  -> Not Applicable / Not Configured
ECN/WRED: L -> Queue Length ECN Enabled     W -> WRED Enabled     D -> Disabled

bandwidth percent (Petra)

The bandwidth percent command configures the bandwidth share of the transmit queue when configured for round robin priority. Bandwidth is allocated to all queues based on the cumulative configured bandwidth of all the port’s round robin queues.

The cumulative operational bandwidth of all round robin queues is always less than or equal to 100%. If the cumulative configured bandwidth is greater than 100%, each port’s operational bandwidth is its configured bandwidth divided by the cumulative configured bandwidth.

The no bandwidth percent and default bandwidth percent commands restore the default bandwidth share of the transmit queue by removing the corresponding bandwidth percent command running-config.

 

Command Mode

Tx-Queue Configuration

 

Command Syntax

bandwidth percent proportion

no bandwidth percent

default bandwidth percent

 

Parameter

proportionBandwidth percentage assigned to queues. Values range from 1 to 100.

 

Related Command

tx-queue (Petra)places the switch in tx-queue configuration mode.

 

Examples
  • These commands configure queues 0 through 3 (interface ethernet 3/28) as round robin, then allocate bandwidth for three queues at 30% and one queue at 10%. 
    switch(config)# interface ethernet 3/28
switch(config-if-Et3/28)# tx-queue 3
switch(config-if-Et3/28-txq-3)# no priority
switch(config-if-Et3/28-txq-3)# bandwidth percent 10
switch(config-if-Et3/28-txq-3)# tx-queue 2
switch(config-if-Et3/28-txq-2)# bandwidth percent 30
switch(config-if-Et3/28-txq-2)# tx-queue 1
switch(config-if-Et3/28-txq-1)# bandwidth percent 30
switch(config-if-Et3/28-txq-1)# tx-queue 0
switch(config-if-Et3/28-txq-0)# bandwidth percent 30
switch(config-if-Et3/28-txq-0)# show qos interface ethernet 3/28

Ethernet3/28:

   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
   -----------------------------------------------
          7         N/A     disabled        strict
          6         N/A     disabled        strict
          5         N/A     disabled        strict
          4         N/A     disabled        strict
          3          10     disabled   round-robin
          2          30     disabled   round-robin
          1          30     disabled   round-robin
          0          30     disabled   round-robin

switch(config-if-Et3/28-txq-0)#

     

  • These commands re-configure the bandwidth share of the fourth queue at 30%. 
    switch(config-if-Et3/28-txq-0)# tx-queue 3
switch(config-if-Et3/28-txq-3)# bandwidth percent 30
switch(config-if-Et3/28-txq-3)# show qos interface ethernet 3/28

Ethernet3/28:
   Trust Mode: COS

   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
-----------------------------------------------
          7         N/A     disabled        strict
          6         N/A     disabled        strict
          5         N/A     disabled        strict
          4         N/A     disabled        strict
          3          24     disabled   round-robin
          2          24     disabled   round-robin
          1          24     disabled   round-robin
          0          24     disabled   round-robin

switch(config-if-Et3/28-txq-3)#

     

  • These commands configure the bandwidth share of the fourth queue at 2%. 
    switch(config-if-Et3/28)# tx-queue 3
switch(config-if-Et3/28-txq-3)# bandwidth percent 2
switch(config-if-Et3/28-txq-3)# show qos interface ethernet 3/28

Ethernet3/28:
   Trust Mode: COS


   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
   -----------------------------------------------
          7         N/A     disabled        strict
          6         N/A     disabled        strict
          5         N/A     disabled        strict
          4         N/A     disabled        strict
          3           2     disabled   round-robin
          2          30     disabled   round-robin
          1          30     disabled   round-robin
          0          30     disabled   round-robin

switch(config-if-Et3/28-txq-3)#

bandwidth percent (Trident and Tomahawk)

The bandwidth percent command configures the bandwidth share of the transmit queue when configured for round robin priority. Bandwidth is allocated to all queues based on the cumulative configured bandwidth of all the port’s round robin queues.

The cumulative operational bandwidth of all round robin queues is always less than or equal to 100%. If the cumulative configured bandwidth is greater than 100%, each port’s operational bandwidth is its configured bandwidth divided by the cumulative configured bandwidth.

The no bandwidth percent and default bandwidth percent commands restore the default bandwidth share of the transmit queue by removing the corresponding bandwidth percent command running-config.

 

Command Mode

Mc-Tx-Queue configuration

Uc-Tx-Queue configuration

 

Command Syntax

bandwidth percent proportion

no bandwidth percent

default bandwidth percent

 

Parameter

proportion Bandwidth percentage assigned to queues. Values range from 1 to 100.

 

Related Commands
  • mc-tx-queue places the switch in mc-tx-queue configuration mode.
  • uc-tx-queue places the switch in uc-tx-queue configuration mode.

     

Examples
  • These commands configure unicast transmit queue 3 (and all other queues of lower priority) as round robin, then allocate bandwidth for unicast transmit queues 1, 2, and 3 at 30% and multicast transmit queue 1 at 10%. 
    switch(config)# interface ethernet 7
switch(config-if-Et7)# uc-tx-queue 3
switch(config-if-Et7-uc-txq-3)# no priority
switch(config-if-Et7-uc-txq-3)# bandwidth percent 30
switch(config-if-Et7-uc-txq-3)# uc-tx-queue 2
switch(config-if-Et7-uc-txq-2)# bandwidth percent 30
switch(config-if-Et7-uc-txq-2)# uc-tx-queue 1
switch(config-if-Et7-uc-txq-1)# bandwidth percent 30
switch(config-if-Et7-uc-txq-1)# mc-tx-queue 1
switch(config-if-Et7-mc-txq-1)# bandwidth percent 10
switch(config-if-Et7-mc-txq-1)# show qos interfaces ethernet 7

Ethernet7:
   Trust Mode: COS
   Default COS: 0
   Default DSCP: 0

   Port shaping rate: disabled

   Tx-Queue   Bandwidth    Shape Rate     Priority   Priority Group
              (percent)       (Kbps)
   ----------------------------------------------------------------
        UC7         N/A     disabled        strict                1
        UC6         N/A     disabled        strict                1
        MC3         N/A     disabled        strict                1
        UC5         N/A     disabled        strict                0
        UC4         N/A     disabled        strict                0
        MC2         N/A     disabled        strict                0
        UC3          30     disabled   round-robin                0
        UC2          30     disabled   round-robin                0
        MC1          10     disabled   round-robin                0
        UC1          30     disabled   round-robin                0
        UC0           0     disabled   round-robin                0
        MC0           0     disabled   round-robin                0

switch(config-if-Et7-mc-txq-1)#

     

  • These commands re-configure the bandwidth share of unicast queue 3 at 55%. 
    switch(config-if-Et7-mc-txq-1)# uc-tx-queue 3
switch(config-if-Et7-uc-txq-3)# bandwidth percent 55
switch(config-if-Et7-uc-txq-3)# show qos interface ethernet 7

Ethernet7:
   Trust Mode: COS
   Default COS: 0
   Default DSCP: 0

   Port shaping rate: disabled

   Tx-Queue   Bandwidth    Shape Rate     Priority   Priority Group
              (percent)       (Kbps)
   ----------------------------------------------------------------
        UC7         N/A     disabled        strict                1
        UC6         N/A     disabled        strict                1
        MC3         N/A     disabled        strict                1
        UC5         N/A     disabled        strict                0
        UC4         N/A     disabled        strict                0
        MC2         N/A     disabled        strict                0
        UC3          44     disabled   round-robin                0
        UC2          24     disabled   round-robin                0
        MC1           8     disabled   round-robin                0
        UC1          24     disabled   round-robin                0
        UC0           0     disabled   round-robin                0
        MC0           0     disabled   round-robin                0

switch(config-if-Et7-uc-txq-3)#

color

Use the color command for the ability to configure the color extended community in route-map set clauses and in an extcommunity-list for inbound and outbound policy application.

 

Command Mode

Route-maps and extcommunity-lists

 

Command Syntax

color COLOR-VALUE [color-only [exact-match | [endpoint-match [any | null]]]]

 

Parameters
  • COLOR-VALUE A single policy color value, range 0 to 4294967295.
  • color-onlyAllows configuration of color-only bits.
  • exact-matchExplicitly sets the color-only bits of the extended community to 00 (optional).
  • endpoint-match anySets the color-only bits of the extended community to 10.
  • endpoint-match null Sets the color-only bits of the extended community to 01.

     

Example

switch(config)# route-map foo
switch(config0route-map-foo)# set community color 2 color-only endpoint-match any

dscp to traffic-class (DSCP map)

 

The dscp to traffic-class command configures the specified QoS map to map one or more DSCP classes to a traffic class. Only one traffic class may be specified per command. The command can be repeated to configure additional traffic classes. The configuration is modified immediately. Each dscp to traffic-class command overwrites the existing entries in the map.

The default dscp to traffic-class and no dscp to traffic-class commands restore the global map values for the given DSCP classes.

 

Command Mode

DSCP Map Configuration

 

Command Syntax

dscp dscp_classes to traffic-class traffic_class

default dscp dscp_classes to traffic-class

no dscp dscp_classes to traffic-class

 

Parameters

  • dscp_classes The DSCP class or classes to map to a new traffic-class value. These can be provided as a single value, a range given with a hyphen (such as 20-25), a comma separated list (such as 1,4,9), or a combination (such as 20-25, 35). The range for each value is 0-63.
  • traffic_class The traffic class to map the specified DSCP class or classes to.

     

Example

These commands configure the DSCP-to-traffic-class map map1 to map DSCP class 35 to traffic class 7, and DSCP classes 20-25 to traffic class 6. 
switch(config)#qos map dscp to traffic-class name map1
switch(config-dscp-map-map1)#dscp 35 to traffic-class 7
switch(config-dscp-map-map1)#dscp 20-25 to traffic-class 6

hardware access-list qos resource sharing vlan in

The hardware access-list qos resource sharing vlan in command enables the ACL based QoS resources sharing on a VLAN interface.

The no hardware access-list qos resource sharing vlan in disables the ACL based QoS resources sharing on a VLAN interface. By default this function is disabled.

 

Command Mode

Global Configuration

 

Command Syntax

hardware access-list qos resource sharing vlan in

no hardware access-list qos resource sharing vlan in

 

Example
This commands enables the ACL based QoS resources sharing on a VLAN interface. 
switch(config)# hardware access-list qos resource sharing vlan in

interface fabric (Trident II)

The interface fabric command places the switch in Fabric-interface configuration mode and allows the user to attach the QoS profile to the fabric interface of the switch.

 

Command Mode

Global Configuration

 

Command Syntax

interface fabric

 

Example
This command places the switch in Fabric-interface configuration mode. 
switch(config)# interface fabric
switch(config-if-fabric)#

ip extcommunity-list

The ip extcommunity-list command adds a color extended community to an extcommunity-list. Multiple color extended communities can be added to the list. Negating the command removes the corresponding color extended community from the list.

 

Command Mode

Configuration mode

 

Command Syntax

ip extcommunity-list WORD [permit | deny][COLOR-EXPRESSION]

no ip extcommunity-list WORD [permit | deny] COLOR-EXPRESSION]

default ip extcommunity-list WORD [permit | deny][COLOR-EXPRESSION]

 

Parameters
  • WORDCommunity list name.
  • permitSpecifies community to accept.
  • denySpecifies comminity to reject.
  • COLOR-EXPRESSION Color extended community.

     

Example 
switch(config)# ip extcommunity-list foo permit color 1 color 2
switch(config)# ip extcommunity-list bar permit color 3 color-only endpoint-match null color 4 color-only endpoint-match any

mc-tx-queue

The mc-tx-queue command places the switch in mc-tx-queue configuration mode to configure a multicast transmit queue on the configuration mode interface. Mc-tx-queue configuration mode is not a group change mode; running-config is changed immediately after commands are executed. The exit command does not affect the configuration.

Trident and Tomahawk switches have four multicast queues (MC0 – MC03) and eight unicast queues (UC0 – UC7), categorized into two priority groups. All queues are exposed through the CLI and are user configurable.
  • Priority Group 1: UC7, UC6, MC3

     

  • Priority Group 0: UC5, UC4, MC2, UC3, UC2, MC1, UC1, UC0, MC0

     

The exit command returns the switch to the configuration mode for the base Ethernet or port channel interface.

The no mc-tx-queue and default mc-tx-queue commands remove the configuration for the specified transmit queue by deleting the all corresponding mc-tx-queue mode commands from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

mc-tx-queue queue_level

 

Parameter

queue_level      The multicast transmit queue number. Values range from 0 to 3.

 

Commands Available in tx-queue Configuration Mode

Related Command

uc-tx-queue Configures unicast transmit queues on Trident and Tomahawk platform switches.

 

Example
This command enters mc-tx-queue configuration mode for multicast transmit queue 3 of interface ethernet 5. 
switch(config)# interface ethernet 5
switch(config-if-Et5)# mc-tx-queue 3
switch(config-if-Et5-mc-txq-3)#

platform petraA traffic-class

The platform petraA traffic-class command configures the default traffic class used by all ports on a specified chip. The default traffic class is implemented by Petra platform switches to replace qos cos and qos dscp commands. Traffic class values range from 0 to 7. The default traffic class is 1.

When platform ? returns Petra:
  • CoS trusted ports: inbound untagged packets are assigned to the default traffic class. Tagged packets are assigned to the traffic class that corresponds to the contents of its CoS field.

     

  • DSCP trusted ports: inbound non-IP packets are assigned to the default traffic class. IP packets are assigned to the traffic class that corresponds to the contents of its DSCP field.

     

  • Untrusted ports: all inbound packets are assigned to the default traffic class.

     

The no platform petraA traffic-class and default platform petraA traffic-class commands restore the default traffic class of one for all ports on the specified chips by deleting the corresponding platform petraA traffic-class command from running-config.

 

Command Mode

Global Configuration

 

Command Syntax

platform petraA [CHIP_NAME] traffic-class tc_value

no platform petraA [CHIP_NAME] traffic-class

default platform petraA [CHIP_NAME] traffic-class

 

Parameters

CHIP_NAME Trust mode assigned to the specified ports. Port designation options include:
    • no parameter      All ports on the switch.
    • module cardX      All ports on specified linecard (7500 Series).
    • petra cardX / chipY      All ports on PetraA chip chipY on linecard cardX (7500 Series).
    • petra -chipZ      All ports on PetraA chip chipZ (7048 Series)

       

7500 Series

Switches can contain up to eight linecards. CardX varies from 3 to 10.

Each linecard contains six PetraA chips. Each chip controls eight ports. ChipY varies from 0 to 5:
  • 0 controls ports 1 through 8:
    • 1 controls ports 9 through 16.
    • 2 controls ports 17 through 24.
    • 3 controls ports 25 through 32.
    • 4 controls ports 33 through 40.
    • 5 controls ports 41 through 48.

       

7048 Series

Each switch contains two PetraA chips. ChipZ varies from 0 to 1:
  • 0 controls ports 1 through 32.
    • 1 controls ports 33 through 52.
  • tc_value      Traffic class value. Values range from 0 to 7. Default value is 1.

     

Related Command

show platform petraA traffic-class displays the traffic class assignment on all specified Petra chips.

 

Example
This command configures the default traffic class 6 for ports 25-32 on linecard 5. 
switch(config)# platform petraA petra5/3 traffic-class 6
switch(config)#

priority (Arad/Jericho)

The priority command specifies the priority of the transmit queue. The switch supports two queue priorities:
  • strict priority: contents are removed from the queue - subject to maximum bandwidth limits, before data from lower priority queues. The default setting on all queues is strict priority.

     

  • round robin priority: contents are removed proportionately from all round robin queues - subject to maximum bandwidth limits assigned to the strict priority queues.

     

Tx-queue 7 is set to strict priority and is not configurable.

When a queue is configured as a round robin queue, all lower priority queues also function as round robin queues. A queue’s numerical label denotes its priority: higher labels denote higher priority. Tx-queue 6 has higher priority than Tx-queue 5, and Tx-queue 0 has the lowest priority.

The priority strict and default priority commands configure a transmit queue to function as a strict priority queue unless a higher priority queue is configured as a round robin queue.

The no priority command configures a transmit queue as a round robin queue. All lower priority queues also function as round robin queues regardless of their configuration.

 

Command Mode

Tx-Queue Configuration

 

Command Syntax

priority strict

no priority

default priority

 

Related Command

tx-queue (Arad/Jericho) places the switch in tx-queue configuration mode.

 

Example
These commands perform the following on interface ethernet 3/4/1:
  • Displays the default state of all transmit queues.
  • Configures transmit queue 3 as a round robin queue.
  • Displays the effect of the no priority command on all transmit queues on the interface.
switch(config)# interface ethernet 3/4/1
switch(config-if-Et3/4/1)# show qos interfaces ethernet 3/4/1

Ethernet3/4/1:

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D
   6      - / -        - / -    (  -  )    SP / SP    D
   5      - / -        - / -    (  -  )    SP / SP    D
   4      - / -      999 / 1000 ( Mbps )   SP / SP    D
   3      - / -      999 / 1000 ( Mbps )   SP / SP    D
   2      - / -        - / -    (  -  )    SP / SP    D
   1      - / -        - / -    (  -  )    SP / SP    D
   0      - / -        - / -    (  -  )    SP / SP    D

Note: Values are displayed as Operational/Configured

switch(config-if-Et3/4/1)# tx-queue 3
switch(config-if-Et3/4/1-txq-3)# no priority
switch(config-if-Et3/4/1-txq-3)# show qos interfaces ethernet 3/4/1

Ethernet3/4/1:

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D
   6      - / -        - / -    (  -  )    SP / SP    D
   5      - / -        - / -    (  -  )    SP / SP    D
   4      - / -      999 / 1000 ( Mbps )   SP / SP    D
   3     25 / -      999 / 1000 ( Mbps )   RR / RR    D
   2     25 / -        - / -    (  -  )    RR / SP    D
   1     25 / -        - / -    (  -  )    RR / SP    D
   0     25 / -        - / -    (  -  )    RR / SP    D

Note: Values are displayed as Operational/Configured

switch(config-if-Et3/4/1-txq-3)#

priority (FM6000)

The priority command specifies the priority of the transmit queue. The switch supports two queue priorities:
  • strict priority: contents are removed from the queue - subject to maximum bandwidth limits, before data from lower priority queues. The default setting on all queues is strict priority.

     

  • round robin priority: contents are removed proportionately from all round robin queues - subject to maximum bandwidth limits assigned to the strict priority queues.

     

When a queue is configured as a round robin queue, all lower priority queues also function as round robin queues. A queue’s numerical label denotes its priority: higher labels denote higher priority. Tx-queue 6 has higher priority than Tx-queue 5, and Tx-queue 0 has the lowest priority.

The priority strict and default priority commands configure a transmit queue to function as a strict priority queue unless a higher priority queue is configured as a round robin queue.

The no priority command configures a transmit queue as a round robin queue. All lower priority queues also function as round robin queues regardless of their configuration.

 

Command Mode

Tx-Queue Configuration

 

Command Syntax

priority strict

no priority

default priority

 

Related Command

tx-queue (FM6000) places the switch in tx-queue configuration mode.

 

Example
These commands perform the following on interface ethernet 19:
  • Displays the default state of all transmit queues.
  • Configures transmit queue 3 as a round robin queue.
  • Displays the effect of the no priority command on all transmit queues on the interface. 
    switch(config)# interface ethernet 19
switch(config-if-Et19)# show qos interface ethernet 19

Ethernet19:
   Trust Mode: COS

   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
   -----------------------------------------------
          6         N/A     disabled        strict
          5         N/A     disabled        strict
          4         N/A     disabled        strict
          3         N/A     disabled        strict
          2         N/A     disabled        strict
          1         N/A     disabled        strict
          0         N/A     disabled        strict

switch(config-if-Et19)# tx-queue 3
switch(config-if-Et19-txq-3)# no priority
switch(config-if-Et19-txq-3)# show qos interface ethernet 19

Ethernet19:
   Trust Mode: COS

   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
   -----------------------------------------------
          6         N/A     disabled        strict
          5         N/A     disabled        strict
          4         N/A     disabled        strict
          3          25     disabled   round-robin
          2          25     disabled   round-robin
          1          25     disabled   round-robin
          0          25     disabled   round-robin

switch(config-if-Et19-txq-3)#

priority (Petra)

The priority command specifies the priority of the transmit queue. The switch supports two queue priorities:
  • strict priority: contents are removed from the queue - subject to maximum bandwidth limits, before data from lower priority queues. The default setting on all queues is strict priority.

     

  • round robin priority: contents are removed proportionately from all round robin queues - subject to maximum bandwidth limits assigned to the strict priority queues.

     

Tx-queue 7 is set to strict priority and is not configurable.

When a queue is configured as a round robin queue, all lower priority queues also function as round robin queues. A queue’s numerical label denotes its priority: higher labels denote higher priority. Tx-queue 6 has higher priority than Tx-queue 5, and Tx-queue 0 has the lowest priority.

The priority strict and default priority commands configure a transmit queue to function as a strict priority queue unless a higher priority queue is configured as a round robin queue.

The no priority command configures a transmit queue as a round robin queue. All lower priority queues also function as round robin queues regardless of their configuration.

 

Command Mode

Tx-Queue Configuration

 

Command Syntax

priority strict

no priority

default priority

 

Related Command

tx-queue (Petra) places the switch in tx-queue configuration mode.

 

Example
These commands perform the following on Ethernet interface 3/28:
  • Displays the default state of all transmit queues.
  • Configures transmit queue 3 as a round robin queue.
  • Displays the effect of the no priority command on all transmit queues on the interface. 
    switch(config)# interface ethernet 3/28
switch(config-if-Et3/28)# show qos interface ethernet 3/28

Ethernet3/28:
   Trust Mode: COS

   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
   -----------------------------------------------
          7         N/A     disabled        strict
          6         N/A     disabled        strict
          5         N/A     disabled        strict
          4         N/A     disabled        strict
          3         N/A     disabled        strict
          2         N/A     disabled        strict
          1         N/A     disabled        strict
          0         N/A     disabled        strict

switch(config-if-Et3/28)# tx-queue 3
switch(config-if-Et3/28-txq-3)# no priority
switch(config-if-Et3/28-txq-3)# show qos interface ethernet 3/28

Ethernet3/28:
   Trust Mode: COS

   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
   -----------------------------------------------
          7         N/A     disabled        strict
          6         N/A     disabled        strict
          5         N/A     disabled        strict
          4         N/A     disabled        strict
          3          25     disabled   round-robin
          2          25     disabled   round-robin
          1          25     disabled   round-robin
          0          25     disabled   round-robin

switch(config-if-Et3/28-txq-3)#

priority (Trident and Tomahawk)

The priority command specifies the priority of the transmit queue. The switch supports two queue priorities:
  • strict priority: contents are removed from the queue - subject to maximum bandwidth limits, before data from lower priority queues. The default setting on all other queues is strict priority.

     

  • round robin priority: contents are removed proportionately from all round robin queues - subject to maximum bandwidth limits assigned to the strict priority queues.

     

Trident and Tomahawk switches have eight unicast queues (UC0 – UC7) and four multicast queues (MC0 – MC03), categorized into two priority groups. Priority group 1 queues have priority over priority 0 queues. The following lists display the priority group queues in order from higher priority to lower priority.
  • Priority Group 1: UC7, UC6, MC3

     

  • Priority Group 0: UC5, UC4, MC2, UC3, UC2, MC1, UC1, UC0, MC0

     

Priority group 1 queues are strict priority queues and are not configurable as round robin. Priority 0 queues are strict priority by default and are configurable as round robin. When a queue is configured as a round robin queue, all lower priority queues automatically function as round robin queues.

The priority strict and default priority commands configure a transmit queue to function as a strict priority queue unless a higher priority queue is configured as a round robin queue.

The no priority command configures a transmit queue as a round robin queue. All lower priority queues also function as round robin queues regardless of their configuration.

 

Command Mode

Mc-Tx-Queue configuration

Uc-Tx-Queue configuration

 

Command Syntax

priority strict

no priority

default priority

 

Related Commands
  • mc-tx-queue places the switch in mc-tx-queue configuration mode.
  • uc-tx-queue places the switch in uc-tx-queue configuration mode.

     

Example
These commands perform the following on interface ethernet 7:
  • Displays the default state of all transmit queues.
  • Configures transmit queue 3 as a round robin queue.
  • Displays the effect of the no priority command on all transmit queues on the interface. 
    switch(config) #interface ethernet 7
switch(config-if-Et7)# show qos interface ethernet 7

Ethernet7:
   Trust Mode: COS

   Tx-Queue   Bandwidth    Shape Rate     Priority   Priority Group
              (percent)       (Kbps)
   ----------------------------------------------------------------
        UC7         N/A     disabled        strict                1
        UC6         N/A     disabled        strict                1
        MC3         N/A     disabled        strict                1
        UC5         N/A     disabled        strict                0
        UC4         N/A     disabled        strict                0
        MC2         N/A     disabled        strict                0
        UC3         N/A     disabled        strict                0
        UC2         N/A     disabled        strict                0
        MC1         N/A     disabled        strict                0
        UC1         N/A     disabled        strict                0
        UC0         N/A     disabled        strict                0
        MC0         N/A     disabled        strict                0

switch(config-if-Et7)# uc-tx-queue 3
switch(config-if-Et7-uc-txq-3)# no priority
switch(config-if-Et7-uc-txq-3)# show qos interface ethernet 7

Ethernet7:
   Trust Mode: COS

   Tx-Queue   Bandwidth    Shape Rate     Priority   Priority Group
              (percent)       (Kbps)
   ----------------------------------------------------------------
        UC7         N/A     disabled        strict                1
        UC6         N/A     disabled        strict                1
        MC3         N/A     disabled        strict                1
        UC5         N/A     disabled        strict                0
        UC4         N/A     disabled        strict                0
        MC2         N/A     disabled        strict                0
        UC3          20     disabled   round-robin                0
        UC2          16     disabled   round-robin                0
        MC1          16     disabled   round-robin                0
        UC1          16     disabled   round-robin                0
        UC0          16     disabled   round-robin                0
        MC0          16     disabled   round-robin                0

switch(config-if-Et7-uc-txq-3)#

qos cos

The qos cos command specifies the default class of service (CoS) value of the configuration mode interface. CoS values range from 0 to 7. Default value is 0.

Arad, Jericho, fm6000, Trident, Tomahawk, and Trident II platform switches:
  • CoS trusted ports: the default CoS value determines the traffic class for inbound untagged packets. Tagged packets are assigned to the traffic class that corresponds to the contents of its CoS field.

     

  • Untrusted ports: the default CoS value determines the traffic class for all inbound packets.

     

Petra platform switches:
  • CoS trusted ports: inbound untagged packets are assigned to the default traffic class, as configured by platform petraA traffic-class. Tagged packets are assigned to the traffic class that corresponds to the contents of its CoS field.

     

  • Untrusted ports: all inbound packets are assigned to the default traffic class.

     

The no qos cos and default qos cos commands restore the port’s default CoS value to zero by deleting the corresponding qos cos command from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

qos cos cos_value

no qos cos

default qos cos

 

Parameter

cos_valueCoS value assigned to port. Value ranges from 0 to 7. Default value is 0.

 

Example
This command configures the default CoS 4 on interface ethernet 8. 
switch(config-if-Et8)# qos cos 4
switch(config-if-Et8)#

qos dscp

The qos dscp command specifies the default Differentiated Services Code Point (DSCP) value of the configuration mode interface. The default DSCP determines the traffic class for non-IP packets that are inbound on DSCP trusted ports. DSCP trusted ports determine the traffic class for inbound packets as follows:
  • Arad, Jericho, fm6000, Trident, Tomahawk, and Trident II platform switches:
    • non-IP packets: default DSCP value specified by qos dscp determines the traffic class.
    • IP packets: assigned to the traffic class corresponding to its DSCP field contents.

       

  • Petra platform switches:
    • non-IP packets: assigned to default traffic class configured by platform petraA traffic-class.
    • IP packets: assigned to the traffic class corresponding to its DSCP field contents.

       

The no qos dscp and default qos dscp commands restore the port’s default DSCP value to zero by deleting the corresponding qos dscp command from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

qos dscp dscp_value

no qos dscp

default qos dscp

 

Parameter

dscp_value DSCP value assigned to the port. Value ranges from 0 to 63. Default value is 0.

 

Example
This command sets the default DSCP of 44 on interfacee thernet 7. 
switch(config)# interface ethernet 7
switch(config-if-Et7)# qos dscp 44
switch(config-if-Et7)

qos map cos

The qos map cos command associates a traffic class to a list of class of service (CoS) settings. Multiple commands create a complete CoS to traffic class map. The switch uses this map to assign a traffic class to data packets on the basis of the packet’s CoS field or the port upon which it is received.

The no qos map cos and default qos map cos commands restore the specified CoS values to their default traffic class setting by deleting the corresponding qos map cos statements from running-config.

 

Command Mode

Global Configuration

 

Command Syntax

qos map cos cos_value_1 [cos_value_2 ... cos_value_n] to traffic-class tc_value

no qos map cos cos_value_1 [cos_value_2 ... cos_value_n]

default qos map cos cos_value_1 [cos_value_2 ... cos_value_n]

 

Parameters
  • cos_value_x      Class of Service (CoS) value. Value ranges from 0 to 7.
  • tc_value     Traffic class value. Value range varies by platform.

     

Default CoS to traffic class map varies by platform (Table 36).

 

Default Inbound CoS to Traffic Class Map

Table 36 displays the default CoS to traffic class map for each platform.

Table 36. Default CoS to Traffic Class Map
Inbound CoS untagged 0 1 2 3 4 5 6 7
Traffic Class (Arad /Jericho) Derived: use default CoS as inbound CoS 1 0 2 3 4 5 6 7
Traffic Class (FM6000) Derived: use default CoS as inbound CoS 1 0 2 3 4 5 6 7
Traffic Class (Helix) Derived: use default CoS as inbound CoS 1 0 2 3 4 5 6 7
Traffic Class (Petra) Assigned default traffic class 1 0 2 3 4 5 6 7
Traffic Class (Trident and Tomahawk) Derived: use default CoS as inbound CoS 1 0 2 3 4 5 6 7
Traffic Class (Trident II) Derived: use default CoS as inbound CoS 1 0 2 3 4 5 6 7

 

Related Commands
Example
This command assigns the traffic class 5 to the classes of service 1, 3, 5, and 7. 
switch(config)# qos map cos 1 3 5 7 to traffic-class 5
switch(config)#

qos map dscp

The qos map dscp command associates a traffic class to a set of Differentiated Services Code Point (DSCP) values. Multiple commands create a complete DSCP to traffic class map. The switch uses this map to assign a traffic class to data packets on the basis of the packet’s DSCP field or the chip upon which it is received.

This command configures the global DSCP to traffic-class map. To create additional named maps that can be attached to specific VRFs, use the qos map dscp to traffic-class command with the name option.

The no qos map dscp and default qos map dscp commands restore the specified DSCP values to their default traffic class settings by deleting corresponding qos map dscp statements from running-config.

 

Command Mode

Global Configuration

 

Command Syntax

qos map dscp dscpv_1 [dscpv_2...dscpv_n] to traffic-class tc_value

no qos map dscp dscpv_1 [dscpv_2...dscpv_n]

default qos map dscp dscpv_1 [dscpv_2...dscpv_n]

 

Parameters
  • dscpv_x      Differentiated Services Code Point (DSCP) value. Value ranges from 0 to 63.
  • tc_value      Traffic class value. Value range varies by platform.

     

Default map varies by platform (Table 37).

 

Default Inbound DSCP to Traffic Class Map

Table 37 displays the default DSCP to traffic class map for each platform.

Table 37. Default DSCP to Traffic Class Map
Inbound DSCP 0-7 8-15 16-23 24-31 32-39 40-47 48-55 56-63
Traffic Class (Arad /Jericho) 1 0 2 3 4 5 6 7
Traffic Class (FM6000) 1 0 2 3 4 5 6 7
Traffic Class (Helix) 1 0 2 3 4 5 6 7
Traffic Class (Petra) 1 0 2 3 4 5 6 7
Traffic Class (Trident and Tomahawk) 1 0 2 3 4 5 6 7
Traffic Class (Trident II) 1 0 2 3 4 5 6 7

 

Example
This command assigns the traffic class 3 to the DSCP values of 12, 13, 25, and 37. 
switch(config)# qos map dscp 12 13 25 37 to traffic-class 3
switch(config)#

qos map dscp to traffic-class

 

The qos map dscp to traffic-class command puts the switch in DSCP Map Configuration mode for the specified QoS map. If the map does not already exist, it is created as a copy of the global DSCP-to-traffic-class map. In DSCP Map Configuration mode, the dscp to traffic-class command is available to make changes to the map.

The no and default forms of the command remove the specified custom map.

 

Command Mode

Global Configuration

 

Command Syntax

qos map dscp to traffic-class name map_name

no qos map dscp to traffic-class name map_name

default qos map dscp to traffic-class name map_name

 

Parameters

  • map_name The name of the map to configure. If the map does not exist, it is created as a copy of the global DSCP-to-traffic-class map.

     

Example

This command creates the map map1 and places the switch in DSCP Map Configuration mode. 
switch(config)#qos map dscp to traffic-class name map1
switch(config-dscp-map-map1)#

qos map dscp to traffic-class (MPLS tunnel termination VRF)

The qos map dscp to traffic-class command assigns a DSCP-to-traffic-class map to a VRF, replacing the global map or previous custom map. The switch uses this map to assign a traffic class to data packets routed to this VRF on the basis of the DSCP fields of these packets.

The no qos map dscp to traffic-class and default qos map dscp to traffic-map commands remove the assignment of a custom map from the VRF, restoring the global map. default traffic class settings by deleting corresponding qos map dscp statements from running-config.

 

Command Mode

MPLS Tunnel Termination VRF Configuration

 

Command Syntax

qos map dscp to traffic-class map_name

no qos map dscp to traffic-class map_name

default qos map dscp to traffic-class map_name

 

Parameter
  • map_name      DSCP to traffic-class map name.

     

Example
These commands assign the map1 QoS DSCP-to-traffic-class map to the newVRF1 and newVRF2 VRFs. 
switch(config)#mpls tunnel termination
switch(config-mpls-tunnel-termination)#vrf newVRF1
switch(config-tunnel-termination-vrf-newVRF1)#qos map dscp to traffic-class map1
switch(config-tunnel-termination-vrf-newVRF1)#exit
switch(config-mpls-tunnel-termination)#vrf newVRF2
switch(config-tunnel-termination-vrf-newVRF2)#qos map dscp to traffic-class map1
switch(config-tunnel-termination-vrf-newVRF2)#exit
switch(config-tunnel-termination)#

qos map traffic-class to cos

The qos map traffic-class to cos command associates a class of service (CoS) to a list of traffic classes. Multiple commands create a complete traffic class to CoS map. The switch uses this map in CoS rewrite operations to fill the CoS field in outbound packets. This map is applicable to DSCP trusted ports and untrusted ports. CoS rewrite is disabled on CoS trusted ports. The show qos maps command displays the CoS to traffic class map.

The no qos traffic-class to cos and default qos traffic-class to cos commands restore the specified traffic class values to their default CoS settings by removing the corresponding qos map traffic-class to cos command from running-config.

 

Command Mode

Global Configuration

 

Command Syntax

qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to cos cos_value

no qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to cos

default qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to cos

 

Parameters
  • tc_num_x      Traffic class value. Value range varies by switch platform.
  • cos_value      Class of Service (CoS) value. Value ranges from 0 to 7.

     

Default Inbound Traffic Class to CoS Map

Table 38 displays the default traffic class to CoS map for each platform.

Table 38. Default Traffic Class to CoS Rewrite Value Map
Traffic Class 0 1 2 3 4 5 6 7
CoS Rewrite Value (Arad and /Jericho) 1 0 2 3 4 5 6 7
CoS Rewrite Value (FM6000) 1 0 2 3 4 5 6 7
CoS Rewrite Value (Helix) 1 0 2 3 4 5 6 7
CoS Rewrite Value (Petra) 1 0 2 3 4 5 6 7
CoS Rewrite Value (Trident and Tomahawk) 1 0 2 3 4 5 6 7
CoS Rewrite Value (Trident II) 1 0 2 3 4 5 6 7

 

Example
This command assigns the CoS 2 to traffic classes 1, 3, and 5. 
switch(config)# qos map traffic-class 1 3 5 to cos 2
switch(config)#

qos map traffic-class to dscp

The qos map traffic-class to dscp command associates a Differentiated Services Code Point (DSCP) value to a list of traffic classes. Multiple commands create a complete traffic class to DSCP map. The switch uses this map in DSCP rewrite operations to fill the DSCP field in outbound packets. This map is applicable to CoS trusted ports and untrusted ports but disabled by default on these ports. DSCP rewrite is disabled on DSCP trusted ports. The show qos maps command displays the traffic class to DSCP map.

The no qos traffic-class to dscp and default qos traffic-class to dscp commands restore the specified traffic class values to their default DSCP settings by removing the corresponding qos map traffic-class to dscp command from running-config.

 

Command Mode

Global Configuration

 

Command Syntax

qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to dscp dscp_value

no qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to dscp

default qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to dscp

 

Parameters
  • tc_num_x      Traffic class value. Value range varies by switch platform.
  • dscp_value      Differentiated Services Code Point (DSCP) value. Value ranges from 0 to 63.

     

Default Inbound Traffic Class to DSCP Map

Table 39 displays the default traffic class to DSCP map for each platform.

Table 39. Default Traffic Class to DSCP Rewrite Value Map
Traffic Class 0 1 2 3 4 5 6 7
DSCP Rewrite Value (FM6000) 8 0 16 24 32 40 48 56
DSCP Rewrite Value (Helix) 8 0 16 24 32 40 48 56
DSCP Rewrite Value (Trident and Tomahawk) 8 0 16 24 32 40 48 56
DSCP Rewrite Value (Trident II) 8 0 16 24 32 40 48 56

 

Example
This command assigns the DSCP value of 17 to traffic classes 1, 2, and 4. 
switch(config)# qos map traffic-class 1 2 4 to dscp 17
switch(config)#

qos map traffic-class to mc-tx-queue

The qos map traffic-class to mc-tx-queue command associates a multicast transmit queue to a list of traffic classes. Multiple commands create a complete traffic class to mc-tx-queue map. The switch uses this map to route outbound packets to transmit queues, which in turn schedules their transmission from the switch. The show qos maps command displays the traffic class to multicast transmit queue map.

The no qos traffic-class to mc-tx-queue and default qos traffic-class to mc-tx-queue commands restore the default traffic class to multicast transmit queue map for the specified traffic class values by removing the corresponding qos map traffic-class to mc-tx-queue command from running-config.

 

Command Mode

Global Configuration

 

Command Syntax

qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to mc-tx-queue mtq_value

no qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to mc-tx-queue

default qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to mc-tx-queue

 

Parameters
  • tc_num_x     Traffic class value. Value ranges from 0 to 7.
  • mtq_value      Multicast transmit queue number. Value ranges from 0 to 3.

     

Default Inbound Traffic Class to Multicast Transmit Queue Map

Table 40 displays the default traffic class to multicast transmit queue map for Trident and Tomahawk platform switches.

Table 40. Default Traffic Class to Multicast Transmit Queue Map
Traffic Class 0 1 2 3 4 5 6 7
Multicast Transmit Queue (Trident and Tomahawk) 0 0 1 1 2 2 3 3

 

Related Commands

 

Example
This command maps traffic classes 0, 4, and 5 to mc-tx-queue 2. 
switch(config)# qos map traffic-class 0 4 5 to mc-tx-queue 2
switch(config)#

qos map traffic-class to tx-queue

The qos map traffic-class to tx-queue command associates a transmit queue (tx-queue) to a list of traffic classes. Multiple commands create a complete traffic to tx-queue map. The switch uses this map to route outbound packets to transmit queues, which in turn schedules their transmission from the switch. The show qos maps command displays the transmit queue to traffic class map.

The no qos traffic-class to tx-queue and default qos traffic-class to tx-queue commands restore the specified traffic class values to their default transmit queue settings by removing the corresponding qos map traffic-class to tx-queue command from running-config.

 

Command Mode

Global Configuration

 

Command Syntax

qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to tx-queue txq_value

no qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to tx-queue

default qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to tx-queue

 

Parameters
  • tc_num_x      Traffic class value. Value range varies by platform.
  • txq_value      Transmit queue value. Value range varies by platform.

     

Restrictions

FM6000: When Priority Flow Control (PFC) is enabled, traffic classes are mapped to their corresponding transmit queues, regardless of existing qos map traffic-class to tx-queue statements.

Arad, Jericho, and Petra: Traffic class 7 always maps to transmit queue 7. This association is not editable.

Default Inbound Traffic Class to Transmit Queue Map

Table 41 displays the transmit queue to traffic class map.

 

Table 41. Default Traffic Class to Transmit Queue Map
Traffic Class 0 1 2 3 4 5 6 7
Transmit Queue (Arad /Jericho) 0 1 2 3 4 5 6 7
Transmit Queue (FM6000) 0 1 2 3 4 5 6 7
Transmit Queue (Helix) 0 1 2 3 4 5 6 7
Transmit Queue (Petra) 0 1 2 3 4 5 6 7
Transmit Queue (Trident II) 0 1 2 3 4 5 6 7

 

Related Commands
Example
This command maps traffic classes 0, 4, and 5 to tx-queue 4. 
switch(config)# qos map traffic-class 0 4 5 to tx-queue 4
switch(config)#

qos map traffic-class to uc-tx-queue

The qos map traffic-class to uc-tx-queue command associates a unicast transmit queue to a list of traffic classes. Multiple commands create a complete traffic class to unicast transmit queue map. The switch uses this map to route outbound packets to transmit queues, which in turn schedules their transmission from the switch. The show qos maps command displays the traffic class to unicast transmit queue map.

The no qos traffic-class to uc-tx-queue and default qos traffic-class to uc-tx-queue commands restore the default traffic class to unicast transmit queue map for the specified traffic class values by removing the corresponding qos map traffic-class to uc-tx-queue command from running-config.

 

Command Mode

Global Configuration

 

Command Syntax

qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to uc-tx-queue utq_value

no qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to uc-tx-queue

default qos map traffic-class tc_num_1 [tc_num_2 ... tc_num_n] to uc-tx-queue

 

Parameters
  • tc_num_x     Traffic class value. Value ranges from 0 to 7.
  • utq_value      Unicast transmit queue number. Value ranges from 0 to 7.

     

Default Inbound Traffic Class to Unicast Transmit Queue Map

Table 42 displays the default traffic class to Unicast transmit queue map for Trident and Tomahawk platform switches.

 

Table 42. Default Traffic Class to Unicast Transmit Queue Map
Traffic Class 0 1 2 3 4 5 6 7
Unicast Transmit Queue (Trident and Tomahawk) 0 1 2 3 4 5 6 7

 

Related Commands
Example
This command maps traffic classes 0, 4, and 5 to unicast transmit queue 4. 
switch(config)# qos map traffic-class 0 4 5 to uc-tx-queue 4
switch(config)#

qos profile

The qos profile command places the switch in QoS profile configuration mode and for the specified profile and creates the profile if it does not already exist. QoS profiles are used to apply the same QoS configuration to multiple interfaces.

The no qos profile and default qos profile command deletes the QoS profile from the running configuration.

The exit command returns the switch to global configuration mode.

 

Command Mode

Global Configuration

 

Command Syntax

qos profile profile_name

no qos profile profile_name

default qos profile profile_name

 

Parameter

profile_name     QoS profile name.

 

Note: Commands use a subset of the listed fields. Available subset depends on the specified parameter. Use CLI syntax assistance to view options for specific parameter when creating a QoS profile.

 

Example

This command places the switch in QoS profile configuration mode for policy map policy map TP and creates the policy map if it does not already exist.

switch(config)# qos profile TP
switch(config-qos-profile-TP)#

qos random-detect ecn allow non-ect chip-based (Tomahawk and Trident)

The qos random-detect ecn allow non-ect chip-based enables per color queue thresholds using color based queue thresholds and drop-precedence values along with drop of non-ect traffic by allowing non-ect and set drop-precedence 1 in a policy map simultaneously.

The no qos random-detect ecn allow non-ect chip-based and default qos random-detect ecn allow non-ect chip-based commands disbales the use of non-ect and set drop-precedence 1 simultaneously in a policy map in the running-config.

 

Command Mode

Global Configuration

 

Command Syntax

qos random-detect ecn allow non-ect chip-based

no qos random-detect ecn allow non-ect chip-based

default qos random-detect ecn allow non-ect chip-based

 

Example

The following command enables the use of non-ect and set drop-precedence 1 simultaneously in a policy map. 
switch(config)# qos random-detect ecn allow non-ect chip-based

qos random-detect ecn global-buffer (Helix)

The qos random-detect ecn global-buffer command enables ECN marking for globally shared packet memory and specifies minimum and maximum queue threshold sizes. Hosts can advertise their ECN capabilities in the ToS DiffServ field’s two least significant bits:
  • 00     Non ECN Capable transport.

     

  • 10     ECN Capable transport.

     

  • 01     ECN Capable transport.

     

  • 11     Congestion encountered.

     

Congestion is determined by comparing average queue size with queue thresholds. Average queue size is calculated through a formula based on the previous average and current queue size. Packets are marked based on this average size and the specified thresholds:
  • Average queue size below minimum threshold: Packets are queued normally.

     

  • Average queue size above maximum threshold: Packets are marked congestion encountered.

     

  • Average queue size between minimum and maximum thresholds. Packets are queued or marked congestion encountered. The proportion of marked packets varies linearly with average queue size:
    • 0% are marked when average queue size is less than or equal to minimum threshold.
    • 100% are marked when average queue size is greater than or equal to maximum threshold.

       

    When transmitted packets are marked Non ECN Capable, congestion packets are dropped, not marked.

The no qos random-detect ecn global-buffer and default qos random-detect ecn global-buffer commands disables ECN marking for the shared buffer by removing the qos random-detect ecn global-buffer command from running-config.

 

Command Mode

Global Configuration

 

Command Syntax

qos random-detect ecn global-buffer minimum-threshold MIN maximum-threshold MAX

no qos random-detect ecn global-buffer

default qos random-detect ecn global-buffer

 

Guidelines

Packet memory is divided into 46080 208-byte cells, whose allocation is managed by the memory management unit (MMU). The MMU tracks the cells that each entity uses and determines the number of cells that can be allocated to an entity.

 

Parameters

MIN and MAX parameters must use the same data unit.
  • MINMinimum threshold. Options include:
    • 1 to 19456 segments     208-byte segments units.
    • 1 to 4 mbytes     Megabyte units.
    • 1 to 4046 kbytes     Kilobyte units.
    • 1 to 4046848 bytes    Byte units.

       

  • MAX Maximum threshold. Options include:
    • 1 to 19456 segments     208-byte segments units.
    • 1 to 4 mbytes     Megabyte units.
    • 1 to 4046 kbytes     Kilobyte units.
    • 1 to 4046848 bytes    Byte units.

       

    Related Command

    random-detect ecn (Helix) enables ECN marking for a unicast transmit queue.

     

Examples
  • This command enables ECN marking of unicast packets from the global data pool and sets the minimum and maximum thresholds at 20 and 500 segments. 
    switch(config)# qos random-detect ecn global-buffer minimum-threshold 20 segments 
maximum-threshold 500 segments
switch(config)#

     

  • This command disables ECN marking of unicast packets from the global data pool. 
    switch(config)# no qos random-detect ecn global-buffer
switch(config)#

     

qos random-detect ecn global-buffer (Trident and Tomahawk)

The qos random-detect ecn global-buffer command enables ECN marking for globally shared packet memory and specifies minimum and maximum queue threshold sizes. Hosts can advertise their ECN capabilities in the ToS DiffServ field’s two least significant bits:
  • 00     Non ECN Capable transport.

     

  • 10     ECN Capable transport.

     

  • 01     ECN Capable transport.

     

  • 11     Congestion encountered.

     

Congestion is determined by comparing average queue size with queue thresholds. Average queue size is calculated through a formula based on the previous average and current queue size. Packets are marked based on this average size and the specified thresholds:
  • Average queue size below minimum threshold: Packets are queued normally.

     

  • Average queue size above maximum threshold: Packets are marked congestion encountered.

     

  • Average queue size between minimum and maximum thresholds. Packets are queued or marked congestion encountered. The proportion of marked packets varies linearly with average queue size:
    • 0% are marked when average queue size is less than or equal to minimum threshold.
    • 100% are marked when average queue size is greater than or equal to maximum threshold.

       

    When transmitted packets are marked Non ECN Capable, congestion packets are dropped, not marked.

The no qos random-detect ecn global-buffer and default qos random-detect ecn global-buffer commands disables ECN marking for the shared buffer by removing the qos random-detect ecn global-buffer command from running-config.

 

Command Mode

Global Configuration

 

Command Syntax

qos random-detect ecn global-buffer minimum-threshold MIN maximum-threshold MAX

no qos random-detect ecn global-buffer

default qos random-detect ecn global-buffer

 

Guidelines

Packet memory is divided into 46080 208-byte cells, whose allocation is managed by the memory management unit (MMU). The MMU tracks the cells that each entity uses and determines the number of cells that can be allocated to an entity.

Parameters

MIN and MAX parameters must use the same data unit.
  • MINMinimum threshold. Options include:
    • 1 to 46080 segments      208-byte segments units.
    • 1 to 9 mbytes     Megabyte units.
    • 1 to 9584 kbytes     Kilobyte units.
    • 1 to 9584640 bytes    Byte units.

       

  • MAXMaximum threshold. Options include:
    • 1 to 46080 segments     208-byte segments units.
    • 1 to 9 mbytes     Megabyte units.
    • 1 to 9584 kbytes     Kilobyte units.
    • 1 to 9584640 bytes    Byte units.

       

Related Command

random-detect ecn (Trident and Tomahawk) enables ECN marking for a unicast transmit queue.

 

Examples
  • This command enables ECN marking of unicast packets from the global data pool and sets the minimum and maximum thresholds at 20 and 500 segments. 
    switch(config)# qos random-detect ecn global-buffer minimum-threshold 20 segments maximum-threshold 500 segments
switch(config)#

     

  • This command disables ECN marking of unicast packets from the global data pool. 
    switch(config)# no qos random-detect ecn global-buffer
switch(config)#

     

qos rewrite cos

The qos rewrite cos command enables the rewriting of the CoS field for outbound tagged packets that were received on DSCP trusted ports and untrusted ports. CoS rewrite is always disabled on CoS trusted ports. The CoS value that is written into the packet is based on the data stream’s traffic class. CoS rewriting is active by default.

The no qos rewrite cos command disables CoS rewriting on the switch. The default qos rewrite cos command restores the default setting of enabling CoS rewriting by removing the no qos rewrite cos command from running-config.

 

Command Mode

Global Configuration

 

Command Syntax

qos rewrite cos

no qos rewrite cos

default qos rewrite cos

 

Related Command

qos map traffic-class to cos configures the traffic class to CoS rewrite map.

 

Example

This command enables CoS rewrite.

switch(config)# qos rewrite cos
switch(config)#

qos rewrite dscp

The qos rewrite dscp command enables the rewriting of the DSCP field for outbound tagged packets that were received on CoS trusted ports and untrusted ports. DSCP rewrite is always disabled on DSCP trusted ports. The DSCP value that is written into the packet is based on the data stream’s traffic class. DSCP rewriting is disabled by default.

The no qos rewrite dscp and default qos rewrite dscp commands disable DSCP rewriting on the switch by removing the no qos rewrite dscp command from running-config.

 

Command Mode

Global Configuration

 

Command Syntax

qos rewrite dscp

no qos rewrite dscp

default qos rewrite dscp

 

Related Command

qos map traffic-class to dscp configures the traffic class to DSCP rewrite map.

 

Example
This command enables DSCP rewrite. 
switch(config)# qos rewrite dscp
switch(config)#

qos trust

The qos trust command configures the quality of service port trust mode for the configuration mode interface. Trust-enabled ports classify traffic by examining the traffic’s CoS or DSCP value. Port trust mode default setting is cos for switched interfaces and dscp for routed interfaces.

The default qos trust command restores the default trust mode on the configuration mode interface by removing the corresponding qos trust or no qos trust statement from running-config.

The no qos trust command performs the following:
  • no qos trust places the port in untrusted mode.

     

  • no qos trust cos removes the corresponding qos trust cos statement.

     

  • no qos trust dscp removes the corresponding qos trust dscp statement.

     

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

qos trust [MODE]

no qos trust [MODE]

default qos trust

 

Parameters
  • MODETrust mode assigned to the port. Options include:
    • cos      Enables cos trust mode.
    • dscp      Enables dscp trust mode.

       

  • no qos trust Enables untrusted mode on the port.

     

Examples
  • This command configures trust mode of dscp for interface ethernet 7. 
    switch(config)# interface ethernet 7
switch(config-if-Et7)# qos trust dscp
switch(config-if-Et7)# show active
interface Ethernet7
   qos trust dscp
switch(config-if-Et7)#

     

  • This command configures trust mode of untrusted for Port Channel interface 23. 
    switch(config)# interface port-channel 23
switch(config-if-Po23)# no qos trust
switch(config-if-Po23)# show active
interface Port-Channel23
   no qos trust
switch(config-if-Po23)#

random-detect ecn (Arad/Jericho)

The random-detect ecn command enables ECN marking for the configuration mode unicast transmit queue and specifies threshold queue sizes. Hosts can advertise their ECN capabilities in the ToS DiffServ field’s two least significant bits:
  • 00     Non ECN Capable transport.

     

  • 10     ECN Capable transport.

     

  • 01     ECN Capable transport.

     

  • 11     Congestion encountered.

     

Congestion is determined by comparing average queue size with queue thresholds. Average queue size is calculated through a formula based on the previous average and current queue size. Packets are marked based on this average size and the specified thresholds:
  • Average queue size below minimum threshold: Packets are queued normally.

     

  • Average queue size above maximum threshold: Packets are marked congestion encountered.

     

  • Average queue size between minimum and maximum thresholds. Packets are queued or marked congestion encountered. The proportion of marked packets varies linearly with average queue size:
    • 0% are marked when average queue size is less than or equal to minimum threshold.
    • 100% are marked when average queue size is greater than or equal to maximum threshold.

       

    When transmitted packets are marked Non ECN Capable, congestion packets are dropped, not marked.

The no random-detect ecn and default qos random-detect ecn commands disables ECN marking for the shared buffer by removing the qos random-detect ecn command from running-config.

 

Command Mode

Tx-Queue configuration

 

Command Syntax

random-detect ecn minimum-threshold MIN maximum-threshold MAX

no random-detect ecn

default random-detect ecn

 

Parameters

MIN and MAX parameters must use the same data unit.
  • MINMinimum threshold. Options include:
    • 1 to 256 mbytes     Megabyte units.
    • 1 to 256000 kbytes     Kilobyte units.
    • 1 to 256000000 bytes    Byte units.

       

  • MAXMaximum threshold. Options include:
    • 1 to 256 mbytes     Megabyte units.
    • 1 to 256000 kbytes     Kilobyte units.
    • 1 to 256000000 bytes    Byte units.

       

Related Command

tx-queue (Arad/Jericho) places the switch in tx-queue configuration mode.

 

Example
These commands enable ECN marking of unicast packets from unicast transmit queue 4 of interface Ethernet 3/5/1, setting thresholds at 128 kbytes and 1280 kbytes. 
switch(config)# interface ethernet 3/5/1
switch(config-if-Et3/5/1)# tx-queue 4
switch(config-if-Et3/5/1-txq-4)# random-detect ecn minimum-threshold 128 kbytes 
maximum-threshold 1280 kbyte
switch(config-if-Et3/5/1-txq-4)# show active
interface Ethernet3/5/1
   tx-queue 4
      random-detect ecn minimum-threshold 128 kbytes maximum-threshold 1280 kbytes
switch(config-if-Et3/5/1-txq-4)#

random-detect ecn (Helix)

The random-detect ecn command enables ECN marking for the configuration mode unicast transmit queue and specifies threshold queue sizes. Hosts can advertise their ECN capabilities in the ToS DiffServ field’s two least significant bits:
  • 00     Non ECN Capable transport.

     

  • 10     ECN Capable transport.

     

  • 01     ECN Capable transport.

     

  • 11     Congestion encountered.

     

Congestion is determined by comparing average queue size with queue thresholds. Average queue size is calculated through a formula based on the previous average and current queue size. Packets are marked based on this average size and the specified thresholds:
  • Average queue size below minimum threshold: Packets are queued normally.

     

  • Average queue size above maximum threshold: Packets are marked congestion encountered.

     

  • Average queue size between minimum and maximum thresholds. Packets are queued or marked congestion encountered. The proportion of marked packets varies linearly with average queue size:
    • 0% are marked when average queue size is less than or equal to minimum threshold.
    • 100% are marked when average queue size is greater than or equal to maximum threshold.

       

    When transmitted packets are marked Non ECN Capable, congestion packets are dropped, not marked.

    Average queue length is tracked for transmit queues and the global pool independently. When either entity reaches its maximum threshold, all subsequent packets are marked.

     

The no random-detect ecn and default random-detect ecn commands disable ECN marking on the configuration mode queue, deleting the corresponding random-detect ecn command from running-config.

 

Command Mode

Tx-Queue configuration

 

Command Syntax

random-detect ecn minimum-threshold MIN maximum-threshold MAX

no random-detect ecn

default random-detect ecn

 

Parameters

MIN and MAX parameters must use the same data unit.
  • MINMinimum threshold. Options include:
    • 1 to 46080 segments      208-byte segments units.
    • 1 to 9 mbytes      Megabyte units.
    • 1 to 9584 kbytes      Kilobyte units.
    • 1 to 9584640 bytes     Byte units.

       

  • MAX Maximum threshold. Options include:
    • 1 to 46080 segments     208-byte segments units.
    • 1 to 9 mbytes     Megabyte units.
    • 1 to 9584 kbytes     Kilobyte units.
    • 1 to 9584640 bytes    Byte units.

       

Related Commands
Examples
  • These commands enable ECN marking of unicast packets from transmit queue 4 of interface ethernet 15, setting thresholds at 10 and 100 segments. 
    switch(config)# interface ethernet 15
switch(config-if-Et15)# uc-tx-queue 4
switch(config-if-Et15-txq-4)# random-detect ecn minimum-threshold 10 segments 
maximum-threshold 100 segments
switch(config-if-Et15-txq-4)# show active
interface Ethernet15
   tx-queue 4
      random-detect ecn minimum-threshold 10 segments maximum-threshold 100 
segments
switch(config-if-Et15-txq-4)# exit
switch(config-if-Et15)

     

  • This command disables ECN marking of unicast packets from transmit queue 4 of interface ethernet 15. 
    switch(config-if-Et15-txq-4)# no random-detect ecn
switch(config-if-Et15-txq-4)# show active
interface Ethernet15
switch(config-if-Et15-txq-4)# exit
switch(config-if-Et15)#

random-detect ecn (Trident and Tomahawk)

The random-detect ecn command enables ECN marking for the configuration mode unicast transmit queue and specifies threshold queue sizes. Hosts can advertise their ECN capabilities in the ToS DiffServ field’s two least significant bits:
  • 00 Non ECN Capable transport.

     

  • 10     ECN Capable transport.

     

  • 01     ECN Capable transport.

     

  • 11     Congestion encountered.

     

Congestion is determined by comparing average queue size with queue thresholds. Average queue size is calculated through a formula based on the previous average and current queue size. Packets are marked based on this average size and the specified thresholds:
  • Average queue size below minimum threshold: Packets are queued normally.

     

  • Average queue size above maximum threshold: Packets are marked congestion encountered.

     

  • Average queue size between minimum and maximum thresholds. Packets are queued or marked congestion encountered. The proportion of marked packets varies linearly with average queue size:
    • 0% are marked when average queue size is less than or equal to minimum threshold.
    • 100% are marked when average queue size is greater than or equal to maximum threshold.

       

    When transmitted packets are marked Non ECN Capable, congestion packets are dropped, not marked.

    Average queue length is tracked for transmit queues and the global pool independently. When either entity reaches its maximum threshold, all subsequent packets are marked.

     

The no random-detect ecn and default random-detect ecn commands disable ECN marking on the configuration mode queue, deleting the corresponding random-detect ecn command from running-config.

 

Command Mode

Uc-Tx-Queue configuration

 

Command Syntax

random-detect ecn minimum-threshold MIN maximum-threshold MAX

no random-detect ecn

default random-detect ecn

 

Parameters

MIN and MAX parameters must use the same data unit.
  • MINMinimum threshold. Options include:
    • 1 to 46080 segments      208-byte segments units.
    • 1 to 9 mbytes      Megabyte units.
    • 1 to 9584 kbytes      Kilobyte units.
    • 1 to 9584640 bytes     Byte units.

       

  • MAX Maximum threshold. Options include:
    • 1 to 46080 segments      208-byte segments units.
    • 1 to 9 mbytes      Megabyte units.
    • 1 to 9584 kbytes      Kilobyte units.
    • 1 to 9584640 bytes     Byte units.

       

Related Commands

 

Examples
  • These commands enable ECN marking of unicast packets from unicast transmit queue 4 of interface ethernet 15, setting thresholds at 10 and 100 segments. 
    switch(config)# interface ethernet 15
switch(config-if-Et15)# uc-tx-queue 4
switch(config-if-Et15-uc-txq-4)# random-detect ecn minimum-threshold 10 segments 
maximum-threshold 100 segments 
switch(config-if-Et15-uc-txq-4)#show active
interface Ethernet15
   uc-tx-queue 4
      random-detect ecn minimum-threshold 10 segments maximum-threshold 100 
segments
switch(config-if-Et15-uc-txq-4)# exit
switch(config-if-Et15)#

     

  • This command disables ECN marking of unicast packets from unicast transmit queue 4 of interface ethernet 15. 
    switch(config-if-Et15-uc-txq-4)# no random-detect ecn
switch(config-if-Et15-uc-txq-4)# show active
interface Ethernet15
switch(config-if-Et15-uc-txq-4)# exit
switch(config-if-Et15)#

random-detect ecn delay threshold

The random-detect ecn delay threshold command configures latency-based ECN on a per transmit queue basis.

The [no|default] version of the command disables the configuration and deletes the random-detect ecn delay threshold from the running-config.

Command Mode

Interface Configuration

Command Syntax

random-detect ecn delay threshold [microseconds | milliseconds ]

Parameters

  • random-detect - Set WRED-based congestion control parameters.
  • ecn - Set ECN parameters.
  • delay - Set the delay parameter.
  • threshold - Configure the threshold to trigger latency-based ECN.
    • microseconds - Configure a value from 1 to 4294967 microseconds.
    • milliseconds - Configure a value from 1 to 4294 milliseconds.

Example

Use the following commands to configure transmit queue 1 on Ethernet 1/1 for latency-based ECN:

switch(config)#interface Ethernet 1/1
switch(config-if-Et1/1)#tx-queue 3
switch(config-if-Et1/1-txq-3)#random-detect ecn delay threshold 33 milliseconds

service-policy type qos input

The service-policy type qos input command applies the specified policy map to a QoS profile. The profile is then applied to an interface in interface configuration mode using the service-profile command.

The no service-policy type qos and default service-policy type qos command deletes the policy map from the profile.

The exit command returns the switch to global configuration mode.

 

Command Mode

QoS Profile Configuration

 

Command Syntax

service-policy type qos input policy_map_name

no service-policy type qos input policy_map_name

default service-policy type qos input policy_map_name

 

Parameter

policy_map_name      QoS policy map name.

 

Example
This command applies the policy map PM-1 to the QoS profile TP. 
switch(config-qos-profile-TP)# service-policy type qos input PM-1
switch(config-qos-profile-TP)#

service-profile

The command applies the QoS profile to the configuration mode interface.

The no service-profile and the default service-profile command removes the QoS profile from the interface.

The exit command returns the switch to global configuration mode.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

service-profile profile_name

no service-profile profile_name

default service-profile profile_name

 

Parameter

profile_name QoS profile name.

 

Example
This commands applies the QoS profile TP to interfaceethernet 13. 
switch(config)# interface ethernet 13
switch(config-if-Et13)# service-profile TP

set extcommunity

The set extcommunity command adds a color extended community to be applied to routes affected by the route-map. Multiple set clauses can be applied to a single route-map to configure multiple colors for routes.Negating the command removes the entry from the route-map.

 

Command Mode

Config-route-map mode

 

Command Syntax

set extcommunity COLOR-EXPRESSION [additive | delete]

no set extcommunity COLOR-EXPRESSION [additive | delete]

default set extcommunity COLOR-EXPRESSION [additive | delete]

 

Parameters
  • COLOR-EXPRESSION The color extended community to be applied to routes affected by the route-map.
  • additiveAdds the extended communities to those received.
  • delete Deletes any matching extended color communities.

     

Example 
switch(config)# route-map foo
switch(config-route-map foo)# set extcommunity color 1
switch(config-route-map foo)# set extcommunity color 2 color-only exact-match
switch(config-route-map foo)# set extcommunity color 3 color-only endpoint-match null
switch(config-route-map foo)# set extcommunity color 4 color-only endpoint-match any

shape rate (Interface – Arad/Jericho)

The shape rate command specifies the maximum bandwidth for outbound traffic on the configuration mode interface, also known as queue shaping. The shape rate for individual transmit queues is configured by the shape rate (Tx-queue – Arad/Jericho) command. By default, outbound transmission rate is not bounded by a shape rate.

The no shape rate and default shape rate commands remove the shape rate bandwidth limit on the configuration mode interface by deleting the corresponding shape rate command from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

shape rate byte_limit [kbps]

no shape rate

default shape rate

 

Parameters

byte_limit      Shape rate applied to interface (Kbps). Value ranges from 162 to 100000000.

 

Example
This command configures a port shape rate of 5 Gbps on interface ethernet 3/5/1. 
switch(config)# interface ethernet 3/5/1
switch(config-if-Et3/5/1)# shape rate 5000000
switch(config-if-Et3/5/1)# show qos interfaces ethernet 3/5/1

Ethernet3/5/1:

   Port shaping rate: 5000012 / 5000000 kbps

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D
   6      - / -        - / -    (  -  )    SP / SP    D
   5      - / -        - / -    (  -  )    SP / SP    D
   4      - / -        - / -    (  -  )    SP / SP    D
   3      - / -        - / -    (  -  )    SP / SP    D
   2      - / -        - / -    (  -  )    SP / SP    D
   1      - / -        - / -    (  -  )    SP / SP    D
   0      - / -        - / -    (  -  )    SP / SP    D

switch(config-if-Et3/5/1)#

shape rate (Interface – FM6000)

The shape rate command specifies the maximum bandwidth for outbound traffic on the configuration mode interface, also known as queue shaping. The shape rate for individual transmit queues is configured by the shape rate (Tx-queue – FM6000)command. By default, outbound transmission rate is not bounded by a shape rate.

The no shape rate and default shape rate commands remove the shape rate bandwidth limit on the configuration mode interface by deleting the corresponding shape rate command from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

shape rate byte_limit [kbps]

no shape rate

default shape rate

 

Parameter

byte_limit      Shape rate applied to interface (Kbps). Value ranges from 7000 to 10000000.

 

Guidelines

Enabling port shaping on an FM6000 interface disables queue shaping internally. Disabling port shaping restores queue shaping as specified in running-config.

 

Example
This command configures a port shape rate of 5 Gbps on interface ethernet 5. 
switch(config)# interface ethernet 5
switch(config-if-Et5)# shape rate 5000000
switch(config-if-Et5)#

shape rate (Interface – Helix)

The shape rate command specifies the maximum bandwidth for outbound traffic on the configuration mode interface, also known as queue shaping. The shape rate for individual transmit queues is configured by the shape rate (Interface – Helix)command. By default, outbound transmission rate is not bounded by a shape rate.

The no shape rate and default shape rate commands remove the shape rate bandwidth limit on the configuration mode interface by deleting the corresponding shape rate command from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

shape rate DATA_LIMIT

no shape rate

default shape rate

 

Parameters
  • DATA_LIMIT Shape rate applied to interface. Value range varies with data unit:
    • 8 to 40000000 8 to 40000000 kbytes per second.
    • 8 to 40000000kbps      8 to 40000000 kbytes per second.
    • 8 to 60000000pps      8 to 60000000 packets per second.

       

Guidelines

Shaping rates of at least 8 kbps are supported. At shaping rates smaller than 1 Mbps, granularity and rounding errors may skew the actual shaping rate by 20% from the specified rate.

 

Example
This command configures a port shape rate of 5 Gbps on interface ethernet 17. 
switch(config)# interface ethernet 17
switch(config-if-Et17)# shape rate 5000000 kbps
switch(config-if-Et17)# show qos interface ethernet 17/3

Ethernet17:
   Trust Mode: COS
   Default COS: 0
   Default DSCP: 0

   Port shaping rate: 5000000 / 5000000 kbps

  Tx       Bandwidth                 Shape Rate        Priority
 Queue     Guaranteed (units)         (units)
   ------------------------------------------------------------
   7        - / -    (  -  )       - / -    (  -  )    SP / SP
   6        - / -    (  -  )       - / -    (  -  )    SP / SP

switch(config-if-Et17)#

shape rate (Interface – Petra)

The shape rate command specifies the maximum bandwidth for outbound traffic on the configuration mode interface, also known as queue shaping. The shape rate for individual transmit queues is configured by the shape rate (Tx-queue – Petra) command. By default, outbound transmission rate is not bounded by a shape rate.

The no shape rate and default shape rate commands remove the shape rate bandwidth limit on the configuration mode interface by deleting the corresponding shape rate command from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

shape rate data_limit [kbps]

no shape rate

default shape rate

 

Parameters

data_limit      Shape rate applied to interface (Kbps). Value ranges from 100 to 10000000.

 

Guidelines

The following port shaping rates are supported:
  • 1G ports: above 100 kbps.
  • 10G ports: above 7900 kbps.

     

Commands that specify a smaller shape rate disable port shaping on the interface.

 

Example
This command configures a port shape rate of 5 Gbps on interface ethernet 3/3. 
switch(config)# interface ethernet 3/3
switch(config-if-Et3/3)# shape rate 5000000
switch(config-if-Et3/3)# show active
interface Ethernet3/3
   shape rate 5000000
switch(config-if-Et3/3)#

shape rate (Interface – Trident and Tomahawk)

The shape rate command specifies the maximum bandwidth for outbound traffic on the configuration mode interface, also known as queue shaping. The shape rate for individual transmit queues is configured by the shape rate (Tx-queue – Trident and Tomahawk) command. By default, outbound transmission rate is not bounded by a shape rate.

The no shape rate and default shape rate commands remove the shape rate bandwidth limit on the configuration mode interface by deleting the corresponding shape rate command from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

shape rate DATA_LIMIT

no shape rate

default shape rate

 

Parameters
  • DATA_LIMITShape rate applied to interface. Value range varies with data unit:
    • 8 to 40000000      8 to 40000000 kbytes per second.
    • 8 to 40000000kbps      8 to 40000000 kbytes per second.
    • 8 to 60000000pps      8 to 60000000 packets per second.

       

Guidelines

Shaping rates of at least 8 kbps are supported. At shaping rates smaller than 1 Mbps, granularity and rounding errors may skew the actual shaping rate by 20% from the specified rate.

 

Example
This command configures a port shape rate of 5 Gbps on interface ethernet 5. 
switch(config)# interface ethernet 5
switch(config-if-Et5)# shape rate 5000000
switch(config-if-Et5)#

shape rate (Interface – Trident II)

The shape rate command specifies the maximum bandwidth for outbound traffic on the configuration mode interface, also known as queue shaping. The shape rate for individual transmit queues is configured by the shape rate (Tx-queue – Trident II) command. By default, outbound transmission rate is not bounded by a shape rate.

The no shape rate and default shape rate commands remove the shape rate bandwidth limit on the configuration mode interface by deleting the corresponding shape rate command from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

shape rate DATA_LIMIT

no shape rate

default shape rate

 

Parameters

DATA_LIMIT Shape rate applied to interface. Value range varies with data unit:
    • 8 to 40000000 kbps    8 to 40000000 kbytes per second.
    • 8 to 40000000 kbps      8 to 40000000 kbytes per second.

    • 8 to 60000000 pps      8 to 60000000 packets per second.

       

Guidelines

Shaping rates of at least 8 kbps are supported. At shaping rates smaller than 1 Mbps, granularity and rounding errors may skew the actual shaping rate by 20% from the specified rate.

 

Example
This command configures a port shape rate of 5 Gbps on interface ethernet 17/3. 
switch(config)# interface ethernet 17/3
switch(config-if-Et17/3)# shape rate 5000000 kbps
switch(config-if-Et17/3)# show qos interface ethernet 17/3

Ethernet17/3:
   Trust Mode: COS
   Default COS: 0
   Default DSCP: 0

   Port shaping rate: 5000000 / 5000000 kbps

  Tx       Bandwidth                 Shape Rate        Priority
 Queue     Guaranteed (units)         (units)
   ------------------------------------------------------------
   7        - / -    (  -  )       - / -    (  -  )    SP / SP
   6        - / -    (  -  )       - / -    (  -  )    SP / SP

switch(config-if-Et17/3)#

shape rate (Tx-queue – Arad/Jericho)

The shape rate command specifies the maximum bandwidth for outbound traffic on the transmit queue, also known as queue shaping. The shape rate for interfaces is configured by the shape rate (Interface – Arad/Jericho) command. By default, the configured outbound transmission rate is not bounded by a transmit queue shape rate.

Shaping rates greater than 50000 kbps are supported. At lower shaping rates (less than 10 Mbps), granularity and rounding errors may skew the actual shaping rate by 20% from the specified rate.

The no shape rate and default shape rate commands remove the shape rate bandwidth limit on the configuration mode queue by deleting the corresponding shape rate command from running-config.

 

Command Mode

Tx-Queue Configuration

 

Command Syntax

shape rate byte_limit [kbps]

no shape rate

default shape rate

 

Parameters

byte_limit     Shape rate applied to interface (Kbps). Value ranges from 50000 to 100000000.

 

Related Command

tx-queue (Arad/Jericho) places the switch in tx-queue configuration mode.

 

Related Information

shape rate (Interface – Arad/Jericho)

 

Example
These commands configure a shape rate of 1 Gbps on transmit queues 3 and 4 of interface ethernet 3/4/1. 
switch(config)# interface ethernet 3/4/1
switch(config-if-Et3/4/1)# tx-queue 4
switch(config-if-Et3/4/1-txq-4)# shape rate 1000000 kbps
switch(config-if-Et3/4/1-txq-4)# tx-queue 3
switch(config-if-Et3/4/1-txq-3)# shape rate 1000000 kbps
switch(config-if-Et3/4/1-txq-3)# show qos interface ethernet 3/4/1

Ethernet3/4/1:

   Port shaping rate: disabled

  Tx    Bandwidth       Shape Rate        Priority  ECN
 Queue  (percent)        (units)
   -----------------------------------------------------
   7      - / -        - / -    (  -  )    SP / SP    D
   6      - / -        - / -    (  -  )    SP / SP    D
   5      - / -        - / -    (  -  )    SP / SP    D
   4      - / -      999 / 1000 ( Mbps )   SP / SP    D
   3      - / -      999 / 1000 ( Mbps )   SP / SP    D
   2      - / -        - / -    (  -  )    SP / SP    D
   1      - / -        - / -    (  -  )    SP / SP    D
   0      - / -        - / -    (  -  )    SP / SP    D

switch(config-if-Et3/4/1-txq-3)#

shape rate (Tx-queue – FM6000)

The shape ratecommand specifies the maximum bandwidth for outbound traffic on the transmit queue, also known as queue shaping. The shape rate for interfaces is configured by the shape rate (Interface – FM6000) command. By default, the configured outbound transmission rate is not bounded by a transmit queue shape rate.

Queue shaping on an FM6000 port is supported only when port shaping is not enabled on the interface. Enabling port shaping on a port disables queue shaping internally. Disabling port shaping restores queue shaping as specified by running-config.

Shaping rates greater than 460 kbps are supported. At lower shaping rates (less than 10 Mbps), granularity and rounding errors may skew the actual shaping rate by 20% from the specified rate.

The no shape rate and default shape rate commands remove the shape rate bandwidth limit on the transmit queue by deleting the corresponding shape rate command from running-config.

 

Command Mode

Tx-Queue Configuration

 

Command Syntax

shape rate byte_limit [kbps]

no shape rate

default shape rate

 

Parameters

byte_limit      Shape rate applied to interface (Kbps). Value ranges from 464 to 10000000.

 

Related Commands
Example
These commands configure a shape rate of 1 Gbps (1,000,000 Kbps) on transmit queues 3 and 4 of interface ethernet 19. 
switch(config)# interface ethernet 19
switch(config-if-Et19)# tx-queue 4
switch(config-if-Et19-txq-4)# shape rate 1000000
switch(config-if-Et19-txq-4)# tx-queue 3
switch(config-if-Et19-txq-3)# shape rate 1000000
switch(config-if-Et19-txq-3)# show qos interface ethernet 19

Ethernet19:
   Trust Mode: COS

   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
   -----------------------------------------------
          6         N/A     disabled        strict
          5         N/A     disabled        strict
          4         N/A      1000000        strict
          3          25      1000000   round-robin
          2          25     disabled   round-robin
          1          25     disabled   round-robin
          0          25     disabled   round-robin

switch(config-if-Et19-txq-3)#

shape rate (Tx-queue – Helix)

The shape rate command specifies the maximum bandwidth for outbound traffic on the transmit queue, also known as queue shaping. The shape rate for interfaces is configured by the shape rate (Interface – Helix) command. By default, the configured outbound transmission rate is not bounded by a transmit queue shape rate.

The no shape rate and default shape rate commands remove the shape rate bandwidth limit on the configuration mode transmit queue by deleting the corresponding shape rate command from running-config.

 

Command Mode

Tx-Queue Configuration

 

Command Syntax

shape rate byte_limit [kbps]

no shape rate

default shape rate

 

Parameters

DATA_LIMIT Shape rate applied to the queue. Value range varies with data unit:
    • 8 to 40000000       8 to 40,000,000 kbytes per second.
    • 8 to 40000000 kbps      8 to 40000000 kbytes per second.
    • 8 to 60000000 pps      8 to 60000000 packets per second.

       

Restrictions

Queue shaping is not supported in cut-through mode.

 

Related Commands
Example
These commands configure a shape rate of 1 Gbps (1,000,000 Kbps) on transmit queues 3 and 4 of interface Eethernet 17/3. 
switch(config)# interface ethernet 17/3
switch(config-if-Et17/3)# tx-queue 4
switch(config-if-Et17/3-txq-4)# shape rate 1000000 kbps
switch(config-if-Et17/3-txq-4)# tx-queue 3
switch(config-if-Et17/3-txq-3)# shape rate 1000000 kbps
switch(config-if-Et17/3-txq-3)# show qos interface ethernet 17/3

Ethernet17/3:

  Tx       Bandwidth                 Shape Rate        Priority
 Queue     Guaranteed (units)         (units)
   ------------------------------------------------------------
   7        - / -    (  -  )       - / -    (  -  )    SP / SP
   6        - / -    (  -  )       - / -    (  -  )    SP / SP
   5        - / -    (  -  )       - / -    (  -  )    SP / SP
   4        - / -    (  -  )       1 / 1    ( Gbps )   SP / SP
   3        - / -    (  -  )       1 / 1    ( Gbps )   SP / SP
   2        - / -    (  -  )       - / -    (  -  )    SP / SP
   1        - / -    (  -  )       - / -    (  -  )    SP / SP
   0        - / -    (  -  )       - / -    (  -  )    SP / SP

switch(config-if-Et17/3-txq-3)#

shape rate (Tx-queue – Petra)

The shape rate command specifies the maximum bandwidth for outbound traffic on the configuration mode transmit queue, also known as queue shaping. The shape rate for interfaces is configured by the shape rate (Interface – Petra) command. By default, the configured outbound transmission rate is not bounded by a transmit queue shape rate.

Queue shaping applies only to unicast traffic. Shaping rates of at least 162 Kbps are supported.

The no shape rate and default shape rate commands remove the shape rate bandwidth limit on the configuration mode queue by deleting the corresponding shape rate command from running-config.

 

Command Mode

Tx-Queue Configuration

 

Command Syntax

shape rate DATA_LIMIT

no shape rate

default shape rate

 

Parameters

DATA_LIMITShape rate applied to the queue. Value range varies with data unit:
    • 8 to 40000000 kbps Range is from 8 to 40000000 kbytes per second.
    • 8to 60000000pps Range is from 8 to 60000000 packets per second.

       

    Shaping rates greater than 460 kbps are supported. At lower shaping rates (less than 10 Mbps), granularity and rounding errors may skew the actual shaping rate by 20% from the specified rate.

     

Related Commands
Example
These commands configure a shape rate of 1 Gbps (1,000,000 Kbps) on transmit queues 3 and 4 of interface ethernet 3/28. 
switch(config)# interface ethernet 3/28
switch(config-if-Et3/28)# tx-queue 4
switch(config-if-Et3/28-txq-4)# shape rate 1000000
switch(config-if-Et3/28-txq-4)# tx-queue 3
switch(config-if-Et3/28-txq-3)# shape rate 1000000
switch(config-if-Et3/28-txq-3)# show qos interface ethernet 3/28

Ethernet3/28:

   Tx-Queue   Bandwidth    Shape Rate     Priority
              (percent)       (Kbps)
   -----------------------------------------------
          7         N/A     disabled        strict
          6         N/A     disabled        strict
          5         N/A     disabled        strict
          4         N/A      1000000        strict
          3          25      1000000   round-robin
          2          25     disabled   round-robin
          1          25     disabled   round-robin
          0          25     disabled   round-robin

switch(config-if-Et3/28-txq-3)#

shape rate (Tx-queue – Trident and Tomahawk)

The shape rate command specifies the maximum bandwidth for outbound traffic on the configuration mode transmit queue, also known as queue shaping. The shape rate for interfaces is configured by the shape rate (Interface – Trident and Tomahawk) command. By default, the configured outbound transmission rate is not bounded by a transmit queue shape rate.

The no shape rate and default shape rate commands remove the shape rate limit from the configuration mode transmit queue by deleting the corresponding shape rate command from running-config.

 

Command Mode

Mc-Tx-Queue configuration

Uc-Tx-Queue configuration

 

Command Syntax

shape rate DATA_LIMIT

no shape rate

default shape rate

 

Parameters
  • DATA_LIMIT Shape rate applied to the queue. Value range varies with data unit:
    • 8 to 40000000  kbps     Range is from 8 to 40000000 kbytes per second.

    • 8 to 60000000 pps      Range is from 8 to 60000000 packets per second.

       

Related Commands

Guidelines

Shaping rates of at least 8 kbps are supported. At shaping rates smaller than 1 Mbps, granularity and rounding errors may skew the actual shaping rate by 20% from the specified rate.

When two queues source traffic from the same traffic class and the higher priority queue is shaped, that queue consumes all internal buffers, starving the lower priority queue even if bandwidth is available.

 

Example
These commands configure a shape rate of 1 Gbps (1,000,000 Kbps) on unicast transmit queues 3 and multicast transmit 4 of interface ethernet 7. 
switch(config)# interface ethernet 7
switch(config-if-Et7)# uc-tx-queue 3
switch(config-if-Et7-uc-txq-3)# shape rate 1000000
switch(config-if-Et7-uc-txq-3)# mc-tx-queue 2
switch(config-if-Et7-mc-txq-2)# shape rate 1000000
switch(config-if-Et7-mc-txq-2)# show qos interface ethernet 7

Ethernet7:

   Tx-Queue   Bandwidth    Shape Rate     Priority   Priority Group
              (percent)       (Kbps)
   ----------------------------------------------------------------
        UC7         N/A     disabled        strict                1
        UC6         N/A     disabled        strict                1
        MC3         N/A     disabled        strict                1
        UC5         N/A     disabled        strict                0
        UC4         N/A     disabled        strict                0
        MC2         N/A      1000000        strict                0
        UC3          20      1000000   round-robin                0
        UC2          16     disabled   round-robin                0
        MC1          16     disabled   round-robin                0
        UC1          16     disabled   round-robin                0
        UC0          16     disabled   round-robin                0
        MC0          16     disabled   round-robin                0

switch(config-if-Et7-mc-txq-2)#

shape rate (Tx-queue – Trident II)

The shape rate command specifies the maximum bandwidth for outbound traffic on the configuration mode transmit queue, also known as queue shaping. The shape rate for interfaces is configured by the shape rate (Interface – Trident II) command. By default, the configured outbound transmission rate is not bounded by a transmit queue shape rate.

The no shape rate and default shape rate commands remove the shape rate bandwidth limit on the configuration mode transmit queue by deleting the corresponding shape rate command from running-config.

 

Command Mode

Tx-Queue Configuration

 

Command Syntax

shape rate byte_limit [kbps]

no shape rate

default shape rate

 

Parameters

DATA_LIMIT Shape rate applied to the queue. Value range varies with data unit:
    • 8 to 40000000 kbps      Range is from 8 to 40000000 kbytes per second.
    • 8 to 60000000 pps       Range is from 8 to 60000000 packets per second.

       

Restrictions

Queue shaping is not supported in cut-through mode

 

Related Commands
Example
These commands configure a shape rate of 1 Gbps (1,000,000 Kbps) on transmit queues 3 and 4 of interface ethernet 17/3. 
switch(config)# interface ethernet 17/3
switch(config-if-Et17/3)# tx-queue 4
switch(config-if-Et17/3-txq-4)# shape rate 1000000 kbps
switch(config-if-Et17/3-txq-4)# tx-queue 3
switch(config-if-Et17/3-txq-3)# shape rate 1000000 kbps
switch(config-if-Et17/3-txq-3)# show qos interface ethernet 17/3

Ethernet17/3:

  Tx       Bandwidth                 Shape Rate        Priority
 Queue     Guaranteed (units)         (units)
   ------------------------------------------------------------
   7        - / -    (  -  )       - / -    (  -  )    SP / SP
   6        - / -    (  -  )       - / -    (  -  )    SP / SP
   5        - / -    (  -  )       - / -    (  -  )    SP / SP
   4        - / -    (  -  )       1 / 1    ( Gbps )   SP / SP
   3        - / -    (  -  )       1 / 1    ( Gbps )   SP / SP
   2        - / -    (  -  )       - / -    (  -  )    SP / SP
   1        - / -    (  -  )       - / -    (  -  )    SP / SP
   0        - / -    (  -  )       - / -    (  -  )    SP / SP

switch(config-if-Et17/3-txq-3)#

show interface counters queue drop-precedence

The show interface counters queue drop-precedence command displays the drop-precedence counters.

 

Command Mode

EXEC

 

Command Syntax

show interface counters queue drop-precedence

 

Example
This command displays the drop precedence counts on two interfaces. 
switch# show interface counters queue drop-precedence
intf        0          1          2
Et1/1     100          0        200
Et1/2     200          0        300
switch#

show platform petraA traffic-class

The show platform petraA traffic-class command displays the traffic class assignment on all specified Petra chips. Each chip controls eight Ethernet interfaces. The default traffic class of an interface is specified by the traffic class assigned to the chip that controls the interface.

Traffic class assignments are configured with the platform petraA traffic-class command.

Valid command options include:
  • show platform petraA traffic-class       Traffic class of all chips on all linecard.
  • show platform petraA CHIP_NAME traffic-class      Traffic class of specified chip.
  • show platform petraA MODULE_NAME traffic-class    Traffic class of all chips on specified linecard.

     

Command Mode

EXEC

 

Command Syntax

show platform petraA traffic-class

show platform petraA CHIP_NAME traffic-class

show platform petraA MODULE_NAME traffic-class

 

Parameters
  • CHIP_NAMEName of Petra chip on linecard that control Ethernet ports. Options include:
    • petra cardX / chipY      All ports on PetraA chip chipY on linecard cardX (7500 Series).
    • petra chipZ      All ports on PetraA chip chipZ (7048 Series).

       

    7500 Series

    Switches can contain up to eight linecards. cardX varies from 3 to 10.

    Each linecard contains six PetraA chips. Each chip controls eight ports. chipY varies from 0 to 5:
    • 0 controls ports 1 through 8
    • 1 controls ports 9 through 16
    • 2 controls ports 17 through 24
    • 3 controls ports 25 through 32
    • 4 controls ports 33 through 40
    • 5 controls ports 41 through 48

       

    7048 Series

    Each switch contains two PetraA chips. chipZ varies from 0 to 1:
    • 0 controls ports 1 through 32
    • 1 controls ports 33 through 52

       

  • MODULE_NAME Name and number of linecard (7500 Series). Options include:
    • module linecard mod_num     Linecard number (3 to 10).
    • module mod_num      Linecard number (3 to 10).

       

Related Command

platform petraA traffic-class configures the default traffic class used by all ports on a specified chip.

 

Example
This command displays the traffic class of all chips on linecard 3. 
switch# show platform petraA module linecard 3 traffic-class
Petra3/0 traffic-class: 1
Petra3/1 traffic-class: 1
Petra3/2 traffic-class: 1
Petra3/3 traffic-class: 1
Petra3/4 traffic-class: 5
Petra3/5 traffic-class: 1
switch#

show platform trident tcam qos detail

The show platform trident tcam qos detail command displays the list of all the SVIs that are sharing the TCAM entries.

 

Command Mode

EXEC

 

Command Syntax

show platform trident tcam qos detail

 

Example
This command displays the list of all the SVIs that are sharing the TCAM entries. 
switch(config)# show platform trident tcam qos detail

=== Policy-map p01 type qos on switch Linecard0/0 ===
Interfaces : Vlan2 Vlan1
=-= Interface BitMap =-=
0x000000000000000001FFFFFE

show platform trident tcam shared vlan interface-class-id

The show platform trident tcam shared vlan interface-class-id command displays what SVIs are currently sharing the QoS policy-map in the below output under QoS PMAP Data.

 

Command Mode

EXEC

 

Command Syntax

show platform trident tcam shared vlan interface-class-id

 

Example
This command displays what SVIs are currently sharing the QoS policy-map in the below output under QoS PMAP Data. 
switch(config)# show platform trident tcam shared vlan interface-class-id

=== Shared RACL Data on switch Linecard0/0 ===
=== Shared QoS Policy-map Data on switch Linecard0/0 ===
Interface Class Id             VLANs
1                               1 2

show platform xp qos tcam hit

The show platform xp qos tcam hit command displays the TCAM entries programmed for each policy-map as well as the traffic hits. The hits option is used to see the TCAM entries with nonzero traffic hits.

 

Command Mode

EXEC

 

Command Syntax

show platform xp qos tcam hit

 

Example
This command displays the QoS TCAM hits on interface ethernet 10/1. 
switch# show platform xp qos tcam hit

=== Policy-map test type qos on switch 0 ===
Assigned to ports: Ethernet10/1
=-= Class-map test type qos =-=
=== ACL test
=========================================================================================
|Seq|AclId|Prot|Port|SPort|Ecn|FFlg|DPort|Vlan|Action|Hits|Src Ip|Dest Ip|hwId    | | |     |      | | | |dscp|cos  |tc|PolId| | | |
=========================================================================================
| 10| 0x01|    |    |     |   |0x04|     |    | 4    |-   | -    | -     |91852787| | | | 0 | 0x00 | | | |     |0xfb|  |     |  | | |  
-----------------------------------------------------------------------------------------

show policy-map interface

The show policy-map interface command displays contents of the policy map applied to specified the interface.

 

Command Mode

EXEC

 

Command Syntax

show policy-map interface interface_name

 

Parameters

interface_name     Interface for which command returns data. Options include:
  • no parameter      Returns data for all interfaces.
  • ethernet e_range      Ethernet interfaces specified by e_range.
  • port-channel p_range      Port channel interfaces specified by p_range.

     

Example
This command displays the name and contents of the policy map applied to interface Ethernet 1. 
switch# show policy-map interface ethernet 1
Service-policy input: p1
 Hardware programming status: Successful

 Class-map: c2001 (match-any)
    Match: vlan 2001 0xfff
       set dscp 4

 Class-map: c2002 (match-any)
    Match: vlan 2002 0xfff
       set dscp 8

 Class-map: c2003 (match-any)
    Match: vlan 2003 0xfff
       set dscp 12

show policy-map

The show policy-map command displays the policy map information for the configured policy map.

 

Command Mode

EXEC

 

Command Syntax

show policy-map policy_map_name [counters][interface | summary]

 

Parameters
  • policy_map_name QoS policy map name.
  • counters      Specifies the policy map traffic match count (This parameter is applicable only on DCS-7010, DCS-7050X, DCS7250X, DCS-7300X and DCS-7280(E/R), DCS-7500(E/R) series switches.)
  • interface      Specifies the service policy on an interface.
  • summary      Policy map summary.

     

Examples
  • The show policy-map command displays the information for the policy map policy1. 
    switch# show policy-map policy1
Service-policy policy1
Class-map: class1 (match-any)
Match: ip access-group name acl1
Police cir 512000 bps bc 96000 bytes
Class-map: class-default (match-any)

     

  • The show policy-map counters command displays the policy map traffic match count for the policy map configured. 
    switch# show policy-map policy1 counters

Service-policy input: policy1
 Hardware programming status: Successful
 Class-map: class1 (match-any)
    Match: vlan 20-40,1000-1250
       police rate 100 mbps burst-size 100 kbytes
        Interface: Ethernet16/1
          Conformed 28621 packets, 7098008 bytes -------------- packet match count
 
Class-map: class-default (match-any)
      Matched Packets: 19 -------------- packet match count

show qos interfaces random-detect ecn

The show qos interfaces random-detect ecn command displays the Explicit Congestion Notification (ECN) configuration for each transmit queue on the specified interfaces.

 

Command Mode

EXEC

 

Command Syntax

show qos interfaces [INTERFACE_NAME] random-detect ecn

 

Parameters

INTERFACE_NAME Interface for which command returns data. Options include:
  • no parameter      Returns data for all interfaces.
  • ethernet e_range      Ethernet interfaces specified by e_range.
  • port-channel p_range      Port-Channel Interfaces specified by p_range.

     

Example
This command configures ECN parameters for transmit queues 0 through 3 on interface ethernet 3/5/1, then displays that configuration. 
switch(config)# interface ethernet 3/5/1
switch(config-if-Et3/5/1)# tx-queue 0
switch(config-if-Et3/5/1-txq-0)# random-detect ecn minimum-threshold 2560 kbytes 
maximum-threshold 256000 kbytes
switch(config-if-Et3/5/1-txq-0)# tx-queue 1
switch(config-if-Et3/5/1-txq-1)# random-detect ecn minimum-threshold 25600 kbytes 
maximum-threshold 128000 kbytes
switch(config-if-Et3/5/1-txq-1)# tx-queue 2
switch(config-if-Et3/5/1-txq-2)# random-detect ecn minimum-threshold 25600 bytes 
maximum-threshold 128000 bytes
switch(config-if-Et3/5/1-txq-2)# tx-queue 3
switch(config-if-Et3/5/1-txq-3)# random-detect ecn minimum-threshold 25 mbytes 
maximum-threshold 128 mbytes
switch(config-if-Et3/5/1-txq-3)# show qos interfaces ethernet 3/5/1 random-detect 
ecn

Ethernet3/5/1:

   Tx-Queue   Mininimum Threshold    Maximum Threshold    Threshold Unit
   ---------------------------------------------------------------------
          7                     -                    -                 -
          6                     -                    -                 -
          5                     -                    -                 -
          4                     -                    -                 -
          3                    25                  128             mbytes
          2                 25600               128000              bytes
          1                 25600               128000             kbytes
          0                  2560               256000             kbytes

switch(config-if-Et3/5/1-txq-3)#

show qos interfaces trust

The show qos interfaces trust command displays the configured and operational QoS trust mode of all specified interfaces.

 

Command Mode

EXEC

 

Command Syntax

show qos interfaces [INTERFACE_NAME] trust

 

Parameters

INTERFACE_NAME Interface for which command returns data. Options include:
  • no parameter      Returns data for all interfaces.
  • ethernet e_range      Ethernet interfaces specified by e_range.
  • port-channel p_range      Port-Channel Interfaces specified by p_range.

     

Example
These commands configure a variety of QoS trust settings on a set of interfaces, then displays the QoS trust mode on these interfaces. 
switch(config)# interface ethernet 1/1
switch(config-if-Et1/1)# qos trust cos
switch(config-if-Et1/1)# interface ethernet 1/2
switch(config-if-Et1/2)# qos trust dscp
switch(config-if-Et1/2)# interface ethernet 1/3
switch(config-if-Et1/3)# no qos trust
switch(config-if-Et1/3)# interface ethernet 1/4
switch(config-if-Et1/4)# default qos trust
switch(config-if-Et1/4)# interface ethernet 2/1
switch(config-if-Et2/1)# no switchport
switch(config-if-Et2/1)# default qos trust
switch(config-if-Et2/1)# show qos interface ethernet 1/1 - 2/4 trust

Port                                       Trust Mode
                               Operational           Configured
---------------------------------------------------------------
Ethernet1/1                    COS                   COS
Ethernet1/2                    DSCP                  DSCP
Ethernet1/3                    UNTRUSTED             UNTRUSTED
Ethernet1/4                    COS                   DEFAULT
Ethernet2/1                    DSCP                  DEFAULT
Ethernet2/2                    COS                   DEFAULT
Ethernet2/3                    COS                   DEFAULT
Ethernet2/4                    COS                   DEFAULT

switch(config-if-Et2/1)#

show qos interfaces

The show qos interfaces command displays the QoS, DSCP, and transmit queue configuration on a specified interface. Information provided by this command includes the ports trust setting, the default CoS value, and the DSCP value.

 

Command Mode

EXEC

 

Command Syntax

show qos interfaces INTERFACE_NAME

 

Parameters

INTERFACE_NAME Interface For which command returns data. Options include:
  • no parameter     Returns data for all interfaces.
  • ethernet e_num      Ethernet interface specified by e_num.
  • port-channel p_num Port-Channel Interface specified by p_num.

     

Example
This command lists the QoS configuration for interface ethernet 4. 
switch> show qos interfaces ethernet 4

Ethernet4:
   Trust Mode: COS
   Default COS: 0
   Default DSCP: 0

   Port shaping rate: 5000000Kbps

   Tx-Queue   Bandwidth    ShapeRate      Priority
              (percent)       (Kbps)
   -----------------------------------------------
          0          50     disabled   round-robin
          1          50     disabled   round-robin
          2         N/A     disabled        strict
          3         N/A      1000000        strict
          4         N/A      1000000        strict
          5         N/A      1500000        strict
          6         N/A      2000000        strict

switch>

show qos interfaces latency maximum

The show qos interfaces latency maximum command displays the maximum latency tail-drop threshold active on each Tx queue for a specified interface.

 

Command Mode

EXEC

 

Command Syntax

show qos interfaces INTERFACE_NAME latency maximum

 

Parameters

INTERFACE_NAME: Name of the interface.

 

This command lists the maximum latency for VOQ tail drop on interface ethernet 23/1. 
switch# show qos interfaces ethernet 23/1 latency maximum

Ethernet23/1:
Tx Queue            Maximum Latency
--------            ---------------
       7                          -         
       6                          -         
       5                          -         
       4                          -         
       3                      10 ms
       2                          -         
       1                          -         
       0                          -         

switch# show qos profile
qos profile latency
    tx-queue 3
        latency maximum 4000 microseconds
    Tx-queue 4
        latency maximum 30 milliseconds

switch#

show qos maps

The show qos maps command lists the number of traffic classes that the switch supports and displays the CoS-Traffic Class, DSCP-Traffic Class, Traffic Class-CoS, and Traffic Class-Transmit Queue maps.

 

Command Mode

EXEC

 

Command Syntax

show qos maps

 

Example
This command displays the QoS maps that are configured on the switch. 
switch> show qos maps
Number of Traffic Classes supported: 8
   Number of Transmit Queues supported: 8
   Cos Rewrite:  Disabled
   Dscp Rewrite:  Disabled

   Cos-tc map:
     cos:  0  1  2  3  4  5  6  7
     ----------------------------
     tc:   1  0  2  3  4  5  6  7

   Dscp-tc map:
     d1 :  d2 0  1  2  3  4  5  6  7  8  9
     --------------------------------------
      0 :     1  1  1  1  1  1  1  1  0  0
      1 :     0  0  0  0  0  0  2  2  2  2
      2 :     2  2  2  2  3  3  3  3  3  3
      3 :     3  3  4  4  4  4  4  4  4  4
      4 :     5  5  5  5  5  5  5  5  6  6
      5 :     6  6  6  6  6  6  7  7  7  7
      6 :     7  7  7  7

   Tc-cos map:
     tc:   0  1  2  3  4  5  6  7
     ----------------------------
     cos:  1  0  2  3  4  5  6  7

   Tc-dscp map:
     tc:    0  1  2  3  4  5  6  7
     -----------------------------
     dscp:  8  0 16 24 32 40 48 56

   Tc - tx-queue map:
     tc:        0  1  2  3  4  5  6  7
     ---------------------------------
     tx-queue:  0  1  2  3  4  5  6  7

switch>

show qos map dscp to traffic-class

 

The show qos map dscp to traffic-class command shows all DSCP to traffic-class maps, or one specified DSCP to TC map.

 

Command Mode

Privileged EXEC mode

 

Command Syntax

show qos map dscp to traffic-class [ map_name ]

 

Parameters

  • map_name The name of the DSCP to traffic-class map. If this is not specified, all DSCP to TC maps are shown.

     

Example

This command shows the DSCP to TC map named map1. 
switch#show qos map dscp to traffic-class map1
   DSCP to TC map: map1
     d1 :  d2 0  1  2  3  4  5  6  7  8  9
     --------------------------------------
      0 :     1  1  1  1  1  1  1  1  0  0
      1 :     0  0  0  0  0  0  2  2  2  2
      2 :     6  6  6  6  6  6  3  3  3  3
      3 :     3  3  4  4  4  7  4  4  4  4
      4 :     5  5  5  5  5  5  5  5  6  6
      5 :     6  6  6  6  6  6  7  7  7  7
      6 :     7  7  7  7
switch#

show qos profile summary

The show qos profile summary command displays the QoS profile summary of those which are part of the running configuration.

 

Command Mode

EXEC

 

Command Syntax

show qos profile summary

 

Example
This command shows a summary of all QoS profiles configured on the switch. 
switch(config)# show qos profile summary
Qos Profile: p
Configured on: Et13,7
Fabric
Po12
Qos Profile: p2
Configured on: Et56

show qos profile

The show qos profile command displays the contents of the specified QoS profile or of all QoS profiles in the running configuration.

 

Command Mode

EXEC

 

Command Syntax

show qos profile profile_name

 

Parameter

profile_name QoS profile name.

 

Examples
  • This command displays the contents of all QoS profiles configured on the switch. 
    switch(config)# show qos profile
qos profile p
qos cos 1
no priority-flow-control pause watchdog
priority-flow-control priority 1 no-drop
priority-flow-control priority 2 no-drop
qos profile p2
qos cos 3
priority-flow-control priority 0 no-drop

     

  • This command displays the configuration attached and information specific to QoS profile p2. 
    switch# show qos profile p2
qos profile p2
qos cos 3
priority-flow-control priority 0 no-drop

show qos random-detect ecn

The command displays the global Explicit Congestion Notification (ECN) configuration.

 

Command Mode

EXEC

 

Command Syntax

show qos random-detect ecn

 

Example
These commands configure global ECN parameters, then displays that configuration. 
switch(config)# qos random-detect ecn global-buffer minimum-threshold 2 mbytes 
maximum-threshold 5 mbytes
switch(config)# show qos random-detect ecn                                                                            
   Minimum Threshold:  2
   Maximum Threshold:  5
   Threshold Unit:  mbytes

switch(config)#

show run|grep sharing

Theshow run|grep sharing command displays whether the QoS policy-map sharing on SVIs is enabled or disabled.

 

Command Mode

EXEC

 

Command Syntax

show run|grep sharing

 

Example
This command displays whether the QoS policy-map sharing on SVIs is enabled or disabled. 
switch# show run|grep sharing
hardware access-list qos resource sharing vlan in ----

 

If this message is displayed then QoS policy-map sharing on SVIs is enabled.

tx-queue (Arad/Jericho)

The tx-queue command places the switch in Tx-queue configuration mode to configure a transmit queue on the configuration mode interface. Tx-queue configuration mode is not a group change mode; running-config is changed immediately after commands are executed. The exit command does not affect the configuration.

Arad and Jericho platform switches have eight queues, 0 through 7, and all queues are exposed through the CLI. However, queue 7 is not user-configurable. Queue 7 is always mapped to traffic class 7, which is reserved for control traffic.

The exit command returns the switch to the configuration mode for the base Ethernet or port channel interface.

The no tx-queue and default tx-queue commands remove the configuration for the specified transmit queue by deleting all corresponding tx-queue mode statements from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

tx-queue queue_level

 

Parameters

queue_level The transmit queue. Values range from 0 to 7.

 

Commands Available in tx-queue Configuration Mode

Guidelines

Arad and Jericho platform switch queues handle unicast traffic. Queues for multicast traffic are not supported.

 

Example
This command enters Tx-queue configuration mode for transmit queue 4 of interface ethernet 3/3/3. 
switch(config)# interface ethernet 3/3/3
switch(config-if-Et3/3/3)# tx-queue 4
switch(config-if-Et3/3/3-txq-4)#

tx-queue (FM6000)

The tx-queue command places the switch in Tx-queue configuration mode to configure a transmit queue on the configuration mode interface. Tx-queue configuration mode is not a group change mode; running-config is changed immediately after commands are executed. The exit command does not affect the configuration.

FM6000 platform switches have eight queues, 0 through 7. All queues are exposed through the CLI and are user configurable.

The exit command returns the switch to the configuration mode for the base Ethernet or port channel interface.

The no tx-queue and default tx-queue commands remove the configuration for the specified transmit queue by deleting the all corresponding tx-queue mode commands from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

tx-queue queue_level

 

Parameter

queue_level The transmit queue. Values range from 0 to 7.

 

Commands Available in tx-queue Configuration Mode

Guidelines

FM6000 platform switch queues handle unicast and multicast traffic.

 

Example
This command enters Tx-queue configuration mode for transmit queue 3 of interface ethernet 5. 
switch(config)# interface ethernet 5
switch(config-if-Et5)# tx-queue 3
switch(config-if-Et5-txq-3)#

tx-queue (Helix)

The tx-queue command places the switch in tx-queue configuration mode to configure a transmit queue on the configuration mode interface. The tx-queue configuration mode is not a group change mode; running-config is changed immediately after commands are executed. The exit command does not affect the configuration.

Helix platform switches have eight unicast (UC0 – UC7) and eight multicast (MC0 – MC7) queues. Each UCx-MCx queue set is combined into a single queue group (L1.x), which is exposed to the CLI through this command.

The exit command returns the switch to the configuration mode for the base Ethernet or port channel interface.

The no tx-queue and default tx-queue commands remove the configuration for the specified transmit queue by deleting the all corresponding tx-queue mode commands from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

tx-queue queue_level

 

Parameter

queue_level Transmit queue group number. Values range from 0 to 7.

 

Commands Available in tx-queue Configuration Mode

Guidelines

Helix platform switch queues handle unicast and multicast traffic.

 

Example
This command enters Tx-queue configuration mode for transmit queue 4 of interface ethernet 17/3. 
switch(config)# interface ethernet 17/3
switch(config-if-Et17/3)# tx-queue 4
switch(config-if-Et17/3-txq-4)#

tx-queue (Petra)

The tx-queue command places the switch in tx-queue configuration mode to configure a transmit queue on the configuration mode interface. The tx-queue configuration mode is not a group change mode; running-config is changed immediately after commands are executed. The exit command does not affect the configuration.

Petra platform switches have eight queues, 0 through 7, and all queues are exposed through the CLI. However, queue 7 is not user-configurable. Queue 7 is always mapped to traffic class 7, which is reserved for control traffic.

The exit command returns the switch to the configuration mode for the base Ethernet or port channel interface.

The no tx-queue and default tx-queue commands remove the configuration for the specified transmit queue by deleting the all corresponding tx-queue mode commands from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

tx-queue queue_level

 

Parameter

queue_level The transmit queue. Values range from 0 to 7.

 

Commands Available in tx-queue Configuration Mode

Guidelines

Petra platform switch queues handle unicast traffic. Queues for multicast traffic are not supported.

 

Example
This command enters the tx-queue configuration mode for transmit queue 3 of interface ethernet 3/3. 
switch(config)# interface ethernet 3/3
switch(config-if-Et3/3)# tx-queue 3
switch(config-if-Et3/3-txq-3)#

tx-queue (Trident II)

The tx-queue command places the switch in tx-queue configuration mode to configure a transmit queue on the configuration mode interface. The tx-queue configuration mode is not a group change mode; running-config is changed immediately after commands are executed. The exit command does not affect the configuration.

Trident II platform switches have eight unicast (UC0 – UC7) and eight multicast (MC0 – MC7) queues. Each UCx-MCx queue set is combined into a single queue group (L1.x), which is exposed to the CLI through this command.

The exit command returns the switch to the configuration mode for the base Ethernet or port channel interface.

The no tx-queue and default tx-queue commands remove the configuration for the specified transmit queue by deleting the all corresponding tx-queue mode commands from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

tx-queue queue_level

 

Parameter

queue_level Transmit queue group number. Values range from 0 to 7.

 

Commands Available in tx-queue Configuration Mode

Trident II platform switch queues handle unicast and multicast traffic.

 

Example
This command enters the tx-queue configuration mode for transmit queue 4 of interface ethernet 17/3. 
switch(config)# interface ethernet 17/3
switch(config-if-Et17/3)# tx-queue 4
switch(config-if-Et17/3-txq-4)#

uc-tx-queue

The uc-tx-queue command places the switch in the uc-tx-queue configuration mode to configure a unicast transmit queue on the configuration mode interface. The uc-tx-queue configuration mode is not a group change mode; running-config is changed immediately after commands are executed. The exit command does not affect the configuration.

Trident and Tomahawk switches have eight unicast queues (UC0 – UC7) and four multicast queues (MC0 – MC03), categorized into two priority groups. All queues are exposed through the CLI and are user-configurable.

  • Priority Group 1: UC7, UC6, MC3

     

  • Priority Group 0: UC5, UC4, MC2, UC3, UC2, MC1, UC1, UC0, MC0

     

The exit command returns the switch to the configuration mode for the base Ethernet or port channel interface.

The no uc-tx-queue and default uc-tx-queue commands remove the configuration for the specified transmit queue by deleting the all corresponding uc-tx-queue mode commands from running-config.

 

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

 

Command Syntax

uc-tx-queue queue_level

 

Parameter

queue_level The multicast transmit queue number. Values range from 0 to 7.

 

Commands Available in uc-tx-queue Configuration Mode

Related Command

mc-tx-queue: Configures multicast transmit queues on Trident and Tomahawk platform switches.

 

Example
This command enters the mc-tx-queue configuration mode for multicast transmit queue 4 of interface ethernet 5. 
switch(config)# interface ethernet 5
switch(config-if-Et5)# uc-tx-queue 4
switch(config-if-Et5-mc-txq-4)#

Chipset Mapping for QoS

Table 43. Chipset Names by Model Number
Model Number Chipset Name
7010T-48 Helix4
7010T-48-DC Helix4
7020SR-24C2 QumranAX
7020SR-32C2 QumranAX
7020SRG-24C2 QumranAX
7020TR-48 QumranAX
7020TRA-48 QumranAX
7048T-4S Petra
7048T-A Petra
7050CX3-32S Trident3X7
7050CX3M-32S Trident3X7
7050Q-16 Trident+
7050QX2-32S Trident2+
7050QX-32 Trident2
7050QX-32S Trident2
7050S-52 Trident+
7050S-64 Trident+
7050SX-128 Trident2
7050SX2-128 Trident2+
7050SX2-72Q Trident2+
7050SX3-48C8 Trident3X5
7050SX3-48YC Trident3X5
7050SX3-48YC12 Trident3X7
7050SX3-96YC8 Trident3X7
7050SX-64 Trident2
7050SX-72 Trident2
7050SX-72Q Trident2
7050SX-96 Trident2
7050T-36 Trident+
7050T-36 (HwRev4) Trident+
7050T-52 Trident+
7050T-52 (HwRev4) Trident+
7050T-64 Trident+
7050T-64 (HwRev4) Trident+
7050TX-128 Trident2
7050TX2-128 Trident2+
7050TX3-48C8 Trident3X5
7050TX-48 Trident2
7050TX-64 Trident2
7050TX-72 Trident2
7050TX-72Q Trident2
7050TX-96 Trident2
7060CX2-32S Tomahawk+
7060CX-32S Tomahawk
7060DX4-32 Tomahawk3
7060PX4-32 Tomahawk3
7060SX2-48YC6 Tomahawk+
7120T-4S Bali
7124FX Bali
7124S Bali
7124SX Bali
7140T-8S Bali
7148S Bali
7148SX Bali
7150S-24 Alta
7150S-24-CL Alta
7150S-52-CL Alta
7150S-64-CL Alta
7150SC-24-CLD Alta
7150SC-64-CLD Alta
7170-32C Tofino
7170-32CD Tofino
7170-64C Tofino
720XP-24Y6 Trident3X3
720XP-24ZY4 Trident3X3
720XP-48Y6 Trident3X3
720XP-48ZC2 Trident3X3
720XP-96ZC2 Trident3X3
7250QX-64 Trident2
7260CX3-64 Tomahawk2
7260CX3-64E Tomahawk2
7260CX-64 Tomahawk
7260QX-64 Tomahawk
7280CR2-60 Jericho+
7280CR2A-60 Jericho+
7280CR2AK-30 Jericho+
7280CR2K-30 Jericho+
7280CR2K-60 Jericho+
7280CR2M-30 Jericho+
7280CR3-32D4 Jericho2
7280CR3-32P4 Jericho2
7280CR3-96 Jericho2
7280CR3K-32D4 Jericho2
7280CR3K-32P4 Jericho2
7280CR3K-96 Jericho2
7280CR3MK-32D4 Jericho2
7280CR3MK-32P4 Jericho2
7280CR-48 Jericho
7280DR3-24 Jericho2
7280DR3K-24 Jericho2
7280PR3-24 Jericho2
7280PR3K-24 Jericho2
7280QRA-C36S Jericho
7280QR-C36 QumranMX
7280QR-C72 Jericho
7280SE-64 Arad+
7280SE-68 Arad+
7280SE-72 Arad+
7280SR2-48YC6 Jericho+
7280SR2A-48YC6 Jericho+
7280SR2K-48C6 Jericho+
7280SR3-40YC6 Jericho2C Q2A
7280SR-48C6 QumranMX
7280SRA-48C6 QumranMX
7280SRAM-48C6 QumranMX
7280SRM-40CX2 QumranMX
7280TR3-40C6 Jericho2C Q2A
7280TR-48C6 QumranMX
7280TRA-48C6 QumranMX
DCS-7304 Trident3
DCS-7304 Tomahawk
DCS-7304 Trident2
DCS-7308 Trident3
DCS-7308 Tomahawk
DCS-7308 Trident2
DCS-7316 Trident2
DCS-7368X4 Tomahawk3
DCS-7504 Petra
DCS-7504E Arad/Arad+
DCS-7504N Jericho 2
DCS-7504N Jericho/Jericho+
DCS-7508 Petra
DCS-7508E Arad/Arad+
DCS-7508N Jericho 2
DCS-7508N Jericho/Jericho+
DCS-7512N Jericho 2
DCS-7512N Jericho/Jericho+
DCS-7516N Jericho/Jericho+
DCS-7804-CH Jericho 2
DCS-7808-CH Jericho 2

Traffic Management

This chapter describes Arista’s Traffic Management, including configuration instructions and command descriptions. Topics covered by this chapter include:

Traffic Management Conceptual Overview

Traffic is managed through policy maps that apply data shaping methods to specific data streams. A policy map is a data structure that identifies specific data streams and then defines shaping parameters that modify packets within the streams. The switch defines four types of policies:
A policy map consists of classes. Each class contains an eponymous class map and traffic resolution commands.
  • A class map is a data structure that defines a data stream by specifying characteristics of data packets that comprise that stream. Each class map is typed as either QoS, control plane, or PBR and is available only to identically typed policy maps.

  • Traffic resolution commands specify data handling methods for traffic that matches a class map. Traffic resolution options vary by policy map type.

Data packets that enter an entity to which a policy map is assigned are managed with traffic resolution commands of the first class that matches the packets.

Control Plane Policies

The switch defines one control plane policy map named copp-system-policy. The copp-system-policy policy map is always applied to the control plane and cannot be removed from the switch. Other control plane policy maps cannot be added. Copp-system-policy consists of preconfigured classes, each containing a static class map and traffic resolution commands. Preconfigured classes cannot be removed from copp-system-policy.

Static class maps are provided by the switch and cannot be modified or deleted. The naming convention of static class maps is copp-system- name, where name differentiates the class maps. Static class maps have pre-defined internal conditions, are not based on ACLs, and are only listed in running-config as components of copp-system-policy. The sequence of static class maps in the policy map is not significant. Traffic resolution commands define minimum (bandwidth) and maximum (shape) transmission rates for data streams matching the corresponding class map.

Copp-system-policy can be modified through the following steps:
  1. Add classes consisting of an eponymous dynamic class map and traffic resolution commands.

    Dynamic class maps are user created, can be edited or deleted, filter traffic with a single IPv4 ACL, and are listed in running-config.

  2. Change traffic resolution commands for a preconfigured class.

These sections describe control plane traffic policy configuration procedures:

QoS Policies

QoS policy maps are user defined. The switch does not provide preconfigured QoS policy maps and in the default configuration, policy maps are not applied to any Ethernet or port channel interface. Policy maps and class maps are created and applied to interfaces through configuration commands.

A QoS policy map is composed of one or more classes. Each class contains an eponymous dynamic class map and traffic resolution commands. Dynamic class maps are user created, can be edited or deleted, filter traffic with a single IPv4 ACL, and are listed in running-config.

QoS traffic resolution commands perform one of the following:
  • Set the Layer 2 CoS field

  • Set the DSCP value in the ToS byte

  • Specify a traffic class queue

The last class in all QoS policy maps is class-default, which is composed as follows:
  • The class-default class map matches all traffic except IPv4 or IPv6 traffic and is not editable.

  • By default, class-default class contains no traffic resolution commands. Traffic resolution commands can be added through configuration commands.

Data packets that enter an interface to which a policy map is assigned are managed with traffic resolution commands that correspond to the first class that matches the packet.

These sections describe QoS traffic policy configuration procedures:

Segment Routing Traffic Engineering Policy (SR-TE)

Segment Routing Traffic Engineering Policy (SR-TE) policy uses Segment Routing (SR) to enable a headend to steer traffic along any path without maintaining per flow state in every node based on the policy. Configuring SR policy for the MPLS dataplane (SR-MPLS) for Type-1 SR policy segments with BGP and locally configured policies as sources of SR policy is available on DCS-7500 and DCS-7280 family of switches.

SR Policy Overview

SR Policy Identification
The following identifies an SR policy.
  • Endpoint - An IPv4 or IPv6 address which refers to the destination of the policy. EOS allows 0/0 and 0:: and calls these IP addresses null endpoints.
  • Color - An unsigned 32-bit opaque numerical quantity. Define the semantic of a color as you prefer. It can refer to, for instance, an application or a type of traffic, such as low latency, or a geographical location.
SR Policy Constituents
The SR policy consists of candidate paths. Each candidate path has the following.
  • SID-lists (SLs) - An ordered list of Segment Identifiers. Each SID provides a MPLS label in the MPLS instantiation of SR). An SL encodes one path from the headend to the destination. Each SL has an optional weight attached to it for the purpose of Unequal Cost Multipath (UCMP) traffic distribution. The default value for SL weight is 1.
  • Preference - An optional, unsigned 32-bit integer used in the candidate path selection algorithm to select the active candidate path. The default value for preference is 100.
  • Binding SID (BSID) - an optional SID.
    Note: In EOS, a BSID is mandatory for each candidate path.
SR Policy Sources
A headend learns SR policies using the following methods:
  • BGP
    • Single agent routing model (Ribd)
    • Multi-agent routing model
  • Local configuration using CLI
    • Single agent routing model (Ribd)
    • Multi-agent routing model
    • Openconfig YANG models
  • PCEP
    Note: EOS does not support PCEP.

Identity of a Candidate Path

A candidate path within an SR policy is identified by a 3-tuple of {Protocol-Origin, Originator, Discriminator}. In EOS, for locally configured policies:
  • The ASN in the Originator set to 0.
  • The node address in the Originator set to 0.0.0.0.
  • The discriminator set to the Preference configured.
    Note: EOS CLI allows configuring only one candidate path at a given preference and does not allow configuring the discriminator for a candidate path.

State of an SID List (SL)

The following describes the state of an SL:
  • Valid - The top label of the SL resolves within the LFIB to the outgoing next hop(s), interface(s) and a label action.
  • Invalid - The top label of the SL unresolvable to the outgoing next hop(s), interface(s) and a label action. An SL is also marked as invalid when the SL is resolvable, but the resolved labeled stack exceeds the platform’s maximum SID depth (SID), that is, exceeds the maximum number of labels the platform can push in to the outgoing packet.
    Note: The state is either valid or invalid.

State of a Candidate Path

The following describes the states of a candidate path.
  • Invalid - Not eligible to participate in the best/active candidate path selection algorithm because of one of the reasons below.
    • Invalid constituent SLs in the candidate path.
    • No Binding SID present in the candidate path.
    • Binding SIDpresent but outside SRLB range for the candidate path.
  • Valid - At least one valid SL has lost out to some other candidate path in the best / active candidate path selection algorithm.
  • Active: - A valid candidate path exists and wins the best / active candidate path selection algorithm. The active candidate path installs in the switch hardware and forwards traffic.

State of an SR Policy

EOS considers an SR policy as valid when at least one of its candidate paths is valid. Otherwise, the SR policy is invalid.

Resolution of an SL

An SL resolves if the top label (first SID) can be resolved in the system Labeled FIB (LFIB) to yield a nexthop and outgoing interface(s). The other labels in the SID-List do not play a part in resolution.

Best Candidate Path (Active Candidate Path) Selection Algorithm

EOS overrides selection based on discriminator by retaining the current active candidate path even when current active path has a lower discriminator value. This reduces the active path flap when a new path appears with the same significance. The following lists a summary of valid candidate paths ordering for a given policy.
  1. The candidate path with higher preference selected.
  2. Locally configured candidate path selected over a BGP learned path
  3. Lower originator selected in the following instances:
    1. Lower AS number of Originator field selected.
    2. Lower Node address of Originator field selected.
  4. Current active candidate path selected in the following instances:

The following displays the reason for not selecting a path as an active path for a specified policy.

switch#show traffic-engineering segment-routing policy endpoint <endpoint> color <color>

Binding SID

The following describes the use cases for the Binding SID:
  • Stitch together multiple domains.
  • Stitch together different traffic tunnels .
  • Overcome label stack imposition limitation in hardware.

BSID Conflict Handling

Examples

  1. Between Policies - If the policy (E1, C1) becomes eligible to be active first, then it installs in the LFIB and the policy (E2,C2) whose best path(CP1) conflicts with the Policy (E1, C1) and does not become active.
    • Policy(E1, C1): CP1: Binding-SID 965536 (wins best path)
    • Policy(E2, C2): CP1: Binding-SID 965536 (wins best path)
    • CP2: Binding-SID 965537
  2. with another Application: The SR-TE policies have the lowest preference when a conflict exists with any other application in EOS using the SRLB range. The candidate paths with the same binding-SID as that of an LFIB entry by another application, for example, static adjacency segment, remains invalid.

In both the cases, when the conflict no longer exists, the candidate paths re-evaluate and may become active.

BGP as a Source of Policies

SR Policies from a BGP peer (a controller, route reflector) received for installation at the headend by EOS. It does not propagate the received policies to BGP peers nor does it originate SR Policies for transmission to BGP peers.

The following supports IPv4 or IPv6 peers which can be single hop or multi-hop iBGP or eBGP peers.

  1. SAFI 73 for AFI 1 and AFI 2: IPv4 and IPv6 policy endpoints, with the encoding defined in section 2.1 of Advertising Segment Routing Policies in BGP.
    Note: The nexthop address-family must match the AFI of the NLRI.
  2. Sub-TLVs of Tunnel Encapsulation TLV of type 15 (SR-TE Policy Type) of the Tunnel Encapsulation Path Attribute
    1. Preference (Sub-TLV Type 12)
    2. Binding SID (Sub-TLV Type 13) of length 2 or 6 bytes
    3. Segment List (Sub-TLV Type 128). The following Segment List sub-TLVs are supported:
      1. Type 1 Segment (Sub-TLV type 1)
      2. Weight (Sub-TLV type 9)
    4. Explicit NULL Label Policy (Sub-TLV Type 14)
    5. SR Prefix SID (sub TLV 3 of TLV 149, TLV 150)
    6. SR Range - Contents of TLV 149, TLV 150 (multi-topology)
Note: EOS ignores all other sub-TLVs of the Tunnel Encapsulation TLV and Segment List sub-TLVs.

Route-Target and NO_ADVERTISE Community in SR-TE SAFI Updates

EOS implements the Acceptance and Usability checks as defined in sections 4.2.1 and 4.2.2 of the IETF draft Advertising Segment Routing Policies in BGP. However EOS skips matching the Route-Target with the router-ID of the headend if the SR-TE NLRI is tagged with NO_ADVERTISE community.

ECMP does not support SR-TE SAFI Paths

EOS does not support ECMP for BGP SR-TE SAFI. The BGP path selects only one best candidate path and publishes it to SR-TE Policy Agent for candidate path selection.
Note: EOS supports ECMP of BGP next hops where each next hop resolves to an SR-TE policy.

Path Selection within BGP

The IETF draft Advertising Segment Routing Policies in BGP supports passing multiple candidate paths from a single protocol source for an SR-TE policy path selection. Therefore, it includes a field distinguisher in the NLRI which can be unique for each controller to make BGP pass through the policies. However when multiple sources use the same distinguisher, BGP performs a path selection for the tuple: Endpoint, Color and Distinguisher. The best path for that tuple publishes to the SR-TE Policy Agent for selecting an Active path. The best bgp-best-path selection applies to SR-TE SAFI as well.

Error Handling / Edge Cases

  • Weight 0: The IETF draft does not limit the range of SL weight to exclude weight 0. A SID-List with weight 0 is not used for forwarding so BGP module in EOS does not pass on SID-Lists with weight 0 to the SR-TE policy agent. Such SID-Lists will be visible in show bgp sr-te commands but not in show traffic-engineering segment-routing policy commands.
  • Empty SLs: Given the TLV encoding used to propagate SR Policies in BGP, it is possible to receive SID-Lists without SIDs. The BGP module in EOS does not pass empty SID-Lists to SR-TE policy agent. Such SID-Lists are visible in show bgp sr-te commands but not in show traffic-engineering segment-routing policy commands.
  • Non Type 1 segments: EOS supports only Type-1 segments. When receiving a BGP update with a SID-List that has non Type-1 segments, EOS ignores the entire SID-List and sends a BGP-4-SRTE_IGNORED_SEGMENT_LIST_UNSUPPORTED_SEGMENTS syslog. Such SID-Lists are not stored locally, and show bgp sr-te command does not display them.
    Note: The SID-Lists made up of all Type-1 segments pass to the SR-TE policy agent.

Steering Traffic into a Policy

Incoming label as BSID - Labelled Steering

At the headend when receiving a packet with a label stack with a BSID of an active CP of a valid SR Policy as the top label, the headend pops the label, and imposes the resolved label stack on the outgoing packet.

Example

For instance, an SR Policy with an active candidate path with BSID 965536 and SL with label stack [965540, 900001, 900002]. Assume that 965540 is an IS-IS SR Adjacency SID. An incoming packet has a label stack [965536, 100000] then the outgoing label stack consists of [900001, 900002, 100000].

Steering BGP learnt IP(v6) prefixes - IP Steering

Incoming label is BSID - Labelled Steering

At the headend, BGP IPv4 and IPv6 routes receive one or more extended color communities and recursively resolves them through any active SR Policy that matches the BGP routes’ nexthop and color. When receiving an IPv4 or IPv6 packetforwarded using this policy, the SL’s resolved label stack imposes on the outgoing packet.

For BGP routes received with color community to be steered via an SR policy, the route’s nexthop must already be resolvable through IGP. If no resolving route exists in IGP, the route is considered unresolvable and does not program in hardware even if a matching SR policy existsfor the corresponding nexthop and color.

If no matching SR policy exists for the received BGP nexthop and color, the route resolves through the IGP route in IP RIB. If an active SR policy that matches the BGP nexthop and color gets instantiated at a later time, the BGP route changes from resolving through IGP to the new active SR policy.
Note: The recursion through SR policy is only applicable for active BGP routesin RIB.

Color only IP steering using CO bits

It is possible to relax the requirement of an exact match of the BGP route’s nexthop with the endpoint of the SR Policy using the “CO” (Color Only) bits in the color extended community. The “CO” bits are 2 reserved bits repurposed for color only steering as defined in section 3 of Advertising Segment Routing Policies in BGP. The exact match of the nexthop is done with the CO bits set to 00 or 11.

CO = 01 Steering: relaxes the nexthop to match the null endpoint of a policy. For a BGP route with nexthop N and color C, the following order is used for resolution. If there is no IGP route resolving the BGP nexthop, the route is not programmed in hardware.
  1. Active SR policy with endpoint N and color C
  2. Active SR policy with null endpoint (from the same AFI as the BGP route) and color C
  3. Active SR policy with null endpoint from any AFI and color C
  4. IGP route

CO = 10 Steering: in addition to the steps in CO = 01 steering, CO = 10 additionally relaxes the nexthop to match any endpoint. The following order is used for resolving a BGP route with nexthop N and color C. The behavior described is in accordance with section 8.8.1 of the IETF draft Segment Routing Policy for Traffic Engineering.

  1. Active SR policy with endpoint N and color C
  2. Active SR policy with null endpoint (from the same AFI as the BGP route) and color C
  3. Active SR policy with null endpoint from any AFI and color C
  4. Active SR policy for any endpoint from the same AFI as the BGP route and color C
  5. Active SR policy for any endpoint from any AFI and color C
  6. IGP route

ECMP of IPv4/IPv6 Prefixes that Resolve over SR-TE Policies

When multiple BGP paths of BGP unicast prefixes resolve through active SR policies form ECMP, the resulting FIB entry for the BGP route has an ECMP of segment list paths which is a union of all the segments-list entries present in each of the resolving SR policies for the BGP paths.

Example

The following table displays four paths for prefix 192.1.0.0/31, and each of the four paths resolves via SR-TE policies.

Table 1. List of Paths Resolved via SR-TE Policies
Path Nexthop Color Policy EP Policy Color Segment Lists Per SL Traffic Distribution
1 1.0.0.2 CO(00):1000 1.0.0.2 1000 [2500 500], Weight: 1

[2501 500], Weight: 2

 8.33%

16.66%
2 1.0.2.2 CO(00):2000 1.0.2.2 2000 [2502 500], Weight: 1

[2503 500], Weight: 1

 12.5%

12.5%
3 1.0.4.2 CO(00):3000 1.0.4.2 3000 [2504 500], Weight: 1

[2505 500], Weight: 1

 12.5%

12.5%
4 1.0.6.2 CO(00):4000 1.0.6.2 4000 [2506 500], Weight: 1

[2507 500], Weight: 1

 12.5%

12.5%

 
 B I    192.1.0.0/31 [200/0] via SR-TE Policy 1.0.4.2, color 3000
                             via SR-TE tunnel index 6, weight 1
                                via 1.0.4.2, Ethernet1, label 2505 500
                             via SR-TE tunnel index 5, weight 1
                                via 1.0.4.2, Ethernet1, label 2504 500
                          via SR-TE Policy 1.0.0.2, color 1000
                             via SR-TE tunnel index 2, weight 1
                                via 1.0.0.2, Ethernet2, label 2501 500
                             via SR-TE tunnel index 1, weight 1
                                via 1.0.0.2, Ethernet2, label 2500 500
                          via SR-TE Policy 1.0.2.2, color 2000
                             via SR-TE tunnel index 4, weight 1
                                via 1.0.2.2, Ethernet3, label 2503 500
                             via SR-TE tunnel index 3, weight 1
                                via 1.0.2.2, Ethernet3, label 2502 500
                          via SR-TE Policy 1.0.6.2, color 4000
                             via SR-TE tunnel index 8, weight 1
                                via 1.0.6.2, Ethernet6, label 2507 500
                             via SR-TE tunnel index 7, weight 1
                                via 1.0.6.2, Ethernet6, label 2506 500

The traffic distribution honors the weights of the SID-Lists. In the example, each of the four SR Policies will get 25% of the total traffic meant for prefix 192.1.0.0/31. Within each policy, the distribution is based on the weights of the SID-Lists.

ECMP Group when some BGP unicast paths resolve over SR Policies and some via non SR Policy IGP paths

If some BGP paths resolve via SR Policy paths and some BGP paths resolve via non SR Policy IGP, then the ECMP group formed programmed as the active route in FIB, only considers the SR Policy paths. ECMP in the FIB is not formed between paths that resolve over SR Policy and paths that resolve via non SR Policy IGP routes. In the example above, if SR Policy with endpoint 1.0.6.2 and color 4000 becomes inactive or is removed, the FIB path for 192.1.0.0/31 resolves via 3 SR Policies as shown below.
B I    192.1.0.0/31 [200/0] via SR-TE Policy 1.0.4.2, color 3000
                             via SR-TE tunnel index 6, weight 1
                                via 1.0.4.2, Ethernet1, label 2505 500
                             via SR-TE tunnel index 5, weight 1
                                via 1.0.4.2, Ethernet1, label 2504 500
                          via SR-TE Policy 1.0.0.2, color 1000
                             via SR-TE tunnel index 2, weight 1
                                via 1.0.0.2, Ethernet2, label 2501 500
                             via SR-TE tunnel index 1, weight 1
                                via 1.0.0.2, Ethernet2, label 2500 500
                          via SR-TE Policy 1.0.2.2, color 2000
                             via SR-TE tunnel index 4, weight 1
                                via 1.0.2.2, Ethernet3, label 2503 500
                             via SR-TE tunnel index 3, weight 1
                                via 1.0.2.2, Ethernet3, label 2502 500
Note: show ip bgp still shows a 4-way ECMP. The FIB paths switch to resolving via the (non SR Policy) IGP paths when there are no BGP paths in the ECMP group that resolve via an SR Policy.

UCMP of IPv4/IPv6 prefixes using LinkBandwidth (LBW) Extended Community that resolve over SR-TE policies not supported

When multiple BGP paths of BGP unicast prefixes resolve through active SR policies form ECMP, and the unicast paths also contain the LBW extended community, EOS does not form UCMP amongst the unicast paths. Only ECMP is formed at the unicast prefix level. The LBW is ignored the behavior is identical to the behavior explained in the previous section.

Resolution of BGP unicast prefixes that resolve over other BGP unicast prefixes resolved via SR Policies

A BGP unicast prefix P1, that is recursively resolved via another BGP prefix P2, such that P2 resolves via an SR Policy, then in the FIB, P1 is programmed with the resolved nexthop pointing to the non SR Policy resolution of P2. P1 does not use P2s SR Policy for forwarding.

Explicit Null Label Imposition

When the address family of the BGP unicast prefix is not the same as the address family of the endpoint of the SR Policy that the unicast prefixes resolves via, an explicit null label is automatically imposed in the outgoing label stack.

Example

If an IPv4 unicast prefix P1 resolves over a policy whose endpoint EP1 is an IPv6 address (this can happen due to color only CO=01/10 steering with P1 having an IPv4 nexthop) and the SR Policy had a SID-List whose resolved label stack is [1001, 1002, 1003], the outgoing packet is imposed with [1001, 1002, 1003, 2] where 0 is the IPv4 explicit null label.

If an IPv6 prefix P2, resolves over a policy whose endpoint EP2 is an IPv4 address (this can happen with color only CO=01/10 steering with P2 having a IPv6 nexthop) and the SR Policy had a SID-List whose resolved label stack is [1001, 1002, 1003], the outgoing packet is imposed with [1001, 1002, 1003, 2] where 2 is the IPv6 explicit null label.

The following table lists the configurations which result in having explicit-null label in the resolved label stack.

Table 2. Configurations resulting in Explicit-Null Label in Resolved Label Stack
ENLP configuration for the resolving SR Policy IPv4 Prefixes IPv6 Prefixes
None - -
IPv4 IPv4 explicit null appended to the end of label stack -
IPv6 - IPv6 explicit null appended to the end of label stack
Both IPv4 explicit null appended to the end of label stack IPv6 explicit null appended to the end of label stack
No/Default config (incase of BGP learnt policies ENLP Sub-TLV is not received) Resolving SR Policy has IPv4 Endpoint address:

No explicit-null

 Resolving SR Policy has IPv4 Endpoint address:

IPv6 explicit null appended to the end of label stack
Resolving SR Policy has IPv6 Endpoint address:

IPv4 explicit null appended to the end of label stack

 Resolving SR Policy has IPv6 Endpoint address:

No explicit-null

Traffic Accounting

All egress tunnel counters (MPLS/GRE/MPLSoGRE using SR-TE/Nexthop-group/BGP-LU tunnel types) share the same hardware resource.
  • 7280E/7500E systems: Up to 16k tunnels
  • 7280R/7500R systems: Up to 8k tunnels
Tunnel counters are allocated on a first-come, first-served basis. Configurations using GRE/MPLSoGRE, GRE, and MPLS further limit a maximum of 4k countable egress MPLS tunnels on 7280R/7500R.

FEC Optimizations

The hardware FEC usage could be reduced as the underlying FEC is shared among different routes.
  • Programming of the active candidate path of an SR-TE policy in hardware is shared between the BSID route and IP steering route.
  • If all of the following conditions are met, ISIS-SR MPLS routes and tunnel entries directly point to the next hop FEC generated by the routing agent (IGP FEC).
    • All the next hops of the MPLS route either point to pop or forward (i.e. swapping to the same label) label action.
    • The switch is either a 7280 or a 7500 platform.
  • The corresponding SR-TE policy BSID routes (and corresponding Segment List tunnels) that resolve over ISIS-SR MPLS routes, will directly point to the IGP FEC.

Configuring SR-TE

The following commands start the SrTePolicy agent and enter the switch into the Traffic Engineering configuration sub-mode.
switch(config)# router traffic-engineering
switch(config-te)# segment-routing
Note: The agent must be running even if the only source of policies is BGP.
Static Policy Configuration
The following commands set the policy using endpoint and color value, and define the BSID for the policy.
switch(config-te-sr)# policy endpoint v4Address|v6Address color color-value
switch(config-te-sr-policy)# binding-sid mpls-label
switch(config-te-sr-policy)# path-group preference value
The following commands enter the policy path configuration sub mode, and adds a segment list to the candidate path.
switch(config-te-sr-policy)# path-group preference value
switch(config-te-sr-policy-path)# segment-list label-stack label1 label2 … weight value
Note: The default weight value is 1. Adding weight is optional. Repear the configuration statement for multiple segment lists per candidate path.
The following commands configures a null label policy.
switch(config-te-sr-policy-path)# explicit-null [none|ipv4|ipv6|both]
Note: The null label policy configuration is optional.

BGP configuration for SR-TE SAFI

The following commands configures a BGP router to activate a neighbor to negotiate and accept SR-TE address-family with this peer.
switch(config)# router bgp <as>
switch(config-router-bgp)# address-family ipv4|ipv6 sr-te
switch(config-router-bgp-af-srte)# neighbor neighbor activate
The following command configures an inbound route-map to filter or modify attributes on incoming SR-TE prefixes from the peer.
switch(config-router-bgp-af-srte)# neighbor neighbor route-map routeMapName in

Configuring Egress SR-TE Traffic Accounting

The following command enables egress traffic accounting for SR policies (also known as MPLS tunnels).
switch(config)# hardware counter feature mpls tunnel
The following command displays current status of the MPLS counters.
switch#show hardware counter feature
Feature            Direction        Counter Resource (Engine)
------------------ ---------------- --------------------------
ACL-IPv4           out              Jericho: 2, 3
ACL                in               Jericho: 4, 5, 6, 7
MPLS tunnel        out              Jericho: 8, 9
The following command disables egress traffic accounting for SR policies.
switch(config)# no hardware counter feature mpls tunnel
The following command displays a summary information of SR-TE SAFI.
switch# show bgp sr-te summary
BGP summary information for VRF default
Router identifier 100.1.1.2, local AS number 100
Neighbor Status Codes: m - Under maintenance
  Neighbor         V  AS           MsgRcvd   MsgSent  InQ OutQ  Up/Down State  PfxRcd PfxAcc
  100.1.1.1        4  100              407       413    0    0 00:18:57 Estab  1      1
  1000::1          4  100              407       413    0    0 00:18:57 Estab  1      1
The following command displays a summary information of candidate paths received from neighbors which have negotiated AFI=1 for SR-TE SAFI.
switch# show bgp sr-te ipv4 summary
BGP summary information for VRF default
Router identifier 100.1.1.2, local AS number 100
Neighbor Status Codes: m - Under maintenance
  Neighbor    V  AS   MsgRcvd  MsgSent InQ OutQ  Up/Down  State  PfxRcd PfxAcc
  100.1.1.1   4  100  407      413     0   0     00:18:57 Estab  0      0
The following command displays a summary information of candidate paths received from neighbors which have negotiated AFI=2 for SR-TE SAFI.
switch# show bgp sr-te ipv6 summary
BGP summary information for VRF default
Router identifier 100.1.1.2, local AS number 100
Neighbor Status Codes: m - Under maintenance
  Neighbor     V  AS   MsgRcvd  MsgSent InQ OutQ  Up/Down  State  PfxRcd PfxAcc
  1000::1      4  100  407      413     0   0     00:18:57 Estab  0      0
The following command displays all the SR-TE candidate paths.
switch# show bgp sr-te
BGP routing table information for VRF default
Router identifier 100.1.1.1, local AS number 100
Policy status codes: * - valid, > - active, E - ECMP head, e - ECMP
                    c - Contributing to ECMP
Origin codes: i - IGP, e - EGP, ? - incomplete
AS Path Attributes: Or-ID - Originator ID, C-LST - Cluster List, LL Nexthop - Link Local Nexthop

     Endpoint    Color   Distinguisher   Next Hop    Metric  LocPref Weight  Path
*>   133.1.1.1   0       1               130.1.1.3   0       100     0       ?
*>   133.1.1.1   0       2               130.1.1.3   0       100     0       ?
*>   1330::1     0       1               1300::3     0       100     0       ?
*>   1330::1     0       2               1300::3     0       100     0       ?
The following command displays all the SR-TE candidate paths with IPv4 endpoints.
switch# show bgp sr-te ipv4
BGP routing table information for VRF default
Router identifier 100.1.1.1, local AS number 100
Policy status codes: * - valid, > - active, E - ECMP head, e - ECMP
                    c - Contributing to ECMP
Origin codes: i - IGP, e - EGP, ? - incomplete
AS Path Attributes: Or-ID - Originator ID, C-LST - Cluster List, LL Nexthop - Link Local Nexthop

     Endpoint   Color   Distinguisher   Next Hop    Metric  LocPref Weight  Path
*>   133.1.1.1  0       1               130.1.1.3   0       100     0       ?
*>   133.1.1.1  0       2               130.1.1.3   0       100     0       ?
The following command displays all the SR-TE candidate paths with IPv6 endpoints.
switch# show bgp sr-te ipv6
BGP routing table information for VRF default
Router identifier 100.1.1.1, local AS number 100
Policy status codes: * - valid, > - active, E - ECMP head, e - ECMP
                    c - Contributing to ECMP
Origin codes: i - IGP, e - EGP, ? - incomplete
AS Path Attributes: Or-ID - Originator ID, C-LST - Cluster List, LL Nexthop - Link Local Nexthop

     Endpoint   Color   Distinguisher   Next Hop   Metric  LocPref Weight  Path
*>   1330::1    0       1               1300::3    0       100     0       ?
*>   1330::1    0       2               1300::3    0       100     0       ?
The following command displays information about a specific candidate path.
switch# show bgp sr-te endpoint 133.1.1.1 color 0 distinguisher 1
BGP routing table information for VRF default
Router identifier 100.1.1.1, local AS number 100
BGP routing table entry for Endpoint: 133.1.1.1 Color: 0 Distinguisher: 1
 Paths: 1 available
  Local
    130.1.1.3 from 100.1.1.2 (100.1.1.2)
      Origin INCOMPLETE, metric 0, localpref 100, IGP metric 0, weight 0, 
      received 00:01:29 ago, valid, internal, best
      Community: no-advertise
      Rx SAFI: SR TE Policy
The following command displays information about a specific candidate path including the contents of the Tunnel encapsulation path attribute TLV of type SR policy.
switch# show bgp sr-te endpoint 133.1.1.1 color 0 distinguisher 1 detail
BGP routing table information for VRF default
Router identifier 100.1.1.1, local AS number 100
BGP routing table entry for Endpoint: 133.1.1.1 Color: 0 Distinguisher: 1
 Paths: 1 available
  Local
    130.1.1.3 from 100.1.1.2 (100.1.1.2)
      Origin INCOMPLETE, metric 0, localpref 100, IGP metric 0, weight 0, 
      received 00:01:29 ago, valid, internal, best
      Community: no-advertise
      Rx SAFI: SR TE Policy
      Tunnel encapsulation attribute: SR Policy
         Preference: 200
         Binding SID: 965536
         Explicit null label policy: IPv4
         Segment-List: Label Stack: [ 16004 16003 ], Weight: 10
         Segment-List: Label Stack: [ 2000 3000 ]
The following command displays information about SR candidate paths received from the specified neighbor. The “policies” keyword displays only the candidate paths that are accepted. “received-policies” additionally also displays the rejected candidate paths.
switch# show bgp neighbors 100.1.1.2 ipv4 sr-te policies
BGP routing table information for VRF default
Router identifier 100.1.1.1, local AS number 100
Policy status codes: * - valid, > - active
Origin codes: i - IGP, e - EGP, ? - incomplete
AS Path Attributes: Or-ID - Originator ID, C-LST - Cluster List, LL Nexthop - Link Local Nexthop

     Endpoint   Color   Distinguisher   Next Hop    Metric  LocPref Weight  Path
*>   133.1.1.1  0       1               133.1.1.3   0       100     0       ?
*>   133.1.1.1  0       2               133.1.1.3   0       100     0       ?
The following command displays information about SR candidate paths received from the specified neighbor along with the contents of the Tunnel Encapsulation path attribute’s TLV of type SR Policy. The policies keyword displays only the candidate paths that are accepted. received-policies additionally also displays the rejected candidate paths..
switch# show bgp neighbors 100.1.1.2 ipv4 sr-te policies detail
BGP routing table information for VRF default
Router identifier 100.1.1.1, local AS number 100
BGP routing table entry for Endpoint: 133.1.1.1 Color: 0 Distinguisher: 2
 Paths: 1 available
  Local
    130.1.1.3 from 100.1.1.2 (100.1.1.2)
      Origin INCOMPLETE, metric 0, localpref 100, IGP metric 0, weight 0, 
      received 00:01:29 ago, invalid, internal
      Rx SAFI: SR TE Policy
      Tunnel encapsulation attribute: SR Policy
         Preference: 200
         Binding SID: 965536
         Explicit null label policy: IPv4
         Segment-List: Label Stack: [ 16004 16003 ], Weight: 10
         Segment-List: Label Stack: [ 2000 3000 ]

PBR Policies

Policy-Based Routing (PBR) allows the operator to specify the next hop for selected incoming packets on an L3 interface, overriding the routing table. Incoming packets are filtered through a policy map referencing one or more ACLs, and matching packets are routed to the next hop specified.

A PBR policy map is composed of one or more classes and can include next-hop information for each class. It can also include single-line raw match statements, which have the appearance and function of a single line from an ACL. Each class contains an eponymous class map. Class maps are user-created, can be edited or deleted, filter traffic using IPv4 ACLs, and are listed in running-config.

These sections describe PBR policy configuration procedures:

Traffic Management Configuration Arad Platform Switches

Traffic policies are implemented by policy maps, which are applied to the control plane, or to L3 interfaces for Policy-Based Routing (PBR). Policy maps contain classes, which are composed of class maps and traffic resolution commands.

Traffic Management Conceptual Overview describes traffic policies.

Configuring Control Plane Traffic PoliciesArad Platform Switches

Default control plane traffic policies are implemented automatically without user intervention. These policies are modified by associating traffic resolution commands with static classes that comprise the control plane policy map.

Static Class Maps

Control plane traffic policies utilize static class maps, which are provided by the switch, are not editable, and cannot be deleted.

Editing the Policy Map

The only control plane policy map is copp-system-policy, which cannot be deleted. In its default form, copp-system-policy consists of the classes listed in class (policy-map (control-plane) Arad). Although the underlying class map of each class cannot be edited, the traffic resolution commands can be adjusted. The default classes cannot be removed from the policy map and their sequence within the policy map is not editable.

Policy maps are modified in policy-map configuration mode. The policy-map type copp command enters policy-map configuration mode.

Example

This command enters policy-map configuration mode for editing copp-system-policy.
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)#

The class (policy-map (control-plane) Arad) command enters policy-map-class configuration mode, where traffic resolution commands are modified for the configuration mode class.

Example

This command enters policy-map-class configuration mode for the copp-system-lacp static class.
switch(config-pmap-copp-system-policy)# class copp-system-lacp
switch(config-pmap-c-copp-system-policy-copp-system-lacp)#

Two traffic resolution commands determine bandwidth parameters for class traffic:

Example

These commands configure a bandwidth range of 2000 to 4000 kilobits per seconds (kbps) for traffic filtered by the copp-system-lacp class map:
switch(config-pmap-c-copp-system-policy-copp-system-lacp)# bandwidth kbps 2000
switch(config-pmap-c-copp-system-policy-copp-system-lacp)# shape kbps 4000
switch(config-pmap-c-copp-system-policy-copp-system-lacp)#

Policy-map and policy-map-class configuration modes are group-change modes. Changes are saved with the exit command or discarded with the abort command. The show active command displays the saved version of policy map. The show pending command displays the modified policy map.

Example

These commands exit policy-map-class configuration mode, display the pending policy-map, then exit policy-map configuration mode, which saves the altered policy map to running-config.
switch(config-pmap-c-copp-system-policy-copp-system-lacp)# exit
switch(config-pmap-copp-system-policy)# show pending
policy-map type copp copp-system-policy
  class copp-system-bpdu

  class copp-system-lldp

  class copp-system-lacp
    shape kbps 4000
    bandwidth kbps 2000

  class copp-system-l3ttl1

  class copp-system-l3slowpath


switch(config-pmap-copp-system-policy)# exit
switch(config)#

Applying Policy Maps to the Control Plane

The copp-system-policy policy map is always applied to the control plane. No commands are available to add or remove this assignment.

Displaying Policy Maps

The show policy-map interface type qos command displays the configured values of the policy maps classes and the number of packets filtered and dropped as a result of the class maps.

Example
These commands exit policy-map-class configuration mode, display the pending policy-map, then exit policy-map configuration mode, which saves the altered policy map to running-config.
switch(config)# show policy-map copp copp-system-policy
Service-policy input: copp-system-policy
  Hardware programming status: InProgress

  Class-map: copp-system-mlag (match-any)
       shape : 10000001 kbps
       bandwidth : 10000001 kbps
      Out Packets : 0
      Drop Packets : 0

  Class-map: copp-system-bpdu (match-any)
       shape : 2604 kbps
       bandwidth : 1302 kbps
      Out Packets : 0
      Drop Packets : 0

  Class-map: copp-system-lacp (match-any)
       shape : 4230 kbps
       bandwidth : 2115 kbps
      Out Packets : 0
      Drop Packets : 0

switch(config)#

switch(config-pmap-c-copp-system-policy-copp-system-lacp)# exit

Configuring QoS Traffic Policies Arad Platform Switches

QoS traffic policies are implemented by creating class maps and policy maps, then applying the policy maps to Ethernet and port channel interfaces.

Creating Class Maps

QoS traffic policies utilize dynamic class maps that are created and modified in class-map configuration mode. The class-map type qos command enters class-map configuration mode.

Example

This command enters class-map configuration mode to create QoS class map named Q-CMap_1.
switch(config)# class-map type qos match-any Q-CMap_1
switch(config-cmap-Q-CMap_1)#

A class map contains one IPv4 access control list (ACL). The match ip access-group command assigns an ACL to the class map. Subsequent match commands replace the existing match command. Class maps filter traffic only on ACL permit rules. Deny ACL rules are disregarded.

Example

This command adds the IPv4 ACL named ACL_1 to the class map.
switch(config-cmap-Q-CMap_1)# match ip access-group ACL_1
switch(config-cmap-Q-CMap_1)#

Class-map configuration mode is a group-change mode. Changes made in a group-change mode are saved by exiting the mode. The show active command displays the saved version of class map. The show pending command displays the unsaved class map.

Example

The show active command indicates that the configuration mode class map is not stored in running-config. The show pending command displays the class map to be stored upon exiting class-map configuration mode.
switch(config-cmap-Q-CMap_1)# show active
switch(config-cmap-Q-CMap_1)# show pending
class-map type qos match-any Q-CMap_1
   match ip access-group ACL_1

switch(config-cmap-Q-CMap_1)#

The exit command returns the switch to global configuration mode and saves pending class map changes. The abort command returns the switch to global configuration mode and discards pending changes.

Example

This command exits class-map configuration mode and stores pending changes to running-config.
switch(config-cmap-CP-CMAP_1)# exit
switch(config)# show class-map type control-plane CP-CMAP_1
  Class-map: CP-CMAP_1 (match-any)
    Match: ip access-group name ACLv4_1
switch(config)#

Creating Policy Maps

Policy maps are created and modified in policy-map configuration mode. The policy-map type quality-of-service command enters policy-map configuration mode.

Example

This command places the switch in policy-map configuration mode and creates a QoS policy map named Q-PMAP_1.
switch(config)# policy-map type quality-of-service Q-PMAP_1
switch(config-pmap-Q-PMAP_1)#

Policy map are edited by adding or removing classes. A class automatically contains its eponymous class map; traffic resolution commands are added or edited in policy-map-class configuration mode. The below command adds a class to the configuration mode policy map and places the switch in policy-map-class configuration mode, where traffic resolution commands are added to the class.

Example

This command adds the Q-CMap_1 class to the Q-PMAP_1 policy map and places the switch in policy-map-class configuration mode.
switch(config-pmap-Q-PMAP_1)# class Q-CMap_1
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)#

The set cos commands configure traffic resolution methods for data that passes the class map:
  • set cos sets the Layer 2 CoS field.

  • set dscp sets the DSCP value in the ToS byte.

  • set traffic class specifies a traffic class queue.

Example

These commands configure the policy map to set the CoS field 7 on packets filtered by the class map, then assigns those packets to traffic class 4.
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)# set cos 7
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)# set traffic-class 4
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)#

Policy-map and policy-map-class configuration modes are group-change modes. Changes are saved with the exit command or discarded with the abort command. The show active and show pending commands display the saved and modified policy map versions, respectively.

Example

These commands exit policy-map-class configuration mode, display the pending policy-map, then exit policy-map configuration mode to save the altered policy map to running-config.
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)# exit
switch(config-pmap-Q-PMAP_1)# show pending
policy-map type quality-of-service Q-PMAP_1
  class Q-CMap_1
    set cos 7
    set traffic-class 4

  class class-default

switch(config-pmap-Q-PMAP_1)# exit
switch(config)#

The last class in all QoS policy maps is class-default. The class-default class map matches all traffic except IPv4 or IPv6 traffic and provides no traffic resolution commands. The class-default class map is not editable; traffic resolution commands can be added to the class-default class.

To modify traffic resolution commands for the class-default class, enter policy-map-class configuration mode for the class, then enter the desired set commands.

Example

These commands enter policy-map-class configuration mode for class-default, configures the stream to enter traffic class 2, and saves the altered policy map to running-config.
switch(config)# policy-map type quality-of-service Q-PMap_1
switch(config-pmap-Q-PMap_1)# class class-default
switch(config-pmap-c-Q-PMap_1-class-default)# set traffic-class 2
switch(config-pmap-c-Q-PMap_1-class-default)# exit
switch(config-pmap-Q-PMap_1)# exit
switch(config)# show policy-map type qos Q-PMap_1
Service-policy Q-PMap_1

  Class-map: Q-CMap_1 (match-any)
    Match: ipv6 access-group name ACLv6_1
       set cos 7
       set traffic-class 4

  Class-map: class-default (match-any)
       set traffic-class 2

switch(config)#

Applying Policy Maps to an Interface

The service-policy type qos (Interface mode) command applies a specified policy map to the configuration mode interface.

These commands apply PMAP-1 policy map to interfaceEthernet 8.
switch(config)# interface ethernet 8
switch(config-if-Et8)# show active
switch(config-if-Et8)# service-policy input PMAP-1
switch(config-if-Et8)# show active
interface Ethernet8
   service-policy type qos input PMAP-1
switch(config-if-Et8)#

Configuring PBR Policies Arad Platform Switches

Policy-Based Routing (PBR) is implemented by creating class maps and policy maps, then applying the policy maps to Ethernet interfaces, port channel interfaces or switch virtual interfaces (SVIs).

Creating PBR Class Maps

PBR policies utilize class maps that are created and modified in the class-map configuration mode. The class-map type pbr command enters the class-map configuration mode.

Example

This command enters the class-map configuration mode to create a PBR class map named CMAP1.
switch(config)# class-map type pbr match-any CMAP1
switch(config-cmap-PBR-CMAP1)#

A class map contains one or more access control lists (ACLs). The match (policy-map (pbr)) command assigns an ACL to the class map. Subsequent match commands add additional ACLs to the class map. Class maps filter traffic only on ACL permit rules. Deny ACL rules are disregarded; if a class map includes ACLs with deny rules, the configuration reverts to its previous state.

Example

This command adds the ACL named ACL1 to the class map.
switch(config-cmap-PBR-CMAP1)# match ip access-group ACL1
switch(config-cmap-PBR-CMAP1)#

The class-map configuration mode is a group-change mode. Changes made in a group-change mode are saved by exiting the mode. The show active command displays the saved version of class map.

The show active command indicates that the configuration mode class map is not stored in running-config. 
switch(config-cmap-PBR-CMAP1)# show active
switch(config-cmap-PBR-CMAP1)#

The exit command returns the switch to the global configuration mode and saves pending class map changes. The abort command returns the switch to the global configuration mode and discards pending changes.

Example

This command exits class-map configuration mode and stores pending changes to running-config.
switch(config-cmap-PBR-CMAP1)# exit
switch(config)# show class-map type pbr CMAP1
class-map type pbr match-any CMAP1
   10 match ip access-group ACL1
switch(config)#

Creating PBR Policy Maps

Policy maps are created and modified in policy-map configuration mode. The policy-map type pbr command enters the policy-map configuration mode.

Example

This command enters the policy-map configuration mode for creating a PBR policy map named PMAP1.
switch(config)# policy-map type pbr PMAP1
switch(config-pmap-PMAP1)#

Policy map are edited by adding or removing classes. A class automatically contains its eponymous class map; next-hop commands are added or edited in the policy-map-class configuration mode. The class (policy-map (pbr)) command adds a class to the configuration mode policy map and places the switch in the policy-map-class configuration mode, where next-hop commands are added to the class.

Example
  • This command adds the CMAP1 class to the policy map and places the switch into the policy-map-class configuration mode.
    switch(config-pmap-PMAP1)# class CMAP1
switch(config-pmap-c-PMAP1-CMAP1)#

    The set nexthop (policy-map-class pbr) command configures the next hop for data that passes the class map.

  • This command configures the policy map to set the next hop to 10.12.0.5 on packets filtered by the class map.
    switch(config-pmap-c-PMAP1-CMAP1)# set nexthop 10.12.0.5
switch(config-pmap-c-PMAP1-CMAP1)#

    The set nexthop-group (policy-map-class(pbr) Arad) command configures a nexthop group as the next hop for data that passes the class map.

  • These commands configure the policy map PMAP1 to set the next hop to a nexthop group named GROUP1 for traffic defined by class map CMAP1. 
    switch(config)# policy-map type pbr PMAP1
switch(config-pmap-PMAP1)# class CMAP1
switch(config-pmap-c-PMAP1-CMAP1)# set nexthop-group GROUP1
switch(config-pmap-c-PMAP1-CMAP1)#

    The policy-map and policy-map-class configuration modes are group-change modes. Changes are saved with the exit command or discarded with the abort command. The show active command displays the currently saved map version.

  • These commands exits the policy-map-class configuration mode, then exits the policy-map configuration mode to save the altered policy map to running-config.
    switch(config-pmap-c-PMAP1-CMAP1)# exit
switch(config-pmap-PMAP1)# exit
switch(config)#

Applying a PBR Policy Map to an Interface

The service-policy type pbr (Interface mode) command applies the specified PBR policy map to the configuration mode interface. Only one PBR service policy is supported per interface.

These commands apply the PMAP1 PBR policy map to interface ethernet 8.
switch(config)# interface ethernet 8
switch(config-if-Et8)# service-policy type pbr input PMAP1
switch(config-if-Et8)#

Hardware Decapsulation

When hardware decapsulation takes place, PBR policy maps on Arad platform switches match on outer packet headers (i.e., they match based on the attributes of the packet before it is decapsulated).

Traffic Management Configuration FM6000 Platform Switches

Traffic policies are implemented by policy maps, which are applied to the control plane or an interface. Policy maps contain classes, which are composed of class maps and traffic resolution commands. Traffic Management Conceptual Overview describes traffic policies.

FM6000 platform switches support the following traffic policies:
  • Control plane policies manage control plane traffic.

  • QoS traffic policies manage traffic on Ethernet and port channel interfaces.

These sections describe the construction and application of policy maps on FM6000 platform switches:

Configuring Control Plane Traffic PoliciesFM6000 Platform Switches

Default control plane traffic policies are implemented automatically without user intervention. These policies are modified by associating traffic resolution commands with static classes that comprise the control plane policy map.

Static Class Maps

Control plane traffic policies utilize static class maps, which are provided by the switch, are not editable, and cannot be deleted.

Editing the Policy Map

The only control plane policy map is copp-system-policy, which cannot be deleted. In its default form, copp-system-policy consists of the classes listed in copp-system-policy default classes: FM6000 Platform Switches. Although the underlying class map of each class cannot be edited, the traffic resolution commands can be adjusted. The default classes cannot be removed from the policy map and their sequence within the policy map is not editable.

Table 3. Copp-system-policy Default Classes: FM6000 Platform Switches
Class Name shape (pps) bandwidth (pps)
copp-system-arp 10000 1000
copp-system-default 8000 1000
copp-system-ipmcrsvd 10000 1000
copp-system-ipmcmiss 10000 1000
copp-system-igmp 10000 1000
copp-system-l2rsvd 10000 10000
copp-system-l3slowpath 10000 1000
copp-system-pim-ptp 10000 1000
copp-system-ospf-isis 10000 1000
copp-system-selfip 5000 5000
copp-system-selfip-tc6to7 5000 5000
copp-system-sflow 25000 1000

Policy maps are modified in the policy-map configuration mode. The policy-map type copp command enters the policy-map configuration mode.

Example

This command enters the policy-map configuration mode for editing copp-system-policy.
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)#

The class (policy-map (control-plane) FM6000) command enters the policy-map-class configuration mode, where traffic resolution commands are modified for the configuration mode class.

Example

This command enters the policy-map-class configuration mode for the copp-system-arp static class.
switch(config-pmap-copp-system-policy)# class copp-system-arp
switch(config-pmap-c-copp-system-policy-copp-system-arp)#

Two traffic resolution commands determine bandwidth parameters for class traffic:

Example

These commands configure a bandwidth range of 2000 to 4000 packets per seconds (pps) for traffic filtered by the copp-system-arp class map:
switch(config-pmap-c-copp-system-policy-copp-system-arp)# bandwidth pps 2000
switch(config-pmap-c-copp-system-policy-copp-system-arp)# shape pps 4000
switch(config-pmap-c-copp-system-policy-copp-system-arp)#

The policy-map and policy-map-class configuration modes are group-change modes. Changes are saved with the exit command or discarded with the abort command. The show active command displays the saved version of policy map. The show pending command displays the modified policy map.

Example

These commands exit the policy-map-class configuration mode, display the pending policy-map, then exits the policy-map configuration mode, which saves the altered policy map to running-config.
switch(config-pmap-c-copp-system-policy-CP-CMAP_1)# exit
switch(config-pmap-copp-system-policy)# show pending
policy-map type copp copp-system-policy
  class CP-CMAP_1
    shape pps 4000
    bandwidth pps 2000

  class copp-system-bpdu

  class copp-system-lldp

  class copp-system-lacp

  class copp-system-arp

  class copp-system-arpresolver

  class copp-system-default

switch(config-pmap-copp-system-policy)#exit
switch(config)#

Applying Policy Maps to the Control Plane

The copp-system-policy policy map is always applied to the control plane. No commands are available to add or remove this assignment.

Configuring QoS Traffic Policies FM6000 Platform Switches

QoS traffic policies are implemented by creating class maps and policy maps, then applying the policy maps to Ethernet and port channel interfaces.

Creating Class Maps

QoS traffic policies utilize dynamic class maps that are created and modified in the class-map configuration mode. The class-map type qos command enters the class-map configuration mode.

Example

This command enters the class-map configuration mode to create QoS class map named Q-CMap_1.
switch(config)# class-map type qos match-any Q-CMap_1
switch(config-cmap-Q-CMap_1)#

A class map contains one IPv4 access control list (ACL). The match (class-map (qos) FM6000) command assigns an ACL to the class map. Subsequent match commands replace the existing match command. Class maps filter traffic only on ACL permit rules. Deny ACL rules are disregarded.

Example

This command adds the IPv4 ACL named ACL_1 to the class map.
switch(config-cmap-Q-CMap_1)# match ip access-group ACL_1
switch(config-cmap-Q-CMap_1)#

The class-map configuration mode is a group-change mode. Changes made in a group-change mode are saved by exiting the mode. The show active command displays the saved version of class map. The show pending command displays the unsaved class map.

Example

The show active command indicates that the configuration mode class map is not stored in running-config. The show pending command displays the class map to be stored upon exiting the class-map configuration mode.
switch(config-cmap-Q-CMap_1)# show active
switch(config-cmap-Q-CMap_1)# show pending
class-map type qos match-any Q-CMap_1
   match ip access-group ACL_1

switch(config-cmap-Q-CMap_1)#

The exit command returns the switch to the global configuration mode and saves pending class map changes. The abort command returns the switch to the global configuration mode and discards pending changes.

Example

This command exits the class-map configuration mode and stores pending changes to running-config.
switch(config-cmap-CP-CMAP_1)# exit
switch(config)# show class-map type control-plane CP-CMAP_1
  Class-map: CP-CMAP_1 (match-any)
    Match: ip access-group name ACLv4_1
switch(config)#

Creating Policy Maps

Policy maps are created and modified in the policy-map configuration mode. The policy-map type quality-of-service command enters the policy-map configuration mode.

Example

This command places the switch in the policy-map configuration mode and creates a QoS policy map named Q-PMAP_1.
switch(config)# policy-map type quality-of-service Q-PMAP_1
switch(config-pmap-Q-PMAP_1)#

Policy map are edited by adding or removing classes. A class automatically contains its eponymous class map; traffic resolution commands are added or edited in the policy-map-class configuration mode. The class (policy-map (qos) FM6000) command adds a class to the configuration mode policy map and places the switch in the policy-map-class configuration mode, where traffic resolution commands are added to the class.

Example

This command adds the Q-CMap_1 class to the Q-PMAP_1 policy map and places the switch in the policy-map-class configuration mode.
switch(config-pmap-Q-PMAP_1)# class Q-CMap_1
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)#

set (policy-map-class (qos) FM6000) commands configure traffic resolution methods for data that passes the class map:
  • set cos sets the Layer 2 CoS field.

  • set dscp sets the DSCP value in the ToS byte.

  • set traffic class specifies a traffic class queue.

Example

These commands configure the policy map to set the CoS field 7 on packets filtered by the class map, then assigns those packets to traffic class 4.
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)# set cos 7
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)# set traffic-class 4
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)#

The policy-map and policy-map-class configuration modes are group-change modes. Changes are saved with the exit command or discarded with the abort command. The show active and show pending commands display the saved and modified policy map versions, respectively.

Example

These commands exit the policy-map-class configuration mode, display the pending policy-map, then exits the policy-map configuration mode to save the altered policy map to running-config.
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)# exit
switch(config-pmap-Q-PMAP_1)# show pending
policy-map type quality-of-service Q-PMAP_1
  class Q-CMap_1
    set cos 7
    set traffic-class 4

  class class-default

switch(config-pmap-Q-PMAP_1)# exit
switch(config)#

The last class in all QoS policy maps is class-default. The class-default class map matches all traffic except IPv4 or IPv6 traffic and provides no traffic resolution commands. The class-default class map is not editable; traffic resolution commands can be added to the class-default class.

To modify traffic resolution commands for the class-default class, enter the policy-map-class configuration mode for the class, then enter the desired set commands.

Example

These commands enter the policy-map-class configuration mode for class-default, configures the stream to enter traffic class 2, and saves the altered policy map to running-config.
switch(config)# policy-map type quality-of-service Q-PMap_1
switch(config-pmap-Q-PMap_1) #class class-default
switch(config-pmap-c-Q-PMap_1-class-default)# set traffic-class 2
switch(config-pmap-c-Q-PMap_1-class-default)# exit
switch(config-pmap-Q-PMap_1)# exit
switch(config)# show policy-map type qos Q-PMap_1
Service-policy Q-PMap_1

  Class-map: Q-CMap_1 (match-any)
    Match: ipv6 access-group name ACLv6_1
       set cos 7
       set traffic-class 4

  Class-map: class-default (match-any)
       set traffic-class 2

switch(config)#

Applying Policy Maps to an Interface

The service-policy type qos (Interface mode) command applies a specified policy map to the configuration mode interface.

These commands apply PMAP-1 policy map to interface ethernet 8.
switch(config)# interface ethernet 8
switch(config-if-Et8)# show active
switch(config-if-Et8)# service-policy input PMAP-1
switch(config-if-Et8)# show active
interface Ethernet8
   service-policy type qos input PMAP-1
switch(config-if-Et8)#

Configuring PBR Policies FM6000 Platform Switches

Policy-Based Routing (PBR) is implemented by creating class maps and policy maps, then applying the policy maps to Ethernet interfaces, port channel interfaces or Switch Virtual Interfaces (SVIs).

Creating PBR Class Maps

PBR policies utilize class maps that are created and modified in the class-map configuration mode. The class-map type pbr command enters the class-map configuration mode.

Example

This command enters the class-map configuration mode to create a PBR class map named CMAP1.
switch(config)# class-map type pbr match-any CMAP1
switch(config-cmap-PBR-CMAP1)#

A class map contains one or more IPv4 access control lists (ACLs). The match (policy-map (pbr)) command assigns an ACL to the class map. Subsequent match commands add additional ACLs to the class map. Class maps filter traffic only on ACL permit rules. Deny ACL rules are disregarded; if a class map includes ACLs with deny rules, the configuration reverts to its previous state.

On FM6000 platform switches, counters are not supported, so a counters per-entry (ACL configuration modes) command in an ACL is ignored.

Example

This command adds the IPv4 ACL named ACL1 to the class map.
switch(config-cmap-PBR-CMAP1)# match ip access-group ACL1
switch(config-cmap-PBR-CMAP1)#

The class-map configuration mode is a group-change mode. Changes made in a group-change mode are saved by exiting the mode. The show active command displays the saved version of class map.

The show active command indicates that the configuration mode class map is not stored in running-config. 
switch(config-cmap-PBR-CMAP1)# show active
switch(config-cmap-PBR-CMAP1)#

The exit command returns the switch to global configuration mode and saves pending class map changes. The abort command returns the switch to global configuration mode and discards pending changes.

Example

This command exits the class-map configuration mode and stores pending changes to running-config.
switch(config-cmap-PBR-CMAP1)# exit
switch(config)# show class-map type pbr CMAP1
class-map type pbr match-any CMAP1
   10 match ip access-group ACL1
switch(config)#

Creating PBR Policy Maps

Policy maps are created and modified in the policy-map configuration mode. The policy-map type pbr command enters the policy-map configuration mode.

Example

This command enters the policy-map configuration mode for creating a PBR policy map named PMAP1.
switch(config)# policy-map type pbr PMAP1
switch(config-pmap-PMAP1)#

Policy map are edited by adding or removing classes. A class automatically contains its eponymous class map; next-hop commands are added or edited in the policy-map-class configuration mode. The class (policy-map (pbr)) command adds a class to the configuration mode policy map and places the switch in the policy-map-class configuration mode, where next-hop commands are added to the class.

Examples
  • This command adds the CMAP1 class to the policy map and places the switch in the policy-map-class configuration mode.
    switch(config-pmap-PMAP1)# class CMAP1
switch(config-pmap-c-PMAP1-CMAP1)#

    The set nexthop (policy-map-class pbr) command configures the next hop for data that passes the class map.

  • This command configures the policy map to set the next hop to 10.12.0.5 on packets filtered by the class map.
    switch(config-pmap-c-PMAP1-CMAP1)# set nexthop 10.12.0.5
switch(config-pmap-c-PMAP1-CMAP1)#

    The policy-map and policy-map-class configuration modes are group-change modes. Changes are saved with the exit command or discarded with the abort command. The show active command displays the currently saved map version.

Example
These commands exits the policy-map-class configuration mode, then exits the policy-map configuration mode to save the altered policy map to running-config.
switch(config-pmap-c-PMAP1-CMAP1)# exit
switch(config-pmap-PMAP1)# exit
switch(config)#

Applying a PBR Policy Map to an Interface

The service-policy type pbr (Interface mode) command applies the specified PBR policy map to the configuration mode interface. Only one PBR service policy is supported per interface.

These commands apply the PMAP1 PBR policy map to interface ethernet 8.
switch(config)# interface ethernet 8
switch(config-if-Et8)# service-policy type pbr input PMAP1
switch(config-if-Et8)#

Hardware Decapsulation

When hardware decapsulation takes place, PBR policy maps on FM6000 platform switches match on outer packet headers (i.e., they match based on the attributes of the packet before it is decapsulated).

Traffic Management Configuration Petra Platform Switches

Traffic policies are implemented by policy maps, which are applied to the control plane. Policy maps contain classes, which are composed of class maps and traffic resolution commands. QoS traffic policies are not supported on 7500 Series switches.

Traffic Management Conceptual Overview describes traffic policies.

Configuring Control Plane Traffic PoliciesPetra Platform Switches

Default control plane traffic policies are implemented automatically without user intervention. These policies are modified by associating traffic resolution commands with static classes that comprise the control plane policy map.

Static Class Maps

Control plane traffic policies utilize static class maps, which are provided by the switch, are not editable, and cannot be deleted.

Editing the Policy Map

The only control plane policy map is copp-system-policy, which cannot be deleted. In its default form, copp-system-policy consists of the classes listed in copp-system-policy default classes: Petra Platform Switches. Although the underlying class map of each class cannot be edited, the traffic resolution commands can be adjusted. The default classes cannot be removed from the policy map and their sequence within the policy map is not editable.

Table 4. copp-system-policy default classes: Petra Platform Switches
Class Name shape (kbps) bandwidth (kbps)
copp-system-bpdu 2500 1250
copp-system-default 2500 250
copp-system-igmp 2500 250
copp-system-ipbroadcast 2500 250
copp-system-ipmc 2500 250
copp-system-ipmcmiss 2500 250
copp-system-ipmcrsvd 2500 250
copp-system-ipunicast NO LIMIT 250
copp-system-l3destmiss 2500 250
copp-system-l3slowpath 2500 250
copp-system-l3ttl0 2500 250
copp-system-l3ttl1 2500 250
copp-system-lacp 2500 1250
copp-system-lldp 2500 250
copp-system-unicast-arp 2500 250

Policy maps are modified in the policy-map configuration mode. The policy-map type copp command enters the policy-map configuration mode.

Example
This command enters the policy-map configuration mode for editing copp-system-policy.
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)#

The class (policy-map (control-plane) Petra) command enters the policy-map-class configuration mode, where traffic resolution commands are modified for the configuration mode class.

Example

  • This command enters the policy-map-class configuration mode for the copp-system-lldp static class.
    switch(config-pmap-copp-system-policy)# class copp-system-lldp
switch(config-pmap-c-copp-system-policy-copp-system-lldp)#

Two traffic resolution commands determine bandwidth parameters for class traffic:

Example
These commands configure a bandwidth range of 2000 to 4000 kilobits per seconds (kbps) for traffic filtered by the copp-system-arp class map:
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# bandwidth kbps 2000
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# shape kbps 4000
switch(config-pmap-c-copp-system-policy-copp-system-lldp)#

The policy-map and policy-map-class configuration modes are group-change modes. Changes are saved with the exit command or discarded with the abort command. The show active command displays the saved version of policy map. The show pending command displays the configured policy map.

Petra platform switches do not support all discrete rate values. When a bandwidth or shape command specifies a value that is not supported, the switch converts the rate to the next highest discrete value that it supports. The show policy-map interface type qos command displays the converted rate and not the user configured rate.

Example
These commands exits the policy-map-class configuration mode, display the pending policy-map, then exits the policy-map configuration mode, which saves the altered policy map to running-config.
switch(config-pmap-c-copp-system-policy-copp-system-lacp)# exit
switch(config-pmap-copp-system-policy)# show pending
policy-map type copp copp-system-policy
  class copp-system-bpdu

  class copp-system-lldp
    shape kbps 4000
    bandwidth kbps 2000

  class copp-system-lacp

switch(config-pmap-copp-system-policy)# exit
switch(config)#

Changes are saved with the exit command or discarded with the abort command. The show active command displays the saved version of policy map. The show pending command displays the modified policy map.

Displaying Policy Maps

The show policy-map interface type qos command displays the traffic resolution rates of the policy maps classes and the number of packets filtered and dropped as a result of the class maps. The shape and bandwidth rates may differ from configured values, because the switch does not support all discrete rate values.

Example

These commands exits the policy-map-class configuration mode, display the pending policy-map, then exits the policy-map configuration mode, which saves the altered policy map to running-config.
switch(config)# show policy-map copp copp-system-policy
Service-policy input: copp-system-policy
  Hardware programming status: InProgress

  Class-map: copp-system-mlag (match-any)
       shape : 10000001 kbps
       bandwidth : 10000001 kbps
      Out Packets : 0
      Drop Packets : 0

  Class-map: copp-system-lacp (match-any)
       shape : 2604 kbps
       bandwidth : 1302 kbps
      Out Packets : 0
      Drop Packets : 0

switch(config)#

Applying Policy Maps to the Control Plane

The copp-system-policy policy map is always applied to the control plane. No commands are available to add or remove this assignment.

Configuring QoS Traffic Policies Petra Platform Switches

QoS traffic policies are not supported on Petra platform switches.

Configuring PBR Policies Petra Platform Switches

PBR policies are not supported on Petra platform switches.

Traffic Management Configuration Trident Platform Switches

Traffic policies are implemented by policy maps, which are applied to the control plane or an interface. Policy maps contain classes, which are composed of class maps and traffic resolution commands. Traffic Management Conceptual Overview describes traffic policies.

Trident platform switches support the following traffic policies:
  • Control plane policies manage control plane traffic.

  • QoS traffic policies manage traffic on Ethernet and port channel interfaces.

These sections describe the construction and application of policy maps:

Configuring Control Plane Traffic PoliciesTrident Platform Switches

Default control plane traffic policies are implemented automatically without user intervention. These policies are modified by creating class maps and editing the policy map to include the new class maps.

Creating Class Maps

Control plane traffic policies utilize static and dynamic class maps. Static class maps are provided by the switch, are not editable, and cannot be deleted. Dynamic class maps are created and modified in the class-map configuration mode. The class-map type copp command enters the class-map configuration mode.

Example

This command enters the class-map configuration mode for creating or editing a control plane dynamic class map named CP-CMAP_1.
switch(config)# class-map type copp match-any CP-CMAP_1
switch(config-cmap-CP-CMAP_1)#

Class maps contain one IPv4 or IPv6 access control list (ACL). The match (class-map (control-plane) Trident) command assigns an ACL to the class map. Subsequent match commands replace the existing match command. Class maps filter traffic only on ACL permit rules. Deny ACL rules are disregarded.

Example

This command assigns the IPv4 ACL named ACLv4_1 to the class map.
switch(config-cmap-CP-CMAP_1)# match ip access-group ACLv4_1
switch(config-cmap-CP-CMAP_1)#

The class-map configuration mode is a group-change mode. Changes are saved by exiting the mode. The show active command displays the saved version of class map. The show pending command displays the unsaved class map.

Example

The show active command indicates that the configuration mode class map is not stored in running-config. The show pending command displays the class map to be stored upon exiting the class-map configuration mode.
switch(config-cmap-CP-CMAP_1)# show active
switch(config-cmap-CP-CMAP_1)# show pending
class-map type copp match-any CP-CMAP_1
   match ip access-group ACLv4_1

switch(config-cmap-CP-CMAP_1)#

The exit command returns the switch to the global configuration mode and saves pending class map changes. The abort command returns the switch to the global configuration mode and discards pending class map changes.

Example

This command exits the class-map configuration mode and stores pending changes to running-config.
switch(config-cmap-CP-CMAP_1)# exit
switch(config)# show class-map type control-plane CP-CMAP_1
  Class-map: CP-CMAP_1 (match-any)
    Match: ip access-group name ACLv4_1
switch(config)#

Editing the Policy Map

The only control plane policy map is copp-system-policy, which cannot be deleted. In its default form, copp-system-policy consists of the classes listed in copp-system-policy default classes: Trident Platform Switches. Although the underlying class map of each class cannot be edited, the traffic resolution commands can be adjusted. The default classes cannot be removed from the policy map and their sequence within the policy map is not editable.

Table 5. copp-system-policy default classes: Trident Platform Switches
Class Name shape (pps) bandwidth (pps)
copp-system-bpdu 5000 5000
copp-system-lacp 5000 5000
copp-system-selfip-tc6to7 5000 5000
copp-system-selfip 5000 5000
copp-system-tc6to7 10000 1000
copp-system-lldp 10000 1000
copp-system-ipmcrsvd 10000 1000
copp-system-igmp 10000 1000
copp-system-ipmcmiss 10000 1000
copp-system-glean 10000 1000
copp-system-tc3to5 10000 1000
copp-system-arp 10000 1000
copp-system-arpresolver 10000 1000
copp-system-l3destmiss 10000 1000
copp-system-l3slowpath 10000 1000
copp-system-l3ttl1 10000 1000
copp-system-default 8000 1000
copp-system-acllog 10000 1000
copp-system-sflow 25000 0

Policy maps are modified in the policy-map configuration mode. The policy-map type copp command enters the policy-map configuration mode.

Example

This command enters the policy-map configuration mode for editing copp-system-policy.
switch(config)#policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)#

Dynamic classes are inserted in front of the static classes. Classes automatically contain their eponymous class map; traffic resolution commands are created or edited in the policy-map-class configuration mode. The class (policy-map (control-plane) Trident) command adds a class to the policy map and places the switch in the policy-map-class configuration mode, where traffic resolution commands are added to the class.

Example

This command adds the CP-CMAP_1 class to the copp-system-policy policy map and places the switch in the policy-map-class configuration mode.
switch(config-pmap-copp-system-policy)# class CP-CMAP_1
switch(config-pmap-c-copp-system-policy-CP-CMAP_1)#

Two traffic resolution commands determine bandwidth parameters for class traffic:

Example

These commands configure a bandwidth range of 2000 to 4000 packets per seconds (pps) for traffic filtered by the CP-CMAP_1 class map:
switch(config-pmap-c-copp-system-policy-CP-CMAP_1)# bandwidth pps 2000
switch(config-pmap-c-copp-system-policy-CP-CMAP_1)# shape pps 4000
switch(config-pmap-c-copp-system-policy-CP-CMAP_1)#

Example

The policy-map and policy-map-class configuration modes are group-change modes. Changes are saved with the exit command or discarded with the abort command. The show active command displays the saved version of policy map. The show pending command displays the modified policy map.

Example

These commands exits the policy-map-class configuration mode, display the pending policy-map, then exits the policy-map configuration mode, which saves the altered policy map to running-config.
switch(config-pmap-c-copp-system-policy-CP-CMAP_1)# exit
switch(config-pmap-copp-system-policy)# show pending
policy-map type copp copp-system-policy
  class CP-CMAP_1
    shape pps 4000
    bandwidth pps 2000

  class copp-system-bpdu

  class copp-system-lldp

  class copp-system-lacp

  class copp-system-arp

  class copp-system-arpresolver

  class copp-system-default

switch(config-pmap-copp-system-policy)# exit
switch(config)#

Example

To modify traffic resolution commands for a static class, enter the policy-map-class configuration mode for the class, then enter the desired bandwidth and shape commands.

Example

These commands enters the policy-map-class configuration mode for copp-system-bpdu class, change the bandwidth range for the class, then save the altered policy map to running-config.
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class copp-system-bpdu
switch(config-pmap-c-copp-system-policy-copp-system-bpdu)# shape pps 200
switch(config-pmap-c-copp-system-policy-copp-system-bpdu)# bandwidth pps 100
switch(config-pmap-c-copp-system-policy-copp-system-bpdu)# exit
switch(config-pmap-copp-system-policy)# show pending
policy-map type copp copp-system-policy
  class CP-CMAP_1
    shape pps 4000
    bandwidth pps 2000

  class copp-system-bpdu
    shape pps 200
    bandwidth pps 100

  class copp-system-lldp

switch(config-pmap-copp-system-policy)# exit
switch(config)#

Applying Policy Maps to the Control Plane

The copp-system-policy policy map is always applied to the control plane. No commands are available to add or remove this assignment.

Configuring QoS Traffic Policies Trident Platform Switches

QoS traffic policies are implemented by creating class maps and policy maps, then applying the policy maps to Ethernet and port channel interfaces.

Creating Class Maps

QoS traffic policies utilize dynamic class maps that are created and modified in the class-map configuration mode. The class-map type qos command enters the class-map configuration mode.

Example

This command enters the class-map configuration mode to create QoS class map named Q-CMap_1.
switch(config)# class-map type qos match-any Q-CMap_1
switch(config-cmap-Q-CMap_1)#

A class map contains one IPv4 or IPv6 Access Control List (ACL). The match (class-map (qos) Trident) command assigns an ACL to the class map. Subsequent match commands replace the existing match command. Class maps filter traffic only on ACL permit rules. Deny ACL rules are disregarded.

Example

This command adds the IPv6 ACL named ACLv6_1 to the class map.
switch(config-cmap-Q-CMap_1)# match ipv6 access-group ACLv6_1
switch(config-cmap-Q-CMap_1)#

The class-map configuration mode is a group-change mode. Changes made in a group-change mode are saved by exiting the mode. The show active command displays the saved version of class map. The show pending command displays the unsaved class map.

Example

The show active command indicates that the configuration mode class map is not stored in running-config. The show pending command displays the class map to be stored upon exiting the class-map configuration mode.
switch(config-cmap-Q-CMap_1)# show active
switch(config-cmap-Q-CMap_1)# show pending
class-map type qos match-any Q-CMap_1
   match ipv6 access-group ACLv6_1

switch(config-cmap-Q-CMap_1)#

The exit command returns the switch to global configuration mode and saves pending class map changes. The abort command returns the switch to global configuration mode and discards pending class map changes.

Example

This command exits the class-map configuration mode and stores pending changes to running-config.
switch(config-cmap-CP-CMAP_1)# exit
switch(config)# show class-map type control-plane CP-CMAP_1
  Class-map: CP-CMAP_1 (match-any)
    Match: ip access-group name ACLv4_1
switch(config)#

Creating Policy Maps

Policy maps are created and modified in the policy-map configuration mode. The policy-map type quality-of-service command enters the policy-map configuration mode.

Example

This command enters the policy-map configuration mode for creating a QoS policy map named Q-PMAP_1.
switch(config)# policy-map type quality-of-service Q-PMAP_1
switch(config-pmap-Q-PMAP_1)#

Policy maps are edited by adding or removing classes. A class automatically contains its eponymous class map; traffic resolution commands are added or edited in the policy-map-class configuration mode. The class (policy-map (qos) Trident) command adds a class to the configuration mode policy map and places the switch in the policy-map-class configuration mode, where traffic resolution commands are added to the class.

Example

This command adds the Q-CMap_1 class to the Q-PMAP_1 policy map and places the switch in the policy-map-class configuration mode.
switch(config-pmap-Q-PMAP_1)# class Q-CMap_1
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)#

The set (policy-map-class (qos) Trident) command configures traffic resolution methods for data that passes the class map:
  • set cos sets the layer 2 CoS field.

  • set dscp sets the DSCP value in the ToS byte.

  • set traffic class specifies a traffic class queue.

Example

These commands configure the policy map to set CoS field 7 on packets filtered by the class map, then assigns those packets to traffic class 4.
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)# set cos 7
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)# set traffic-class 4
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)#

The policy-map and policy-map-class configuration modes are group-change modes. Changes are saved with the exit command or discarded with the abort command. The show active and show pending commands display the saved and modified policy map versions, respectively.

Example

These commands exit the policy-map-class configuration mode, display the pending policy-map, then exits the policy-map configuration mode to save the altered policy map to running-config.
switch(config-pmap-c-Q-PMAP_1-Q-CMap_1)# exit
switch(config-pmap-Q-PMAP_1)# show pending
policy-map type quality-of-service Q-PMAP_1
  class Q-CMap_1
    set cos 7
    set traffic-class 4

  class class-default

switch(config-pmap-Q-PMAP_1)# exit
switch(config)#

The last class in all QoS policy maps is class-default. The class-default class map matches all traffic except IPv4 or IPv6 traffic and provides no traffic resolution commands. The class-default class map is not editable; traffic resolution commands can be added to the class-default class.

To modify traffic resolution commands for the class-default class, enter the policy-map-class configuration mode for the class, then enter the desired set commands.

Example

These commands enters the policy-map-class configuration mode for class-default, configures the stream to enter traffic class 2, and saves the altered policy map to running-config.
switch(config)# policy-map type quality-of-service Q-PMap_1
switch(config-pmap-Q-PMap_1)# class class-default
switch(config-pmap-c-Q-PMap_1-class-default)# set traffic-class 2
switch(config-pmap-c-Q-PMap_1-class-default)# exit
switch(config-pmap-Q-PMap_1)# exit
switch(config)# show policy-map type qos Q-PMap_1
Service-policy Q-PMap_1

  Class-map: Q-CMap_1 (match-any)
    Match: ipv6 access-group name ACLv6_1
       set cos 7
       set traffic-class 4

  Class-map: class-default (match-any)
       set traffic-class 2

switch(config)#

Applying Policy Maps to an Interface

The service-policy type qos (Interface mode) command applies a specified policy map to the configuration mode interface.

Example

These commands apply PMAP-1 policy map to interface ethernet 8.
switch(config)# interface ethernet 8
switch(config-if-Et8)# show active
switch(config-if-Et8)# service-policy input PMAP-1
switch(config-if-Et8)# show active
interface Ethernet8
   service-policy type qos input PMAP-1
switch(config-if-Et8)#

Configuring PBR Policies Trident Platform Switches

Policy-Based Routing (PBR) is implemented by creating class maps and policy maps, then applying the policy maps to Ethernet interfaces, port channel interfaces or Switch Virtual Interfaces (SVIs).

Creating PBR Class Maps

PBR policies utilize class maps that are created and modified in the class-map configuration mode. The class-map type pbr command enters the class-map configuration mode.

Example

This command enters the class-map configuration mode to create a PBR class map named CMAP1.
switch(config)# class-map type pbr match-any CMAP1
switch(config-cmap-PBR-CMAP1)#

A class map contains one or more Access Control Lists (ACLs). The match (policy-map (pbr)) command assigns an ACL to the class map. Subsequent match commands add additional ACLs to the class map. Class maps filter traffic only on ACL permit rules. Deny ACL rules are disregarded; if a class map includes ACLs with deny rules, the configuration reverts to its previous state.

Examples

  • This command adds the ACL named ACL1 to the class map.
    switch(config-cmap-PBR-CMAP1)# match ip access-group ACL1
switch(config-cmap-PBR-CMAP1)#

    The class-map configuration mode is a group-change mode. Changes made in a group-change mode are saved by exiting the mode. The show active command displays the saved version of class map.

  • The show active command indicates that the configuration mode class map is not stored in running-config. 
    switch(config-cmap-PBR-CMAP1)# show active
switch(config-cmap-PBR-CMAP1)#

  • The exit command returns the switch to global configuration mode and saves pending class map changes. The abort command returns the switch to global configuration mode and discards pending changes.

  • This command exits the class-map configuration mode and stores pending changes to running-config.
    switch(config-cmap-PBR-CMAP1)# exit
switch(config)# show class-map type pbr CMAP1
class-map type pbr match-any CMAP1
   10 match ip access-group ACL1
switch(config)#

Creating PBR Policy Maps

Policy maps are created and modified in the policy-map configuration mode. The policy-map type pbr command enters policy-map configuration mode.

Examples

  • This command enters the policy-map configuration mode for creating a PBR policy map named PMAP1.
    switch(config)# policy-map type pbr PMAP1
switch(config-pmap-PMAP1)#

    Policy map are edited by adding or removing classes. A class automatically contains its eponymous class map; next-hop commands are added or edited in the policy-map-class configuration mode. The class (policy-map (pbr)) command adds a class to the configuration mode policy map and places the switch in the policy-map-class configuration mode, where next-hop commands are added to the class.

  • This command adds the CMAP1 class to the policy map and places the switch in the policy-map-class configuration mode.
    switch(config-pmap-PMAP1)# class CMAP1
switch(config-pmap-c-PMAP1-CMAP1)#

  • The set nexthop (policy-map-class pbr) command configures the next hop for data that passes the class map.This command configures the policy map to set the next hop to 10.12.0.5 on packets filtered by the class map.
    switch(config-pmap-c-PMAP1-CMAP1)# set nexthop 10.12.0.5
switch(config-pmap-c-PMAP1-CMAP1)#

  • The policy-map and policy-map-class configuration modes are group-change modes. Changes are saved with the exit command or discarded with the abort command. The show active command displays the currently saved map version. These commands exits the policy-map-class configuration mode, then exits the policy-map configuration mode to save the altered policy map to running-config.
    switch(config-pmap-c-PMAP1-CMAP1)# exit
switch(config-pmap-PMAP1)# exit
switch(config)#

Applying a PBR Policy Map to an Interface

The service-policy type pbr (Interface mode) command applies the specified PBR policy map to the configuration mode interface. Only one PBR service policy is supported per interface.
  • These commands apply the PMAP1 PBR policy map to interface ethernet 8.
    switch(config)# interface ethernet 8
switch(config-if-Et8)# service-policy type pbr input PMAP1
switch(config-if-Et8)#

Hardware Decapsulation

When hardware decapsulation takes place, PBR policy maps on Trident platform switches match on inner packet headers (i.e., they match based on the attributes of the decapsulated packet).

Traffic Management Configuration Trident II Platform Switches

Traffic policies are implemented by policy maps, which are applied to the control plane or an interface. Policy maps contain classes, which are composed of class maps and traffic resolution commands. Traffic Management Conceptual Overview describes traffic policies.

Trident platform switches support the following traffic policies:
  • Control plane policies manage control plane traffic.

  • QoS traffic policies manage traffic on Ethernet and port channel interfaces.

Configuring Control Plane Traffic PoliciesTrident II Platform Switches

Default control plane traffic policies are implemented automatically without user intervention. These policies are modified by associating traffic resolution commands with static classes that comprise the control plane policy map.

Static Class Maps

Control plane traffic policies utilize static class maps, which are provided by the switch, are not editable, and cannot be deleted.

Editing the Policy Map

The only control plane policy map is copp-system-policy, which cannot be deleted. In its default form, copp-system-policy consists of the classes listed in copp-system-policy default classes: Trident II Platform Switches. Although the underlying class map of each class cannot be edited, the traffic resolution commands can be adjusted. The default classes cannot be removed from the policy map and their sequence within the policy map is not editable.

Table 6. copp-system-policy default classes: Trident II Platform Switches
Class Name shape (pps) bandwidth (pps)
copp-system-acllog 1000 10000
copp-system-arp 1000 10000
copp-system-arpresolver 1000 10000
copp-system-bfd 5000 10000
copp-system-bgp 5000 5000
copp-system-bpdu 5000 5000
copp-system-default 1000 8000
copp-system-glean 1000 10000
copp-system-igmp 1000 10000
copp-system-ipmcmiss 1000 10000
copp-system-ipmcrsvd 1000 10000
copp-system-l3destmiss 1000 10000
copp-system-l3slowpath 1000 10000
copp-system-l3ttl1 1000 10000
copp-system-lacp 5000 5000
copp-system-lldp 1000 10000
copp-system-mlag 5000 5000
copp-system-selfip 5000 5000
copp-system-selfip-tc6to7 5000 5000
copp-system-sflow 0 25024
copp-system-tc3to5 1000 10000
copp-system-tc6to7 1000 10000
copp-system-urm 1000 10000

Policy maps are modified in the policy-map configuration mode. The policy-map type copp command enters the policy-map configuration mode.

Examples

  • This command enters the policy-map configuration mode for editing copp-system-policy.
    switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)#

  • The class (policy-map (control-plane) Trident II) command enters the policy-map-class configuration mode, where traffic resolution commands are modified for the configuration mode class.

  • This command enters the policy-map-class configuration mode for the copp-system-lacp static class.
    switch(config-pmap-copp-system-policy)# class copp-system-lacp
switch(config-pmap-c-copp-system-policy-copp-system-lacp)#

Two traffic resolution commands determine bandwidth parameters for class traffic:

Examples

  • These commands configure a bandwidth range of 2000 to 4000 packets per seconds (pps) for traffic filtered by the copp-system-lacp class map:
    switch(config-pmap-c-copp-system-policy-copp-system-lacp)# bandwidth pps 2000
switch(config-pmap-c-copp-system-policy-copp-system-lacp)# shape pps 4000
switch(config-pmap-c-copp-system-policy-copp-system-lacp)#

  • The policy-map and policy-map-class configuration modes are group-change modes. Changes are saved with the exit command or discarded with the abort command. The show active command displays the saved version of policy map. The show pending command displays the modified policy map.

  • These commands exits the policy-map-class configuration mode, display the pending policy-map, then exit policy-map configuration mode, which saves the altered policy map to running-config.
    switch(config-pmap-c-copp-system-policy-copp-system-lacp)# exit
switch(config-pmap-copp-system-policy)# show pending
policy-map type copp copp-system-policy
  class copp-system-bpdu

  class copp-system-lldp

  class copp-system-lacp
    shape pps 4000
    bandwidth pps 2000

  class copp-system-arp

switch(config-pmap-copp-system-policy)# exit
switch(config)#

Applying Policy Maps to the Control Plane

The copp-system-policy policy map is always applied to the control plane. No commands are available to add or remove this assignment.

Traffic Management Configuration Commands

Traffic Policy (Control Plane) Configuration Commands

Traffic Policy (PBR) Configuration Commands

CPU Traffic Policy Command

Traffic Policy (QoS) Configuration Commands

Traffic Policy Display and Utility Commands

action set-ttl

The TTL action is effective only when it is configured along with a set nexthop or nexthop-group action. The TCAM profile has the set-ttl-3b or set-ttl action in the pbr ip and pbr ipv6 features, such as in the tc-counters system profile.

Command Mode

For IP

TCAM feature PBR IP configuration mode.

For IPv6

TCAM feature PBR IPv6 configuration mode.

Command Syntax

action set-time [set-ttl | set-ttl-3b]

no action set-time [set-ttl | set-ttl-3b]

default action set-time [set-ttl | set-ttl-3b]

Parameters

  • set-ttl Set time to live.
  • set-ttl-3b Set 3-bit time to live.

Examples

  • In the following example, for IP, the action sets the time to live for the next hop. 

    (config)# hardware tcam
(config-tcam)# profile pbr-set-ttl copy default
(config-tcam-profile-pbr-set-ttl)# feature pbr ip
(config-tcam-feature-pbr-ip)# action set-ttl

  • In the following example, for IPv6, the action sets the time to live for the next hop group.

    config)# hardware tcam
(config-tcam)# profile pbr-set-ttl copy default
(config-tcam-profile-pbr-set-ttl)# feature pbr ip
(config-tcam-feature-pbr-ip)# feature pbr ipv6
(config-tcam-feature-pbr-ipv6)# action set-ttl

bandwidth (policy-map-class (control-plane)Arad)

The bandwidth command specifies the minimum bandwidth for traffic filtered by the configuration mode policy map class.

The no bandwidth and default bandwidth commands remove the minimum bandwidth guarantee for the configuration mode class by deleting the corresponding bandwidth command from running-config.

Command Mode

Policy-map-class (control plane) configuration

accessed through class (policy-map (control-plane) Arad)

Command Syntax

bandwidth kbps kilobits

no bandwidth

default bandwidth

Parameters

kilobits Minimum data rate in kilobits per second. Value ranges from 1 to 10000000.

Related Commands

Static Classes Default Bandwidth

Arad platform switches define these default bandwidths for control plane static classes:
  • copp-system-bgp 250 copp-system-l3lpmoverflow 250
  • copp-system-bpdu 1250 copp-system-l3slowpath 250
  • copp-system-default 250 copp-system-l3ttl1 250
  • copp-system-ipbroadcast 250 copp-system-lacp 1250
  • copp-system-ipmc 250 copp-system-linklocal 250
  • copp-system-ipmcmiss 250 copp-system-lldp 250
  • copp-system-ipunicast 250 copp-system-mlag 250
  • copp-system-l2broadcast 250 copp-system-multicastsnoop 250
  • copp-system-l2unicast 250 copp-system-OspfIsis 250
  • copp-system-l3destmiss 250 copp-system-sflow 250

Example

These commands configure the minimum bandwidth of 500 kbps for data traffic specified by the class map copp-system-lldp of the default control-plane policy map. 
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class copp-system-lldp
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# bandwidth kbps 500
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# exit
switch(config-pmap-copp-system-policy)# exit
switch(config)# show policy-map copp copp-system-policy
Service-policy input: copp-system-policy
  Hardware programming status: InProgress

  Class-map: copp-system-lldp (match-any)
       shape : 2500 kbps
       bandwidth : 500 kbps
      Out Packets : 0
      Drop Packets : 0

switch(config)#

bandwidth (policy-map-class (control-plane)FM6000)

The bandwidth command specifies the minimum bandwidth for traffic filtered by the configuration mode policy map class.

The no bandwidth and default bandwidth commands remove the minimum bandwidth guarantee for the configuration mode class by deleting the corresponding bandwidth command from running-config.

Command Mode

Policy-map-class (control plane) configuration

accessed through class (policy-map (control-plane) FM6000)

Command Syntax

bandwidth pps packets

no bandwidth

default bandwidth

Parameters

packets Minimum data rate in packets per second. Value ranges from 1 to 100000.

Related Commands

Static Classes Default Bandwidth

FM6000 platform switches define these default bandwidths for control plane static classes:
  • copp-system-arp 1000 copp-system-l3slowpath 1000
  • copp-system-default 1000 copp-system-pim-ptp 1000
  • copp-system-ipmcrsvd 1000 copp-system-ospf-isis 1000
  • copp-system-ipmcmiss 1000 copp-system-selfip 5000
  • copp-system-igmp 1000 copp-system-selfip-tc6to7 5000
  • copp-system-l2rsvd 10000 copp-system-sflow 1000

Example

These commands configure the minimum bandwidth of 1000 packets per second for data traffic specified by the class map PMAP-1 in the policy map named copp-system-policy.
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class PMAP-1
switch(config-pmap-c-copp-system-policy-PMAP-1)# bandwidth pps 1000
switch(config-pmap-c-copp-system-policy-PMAP-1)#

bandwidth (policy-map-class (control-plane)Helix)

The bandwidth command specifies the minimum bandwidth for traffic filtered by the configuration mode policy map class.

The no bandwidth and default bandwidth commands remove the minimum bandwidth guarantee for the configuration mode class by deleting the corresponding bandwidth command from running-config.

Command Mode

Policy-map-class (control plane) configuration

accessed through class (policy-map (control-plane) Helix)

Command Syntax

bandwidth pps packets

no bandwidth

default bandwidth

Parameter

packets Minimum data rate in packets per second. Value ranges from 1 to 100000.

Related Commands

Static Classes Default Bandwidth

Helix platform switches define these default bandwidths for control plane static classes:
  • copp-system-acllog 1000 copp-system-l3ttl1 1000
  • copp-system-arp 1000 copp-system-lacp 5000
  • copp-system-arpresolver 1000 copp-system-lldp 1000
  • copp-system-bfd 5000 copp-system-mlag 5000
  • copp-system-bgp 5000 copp-system-OspfIsis 5000
  • copp-system-bpdu 5000 copp-system-selfip 5000
  • copp-system-default 1000 copp-system-selfip-tc6to7 5000
  • copp-system-glean 1000 copp-system-sflow 0
  • copp-system-igmp 1000 copp-system-tc3to5 1000
  • copp-system-ipmcmiss 1000 copp-system-tc6to7 1000
  • copp-system-ipmcrsvd 1000 copp-system-urm 1000
  • copp-system-l3destmiss 1000 copp-system-vrrp 1000
  • copp-system-l3slowpath 1000

Example

These commands configure the minimum bandwidth of 500 packets per second for data traffic specified by the class map copp-system-lldp.
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class copp-system-lldp
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# bandwidth pps 500
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# exit
switch(config-pmap-copp-system-policy)# exit
switch(config)# show policy-map interface control-plan copp-system-policy
Service-policy input: copp-system-policy
  Number of units programmed: 4
  Hardware programming status: Successful

  Class-map: copp-system-lldp (match-any)
       shape : 10000 pps
       bandwidth : 500 pps
      Out Packets : 304996
      Drop Packets : 0

switch(config)#

bandwidth (policy-map-class (control-plane)Petra)

The bandwidth command specifies the minimum bandwidth for traffic filtered by the configuration mode policy map class.

The no bandwidth and default bandwidth commands remove the minimum bandwidth guarantee for the configuration mode class by deleting the corresponding bandwidth command from running-config.

Command Mode

Policy-map-class (control plane) configuration

accessed through class (policy-map (control-plane) Petra)

Command Syntax

bandwidth kbps kilobits

no bandwidth

default bandwidth

Parameter

kbits Minimum data rate in kilobits per second. Value ranges from 1 to 10000000.

Related Commands

Static Classes Default Bandwidth

Petra platform switches define these default bandwidths for control plane static classes:
  • copp-system-bpdu 1250 copp-system-l3destmiss 250
  • copp-system-default 250 copp-system-l3slowpath 250
  • copp-system-igmp 250 copp-system-l3ttl0 250
  • copp-system-ipbroadcast 250 copp-system-l3ttl1 250
  • copp-system-ipmc 250 copp-system-lacp 1250
  • copp-system-ipmcmiss 250 copp-system-lldp 250
  • copp-system-ipmcrsvd 250 copp-system-unicast-arp 250
  • copp-system-ipunicast 250

Guidelines

Petra does not support all discrete rate values. When a specified discrete value is not supported, the switch converts the rate to the next highest discrete value that it supports. The show command displays the converted rate and not the user-configured rate.

Example

These commands configure a minimum bandwidth of 500 kbps for data traffic specified by the class map copp-system-lldp of the default control-plane policy map. Because the switch does not support the discrete value of 500 kbps, it converts the bandwidth up to 651 kbps.
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class copp-system-lldp
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# bandwidth kbps 500
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# exit
switch(config-pmap-copp-system-policy)# exit
switch(config)# show policy-map copp copp-system-policy
Service-policy input: copp-system-policy
  Hardware programming status: InProgress

  Class-map: copp-system-lldp (match-any)
       shape : 2766 kbps
       bandwidth : 651 kbps
      Out Packets : 0
      Drop Packets : 0

switch(config)#

bandwidth (policy-map-class (control-plane)Trident II)

The bandwidth command specifies the minimum bandwidth for traffic filtered by the configuration mode policy map class.

The no bandwidth and default bandwidth commands remove the minimum bandwidth guarantee for the configuration mode class by deleting the corresponding bandwidth command from running-config.

Command Mode

Policy-map-class (control plane) configuration

accessed through class (policy-map (control-plane) Trident II).

Command Syntax

bandwidth pps packets

no bandwidth

default bandwidth

Parameter

packets Minimum data rate in packets per second. Value ranges from 1 to 100000.

Related Commands

Static Classes Default Bandwidth

Trident II platform switches define these default bandwidths for control plane static classes:
  • copp-system-acllog 1000 copp-system-l3slowpath 1000
  • copp-system-arp 1000 copp-system-l3ttl1 1000
  • copp-system-arpresolver 1000 copp-system-lacp 5000
  • copp-system-bfd 5000 copp-system-lldp 1000
  • copp-system-bgp 5000 copp-system-mlag 5000
  • copp-system-bpdu 5000 copp-system-selfip 5000
  • copp-system-default 1000 copp-system-selfip-tc6to7 5000
  • copp-system-glean 1000 copp-system-sflow 0
  • copp-system-igmp 1000 copp-system-tc3to5 1000
  • copp-system-ipmcmiss 1000 copp-system-tc6to7 1000
  • copp-system-ipmcrsvd 1000 copp-system-urm 1000
  • copp-system-l3destmiss 1000

Example

These commands configure the minimum bandwidth of 500 packets per second for data traffic specified by the class map copp-system-lldp.
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class copp-system-lldp
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# bandwidth pps 500
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# exit
switch(config-pmap-copp-system-policy)# exit
switch(config)# show policy-map interface control-plan copp-system-policy
Service-policy input: copp-system-policy
  Number of units programmed: 4
  Hardware programming status: Successful

  Class-map: copp-system-lldp (match-any)
       shape : 10000 pps
       bandwidth : 500 pps
      Out Packets : 304996
      Drop Packets : 0

switch(config)#

bandwidth (policy-map-class (control-plane)Trident)

The bandwidth command specifies the minimum bandwidth for traffic filtered by the configuration mode policy map class.

The no bandwidth and default bandwidth commands remove the minimum bandwidth guarantee for the configuration mode class by deleting the corresponding bandwidth command from running-config.

Command Mode

Policy-map-class (control plane) configuration

accessed through class (policy-map (control-plane) Trident).

Command Syntax

bandwidth pps packets

no bandwidth

default bandwidth

Parameter

packets Minimum data rate in packets per second. Value ranges from 1 to 100000.

Related Commands

Static Classes Default Bandwidth

Trident platform switches define these default bandwidths for control plane static classes:
  • copp-system-arp 1000 copp-system-lldp 1000
  • copp-system-arpresolver 1000 copp-system-l3destmiss 1000
  • copp-system-bpdu 5000 copp-system-l3slowpath 1000
  • copp-system-default 1000 copp-system-l3ttl1 1000
  • copp-system-glean 1000 copp-system-selfip 5000
  • copp-system-igmp 1000 copp-system-selfip-tc6to7 5000
  • copp-system-ipmcmiss 1000 copp-system-sflow 0
  • copp-system-ipmcrsvd 1000 copp-system-tc6to7 1000
  • copp-system-lacp 5000 copp-system-tc3to5 1000

Example

These commands configure the minimum bandwidth of 1000 packets per second for data traffic specified by the class map PMAP-1 in the policy map named copp-system-policy.
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class PMAP-1
switch(config-pmap-c-copp-system-policy-PMAP-1)# bandwidth pps 1000
switch(config-pmap-c-copp-system-policy-PMAP-1)#

class (policy-map (control-plane) Arad)

The class command places the switch in policy-map-class (control plane) configuration mode, which is a group change mode for changing bandwidth and shape parameters associated with a specified class. All changes in a group change mode edit session are pending until the end of the session.

A policy map is an ordered list of classes. The control plane policy map contains 20 static classes. Each class contains an eponymous class map and may contain bandwidth and shape commands.
  • The class map identifies a data stream.

  • bandwidth command defines the streams minimum transmission rate through the control plane.

  • shape command defines the streams maximum transmission rate through the control plane.

Static class maps identify a data stream by definition. Each data packet is managed by commands of the first class whose map matches the packets content. Dynamic classes are not supported for control plane policing on Arad platform switches.

Each class corresponds to a transmission queue. Queue scheduling is round-robin until bandwidth rate for a queue is exceeded. Scheduling becomes strict-priority with CPU queue number determining priority until the shape rate is reached. Packets are dropped after the shape rate is exceeded.

The exit command returns the switch to policy-map configuration mode. Saving policy-map-class changes also require an exit from policy-map mode, which saves pending policy-map-class and policy-map changes to running-config and returns the switch to the global configuration mode. The abort command discards pending changes, returning the switch to the global configuration mode.

The no class and default class commands remove policy-map-class commands for the specified class assignment from the policy map.

Command Mode

Policy-Map (control plane) configuration accessed through policy-map type copp command.

Command Syntax

class class_name

no class class_name

default class class_name

Parameter

class_name name of the class.

Static Classes

Arad platform switches provide the following static control plane classes:
  • copp-system-bgp copp-system-l2broadcast copp-system-linklocal
  • copp-system-bpdu copp-system-l2unicast copp-system-lldp
  • copp-system-default copp-system-l3destmiss copp-system-mlag
  • copp-system-ipbroadcast copp-system-l3lpmoverflow copp-system-multicastsnoop
  • copp-system-ipmc copp-system-l3slowpath copp-system-OspfIsis
  • copp-system-ipmcmiss copp-system-l3ttl1 copp-system-sflow
  • copp-system-ipunicast copp-system-lacp

Commands Available in Policy-map-class (control plane) Configuration Mode

Related Commands

policy-map type copp places switch in policy-map (control plane) configuration mode.

Example

These commands enters policy-map-class configuration mode to modify the shape, bandwidth parameters associated with the static class named copp-system-lldp. 
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class copp-system-lldp
switch(config-pmap-c-copp-system-policy-copp-system-lldp)#

class (policy-map (control-plane) FM6000)

The class command places the switch in policy-map-class (control plane) configuration mode, which is a group change mode for changing bandwidth and shape parameters associated with a specified class. All changes in a group change mode edit session are pending until the end of the session.

A policy map is an ordered list of classes. The control plane policy map contains 12 static classes. Each class contains an eponymous class map and may contain bandwidth and shape commands.
  • The class map identifies a data stream.

  • bandwidth command defines the streams minimum transmission rate through the control plane.

  • shape command defines the streams maximum transmission rate through the control plane.

Static class maps identify a data stream by definition. Each data packet is managed by commands of the first class whose map matches the packets content. Dynamic classes are not supported for control plane policing on FM6000 platform switches.

Each class corresponds to a transmission queue. Queue scheduling is round-robin until bandwidth rate for a queue is exceeded. Scheduling becomes strict-priority with CPU queue number determining priority until the shape rate is reached. Packets are dropped after the shape rate is exceeded.

The exit command returns the switch to policy-map configuration mode. Saving policy-map-class changes also require an exit from policy-map mode, which saves pending policy-map-class and policy-map changes to running-config and returns the switch to the global configuration mode. The abort command discards pending changes, returning the switch to the global configuration mode.

The no class and default class commands remove policy-map-class commands for the specified class assignment from the policy map. The class is removed from the policy map if it is a dynamic class.

Command Mode

Policy-Map (control plane) configuration accessed through policy-map type copp command.

Command Syntax

class class_name

no class class_name

default class class_name

Parameter

class_name name of the class.

Static Classes

FM6000 platform switches provide the following static control plane classes:
  • copp-system-arp copp-system-igmp copp-system-PimPtp
  • copp-system-default copp-system-l2rsvd copp-system-selfip
  • copp-system-ipmcmiss copp-system-l3slowpath copp-system-selfip-tc6to7
  • copp-system-ipmcrsvd copp-system-OspfIsis copp-system-sflow

Commands Available in Policy-map-class (control plane) Configuration Mode

Related Commands

policy-map type copp places switch in policy-map (control plane) configuration mode.

Example

These commands enters policy-map-class configuration mode to modify the shape, bandwidth parameters associated with the static class named copp-system-arp. 
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class copp-system-arp
switch(config-pmap-c-copp-system-policy-copp-system-arp)#

class (policy-map (control-plane) Helix)

The class command places the switch in policy-map-class (control plane) configuration mode, which is a group change mode for changing bandwidth and shape parameters associated with a specified class. All changes in a group change mode edit session are pending until the end of the session.

A policy map is an ordered list of classes. The control plane policy map contains 23 static classes. Each class contains an eponymous class map and may contain bandwidth and shape commands.
  • The class map identifies a data stream.

  • bandwidth command defines the streams minimum transmission rate through the control plane.

  • shape command defines the streams maximum transmission rate through the control plane.

Static class maps identify a data stream by definition. Each data packet is managed by commands of the first class whose map matches the packets content. Dynamic classes are not supported for control plane policing on Helix platform switches.

Each class corresponds to a transmission queue. Queue scheduling is strict-priority; CPU queue number determines priority until the shape rate is reached. Packets are dropped after the shape rate is exceeded.

The exit command returns the switch to policy-map configuration mode. Saving policy-map-class changes also require an exit from policy-map mode, which saves the pending policy-map-class and policy-map changes to running-config and returns the switch to global configuration mode. The abort command discards pending changes, returning the switch to the global configuration mode.

The no class and default class commands remove the policy-map-class commands for the specified class assignment from the policy map.

Command Mode

Policy-Map (control plane) configuration accessed through policy-map type copp command.

Command Syntax

class class_name

no class class_name

default class class_name

Parameter

class_name name of the class.

Static Classes

Helix platform switches provide the following static control plane classes:
  • copp-system-acllog copp-system-ipmcmiss copp-system-OspfIsis
  • copp-system-arp copp-system-ipmcrsvd copp-system-selfip
  • copp-system-arpresolver copp-system-l3destmiss copp-system-selfip-tc6to7
  • copp-system-bfd copp-system-l3slowpath copp-system-sflow
  • copp-system-bgp copp-system-l3ttl1 copp-system-tc3to5
  • copp-system-bpdu copp-system-lacp copp-system-tc6to7
  • copp-system-default copp-system-lldp copp-system-urm
  • copp-system-glean copp-system-lldp copp-system-vrrp
  • copp-system-igmp copp-system-lldp

Commands Available in Policy-map-class (control plane) Configuration Mode

Related Commands

policy-map type copp places switch in policy-map (control plane) configuration mode.

Example

These commands enters policy-map-class configuration mode to modify the shape, bandwidth parameters associated with the static class named copp-system-arp. 
switch(config)# policy-map
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class copp-system-lldp
switch(config-pmap-c-copp-system-policy-copp-system-lldp)#

class (policy-map (control-plane) Petra)

The class command places the switch in policy-map-class (control plane) configuration mode, which is a group change mode for changing bandwidth and shape parameters associated with a specified class. All changes in a group change mode edit session are pending until the end of the session.

A policy map is an ordered list of classes. The control plane policy map contains 15 static classes. Each class contains an eponymous class map and may contain bandwidth and shape commands.
  • The class map identifies a data stream.

  • bandwidth command defines the streams minimum transmission rate through the control plane.

  • shape command defines the streams maximum transmission rate through the control plane.

Static class maps identify a data stream by definition. Each data packet is managed by commands of the first class whose map matches the packets content. Dynamic classes are not supported for control plane policing on Petra platform switches.

Each class corresponds to a transmission queue. Queue scheduling is round-robin until bandwidth rate for a queue is exceeded. Scheduling becomes strict-priority with CPU queue number determining priority until the shape rate is reached. Packets are dropped after the shape rate is exceeded.

The exit command returns the switch to policy-map configuration mode. Saving the policy-map-class changes also require an exit from policy-map mode, which saves the pending policy-map-class and policy-map changes to running-config and returns the switch to the global configuration mode. The abort command discards pending changes, returning the switch to the global configuration mode.

The no class and default class commands remove the policy-map-class commands for the specified class assignment from the policy map.

Command Mode

Policy-Map (control plane) configuration accessed through policy-map type copp command.

Command Syntax

class class_name

no class class_name

default class class_name

Parameter

class_name name of the class.

Static Classes

Petra platform switches provide the following static control plane classes:
  • copp-system-bpdu copp-system-ipmcmiss copp-system-l3ttl0
  • copp-system-default copp-system-ipmcrsvd copp-system-l3ttl1
  • copp-system-igmp copp-system-ipunicast copp-system-lacp
  • copp-system-ipbroadcast copp-system-l3destmiss copp-system-lldp
  • copp-system-ipmc copp-system-l3slowpath copp-system-unicast-arp

Commands Available in Policy-map-class (control plane) Configuration Mode

Related Commands

policy-map type copp places switch in policy-map (control plane) configuration mode.

Example

These commands enters policy-map-class configuration mode to modify the shape, bandwidth parameters associated with the static class named copp-system-lldp. 
switch(config)# policy-map
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class copp-system-lldp
switch(config-pmap-c-copp-system-policy-copp-system-lldp)#

class (policy-map (control-plane) Trident II)

The class command places the switch in policy-map-class (control plane) configuration mode, which is a group change mode for changing bandwidth and shape parameters associated with a specified class. All changes in a group change mode edit session are pending until the end of the session.

A policy map is an ordered list of classes. The control plane policy map contains 23 static classes. Each class contains an eponymous class map and may contain bandwidth and shape commands.

  • The class map identifies a data stream.

  • bandwidth command defines the streams minimum transmission rate through the control plane.

  • shape command defines the streams maximum transmission rate through the control plane.

Static class maps identify a data stream by definition. Each data packet is managed by commands of the first class whose map matches the packets content. Dynamic classes are not supported for control plane policing on Trident II platform switches.

Each class corresponds to a transmission queue. Queue scheduling is strict-priority; CPU queue number determines priority until the shape rate is reached. Packets are dropped after the shape rate is exceeded.

The exit command returns the switch to the policy-map configuration mode. Saving the policy-map-class changes also require an exit from the policy-map mode, which saves the pending policy-map-class and policy-map changes to running-config and returns the switch to the global configuration mode. The abort command discards pending changes, returning the switch to the global configuration mode.

The no class and default class commands remove the policy-map-class commands for the specified class assignment from the policy map.

Command Mode

Policy-Map (control plane) configuration accessed through policy-map type copp command.

Command Syntax

class class_name

no class class_name

default classclass_name

Parameter

class_name name of the class.

Static Classes

Trident II platform switches provide the following static control plane classes:
  • copp-system-acllog copp-system-igmp copp-system-mlag
  • copp-system-arp copp-system-ipmcmiss copp-system-selfip
  • copp-system-arpresolver copp-system-ipmcrsvd copp-system-selfip-tc6to7
  • copp-system-bfd copp-system-l3destmiss copp-system-sflow
  • copp-system-bgp copp-system-l3slowpath copp-system-tc3to5
  • copp-system-bpdu copp-system-l3ttl1 copp-system-tc6to7
  • copp-system-default copp-system-lacp copp-system-urm
  • copp-system-glean copp-system-lldp

Commands Available in Policy-map-class (control plane) Configuration Mode

Related Commands

policy-map type copp places switch in policy-map (control plane) configuration mode.

Example

These commands enters the policy-map-class configuration mode to modify the shape, bandwidth parameters associated with the static class named copp-system-arp. 
switch(config)# policy-map
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class copp-system-lldp
switch(config-pmap-c-copp-system-policy-copp-system-lldp)#

class (policy-map (control-plane) Trident)

The class command places the switch in policy-map-class (control plane) configuration mode, which is a group change mode for changing bandwidth and shape parameters associated with a specified class. The command adds the specified class to the policy map if it was not previously included. All changes in a group change mode edit session are pending until the end of the session.

A policy map is an ordered list of classes. The control plane policy map contains 18 static classes and up to 30 dynamic classes. Dynamic classes contain an eponymous class map. All classes may contain bandwidth and shape commands.
  • The class map identifies a data stream.

  • bandwidth command defines the streams minimum transmission rate through the control plane.

  • shape command defines the streams maximum transmission rate through the control plane.

Dynamic class maps identify a data stream with an ACL assigned by match (class-map (control-plane) Trident). Static class maps identify a data stream by definition. Each data packet is managed by commands of the first class whose map matches the packets content.

Static classes are provided with the switch and cannot be removed from the policy map or modified by the class command. Dynamic classes are user defined and added to the policy map by this command. Dynamic classes are always placed in front of the static classes. Bandwidth and shape parameters are editable for all classes.

Each class corresponds to a transmission queue. Queue scheduling is round-robin until bandwidth rate for a queue is exceeded. Scheduling becomes strict-priority with CPU queue number determining priority until the shape rate is reached. Packets are dropped after the shape rate is exceeded.

The exit command returns the switch to policy-map configuration mode. Saving the policy-map-class changes also require an exit from policy-map mode, which saves the pending policy-map-class and policy-map changes to running-config and returns the switch to the global configuration mode. The abort command discards pending changes, returning the switch to the global configuration mode.

The no class and default class commands remove the policy-map-class commands for the specified class assignment from the policy map. The class is removed from the policy map if it is a dynamic class.

Command Mode

Policy-Map (control plane) configuration accessed through policy-map type copp command.

Command Syntax

class class_name [PLACEMENT]

no class class_name [PLACEMENT]

default class class_name [PLACEMENT]

Parameters
  • class_name name of the class.
  • PLACEMENT Specifies the classs map placement. Configurable only for dynamic classes.
    • no parameter New classes are placed between the dynamic and static classes. Previously defined classes retain their current policy map placement.
    • insert-before dynamic_class Class is inserted in front of the specified dynamic class.

Static Classes

Trident switches provide the following static control plane classes:
  • copp-system-acllog copp-system-ipmcmiss copp-system-lldp
  • copp-system-arp copp-system-ipmcrsvd copp-system-selfip
  • copp-system-arpresolver copp-system-l3destmiss copp-system-selfip-tc6to7
  • copp-system-bpdu copp-system-l3slowpath copp-system-sflow
  • copp-system-glean copp-system-l3ttl1 copp-system-tc3to5
  • copp-system-igmp copp-system-lacp copp-system-tc6to7

Commands Available in Policy-map-class (control plane) Configuration Mode

Related Commands

Example

These commands add CM-1 class to the copp-system-policy policy map. 
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class CM-1
switch(config-pmap-c-copp-system-policy-CM-1)#

class (policy-map (pbr)

The class (policy-map (pbr) command places the switch in policy-map-class (pbr) configuration mode, which is a group change mode that modifies the specified class of the configuration mode Policy-Based Routing (PBR) policy map. The command adds the class to the policy map if it was not previously included in the policy map. All changes in a group change mode edit session are pending until the mode is exited, and can be canceled by using the abort command.

A PBR policy map is an ordered list of classes. Each class contains an eponymous class map and can contain set commands to specify next hop. Classes without set commands translate to no action being performed on that class of packets.
  • The class map identifies a data stream through ACLs. Class maps are configured in the class-map (pbr) configuration mode.

  • Set commands can be used to specify the next hop for a given class. Set commands are configured in policy-map-class (pbr) configuration mode.

PBR policy maps can also contain one or more raw match statements which filter incoming traffic without using ACLs. Data packets are managed by commands of the first class or raw match statement matching the packets contents.

The exit command returns the switch to the policy-map (pbr) configuration mode. However, saving the policy-map-class changes also requires an exit from policy-map (pbr) configuration mode. This saves all the pending policy map and policy-map-class changes to running-config and returns the switch to the global configuration mode. The abort command discards pending changes, returning the switch to the global configuration mode.

The no class and default class commands remove the class assignment from the configuration mode policy map by deleting the corresponding class configuration from running-config.

Command Mode

Policy-Map (pbr) Configuration accessed through policy-map type pbr.

Command Syntax

[sequence_number] class class_name

no [sequence_number] class class_name

default [sequence_number] class class_name

no [sequence_number]

default [sequence_number]

Parameters
  • sequence_number Sequence number (1 to 4294967295) assigned to the rule. If no number is entered, the number is derived by adding 10 to the number of the policy maps last numbered line. To increase the distance between existing entries, use the resequence command.
  • class_name name of the class.

Commands Available in Policy-map-class (pbr) Configuration Mode
  • set nexthop (policy-map-class pbr) sets next hop for the class.
  • exit saves pending class changes and returns switch to policy-map (pbr) configuration mode.
  • abort discards pending class changes and returns switch to policy-map (pbr) configuration mode.

Related Commands

Example

These commands add the CMAP1 class map to the PMAP1 policy map, then place the switch in policy-map-class configuration mode where the next hops can be assigned to the class. Changes will not take effect until both modes are exited.
switch(config)# policy-map type pbr PMAP1
switch(config-pmap-PMAP1)# class CMAP1
switch(config-pmap-c-PMAP1-CMAP1)#

class (policy-map (qos) FM6000)

The class command places the switch in policy-map-class (qos) configuration mode, which is a group change mode that modifies the specified class of the configuration mode policy map. The command adds the class to the policy map if it was not previously included in the policy map. All changes in a group change mode edit session are pending until the end of the session.

A policy map is an ordered list of classes. Each class contains an eponymous class map and at least one set command:
  • The class map identifies a data stream through an ACL. Class maps are configured in the class-map (qos) configuration mode.

  • Set commands either modify a packets content (CoS or DSCP fields) or assigns it to a traffic class queue. Set commands are configured in the policy-map-class (qos) configuration mode.

    Data packets are managed by commands of the first class whose map matches the packets content.

The exit command returns the switch to the policy-map configuration mode. However, saving policy-map-class changes also require an exit from the policy-map mode. This saves all pending policy map and policy-map-class changes to running-config and returns the switch to the global configuration mode. The abort command discards pending changes, returning the switch to the global configuration mode.

The no class and default class commands remove the class assignment from the configuration mode policy map by deleting the corresponding class configuration from running-config.

Command Mode

Policy-Map (qos) Configuration accessed through policy-map type quality-of-service.

Command Syntax

class class_name [PLACEMENT]

no class class_name [PLACEMENT]

default class class_name [PLACEMENT]

Parameters
  • class_name name of the class.
  • PLACEMENT Specifies the map placement within the list of class maps.
    • no parameter Class is placed at the top of the list.
    • insert-before existing_class Class is inserted in front of the specified class.

Commands Available in Policy-map-class (qos) Configuration Mode
  • set (policy-map-class (qos) FM6000)
  • exit saves pending class changes and returns switch to policy-map (qos) configuration mode.
  • abort discards pending class changes and returns switch to policy-map (qos) configuration mode.

Related Commands

Example

These commands add the CMAP_1 class map to the PMAP_1 policy map, then places the switch in the policy-map-class configuration mode.
switch(config)# policy-map type quality-of-service PMAP-1
switch(config-pmap-PMAP-1)# class CMAP-1
switch(config-pmap-c-PMAP-1-CMAP-1)#

class (policy-map (qos) Helix)

The class command places the switch in the policy-map-class (QoS) configuration mode, which is a group change mode that modifies the specified class of the configuration mode policy map. The command adds the class to the policy map if it was not previously included in the policy map. All changes in a group change mode edit session are pending until the end of the session.

A policy map is an ordered list of classes. Each class contains an eponymous class map and at least one set command:
  • The class map identifies a data stream through an ACL. Class maps are configured in the class-map (qos) configuration mode.

  • Set commands either modify a packets content (CoS or DSCP fields) or assigns it to a traffic class queue. Set commands are configured in the policy-map-class (qos) configuration mode.

    Data packets are managed by commands of the first class whose map matches the packets content.

The exit command returns the switch to the policy-map configuration mode. However, saving policy-map-class changes also require an exit from the policy-map mode. This saves all the pending policy map and policy-map-class changes to running-config and returns the switch to the global configuration mode. The abort command discards pending changes, returning the switch to the global configuration mode.

The no class and default class commands remove the class assignment from the configuration mode policy map by deleting the corresponding class configuration from running-config.

Command Mode

Policy-Map (qos) Configuration accessed through policy-map type quality-of-service command.

Command Syntax

class class_name [PLACEMENT]

no class class_name [PLACEMENT]

default class class_name [PLACEMENT]

Parameters
  • class_name name of the class.
  • PLACEMENT Specifies the map placement within the list of class maps.
    • no parameter Class is placed at the top of the list.
    • insert-before existing_class Class is inserted in front of the specified class.

Commands Available in Policy-map-class (QoS) Configuration Mode
  • set (policy-map-class (qos) Helix)
  • exit saves pending class changes and returns switch to policy-map (qos) configuration mode.
  • abort discards pending class changes and returns switch to policy-map (qos) configuration mode.

Related Commands

Example

These commands add the CMAP_1 class map to the PMAP_1 policy map, then places the switch in policy-map-class configuration mode.
switch(config)# policy-map type quality-of-service PMAP-1
switch(config-pmap-PMAP-1)# class CMAP-1
switch(config-pmap-c-PMAP-1-CMAP-1)#

class (policy-map (qos) Trident II)

The class command places the switch in the policy-map-class (QoS) configuration mode, which is a group change mode that modifies the specified class of the configuration mode policy map. The command adds the class to the policy map if it was not previously included in the policy map. All changes in a group change mode edit session are pending until the end of the session.

A policy map is an ordered list of classes. Each class contains an eponymous class map and at least one set command:
  • The class map identifies a data stream through an ACL. Class maps are configured in class-map (qos) configuration mode.

  • Set commands either modify a packets content (CoS or DSCP fields) or assigns it to a traffic class queue. Set commands are configured in policy-map-class (qos) configuration mode.

Data packets are managed by commands of the first class whose map matches the packets content.

The exit command returns the switch to the policy-map configuration mode. However, saving the policy-map-class changes also require an exit from the policy-map mode. This saves all the pending policy map and policy-map-class changes to running-config and returns the switch to the global configuration mode. The abort command discards pending changes, returning the switch to the global configuration mode.

The no class and default class commands remove the class assignment from the configuration mode policy map by deleting the corresponding class configuration from running-config.

Command Mode

Policy-Map (qos) Configuration accessed through policy-map type quality-of-service command.

Command Syntax

class class_name [PLACEMENT]

no class class_name [PLACEMENT]

default class class_name [PLACEMENT]

Parameters
  • class_name name of the class.
  • PLACEMENT Specifies the map placement within the list of class maps.
    • no parameter Class is placed at the top of the list.
    • insert-before existing_class Class is inserted in front of the specified class.

Commands Available in Policy-map-class (qos) Configuration Mode
  • set (policy-map-class (qos) Trident II)
  • exit saves pending class changes and returns switch to policy-map (qos) configuration mode.
  • abort discards pending class changes and returns switch to policy-map (qos) configuration mode.

Related Commands

Example

These commands add the CMAP_1 class map to the PMAP_1 policy map, then places the switch in policy-map-class configuration mode.
switch(config)# policy-map type quality-of-service PMAP-1
switch(config-pmap-PMAP-1)# class CMAP-1
switch(config-pmap-c-PMAP-1-CMAP-1)#

class (policy-map (qos) Trident)

The class command places the switch in policy-map-class (qos) configuration mode, which is a group change mode that modifies the specified class of the configuration mode policy map. The command adds the class to the policy map if it was not previously included in the policy map. All changes in a group change mode edit session are pending until the end of the session.

A policy map is an ordered list of classes. Each class contains an eponymous class map and at least one set command:
  • The class map identifies a data stream through an ACL. Class maps are configured in class-map (qos) configuration mode.

  • Set commands either modify a packets content (CoS or DSCP fields) or assigns it to a traffic class queue. Set commands are configured in policy-map-class (qos) configuration mode.

    Data packets are managed by commands of the first class whose map matches the packets content.

The exit command returns the switch to policy-map configuration mode. However, saving policy-map-class changes also require an exit from policy-map mode. This saves all the pending policy map and policy-map-class changes to running-config and returns the switch to the global configuration mode. The abort command discards pending changes, returning the switch to the global configuration mode.

The no class and default class commands remove the class assignment from the configuration mode policy map by deleting the corresponding class configuration from running-config.

Command Mode

Policy-Map (qos) Configuration accessed through policy-map type quality-of-service command.

Command Syntax

class class_name [PLACEMENT]

no class class_name [PLACEMENT]

default class class_name [PLACEMENT]

Parameters
  • class_name name of the class.
  • PLACEMENT Specifies the map placement within the list of class maps.
    • no parameter Class is placed at the top of the list.
    • insert-before existing_class Class is inserted in front of the specified class.

Commands Available in Policy-map-class (qos) Configuration Mode
  • set (policy-map-class (qos) Trident)
  • exit saves pending class changes and returns switch to policy-map (qos) configuration mode.
  • abort discards pending class changes and returns switch to policy-map (qos) configuration mode.

Related Commands

Example

These commands add the CMAP_1 class map to the PMAP_1 policy map, then places the switch in policy-map-class configuration mode.
switch(config)# policy-map type quality-of-service PMAP-1
switch(config-pmap-PMAP-1)# class CMAP-1
switch(config-pmap-c-PMAP-1-CMAP-1)#

class-map type copp

The class-map type copp command places the switch in Class-Map (control plane) configuration mode, which is a group change mode that modifies a control-plane dynamic class map. A dynamic class map is a data structure that uses Access Control Lists (ACLs) to define a data stream by specifying characteristics of data packets that comprise that stream. Control-plane policy maps use class maps to specify which control plane traffic is controlled by policy map criteria.

The exit command saves pending class map changes to running-config and returns the switch to the global configuration mode. Class map changes are also saved by entering a different configuration mode. The abort command discards pending changes and returns the switch to the global configuration mode.

The no class-map type copp and default class-map type copp commands delete the specified class map by removing the corresponding class-map type copp command and its associated configuration.

Command Mode

Global Configuration

Command Syntax

class-map type copp match-any class_name

no class-map type copp [match-any] class_name

default class-map type copp [match-any] class_name

Parameter

class_name Name of class map.

Commands Available in Class-Map (Control Plane) Configuration Mode

match (class-map (control-plane) Trident)

Related Commands

Example

This command creates the control plane class map named CP-MAP-1 and places the switch in class-map configuration mode.
switch(config)# class-map type copp match-any CP-CMAP-1
switch(config-cmap-CP-CMAP-1)#

class-map type pbr

The class-map type pbr command places the switch in the class-map (pbr) configuration mode for the specified class map, and creates the class map if one does not already exist. The class-map (PBR) configuration mode is a group change mode that modifies a class map for Policy-Based Routing (PBR). PBR class maps contain one or more match statements which filter incoming traffic using ACLs. PBRs can then use these class maps to set next-hop IP addresses for the traffic that matches them. (Classes without set commands translate to no action being performed on that class of packets.)

The exit command saves pending class map changes to running-config, then returns the switch to the global configuration mode. Class map changes are also saved by directly entering a different configuration mode. The abort command discards pending changes and returns the switch to the global configuration mode.

The no class-map type pbr and default class-map type pbr commands delete the specified class map by removing the corresponding class-map type pbr command and its associated configuration.

Command Mode

Global Configuration

Command Syntax

class-map type pbr match-any map_name

no class-map type pbr match-any map_name

default class-map type pbr match-any map_name

Parameter

map_name Name of class map.

Commands Available in Class-Map (PBR) configuration mode

Related Commands

Example

This command creates the PBR class map named MAP1 and places the switch in class-map (pbr) configuration mode where match criteria can be configured for the class.
switch(config)# class-map type pbrmatch-any MAP1
switch(config-cmap-MAP1)#

class-map type qos

The class-map type qos command places the switch in the class-map (QoS) configuration mode, which is a group change mode that modifies a QoS dynamic class map. A dynamic class map is a data structure that uses Access Control Lists (ACLs) to define a data stream by specifying characteristics of data packets that comprise that stream. QoS policy maps use class maps to specify the traffic (to which the policy map is assigned) that is transformed by policy map criteria.

The exit command saves pending class map changes to running-config, then returns the switch to the global configuration mode. Class map changes are also saved by entering a different configuration mode. The abort command discards pending changes and returns the switch to the global configuration mode.

The no class-map type qos and default class-map type qos commands delete the specified class map by removing the corresponding class-map type qos command and its associated configuration. The class-map and class-map type qos commands are equivalent.

Command Mode

Global Configuration

Command Syntax

class-map [type qos] match-any class_name

no class-map [type qos] match-any class_name

default class-map [type qos] match-any class_name

Parameters

class_name Name of class map.

Commands Available in Class-Map (QoS) Configuration Mode

Conditions

class-map map_name and class-map type qos map_name are identical commands.

Related Commands

Example

This command creates the QoS class map named MAP-1 and places the switch in class-map configuration mode.
switch(config)# class-map type qos match-any MAP-1
switch(config-cmap-MAP-1)#

clear policy-map counters

The clear policy-map command resets the specified policy map counters to zero. Policy map counters record the quantity of packets that are filtered by the ACLs that comprise a specified policy map.

Command Mode

Privileged EXEC

Command Syntax

clear policy-map INTERFACE_NAME counters MAP_NAME

Parameters
  • INTERFACE_NAME Interface for which command clears table counters. Options include:
    • interface control-plane Control plane.
  • MAP_NAME Policy map for which command clears counters. Options include:
    • copp-system-policy Name of only policy map supported for the control plane.

feature pbr

Policy-Based Routing (PBR) is a feature that is applied on IPv4 or IPv6 routable ports, to preferentially route packets. Forwarding is based on a policy that is enforced at the ingress of the applied interface and overrides normal routing decisions. In addition to matches on regular ACLs, PBR policy-maps can also include “raw match” statements that look like a single entry of an ACL as a convenience for users.

Configuration Mode

For IP:

TCAM PBR profile set TTL configuration mode.

For IPv6:

TCAM feature PBR IP configuration mode.

Command Syntax

For IP:

feature pbr ip [copy]

no feature pbr ip [copy]

default featue pbr ip [copy]

For IPv6:

feature pbr ipv6[copy | bank]

no feature pbr ipv6 [copy | bank]

default featue pbr ipv6 [copy | bank]

Parameters

For IP:

copy Copy a feature from a TCAM profile.

For IPv6:

  • copyCopy a feature from a TCAM profile.
  • bankTCAM banks to reserve.

Examples

  • In the following example, the PBR is configured on an IP routable port.

    (config)# hardware tcam
(config-tcam)# profile pbr-set-ttl copy default
(config-tcam-profile-pbr-set-ttl)# feature pbr ip

  • In the following example, the PBR is configured on an IPv6 routable port.

    (config)# hardware tcam
(config-tcam)# profile pbr-set-ttl copy default
(config-tcam-profile-pbr-set-ttl)# feature pbr ip
(config-tcam-feature-pbr-ip)# feature pbr ipv6

feature traffic-policy cpu

The feature traffic-policy cpu command configures the CPU traffic policy features for the IPv4 and IPv6 traffic in user-defined TCAM profile.

The no feature traffic-policy cpu and default feature traffic-policy cpu commands remove the CPU policy configurations from running-config.

Command Mode

Hardware TCAM

Command Syntax

feature traffic-policy cpu [ipv4 | ipv6]

no feature traffic-policy cpu [ipv4 | ipv6]

default feature traffic-policy cpu [ipv4 | ipv6]

Parameters
  • ipv4 CPU traffic policy for IPv4 traffic.
  • ipv6 CPU traffic policy for IPv6 traffic.

Example

These commands places the switch in the hardware TCAM profile mode and configures the CPU traffic policy features for IPv4 traffic in the TCAM profile test.
switch(config)# hardware tcam 
switch(config-hw-tcam)# profile test
switch(config-hw-tcam-profile-test)# feature traffic-policy cpu ipv4

feature traffic-policy port

The feature traffic-policy port command configures the port-related traffic policy features for the IPv4 and IPv6 traffic in user-defined TCAM profile.

The no feature traffic-policy port and default feature traffic-policy port commands remove the CPU policy configurations from running-config.

Command Mode

Hardware TCAM

Command Syntax

feature traffic-policy port [ipv4 | ipv6]

no feature traffic-policy port [ipv4 | ipv6]

default feature traffic-policy port [ipv4 | ipv6]

Parameters
  • ipv4 port traffic policy for IPv4 traffic.
  • ipv6 port traffic policy for IPv6 traffic.

Example

These commands places the switch in the hardware TCAM profile mode and configures the port traffic policy features for IPv4 traffic in the TCAM profile test.
switch(config)# hardware tcam 
switch(config-hw-tcam)# profile test
switch(config-hw-tcam-profile-test)# feature traffic-policy port ipv4

match (class-map (control-plane) Helix)

The match command assigns an ACL to the configuration mode class map. A class map can contain only one ACL. Class maps only use permit rules to filter data; deny rules are ignored. The command accepts IPv4 and IPv4 standard ACLs.

A class map is assigned to a policy map by the class (policy-map (control-plane) Helix) command.

The class map (control plane) configuration mode is a group change mode. Match statements are not saved to running-config until the edit session is completed by exiting the mode.

The no match and default match commands remove the match statement from the configuration mode class map by deleting the corresponding command from running-config.

Command Mode

Class-Map (control plane) configuration accessed through class-map type copp command.

Command Syntax

match ip access-group list_name

no match ip access-group list_name

default match ip access-group list_name

Parameters

list_name name of ACL assigned to class map.

Related Commands
  • class-map type copp places the switch in the class-map configuration mode.
  • exit saves pending class map changes, then returns the switch to the global configuration mode.
  • abort discards pending class map changes, then returns the switch to the global configuration mode.
  • class (policy-map (control-plane) Helix) assigns a class map to a policy map.

Guidelines

Static class maps cannot be modified by this command.

Match statements are saved to running-config only upon exiting class-map (control plane) configuration mode.

Example

These commands add the IP ACL list_1 to the map_1 class map, then saves the command by exiting class-map mode.
switch(config)# class-map type copp map_1
switch(config-cmap-map_1)# match ip access-group list_1
switch(config-cmap-map_1)# exit
switch(config)#

match (class-map (control-plane) Trident II)

The match command assigns an ACL to the configuration mode class map. A class map can contain only one ACL. Class maps only use permit rules to filter data; deny rules are ignored. The command accepts IPv4 and IPv4 standard ACLs.

A class map is assigned to a policy map by the class (policy-map (control-plane) Trident II) command.

The class map (control plane) configuration mode is a group change mode. Match statements are not saved to running-config until the edit session is completed by exiting the mode.

The no match and default match commands remove the match statement from the configuration mode class map by deleting the corresponding command from running-config.

Command Mode

Class-Map (control plane) configuration accessed through class-map type copp command.

Command Syntax

list_name

list_name

list_name

Parameter

list_name name of ACL assigned to class map.

Related Commands
  • class-map type copp places the switch in the class-map configuration mode.
  • exit saves pending class map changes, then returns the switch to the global configuration mode.
  • abort discards pending class map changes, then returns the switch to the global configuration mode.
  • class (policy-map (control-plane) Trident II) assigns a class map to a policy map.

Guidelines

Static class maps cannot be modified by this command.

Match statements are saved to running-config only upon exiting class-map (control plane) configuration mode.

Example

These commands add the IP ACL list_1 to the map_1 class map, then saves the command by exiting class-map mode.
switch(config)# class-map type copp map_1
switch(config-cmap-map_1)# match ip access-group list_1
switch(config-cmap-map_1)# exit
switch(config)#

match (class-map (control-plane) Trident)

The match command assigns an ACL to the configuration mode class map. A class map can contain only one ACL. Class maps only use permit rules to filter data; deny rules are ignored. The command accepts IPv4, IPv6, IPv4 standard, and IPv6 standard ACLs.

A class map is assigned to a policy map by the class (policy-map (control-plane) Trident) command.

Class map (control plane) configuration mode is a group change mode. Match statements are not saved to running-config until the edit session is completed by exiting the mode.

The no match and default match commands remove the match statement from the configuration mode class map by deleting the corresponding command from running-config.

Command Mode

Class-Map (control plane) configuration accessed through class-map type copp command

Command Syntax

match IP_VERSION access-group list_name

no match IP_VERSION access-group list_name

default match IP_VERSION access-group list_name

Parameters
  • IP_VERSION IP version of the specified ACL. Options include:
    • ipv4 IPv4.
    • ipv6 IPv6.

  • list_name name of ACL assigned to class map.

Related Commands
  • class-map type copp places the switch in class-map configuration mode.
  • exit saves pending class map changes, then returns the switch to the global configuration mode.
  • abort discards pending class map changes, then returns the switch to the global configuration mode.
  • class (policy-map (control-plane) Trident) assigns a class map to a policy map.

Guidelines

Static class maps cannot be modified by this command.

Match statements are saved to running-config only upon exiting class-map (control plane) configuration mode.

Example

These commands add the IPv4 ACL names list_1 to the map_1 class map, then saves the command by exiting class-map mode.
switch(config)# class-map type copp map_1
switch(config-cmap-map_1)# match ip access-group list_1
switch(config-cmap-map_1)# exit
switch(config)#

match (class-map (pbr))

The match command assigns ACLs to the configuration mode Policy-Based Routing (PBR) class map. The command accepts IPv4, IPv4 standard, IPv6 and IPv6 standard ACLs.

Class map (pbr) configuration mode is a group change mode. Match statements are not saved to running-config until the edit session is completed by exiting the mode.

The no match and default match commands remove the match statement from the configuration mode class map by deleting the corresponding command from running-config.

Note: PBR ACLs use only permit rules to filter data; if there are deny rules in an ACL used by PBR, the configuration will be reverted.

Command Mode

Class-map (pbr) configuration accessed through class-map type pbr command.

Command Syntax

[sequence_number] match [ip | ipv6] access-group list_name

no [sequence_number] match [ip | ipv6] access-group list_name

default [sequence_number] [ip | ipv6] access-group list_name

no [sequence_number]

default [sequence_number]

Parameters

  • sequence_number Sequence number (1 to 4294967295) assigned to the rule. If no number is entered, the number is derived by adding 10 to the number of the class maps last numbered line. To increase the distance between existing entries, use the resequence command.
  • list_name name of ACL assigned to class map.

Related Commands
  • class-map type pbr places the switch in the class-map configuration mode.
  • exit saves pending class map changes, then returns the switch to the global configuration mode.
  • abort discards pending class map changes, then returns the switch to the global configuration mode.
  • class (policy-map (pbr)) assigns a class map to a policy map.

Example

These commands add the IPv4 ACL named list1 to the map1 class map, then save the change by exiting class-map mode.
switch(config)# class-map type pbr map1
switch(config-cmap-map1)# match ip access-group list1
switch(config-cmap-map1)# exit
switch(config)#

match (class-map (qos) FM6000)

The match command assigns an ACL to the configuration mode class map. A class map can contain only one ACL. Class maps only use permit rules to filter data; deny rules are ignored. The command accepts IPv4 and IPv4 standard ACLs.

The class map (qos) configuration mode is a group change mode. Match statements are not saved to running-config until the edit session is completed by exiting the mode.

The no match and default match commands remove the match statement from the configuration mode class map by deleting the corresponding command from running-config.

Command Mode

Class-map (qos) configuration accessed through class-map type qos command.

Command Syntax

match IP_VERSION access-group list_name

no match IP_VERSION access-group list_name

default match IP_VERSION access-group list_name

Parameters
  • IP_VERSION IP version of the specified ACL. Options include:
    • ipv4 IPv4.
  • list_name name of ACL assigned to class map.

Related Commands
  • class-map type qos places the switch in the class-map configuration mode.
  • exit saves pending class map changes, then returns the switch to the global configuration mode.
  • abort discards pending class map changes, then returns the switch to the global configuration mode.
  • class (policy-map (qos) FM6000) assigns a class map to a policy map.

Example

These commands add the IPv4 ACL named list_1 to the map_1 class map, then saves the command by exiting class-map mode.
switch(config)# class-map type qos map_1
switch(config-cmap-map_1)# match ip access-group list_1
switch(config-cmap-map_1)# exit
switch(config)#

match (class-map (qos) Helix)

The match command assigns an ACL to the configuration mode class map. A class map can contain only one ACL. Class maps only use permit rules to filter data; deny rules are ignored. The command accepts IPv4, IPv4 standard, IPv6, and IPv6 standard ACLs.

the class map (QoS) configuration mode is a group change mode. Match statements are not saved to running-config until the edit session is completed by exiting the mode.

The no match and default match commands remove the match statement from the configuration mode class map by deleting the corresponding command from running-config.

Command Mode

Class-Map (QoS) configuration accessed through class-map type qos command.

Command Syntax

match IP_VERSION access-group list_name

no match IP_VERSION access-group list_name

default match IP_VERSION access-group list_name

Parameters
  • IP_VERSION IP version of the specified ACL. Options include:
    • ipv4 IPv4.
    • ipv6 IPv6.

  • list_name name of ACL assigned to class map.

Related Commands
  • class-map type qos places the switch in the class-map configuration mode.
  • exit saves pending class map changes, then returns the switch to the global configuration mode.
  • abort discards pending class map changes, then returns the switch to the global configuration mode.
  • class (policy-map (qos) Helix) assigns a class map to a policy map.

Example

These commands add the IPv4 ACL named list_1 to the map_1 class map, then saves the command by exiting class-map mode.
switch(config)# class-map type qos map_1
switch(config-cmap-map_1)# match ip access-group list_1
switch(config-cmap-map_1)# exit
switch(config)#

match (class-map (qos) Trident II)

The match command assigns an ACL to the configuration mode class map. A class map can contain only one ACL. Class maps only use permit rules to filter data; deny rules are ignored. The command accepts IPv4, IPv4 standard, IPv6, and IPv6 standard ACLs.

The class map (QoS) configuration mode is a group change mode. Match statements are not saved to running-config until the edit session is completed by exiting the mode.

The no match and default match commands remove the match statement from the configuration mode class map by deleting the corresponding command from running-config.

Command Mode

The class-map (qos) configuration accessed through class-map type qos command.

Command Syntax

IP_VERSION list_name

IP_VERSION list_name

IP_VERSION list_name

Parameters
  • IP_VERSION IP version of the specified ACL. Options include:
    • ipv4 IPv4.
    • ipv6 IPv6.

  • list_name name of ACL assigned to class map.

Related Commands
  • class-map type qos places the switch in the class-map configuration mode.
  • exit saves pending class map changes, then returns the switch to the global configuration mode.
  • abort discards pending class map changes, then returns the switch to the global configuration mode.
  • class (policy-map (qos) Trident) assigns a class map to a policy map.

Example

These commands add the IPv4 ACL named list_1 to the map_1 class map, then saves the command by exiting class-map mode.
switch(config)# class-map type qos map_1
switch(config-cmap-map_1)# match ip access-group list_1
switch(config-cmap-map_1)# exit
switch(config)#

match (class-map (qos) Trident)

The match command assigns an ACL to the configuration mode class map. A class map can contain only one ACL. Class maps only use permit rules to filter data; deny rules are ignored. The command accepts IPv4, IPv4 standard, IPv6, and IPv6 standard ACLs.

Class map (QoS) configuration mode is a group change mode. Match statements are not saved to running-config until the edit session is completed by exiting the mode.

The no match and default match commands remove the match statement from the configuration mode class map by deleting the corresponding command from running-config.

Command Mode

Class-Map (qos) configuration accessed through class-map type qos command.

Command Syntax

match IP_VERSION access-group list_name

no match IP_VERSION access-group list_name

default match IP_VERSION access-group list_name

Parameters
  • IP_VERSION IP version of the specified ACL. Options include:
    • ipv4 IPv4.
    • ipv6 IPv6.

  • list_name name of ACL assigned to class map.

Related Commands
  • class-map type qos places the switch in the class-map configuration mode.
  • exit saves pending class map changes, then returns the switch to the global configuration mode.
  • abort discards pending class map changes, then returns the switch to the global configuration mode.
  • class (policy-map (qos) Trident) assigns a class map to a policy map.

Example

These commands add the IPv4 ACL named list_1 to the map_1 class map, then saves the command by exiting class-map mode.
switch(config)# class-map type qos map_1
switch(config-cmap-map_1)# match ip access-group list_1
switch(config-cmap-map_1)# exit
switch(config)#

match (policy-map (pbr))

The match command creates a policy map clause entry that specifies one filtering condition. When a packet matches the filtering criteria, its next hop is set as specified. When a packets properties do not equal the statement parameters, the packet is evaluated against the next clause or class map in the policy map, as determined by sequence number. If all clauses fail to set a next hop for the packet, the packet is routed according to the FIB.

The no match and default match commands remove the match statement from the configuration mode policy map by deleting the corresponding command from running-config.

Command Mode

Policy-Map (pbr) Configuration accessed through policy-map type pbr command.

Command Syntax

[sequence_number] match ip SOURCE_ADDR DEST_ADDR [set nexthop [recursive] NH-addr_1 [NH-addr_2] ... [NH-addr_n]]

no match ip SOURCE_ADDR DEST_ADDR [set nexthop [recursive] NH-addr_1 [NH-addr_2] ... [NH-addr_n]]

default match match ip SOURCE_ADDR DEST_ADDR [set nexthop [recursive] NH-addr_1 [NH-addr_2] ... [NH-addr_n]]

no SEQ_NUM

default SEQ_NUM

Parameters
  • sequence_number Sequence number assigned to the rule. If no number is entered, the number is derived by adding 10 to the number of the policy maps last numbered line. To increase the distance between existing entries, use the resequence command.
  • SOURCE_ADDR and DEST_ADDR source and destination address filters. Options include:
    • network_addr subnet address (CIDR or address-mask).
    • any packets from or to all addresses are matched.
    • host ip_addr IP address (dotted decimal notation).

      Source and destination subnet addresses support discontiguous masks.

  • recursive enables recursive next hop resolution.
  • NH_addr IP address of next hop. If multiple addresses are entered, they are treated as an ECMP group.

Related Commands

Example

These commands create a match rule in policy map PMAP1 which sets the next hop to 192.168.3.5 for packets received from 172.16.0.0/12 regardless of their destination, then exit the mode to save the changes.
switch(config)# policy-map type pbr PMAP1
switch(config-pmap-PMAP1)# match ip 172.16.0.0/12 any set nexthop 192.163.3.5 
switch(config-pmap-PMAP1)# exit
switch(config)#

platform arad tcam counters feature

The platform arad tcam counters feature command enables incrementing PBR hardware counters corresponding to ACL. If counters for PBR are enabled, then counters for ACL will be automatically disabled in all cases. If counters for ACL are enabled, then counters for PBR will be automatically disabled in all cases.

The no platform arad tcam counters feature command disables PBR/ACL counters selection. The default platform arad tcam counters feature commands resets the default behavior.

Command Mode

Global Configuration

Command Syntax

platform arad tcam counters feature [OPTIONS]

no platform arad tcam counters feature [OPTIONS]

default platform arad tcam counters feature [OPTIONS]

Parameters

OPTIONS Assign the TCAM counters feature. Options include:
  • pbr assign the TCAM counters feature PBR hardware counters.
  • acl assign the TCAM counters feature ACL hardware counters.

Examples
  • This command enables incrementing ACL hardware counters selection.
    switch(config)# platform arad tcam counters feature acl
switch(config)#

  • This command disables incrementing ACL hardware counters selection.
    switch(config)# no platform arad tcam counters feature acl
switch(config)#

policy-map type copp

The policy-map type copp command places the switch in the policy-map (control plane) configuration mode, which is a group change mode that modifies a control-plane policy map. A policy map is a data structure that consists of class maps that identify a specific data stream and specify bandwidth and shaping parameters that controls its transmission. Control plane policy maps are applied to the control plane to manage traffic.

The copp-system-policy policy map is supplied with the switch and is always applied to the control plane. The copp-system-policy is the only valid control plane policy map.

The exit command saves pending policy map changes to running-config and returns the switch to the global configuration mode. Policy map changes are also saved by entering a different configuration mode. The abort command discards pending changes, returning the switch to the global configuration mode.

The no policy-map type copp and default policy-map type copp commands delete the specified policy map by removing the corresponding policy-map type copp command and its associated configuration.

Command Mode

Global Configuration

Command Syntax

policy-map type copp copp-system-policy

no policy-map type copp copp-system-policy

default policy-map type copp copp-system-policy

The copp-system-policy is supplied with the switch and is the only valid control plane policy map.

Commands Available in Policy-Map Configuration Mode

Related Commands

class-map type copp enters the control-plane class-map configuration mode for modifying a control-plane dynamic class map.

Only Helix and Trident platform switches support dynamic classes for control plane policing.

Example

This command places the switch in the policy-map configuration mode to edit the copp-system-policy policy map.
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)#

policy-map type pbr

The policy-map type pbr command places the switch in policy-map (pbr) configuration mode, which is a group change mode that modifies a Policy-Based Routing (PBR) policy map. The command also creates the specified policy map if it does not already exist. A PBR policy map is a data structure that consists of class maps that identify specific packets and the next hops for those packets. Policy maps are applied to Ethernet or port channel interfaces to manage traffic.

The exit command saves pending policy map changes to running-config and returns the switch to the global configuration mode. Policy map changes are also saved by entering a different configuration mode. The abort command discards pending changes, returning the switch to the global configuration mode.

The no policy-map type pbr and default policy-map type pbr commands delete the specified policy map by removing the corresponding policy-map type pbr command and its associated configuration.

Command Mode

Global Configuration

Command Syntax

policy-map type pbr map_name

no policy-map type pbr map_name

default policy-map type pbr map_name

Parameter

map_name Name of policy map.

Commands Available in Policy-Map Configuration Mode

Related Commands

Example

This command creates the PBR policy map named PMAP1 and places the switch in policy-map configuration mode.
switch(config)# policy-map type pbr PMAP1
switch(config-pmap-PMAP1)#

policy-map type quality-of-service

The policy-map type quality-of-service command places the switch in the policy-map (QoS) configuration mode, which is a group change mode that modifies a QoS policy map. A policy map is a data structure that consists of class maps that identify a specific data stream and shaping parameters that controls its transmission. Policy maps are applied to Ethernet or port channel interfaces to manage traffic.

The exit command saves pending policy map changes to running-config and returns the switch to the global configuration mode. Policy map changes are also saved by entering a different configuration mode. The abort command discards pending changes, returning the switch to the global configuration mode.

The no policy-map type quality-of-service and default policy-map type quality-of-service commands delete the specified policy map by removing the corresponding policy-map type quality-of-service command and its associated configuration. The policy-map and policy-map type quality-of-service commands are equivalent.

Command Mode

Global Configuration

Command Syntax

policy-map type quality-of-service map_name

no policy-map type quality-of-service map_name

default policy-map type quality-of-service map_name

Parameter

map_name Name of policy map.

Commands Available in Policy-Map Configuration Mode

Conditions

policy-map map_name and policy-map type quality-of-service map_name are identical commands.

Related Commands

Example

This command creates the QoS policy map named PMAP-1 and places the switch in the policy-map configuration mode.
switch(config)# policy-map PMAP-1
switch(config-pmap-PMAP-1)#

policy-map type quality-of-service policer

The policy-map type quality-of-service policer copy command is used to copy an existing QoS policy map to the policy map policer.

The policy-map type quality-of-service policer drop counter command is used to enable drop counters for the QoS policy map policer.

The no policy-map type quality-of-service policer and default policy-map type quality-of-service policer commands delete the policy map policer by removing the corresponding policy-map type quality-of-service policer command and its associated configuration.

The no policy-map type quality-of-service policer drop counter and default policy-map type quality-of-service policer drop counter commands disable drop counters for the policy map policer.

Command Mode

Global Configuration

Command Syntax

policy-map type quality-of-service policer copy map_name

policy-map type quality-of-service policer drop counter

no policy-map type quality-of-service policer

default policy-map type quality-of-service policer

Parameter

map_name Name of policy map to copy.

Related Commands

Examples

  • This command copies the QoS policy map named PMAP-1 to the policy map policer.
    switch(config)#policy-map type quality-of-service policer copy PMAP-1
switch(config-pmap-PMAP-1)#

  • This command enables drop counters for the QoS policy map policer.
    switch(config)#policy-map type quality-of-service policer drop counter
switch(config)#

resequence (class-map (pbr))

The resequence command assigns sequence numbers to rules in the configuration mode class map. Command parameters specify the number of the first rule and the numeric interval between consecutive rules. Once changed, rule numbers persist unless changed again using the resequence command, but the interval used for numbering new rules reverts to 10 on the exiting class-map (pbr) configuration mode.

Maximum rule sequence number is 4294967295.

Command Mode

Class-Map (PBR) Configuration accessed through class-map type pbr command.

Command Syntax

resequence [start_num [inc_num]]

Parameters
  • start_num sequence number assigned to the first rule. Default is 10.
  • inc_num numeric interval between consecutive rules. Default is 10.

Example

The resequence command renumbers the rules in CMAP1, starting the first command at number 100 and incrementing subsequent lines by 20.
switch(config)# class-map type pbr match-any CMAP1
switch(config-cmap-CMAP1)# show active
class-map type pbr match-any CMAP1
10 match ip access-group group1
20 match ip access-group group2
30 match ip access-group group3
switch(config-cmap-CMAP1)# resequence 100 20
switch(config-cmap-CMAP1)# exit
switch(config)# class-map type pbr match-any CMAP1
switch(config-cmap-CMAP1)# show active
class-map type pbr match-any CMAP1
100 match ip access-group group1
120 match ip access-group group2
140 match ip access-group group3

resequence (policy-map (pbr))

The resequence command assigns sequence numbers to rules in the configuration mode policy map. Command parameters specify the number of the first rule and the numeric interval between consecutive rules. Once changed, rule numbers persist unless changed again using the resequence command, but the interval used for numbering new rules reverts to 10 on the exiting policy-map (pbr) configuration mode.

Maximum rule sequence number is 4294967295.

Command Mode

Policy-Map (PBR) Configuration accessed through policy-map type pbr command

Command Syntax

resequence [start_num [inc_num]]

Parameters
  • start_num sequence number assigned to the first rule. Default is 10.
  • inc_num numeric interval between consecutive rules. Default is 10.

Example

The resequence command renumbers the rules in PMAP1, starting the first command at number 100 and incrementing subsequent lines by 20.
switch(config)# policy-map type pbr PMAP1
switch(config-pmap-PMAP1)# show active
policy-map type pbr PMAP1
10 class CMAP1
set nexthop 172.16.1.1
20 class CMAP2
set nexthop 172.16.2.2
30 class CMAP3
set nexthop 172.16.3.3
switch(config-pmap-PMAP1)# resequence 100 20
switch(config-pmap-PMAP1)# exit
switch(config)# policy-map type pbr PMAP1
switch(config-pmap-PMAP1)# show active
class-map type pbr PMAP1
100 class CMAP1
set nexthop 172.16.1.1
120 class CMAP2
set nexthop 172.16.2.2
140 class CMAP3
set nexthop 172.16.3.3
switch(config-pmap-PMAP1)#

service-policy type pbr (Interface mode)

The service-policy pbr command applies the specified Policy-Based Routing (PBR) policy map to the configuration mode interface. A PBR policy map is a data structure that consists of class maps that identify specific packets and the next hops for those packets. Policy maps are applied to Ethernet or port channel interfaces to manage traffic. Only one service policy is supported per interface.

The no service-policy pbr and default service-policy pbr commands remove the service policy assignment from the configuration mode interface by deleting the corresponding service-policy pbr command from running-config.

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

Interface-VLAN Configuration

Command Syntax

service-policy type pbr TRAFFIC_DIRECTION map_name

no service-policy type pbr TRAFFIC_DIRECTION map_name

default service-policy type pbr TRAFFIC_DIRECTION map_name

Parameters
  • TRAFFIC_DIRECTION IP address or peer group name. Values include:
    • input Policy map applies to inbound packet streams.
  • map_name Name of policy map.

Guidelines

A policy map that is attached to a port channel interface takes precedence for member interfaces of the port channel over their individual interface Ethernet configuration. Members that are removed from a port channel revert to the policy map implementation specified by its interface Ethernet configuration.

Related Commands

policy-map type pbr

Example

This command applies the PBR policy map PMAP1 to interface Ethernet 8.
switch# config
switch(config)# interface ethernet 8
switch(config-if-Et8)# service-policy type pbr input PMAP1
switch(config-if-Et8)#

service-policy type qos (Interface mode)

The service-policy command applies a specified policy map to the configuration mode interface. A policy map is a data structure that identifies data traffic through class maps, then specifies actions to classify the traffic (by setting the traffic class), mark the traffic (by setting the cos and dscp values), and police the traffic (by setting the police rate) through data packet field modifications.

The no service-policy and default service-policy commands remove the service policy assignment from the configuration mode interface by deleting the corresponding service-policy command from running-config.

Command Mode

Interface-Ethernet Configuration

Interface-Port-Channel Configuration

Interface-VLAN Configuration

Command Syntax

service-policy [type qos] TRAFFIC_DIRECTION map_name

no service-policy [type qos] TRAFFIC_DIRECTION map_name

default service-policy [type qos] TRAFFIC_DIRECTION map_name

Parameters
  • type qos Parameter has no functional effect.
  • TRAFFIC_DIRECTION Direction of data stream to which command applies. Options include:
    • input Policy map applies to inbound packet streams.
    • map_name Name of policy map.

Guidelines

A policy map that is attached to a port channel interface takes precedence for member interfaces of the port channel over their individual interface Ethernet configuration. Members that are removed from a port channel revert to the policy map implementation specified by its interface Ethernet configuration.

DCS-7500E and DCS-7280E limitations:

  • A maximum of 31 QoS service policies per chip may be applied on L3 interfaces.
  • Applying different QoS service policies to an SVI and its member interfaces causes unpredictable behavior.
  • When an SVI on which QoS service policies are applied experiences partial failure due to limited hardware resources, a forwarding agent restart causes unpredictable behavior.
  • Policy-map programming may fail when QoS service policies are applied on two SVIs if an event causes a member interface to switch membership from one to the other. To change the VLAN membership of an interface in this case, remove the interface from one VLAN before adding it to the other.
  • Outgoing COS rewrite is not supported.
  • QoS policy-map counters are not supported.

DCS-7010, DCS-7050, DCS-7050X, DCS-7250X, and DCS-7300X limitations:

  • When the same policy map is applied to multiple SVIs, TCAM resources are not shared.
  • A policy map applied to an SVI results in TCAM allocation on all chips whether SVI members are present or not.
  • Applying different QoS service policies to an SVI and its member interfaces causes unpredictable behavior.

Related Commands

policy-map type quality-of-service

Example

This command applies the PMAP-1 policy map to interface ethernet 8.
switch# config
switch(config)# interface ethernet 8
switch(config-if-Et8)# show active
switch(config-if-Et8)# service-policy input PMAP-1
switch(config-if-Et8)# show active
interface Ethernet8
   service-policy type qos input PMAP-1
switch(config-if-Et8)#

set (policy-map-class (qos)FM6000)

The set command specifies traffic resolution methods for traffic defined by its associated class map in its configuration mode policy map class. Three set statements are available for each class:

  • cos Sets the Layer 2 class of service field.

  • dscp Sets the differentiated services code point value in the type of service (ToS) byte.

  • traffic-class Sets the traffic class queue for data packets.

Each type of set command can be assigned to a class, allowing for the simultaneous modification of both (cos, dscp) fields and assignment to a traffic class.

The no set and default set commands remove the specified data action from the class map by deleting the associated set command from running-config.

Command Mode

Policy-map-class (qos) configuration

accessed through class (policy-map (qos) FM6000) command.

Command Syntax

set QOS_TYPE value

no set QOS_TYPE

default set QOS_TYPE

Parameters
  • QOS_TYPE Specifies the data stream resolution method. Valid options include:
    • cos Layer 2 class of service field of outbound packet is modified.
    • dscp Differentiated services code point value in the ToS byte is modified.
    • traffic-class Data stream is assigned to a traffic class queue.

  • value Specifies the data field value or traffic class queue. Valid data range depends on QOS_TYPE.
    • QOS_TYPE is cos Value ranges from 0 to 7.
    • QOS_TYPE is dscp Value ranges from 0 to 63.
    • QOS_TYPE is traffic-class Value ranges from 0 to 7.

Related Commands

Example

These commands configure the policy map to set CoS field 7 to data traffic specified by the class map CMAP-1, then assigns that data to traffic class queue 4.
switch(config)# policy-map type quality-of-service PMAP-1
switch(config-pmap-PMAP-1)# class CMAP-1
switch(config-pmap-c-PMAP-1-CMAP-1)# set cos 7
switch(config-pmap-c-PMAP-1-CMAP-1)# set traffic-class 4
switch(config-pmap-c-PMAP-1-CMAP-1)#

set (policy-map-class (qos)Helix)

The set command specifies traffic resolution methods for traffic defined by its associated class map in its configuration mode policy map class. Three set statements are available for each class:

  • cos Sets the Layer 2 class of service field.

  • dscp Sets the differentiated services code point value in the type of service (ToS) byte.

  • traffic-class Sets the traffic class queue for data packets.

Each type of set command can be assigned to a class, allowing for the simultaneous modification of both (cos, dscp) fields and assignment to a traffic class.

The no set and default set commands remove the specified data action from the class map by deleting the associated set command from running-config.

Command Mode

Policy-map-class (qos) configuration accessed through class (policy-map (qos) Helix) command.

Command Syntax

set QOS_TYPE value

no set QOS_TYPE

default set QOS_TYPE

Parameters
  • QOS_TYPE Specifies the data stream resolution method. Valid options include:
    • cos Layer 2 class of service field of outbound packet is modified.
    • dscp Differentiated services code point value in the ToS byte is modified.
    • traffic-class Data stream is assigned to a traffic class queue.

  • value Specifies the data field value or traffic class queue. Valid data range depends on QOS type.
    • QOS_TYPE is cos Value ranges from 0 to 7.
    • QOS_TYPE is dscp Value ranges from 0 to 63.
    • QOS_TYPE is traffic-class Value ranges from 0 to 7.

Related Commands

Example

These commands configure the policy map to set CoS field 7 to data traffic specified by the class map CMAP-1, then assigns that data to traffic class queue 4.
switch(config)# policy-map type quality-of-service PMAP-1
switch(config-pmap-PMAP-1)# class CMAP-1
switch(config-pmap-c-PMAP-1-CMAP-1)# set cos 7
switch(config-pmap-c-PMAP-1-CMAP-1)# set traffic-class 4
switch(config-pmap-c-PMAP-1-CMAP-1)#

set (policy-map-class (qos)Trident II)

The set command specifies traffic resolution methods for traffic defined by its associated class map in its configuration mode policy map class. Three set statements are available for each class:

  • cos Sets the Layer 2 class of service field.

  • dscp Sets the differentiated services code point value in the type of service (ToS) byte.

  • traffic-class Sets the traffic class queue for data packets.

Each type of set command can be assigned to a class, allowing for the simultaneous modification of both (cos, dscp) fields and assignment to a traffic class.

The no set and default set commands remove the specified data action from the class map by deleting the associated set command from running-config.

Command Mode

Policy-map-class (qos) configuration accessed through class (policy-map (qos) Trident) command.

Command Syntax

set QOS_TYPE value

no set QOS_TYPE

default set QOS_TYPE

Parameters
  • QOS_TYPE Specifies the data stream resolution method. Valid options include:
    • cos Layer 2 class of service field of outbound packet is modified.
    • dscp Differentiated services code point value in the ToS byte is modified.
    • traffic-class Data stream is assigned to a traffic class queue.

  • value Specifies the data field value or traffic class queue. Valid data range depends on QOS type.
    • QOS_TYPE is cos Value ranges from 0 to 7.
    • QOS_TYPE is dscp Value ranges from 0 to 63.
    • QOS_TYPE is traffic-class Value ranges from 0 to 7.

Related Commands

Example

These commands configure the policy map to set CoS field 7 to data traffic specified by the class map CMAP-1, then assigns that data to traffic class queue 4.
switch(config)# policy-map type quality-of-service PMAP-1
switch(config-pmap-PMAP-1)# class CMAP-1
switch(config-pmap-c-PMAP-1-CMAP-1)# set cos 7
switch(config-pmap-c-PMAP-1-CMAP-1)# set traffic-class 4
switch(config-pmap-c-PMAP-1-CMAP-1)#

set (policy-map-class (qos)Trident)

The set command specifies traffic resolution methods for traffic defined by its associated class map in its configuration mode policy map class. Three set statements are available for each class:

  • cos Sets the Layer 2 class of service field.

  • dscp Sets the differentiated services code point value in the type of service (ToS) byte.

  • traffic-class Sets the traffic class queue for data packets.

Each type of set command can be assigned to a class, allowing for the simultaneous modification of both (cos, dscp) fields and assignment to a traffic class.

The no set and default set commands remove the specified data action from the class map by deleting the associated set command from running-config.

Command Mode

Policy-map-class (qos) configuration accessed through class (policy-map (qos) Trident) command.

Command Syntax

set QOS_TYPE value

no set QOS_TYPE

default set QOS_TYPE

Parameters
  • QOS_TYPE Specifies the data stream resolution method. Valid options include:
    • cos Layer 2 class of service field of outbound packet is modified.
    • dscp Differentiated services code point value in the ToS byte is modified.
    • traffic-class Data stream is assigned to a traffic class queue.

  • value Specifies the data field value or traffic class queue. Valid data range depends on QOS type.
    • QOS_TYPE is cos Value ranges from 0 to 7.
    • QOS_TYPE is dscp Value ranges from 0 to 63.
    • QOS_TYPE is traffic-class Value ranges from 0 to 7.

Related Commands

Example

These commands configure the policy map to set CoS field 7 to data traffic specified by the class map CMAP-1, then assigns that data to traffic class queue 4.
switch(config)# policy-map type quality-of-service PMAP-1
switch(config-pmap-PMAP-1)# class CMAP-1
switch(config-pmap-c-PMAP-1-CMAP-1)# set cos 7
switch(config-pmap-c-PMAP-1-CMAP-1)# set traffic-class 4
switch(config-pmap-c-PMAP-1-CMAP-1)#

set nexthop (policy-map-class pbr)

The set nexthop command specifies the next hop for traffic defined by its associated class map in its configuration mode policy map class.

The no set nexthop and default set nexthop commands remove the specified action from the class map by deleting the associated set nexthop command from running-config.

Command Mode

Policy-map-class (pbr) configuration accessed through class (policy-map (pbr)) command.

Command Syntax

set nexthop [recursive] NH-addr_1 [NH-addr_2] ... [NH-addr_n]

no set nexthop [recursive]

default set nexthop [recursive]

Parameters
  • recursive enables recursive next hop resolution.
  • NH_addr IP address of next hop. If multiple addresses are entered, they are treated as an ECMP group.

Related Commands

Example

These 192.168.5.3 commands configure the policy map PMAP1 to set the next hop to for traffic defined by class map CMAP1.
switch(config)# policy-map type pbr PMAP1
switch(config-pmap-PMAP1)# class CMAP1
switch(config-pmap-c-PMAP1-CMAP1)# set nexthop 192.168.5.3
switch(config-pmap-c-PMAP1-CMAP1)#

set nexthop-group (policy-map-class(pbr) Arad)

The set nexthop-group command specifies a nexthop group as the next hop for traffic defined by its associated class map in its configuration mode policy map class.

The no set nexthop-group and default set nexthop-group commands remove the specified action from the class map by deleting the associated set nexthop-group command from running-config.

Command Mode

Policy-map-class (pbr) configuration accessed through class (policy-map (pbr)) command.

Command Syntax

set nexthop-group group_name

no set nexthop-group group_name

default set nexthop-group group_name

Parameters

group_name name of ECMP group to use as next hop.

Related Commands

Example

These commands configure the policy map PMAP1 to set the next hop to a nexthop group named GROUP1 for traffic defined by class map CMAP1.
switch(config)# policy-map type pbr PMAP1
switch(config-pmap-PMAP1)# class CMAP1
switch(config-pmap-c-PMAP1-CMAP1)# set nexthop-group GROUP1
switch(config-pmap-c-PMAP1-CMAP1)#

shape (policy-map-class (control-plane)Arad)

The shape command specifies the maximum bandwidth for traffic filtered by the configuration mode policy map class.

The no shape and default shape commands remove the maximum bandwidth restriction for the configuration mode class by deleting the corresponding bandwidth command from running-config.

Command Mode

Policy-map-class (control plane) configuration accessed through class (policy-map (control-plane) Arad)

Command Syntax

Parameter

kilobits Maximum data rate in kilobits per second. Value ranges from 1 to 10000000.

Related Commands

Static Classes Default Shape

Arad platform switches define these default shapes for static classes:
  • copp-system-bgp 2500 copp-system-l3lpmoverflow 2500
  • copp-system-bpdu 2500 copp-system-l3slowpath 2500
  • copp-system-default 2500 copp-system-l3ttl1 2500
  • copp-system-ipbroadcast 2500 copp-system-lacp 2500
  • copp-system-ipmc 2500 copp-system-linklocal 2500
  • copp-system-ipmcmiss 2500 copp-system-lldp 2500
  • copp-system-ipunicast NO LIMIT copp-system-mlag 2500
  • copp-system-l2broadcast 2500 copp-system-multicastsnoop 2500
  • copp-system-l2unicast NO LIMIT copp-system-OspfIsis 2500
  • copp-system-l3destmiss 2500 copp-system-sflow 2500

Example

These commands configure the maximum bandwidth of 2000 kbps for data traffic specified by the class map copp-system-lldp of the default control-plane policy map.
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class copp-system-lldp
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# shape kbps 2000
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# exit
switch(config-pmap-copp-system-policy)# exit
switch(config)# show policy-map copp copp-system-policy
Service-policy input: copp-system-policy

  Class-map: copp-system-lldp (match-any)
       shape : 2000 kbps
       bandwidth : 250 kbps
      Out Packets : 0
      Drop Packets : 0

switch(config)#

shape (policy-map-class (control-plane)FM6000)

The shape command specifies the maximum bandwidth for traffic filtered by the configuration mode policy map class.

The no shape and default shape commands remove the maximum bandwidth restriction for the configuration mode class by deleting the corresponding bandwidth command from running-config.

Command Mode

Policy-map-class (control plane) configuration accessed through class (policy-map (control-plane) FM6000).

Command Syntax

shape pps packets

no shape

default shape

Parameters

packets Maximum data rate in packets per second. Value ranges from 1 to 100000.

Related Commands

Static Classes Default Shape

FM6000 platform switches define these default shapes for static classes:
  • copp-system-arp 10000 copp-system-l3slowpath 10000
  • copp-system-default 8000 copp-system-pim-ptp 10000
  • copp-system-ipmcrsvd 10000 copp-system-ospf-isis 10000
  • copp-system-ipmcmiss 10000 copp-system-selfip 5000
  • copp-system-igmp 10000 copp-system-selfip-tc6to7 5000
  • copp-system-l2rsvd 10000 copp-system-sflow 25000

Example

These commands configure a maximum bandwidth of 5000 packets per second for data traffic specified by the class map PMAP-1 in the policy map named copp-system-policy.
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class PMAP-1
switch(config-pmap-c-copp-system-policy-PMAP-1)# shape pps 5000
switch(config-pmap-c-copp-system-policy-PMAP-1)#

shape (policy-map-class (control-plane)Helix)

The shape command specifies the maximum bandwidth for traffic filtered by the configuration mode policy map class.

The no shape and default shape commands remove the maximum bandwidth restriction for the configuration mode class by deleting the corresponding bandwidth command from running-config.

Command Mode

Policy-map-class (control plane) configuration accessed through class (policy-map (control-plane) Helix).

Command Syntax

shape pps packets

no shape

default shape

Parameters

packets Maximum data rate in packets per second. Value ranges from 1 to 100000.

Static Classes Default Shape

Trident platform switches define these default shapes for static classes:
  • copp-system-acllog 10000 copp-system-l3ttl1 10000
  • copp-system-arp 10000 copp-system-lacp 5000
  • copp-system-arpresolver 10000 copp-system-lldp 10000
  • copp-system-bfd 10000 copp-system-mlag 5000
  • copp-system-bgp 5000 copp-system-OspfIsis 10000
  • copp-system-bpdu 5000 copp-system-selfip 5000
  • copp-system-default 8000 copp-system-selfip-tc6to7 5000
  • copp-system-glean 10000 copp-system-sflow 25024
  • copp-system-igmp 10000 copp-system-tc3to5 10000
  • copp-system-ipmcmiss 10000 copp-system-tc6to7 10000
  • copp-system-ipmcrsvd 10000 copp-system-urm 10000
  • copp-system-l3destmiss 10000 copp-system-vrrp 5000
  • copp-system-l3slowpath 10000

Related Commands

Example

These commands configure a maximum bandwidth of 5000 packets per second for data traffic specified by the copp-system-lldp of the default control-plane policy map.
switch(config)# policy-map type control-plan copp-system-policy
switch(config-pmap-copp-system-policy)# class copp-system-lldp
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# shape pps 5000
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# exit
switch(config-pmap-copp-system-policy)# exit
switch(config)# show policy-map copp copp-system-policy
Service-policy input: copp-system-policy

  Class-map: copp-system-lldp (match-any)
       shape : 5000 pps
       bandwidth : 500 pps
      Out Packets : 305961
      Drop Packets : 0

switch(config)#

shape (policy-map-class (control-plane)Petra)

The shape command specifies the maximum bandwidth for traffic filtered by the configuration mode policy map class.

The no shape and default shape commands remove the maximum bandwidth restriction for the configuration mode class by deleting the corresponding bandwidth command from running-config.

Command Mode

Policy-map-class (control plane) configuration accessed through class (policy-map (control-plane) Petra)

Command Syntax

shape kbps kilobits

no shape

default shape

Parameter

kilobits Maximum data rate in kilobits per second. Value ranges from 1 to 10000000.

Related Commands

Static Classes Default Shape

Petra platform switches define these default shapes for static classes:
  • copp-system-bpdu 2500 copp-system-l3destmiss 2500
  • copp-system-default 2500 copp-system-l3slowpath 2500
  • copp-system-igmp 2500 copp-system-l3ttl0 2500
  • copp-system-ipbroadcast 2500 copp-system-l3ttl1 2500
  • copp-system-ipmc 2500 copp-system-lacp 2500
  • copp-system-ipmcmiss 2500 copp-system-lldp 2500
  • copp-system-ipmcrsvd 2500 copp-system-unicast-arp 2500
  • copp-system-ipunicast No Limit

Guidelines

Petra does not support all discrete rate values. When a specified discrete value is not supported, the switch converts the rate to the next highest discrete value that it supports. The show command displays the converted rate and not the user-configured rate.

Example

These commands configure the maximum bandwidth of 2000 kbps for data traffic specified by the class map copp-system-lldp of the default control-plane policy map. Because the switch does not support the discrete value of 2000 kbps, it converts the bandwidth up to 2115 kbps.
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class copp-system-lldp
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# shape kbps 2000
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# exit
switch(config-pmap-copp-system-policy)# exit
switch(config)# show policy-map copp copp-system-policy
Service-policy input: copp-system-policy

  Class-map: copp-system-lldp (match-any)
       shape : 2115 kbps
       bandwidth : 325 kbps
      Out Packets : 0
      Drop Packets : 0

switch(config)#

shape (policy-map-class (control-plane)Trident II)

The shape command specifies the maximum bandwidth for traffic filtered by the configuration mode policy map class.

The no shape and default shape commands remove the maximum bandwidth restriction for the configuration mode class by deleting the corresponding bandwidth command from running-config.

Command Mode

Policy-map-class (control plane) configuration accessed through class (policy-map (control-plane) Trident II).

Command Syntax

shape pps packets

no shape

default shape

Parameter

packets Maximum data rate in packets per second. Value ranges from 1 to 100000.

Static Classes Default Shape

Trident II platform switches define these default shapes for static classes:
  • copp-system-acllog 10000 copp-system-l3slowpath 10000
  • copp-system-arp 10000 copp-system-l3ttl1 10000
  • copp-system-arpresolver 10000 copp-system-lacp 5000
  • copp-system-bfd 10000 copp-system-lldp 10000
  • copp-system-bgp 5000 copp-system-mlag 5000
  • copp-system-bpdu 5000 copp-system-selfip 5000
  • copp-system-default 8000 copp-system-selfip-tc6to7 5000
  • copp-system-glean 10000 copp-system-sflow 25024
  • copp-system-igmp 10000 copp-system-tc3to5 10000
  • copp-system-ipmcmiss 10000 copp-system-tc6to7 10000
  • copp-system-ipmcrsvd 10000 copp-system-urm 10000

Related Commands

Example

These commands configure a maximum bandwidth of 5000 packets per second for data traffic specified by the copp-system-lldp of the default control-plane policy map.
switch(config)# policy-map type control-plan copp-system-policy
switch(config-pmap-copp-system-policy)# class copp-system-lldp
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# shape pps 5000
switch(config-pmap-c-copp-system-policy-copp-system-lldp)# exit
switch(config-pmap-copp-system-policy)# exit
switch(config)# show policy-map copp copp-system-policy
Service-policy input: copp-system-policy

  Class-map: copp-system-lldp (match-any)
       shape : 5000 pps
       bandwidth : 500 pps
      Out Packets : 305961
      Drop Packets : 0

switch(config)#

shape (policy-map-class (control-plane)Trident)

The shape command specifies the maximum bandwidth for traffic filtered by the configuration mode policy map class.

The no shape and default shape commands remove the maximum bandwidth restriction for the configuration mode class by deleting the corresponding bandwidth command from running-config.

Command Mode

Policy-map-class (control plane) configuration accessed through class (policy-map (control-plane) Trident).

Command Syntax

shape pps packets

no shape

default shape

Parameters

packets Maximum data rate in packets per second. Value ranges from 1 to 100000.

Static Classes Default Shape

Trident platform switches define these default shapes for static classes:
  • copp-system-arp 10000 copp-system-lldp 10000
  • copp-system-arpresolver 10000 copp-system-l3destmiss 10000
  • copp-system-bpdu 5000 copp-system-l3slowpath 10000
  • copp-system-default 8000 copp-system-l3ttl1 10000
  • copp-system-glean 10000 copp-system-selfip 5000
  • copp-system-igmp 10000 copp-system-selfip-tc6to7 5000
  • copp-system-ipmcmiss 10000 copp-system-sflow 25000
  • copp-system-ipmcrsvd 10000 copp-system-tc3to5 10000
  • copp-system-lacp 5000 copp-system-tc6to7 10000

Related Commands

Example

These commands configure a maximum bandwidth of 5000 packets per second for data traffic specified by the class map PMAP-1 in the policy map named copp-system-policy.
switch(config)# policy-map type copp copp-system-policy
switch(config-pmap-copp-system-policy)# class PMAP-1
switch(config-pmap-c-copp-system-policy-PMAP-1)# shape pps 5000
switch(config-pmap-c-copp-system-policy-PMAP-1)

show class-map type control-plane

The show class-map command displays contents of available control-plane class maps. Control-plane class maps can be added to the copp-system-policy policy map. Control-plane class maps can be static class maps defined by the system or dynamic maps created in class-map configuration mode.

Dynamic class maps are composed of statements that match IPv4 access control lists. Static class maps are defined by the switch and cannot be altered.

Command Mode

EXEC

Command Syntax

show class-map type control-plane [MAP_NAME]

Parameters

MAP_NAME Name of class map displayed by the command. Options include:
  • no parameter Command displays all control plane class maps.
  • name_text Command displays specified control-plane class maps.

Related Command

Example

This command displays the available control plane class maps.
switch# show class-map type control-plane
  Class-map: CM-CP1 (match-any)
    Match: ip access-group name LIST-CP1
  Class-map: copp-system-acllog (match-any)
  Class-map: copp-system-arp (match-any)
  Class-map: copp-system-arpresolver (match-any)
  Class-map: copp-system-bpdu (match-any)
  Class-map: copp-system-glean (match-any)
  Class-map: copp-system-igmp (match-any)
  Class-map: copp-system-ipmcmiss (match-any)
  Class-map: copp-system-ipmcrsvd (match-any)
  Class-map: copp-system-l3destmiss (match-any)
  Class-map: copp-system-l3slowpath (match-any)
  Class-map: copp-system-l3ttl1 (match-any)
  Class-map: copp-system-lacp (match-any)
  Class-map: copp-system-lldp (match-any)
  Class-map: copp-system-selfip (match-any)
  Class-map: copp-system-selfip-tc6to7 (match-any)
  Class-map: copp-system-sflow (match-any)
  Class-map: copp-system-tc3to5 (match-any)
  Class-map: copp-system-tc6to7 (match-any)
switch>

show class-map type pbr

The show class-map command displays contents of all available Policy-Based Routing (PBR) class maps, or of a specified PBR class map. PBR class maps are used by PBR policy maps. PBR class maps are dynamic maps that are created in class-map-configuration mode. Dynamic class maps are composed of statements that match IPv4 or IPv6 access control lists.

Command Mode

EXEC

Command Syntax

show class-map type pbr [map_name]

Parameters

map_name Name of class map displayed by the command. If no parameter is entered, command show all available PBR class maps.

Related Command

show policy-map type pbr displays PBR policy maps.

Example

This command displays the contents of the PBR class map CMAP1.
switch# show class-map type pbr CMAP1
  Class-map: CMAP1 (match-any)
    Match: 10 ip access-group PBRgroup1
    Match: 20 ip access-group PBRgroup2
    Match: 30 ip access-group PBRgroup3
switch>

show class-map type qos

The show class-mapcommand displays contents of all available QoS class maps. QoS class maps are used by QoS policy maps. QoS class maps are dynamic maps that are created in class-map configuration mode. Dynamic class maps are composed of statements that match IPv4 or IPv6 access control lists.

Command Mode

EXEC

Command Syntax

show class-map [type qos][MAP_NAME]

Parameters

MAP_NAME Name of class map displayed by the command.
  • no parameter Command displays all QoS class maps.
  • name_text Command displays specified QoS class maps.

show class-map and show class-map type qos are identical commands.

Related Command

show class-map type control-plane displays control plane class maps.

Example

This command displays the available QoS class maps.
switch# show class-map type qos
  Class-map: CM-Q1 (match-any)
    Match: ipv6 access-group name LIST-1
  Class-map: CM-Q2 (match-any)
    Match: ip access-group name LIST-2
switch>

show policy-map copp

The show policy-map copp command displays contents of the control-plane policy map. Control-plane policy maps are applied to the control plane, and copp-system-policy is the only supported policy map.

Command Mode

EXEC

Command Syntax

show policy-map copp copp-system-policy

Example

This command displays the contents and throughput of the policy map applied to the control plane.
switch# show policy-map copp copp-system-policy
Service-policy input: copp-system-policy
  Number of units programmed: 1
  Hardware programming status: Successful

  Class-map: copp-system-bpdu (match-any)
       shape : 5000 pps
       bandwidth : 5000 pps
      Out Packets : 2
      Drop Packets : 0

  Class-map: copp-system-lacp (match-any)
       shape : 5000 pps
       bandwidth : 5000 pps
      Out Packets : 0
      Drop Packets : 0

switch>

show policy-map interface type qos counters

The show policy-map interface command displays the quantity of packets that are filtered by ACLs applied to a interface.

Command Mode

EXEC

Command Syntax

show policy-map [INTERFACE_NAME][type qos][TRAFFIC] counters

Parameters
  • INTERFACE_NAME Filters policy map list by interfaces. Options include:
    • no parameter Displays data for all configured interfaces.
    • interface ethernet e_range Ethernet ports for which command displays policy maps.
    • interface port-channel p_range Port channels for which command displays policy maps.

  • TRAFFIC Filters policy maps by the traffic they manage. Options include:
    • no parameter Policy maps that manage interfaces ingress traffic (same as input option).
    • input Policy maps that manage interfaces ingress traffic.

Example

This command displays the policy maps applied to interfaces Ethernet 7 and 8.
switch# show policy-map interface ethernet 7-8
Service-policy input: PMAP-1
  Hardware programming status: Successful

  Class-map: cmap-1 (match-any)
    Match: ip access-group name LIST-2
       set cos 6

  Class-map: class-default (match-any)

Service-policy input: PMAP-2
  Hardware programming status: Successful

  Class-map: cmap-2 (match-any)
    Match: ip access-group name LIST-2
       set dscp 10

  Class-map: class-default (match-any)

switch#

show policy-map interface type qos

The show policy-map interface command displays contents of the policy maps applied to specified interfaces or to the control plane.

Command Mode

EXEC

Command Syntax

show policy-map interface INTERFACE_NAME [type qos] [TRAFFIC]

Parameters
  • INTERFACE_NAME Filters policy map list by interfaces. Options include:
    • ethernet e_range Ethernet ports for which command displays policy maps.
    • port-channel p_range Port channels for which command displays policy maps.

  • TRAFFIC Filters policy maps by the traffic they manage. Options include:
    • no parameter Policy maps that manage interfaces ingress traffic (same as input option).
    • input Policy maps that manage interfaces ingress traffic.

Example

This command displays the policy maps applied to interfaces Ethernet 7 and 8.
switch# show policy-map interface ethernet 7-8
Service-policy input: PMAP-1
  Hardware programming status: Successful

  Class-map: cmap-1 (match-any)
    Match: ip access-group name LIST-2
       set cos 6

  Class-map: class-default (match-any)

Service-policy input: PMAP-2
  Hardware programming status: Successful

  Class-map: cmap-2 (match-any)
    Match: ip access-group name LIST-2
       set dscp 10

  Class-map: class-default (match-any)

switch#

show policy-map type copp

The show policy-map type copp command displays contents of control plane policy maps. Control-plane policy maps are applied to the control plane; copp-system-policy is the only supported policy map.

Command options filter the output to display contents of all policy maps, contents of a specified policy map, or contents of a single class map within a specified policy map.

Command Mode

EXEC

Command Syntax

show policy-map type copp copp-system-policy [CMAP_NAME]

Parameters

CMAP_NAME Name of class map displayed by the command.
  • no parameter Command displays all class maps in specified policy map.
  • class_name Command displays specified class map.

Example

This command displays the contents of the copp-system-bpdu class map in the copp-system-policy policy maps.
switch# show policy-map type copp copp-system-policy class copp-system-bpdu
  Class-map: copp-system-bpdu (match-any)
       shape : 5000 pps
       bandwidth : 5000 pps

switch>

show policy-map type pbr

The show policy-map pbr command displays contents of Policy-Based Routing (PBR) policy maps. PBR policy maps are applied to Ethernet interfaces, port channel interfaces or switch virtual interfaces (SVIs).

Command options filter the output to either display contents of all policy maps, contents of a specified policy map, or summary contents of all or a specified policy map.

Command Mode

EXEC

Command Syntax

show policy-map type pbr [PMAP_NAME][DATA_LEVEL]

Parameters
  • PMAP_NAME Name of policy map displayed by the command.
    • no parameter Command displays all policy maps.
    • policy_map Command displays specified policy map.

  • DATA_LEVEL Type of information the command displays. Values include:
    • no parameter Command displays all class maps in specified policy map.
    • summary Command displays summary data for the specified policy map.

Example

This command displays the contents of all PBR policy maps in running-config.
switch# show policy-map type pbr
Service policy PMAP1
Configured on:
Applied on:
10: Class-map: CMAP1 (match-any)
Match: 10 ip access-group PBRgroup1
Match: 20 ip access-group PBRgroup2
Match: 30 ip access-group PBRgroup3
Configured actions: set nexthop 172.16.10.12
20: Class-map: CMAP2 (match-any)
Match: 10 ip access-group PBRgroup1
Match: 10 ip access-group PBRgroup4
Match: 20 ip access-group PBRgroup5
Configured actions: set nexthop 192.168.15.15
switch#

show policy-map type qos counters

The show policy-map counters command displays the quantity of packets that are filtered by the ACLs that comprise a specified QoS policy map.

Command Mode

EXEC

Command Syntax

show policy-map [type qos] pmap_name [TRAFFIC] counters [INFO_LEVEL]

Parameters
  • pmap_name Name of policy map displayed by the command.
  • TRAFFIC Filters policy maps by the traffic they manage. Options include:
    • no parameter Policy maps that manage interfaces ingress traffic (same as input option).
    • input Policy maps that manage interfaces ingress traffic.

  • INFO_LEVEL amount of information that is displayed. Options include:
    • no parameter displays summarized information about the policy map.
    • detail displays detailed policy map information.

show policy-map type qos

The show policy-map qos command displays contents of QoS policy maps. QoS policy maps are applied to Ethernet or port channel interfaces.

Command options filter the output to either display contents of all policy maps, contents of a specified policy map, or contents of a single class map within a specified policy map.

Command Mode

EXEC

Command Syntax

show policy-map [type qos][PMAP_NAME [CMAP_NAME]]

Parameters
  • PMAP_NAME Name of policy map displayed by the command.
    • no parameter Command displays all policy maps.
    • policy_map Command displays specified policy map.

  • CMAP_NAME Name of class map displayed by the command. This option is available only when the command includes a policy map name.
    • no parameter Command displays all class maps in specified policy map.
    • class_name Command displays specified class map.

Example

This command displays the contents of all QoS policy maps in running-config.
switch# show policy-map type qos
Service-policy input: PMAP-1
  Hardware programming status: Successful

  Class-map: xeter (match-any)
    Match: ip access-group name LIST-1
       set cos 6

  Class-map: class-default (match-any)

Service-policy PMAP-2

  Class-map: class-default (match-any)

switch#

show traffic-policy

The show traffic-policy command displays traffic policy information on the interface.

Command Mode

EXEC

Command Syntax

show traffic-policy NAME interface

show traffic-policy interface [DETAILS]

Parameters

DETAILS   Details requested. Options include:
  • summary   Display summary information about the policy.
    • errors Display all configured remote grantees, associated profile name and latest update.
    • details Display all interfaces on which the policy has been configured.

Examples
  • This command displays the summary information configured on the switch interfaces.
    switch(config-traffic-policies)# show traffic-policy interface summary
Traffic policy samplePolicy
   Configured on interfaces: Ethernet1/1, Ethernet2/1, Ethernet3/1, ...
   Applied on interfaces for IPv4 traffic: Ethernet1/1, Ethernet2/1, Ethernet3/1, ...
   Applied on interfaces for IPv6 traffic:
   Total number of rules configured: 3
      match SIMPLE ipv4
      match ipv4-all-default ipv4
      match ipv6-all-default ipv6

  • This command displays information about the traffic policy named samplePolicy.
    switch(config-traffic-policies)# show traffic-policy samplePolicy interface
Traffic policy samplePolicy
   Configured on interfaces: Ethernet1/1, Ethernet2/1, Ethernet3/1, ...
   Applied on interfaces for IPv4 traffic: Ethernet1/1, Ethernet2/1, Ethernet3/1, ...
   Applied on interfaces for IPv6 traffic:
   Total number of rules configured: 3
      match SIMPLE ipv4
         Source prefix: 192.0.2.0/24
                        198.51.100.0/24
         Destination prefix: 203.0.113.0/24
         Protocol: tcp
            Source port: 50-100
                         110-200
         Actions: Drop
      match ipv4-all-default ipv4
      match ipv6-all-default ipv6

  • This command displays all interfaces on which samplePolicy has been configured.
    switch(config-traffic-policies)# show traffic-policy interface detail
Traffic policy samplePolicy
   Configured on interfaces: Ethernet1/1, Ethernet2/1, Ethernet3/1, Ethernet4/1
   Applied on interfaces for IPv4 traffic: Ethernet1/1, Ethernet2/1, Ethernet3/1, Ethernet4/1
   Applied on interfaces for IPv6 traffic:
   Total number of rules configured: 3
      match SIMPLE ipv4
         Source prefix: 192.0.2.0/24
                        198.51.100.0/24
         Destination prefix: 203.0.113.0/24
         Protocol: tcp
            Source port: 50-100
                         110-200
         Actions: Drop
      match ipv4-all-default ipv4
      match ipv6-all-default ipv6

  • This command displays installation errors for a match statement. The example has no errors.
    switch(config-traffic-policies)# show traffic-policy interface errors
Traffic policy samplePolicy
   Failed on interface for IPv4 traffic:
   Failed on interface for IPv6 traffic: