Quality of Service and Traffic Management
This chapter describes Arista’s Quality of Service (QoS) implementation and Traffic Management, including configuration instructions and command descriptions. Topics covered by this chapter include:
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 Configuration: Platform-Independent Features
- QoS Configuration: Arad Platform Switches
- QoS Configuration: Jericho Platform Switches
- QoS Configuration: FM6000 Platform Switches
- QoS Configuration: Petra Platform Switches
- QoS Configuration: Trident and Tomahawk Platform Switches
- QoS Configuration: Trident II and Helix Platform Switches
- Support for Configuring Color Extended Communities
- ACL based QoS Configuration
- Configuring IPv6 Flow Label Matches for QoS
- Differentiated MMU Discard Counters
- txQueue Percentage-based Shaping
- Configuring Round Robin Scheduling on Shaped Subinterfaces
- Explicit Congestion Notification (ECN)
- Latency-based Explicit Congestion Notification
- Configuring a Low Latency Transmit Queue Scheduler Profile
- Quality of Service Configuration Commands
- Chipset Mapping for QoS
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:
- Traffic Class Derivations – Arad Platform Switches
- Traffic Class Derivations – Jericho Platform Switches
- Traffic Class Derivations – FM6000 Platform Switches
- Traffic Class Derivations – Petra Platform Switches
- Traffic Class Derivations – Trident and Tomahawk Platform Switches
- Traffic Class Derivations – Trident II and Helix Platform Switches
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:
- Transmit Queues and Port Shaping – Arad Platform Switches
- Transmit Queues and Port Shaping – Jericho Platform Switches
- Transmit Queues and Port Shaping – FM6000 Platform Switches
- Transmit Queues and Port Shaping – Petra Platform Switches
- Transmit Queues and Port Shaping – Trident and Tomahawk Platform
- Transmit Queues and Port Shaping – Trident II and Helix Platform Switches
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.
|
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:
- Create a policy map.
- Create a class-map.
- 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.
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.
| 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.
| 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.
| 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.
|
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.
| 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.
- To configure a port’s shape rate, enter shape rate (Interface – Arad/Jericho) from the port’s interface configuration mode.
- To configure a transmit queue’s shape rate, enter shape rate (Tx-queue – Arad/Jericho) from the queue’s tx-queue configuration mode.
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
- Traffic Class Derivations – Jericho Platform Switches
- CoS Rewrite – Jericho Platform Switches
- Transmit Queues and Port Shaping – Jericho Platform Switches
- ACL Policing – Jericho Platform Switches
Note: QoS traffic policy is supported on Trident and Tomahawk, Trident II, FM6000, Arad, and Jericho.
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.
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.
| 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.
| 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.
| 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.
|
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.
| 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.
- To configure a port’s shape rate, enter shape rate (Interface – Arad/Jericho) from the port’s interface configuration mode.
- To configure a transmit queue’s shape rate, enter shape rate (Tx-queue – Arad/Jericho) from the queue’s tx-queue configuration mode.
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.
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.
| 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.
| 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.
| 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.
|
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.
| 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.
| 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.
- To configure a port’s shape rate, enter shape rate (Interface – FM6000) from the port’s interface configuration mode.
- To configure a transmit queue’s shape rate, enter shape rate (Tx-queue – FM6000) from the queue’s tx-queue configuration mode.
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 Classdescribes 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
- To configure a port’s shape rate, enter shape rate (Interface – Petra) from the port’s interface configuration mode.
- To configure a transmit queue’s shape rate, enter shape rate (Tx-queue – Petra) from the queue’s tx-queue configuration mode.
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
- Traffic Class Derivations – Trident and Tomahawk Platform Switches
- CoS and DSCP Rewrite – Trident and Tomahawk Platform Switches
- Transmit Queues and Port Shaping – Trident and Tomahawk Platform Switches
- ECN Configuration – Trident and Tomahawk Platform Switches
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.
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.
| 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.
| 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.
| 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.
| 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.
|
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.
| 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:
- qos map traffic-class to uc-tx-queue associates a unicast queue to a traffic class set.
- qos map traffic-class to mc-tx-queue associates a multicast queue to a traffic class set.
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.
- To configure a port’s shape rate, enter shape rate (Interface – Trident and Tomahawk) from the port’s interface configuration mode.
- To configure a transmit queue’s shape rate, enter shape rate (Tx-queue – Trident and Tomahawk) from the queue’s tx-queue configuration mode.
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
- Traffic Class Derivations – Trident II and Helix Platform Switches
- CoS and DSCP Rewrite – Trident II and Helix Platform Switches
- Transmit Queues and Port Shaping – Trident II and Helix Platform Switches
- Ingress Policing on LAG
- Fabric QoS -- – Trident II Platform Switches
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.
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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
- To configure a port’s shape rate, enter shape rate (Interface – Trident II) from the port’s interface configuration mode.
- To configure a transmit queue’s shape rate, enter shape rate (Tx-queue – Trident II) from the queue’s tx-queue configuration mode.
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.
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 |
|
| 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 |
|
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:
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.
- 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 - 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 - 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 - Add drop-precedence action to the policy-map
switch(config-pmap-c-quality-of-service-policy1-class1)# set drop-precedence 2 - Create qos profile with the policy map assigned
switch(config)# qos profile qos1 switch(config-qos-profile-qos1)# service-policy input policy1 - 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
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.
Configuring Latency-based ECN
Latency-based ECN can configured on a per transmit queue basis. Use the following commands to configure a transmit queue on interface Ethernet 1/1 with a delay threshold of 33 milliseconds:
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
Configure a delay threshold as a value between 1 to 4294967 microseconds or a value between 1 to 4294 milliseconds.
Displaying the ECN Configuration
Use the following command to display information about the ECN configuration:
switch(config)# show qos interfaces Ethernet 1/1 ecn
Ethernet1/1:
ECN ECN ECN ECN ECN
Minimum Maximum Delay Mark-Prob Weight
Tx-Queue Threshold Unit Threshold Threshold Threshold
-------- -------------- --------- --------- ------------------------- --------- ------
7 - - - - - / - -
6 - - - - - / - -
5 - - - - - / - -
4 - - - - - / - -
3 - - - 33000.000 / 33000.000 (L) - / - -
2 - - - - - / - -
1 - - - - - / - -
0 - - - - - / - -
Delay Threshold Type: G -> Global L -> Local
Note: Values are displayed as Configured/Operational
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
Configuring a Low Latency Transmit Queue Scheduler Profile
Configuring a low latency transmit queue scheduler profile provides an alternative operating mode for queues with reduced latency. By default, the switch has a balanced profile focused on maintaining sustained throughput and avoiding excessive latency. In certain scenarios, this profile may not provide an optimal configuration for latency-sensitive scenarios with critical flow completion time. In this case, configure a responsive low latency scheduler profile validated against the hardware capabilities.
The responsive profile provides maximum benefits in scenarios with low fan-in and bursty flows and reduces the maximum latency from 40 microseconds to 8 microseconds when a flow starts or stops.
Compatible Platforms
The following platforms support the responsive profile feature:
- DCS-7280R3
- DCS-7500R3
- DCS-7800R3
Configuring the Responsive Profile
Enable unified credit rates to allow the scheduler profile to provide credits to the low latency queues at rates optimized for hardware. Use the following command to enable unified credit rates:
switch(config)# platform fap voq credit rates unified
Then configure the responsive profile on a transmit queue with the following command:
switch(config)# qos tx-queue 0-7 scheduler profile responsive
Configure up to eight (8) responsive profiles.
Quality of Service Commands
QoS Data Field and Traffic Class Configuration Commands
- color
- hardware access-list qos resource sharing vlan in
- ip extcommunity-list
- platform petraA traffic-class
- qos cos
- qos dscp
- qos map cos
- qos map dscp
- qos map dscp to traffic-class
- qos map dscp to traffic-class (MPLS tunnel termination VRF)
- qos map traffic-class to cos
- qos map traffic-class to dscp
- qos map traffic-class to mc-tx-queue
- qos map traffic-class to tx-queue
- qos map traffic-class to uc-tx-queue
- qos profile
- qos rewrite cos
- qos rewrite dscp
- qos trust
- service-policy type qos input
- service-profile
- set extcommunity
QoS and ECN Display Commands
- show interface counters queue drop-precedence
- show platform petraA traffic-class
- show platform trident tcam shared vlan interface-class-id
- show platform trident tcam qos detail
- show platform xp qos tcam hit
- show policy-map
- show policy-map interface
- show qos interfaces
- show qos interfaces latency maximum
- show qos interfaces trust
- show qos interfaces random-detect ecn
- show qos maps
- show qos map dscp to traffic-class
- show qos profile
- show run|grep sharing
- show qos profile summary
- show qos random-detect ecn
ECN Configuration Commands
- qos random-detect ecn allow non-ect chip-based (Tomahawk and Trident)
- qos random-detect ecn global-buffer (Helix)
- qos random-detect ecn global-buffer (Trident and Tomahawk)
- random-detect ecn (Arad/Jericho)
- random-detect ecn (Helix)
- random-detect ecn (Trident and Tomahawk)
- random-detect ecn delay threshold
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 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 anydscp to traffic-class (DSCP 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 6hardware 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 ininterface 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 anymc-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.
| 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
- qos cos specifies the default CoS.
- platform petraA traffic-class specifies the default traffic class.
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.
| 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 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.
| 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.
| 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.
| 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
- qos map traffic-class to uc-tx-queue (Trident and Tomahawk) associates traffic classes to a multicast transmit queue.
- qos map traffic-class to tx-queue (all other platforms) associates traffic classes to a transmit queue.
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.
| 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
- qos map traffic-class to mc-tx-queue (Trident and Tomahawk) associates traffic classes to a unicast transmit queue.
- qos map traffic-class to uc-tx-queue (Trident and Tomahawk) associates traffic classes to a multicast transmit queue.
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.
| 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
- qos map traffic-class to mc-tx-queue (Trident and Tomahawk) associates traffic classes to a unicast transmit queue.
- qos map traffic-class to tx-queue (all other platforms) associates traffic classes to a transmit queue.
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-basedqos 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
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.
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.
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.
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 | MAX]| maximum-threshold [MIN | 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 | MAX] maximum-threshold [MIN | 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
- tx-queue (Helix) places the switch in tx-queue configuration mode.
- qos random-detect ecn global-buffer (Helix) enables ECN marking for globally shared packet memory.
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 |MAX] maximum-threshold[MIN | 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
- uc-tx-queue places the switch in the uc-tx-queue configuration mode.
- qos random-detect ecn global-buffer (Trident and Tomahawk) enables ECN marking for globally shared packet memory.
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 millisecondsservice-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 TPset 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 anyshape 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 theshape 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
- tx-queue (FM6000) places the switch in tx-queue configuration mode.
- shape rate (Interface – FM6000) configures the shape rate for a configuration mode interface.
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
- tx-queue (Helix) places the switch in tx-queue configuration mode.
- shape rate (Interface – Helix) configures the shape rate for a configuration mode interface.
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_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.
- 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
- tx-queue (Petra) places the switch in tx-queue configuration mode.
- shape rate (Interface – Petra) configures the shape rate for a configuration mode interface.
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
- mc-tx-queue places the switch in mc-tx-queue configuration mode.
- uc-tx-queue places the switch in uc-tx-queue configuration mode.
- shape rate (Interface – Trident and Tomahawk) configures the shape rate for a configuration mode interface.
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
- tx-queue (Trident II) places the switch in tx-queue configuration mode.
- shape rate (Interface – Trident II) configures the shape rate for a configuration mode interface.
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_NAME Name 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 =-=
0x000000000000000001FFFFFEshow 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 2show 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 12show 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.
Example
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 millisecondsshow 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
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: Et56show 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
| 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 |
Configuring the PTP Delay Mechanism
To set the delay mechanism used in boundary-mode, use the ptp delay-mechanism command.
Example
This command sets the delay mechanism in boundary clock mode for
the interface to
peer-to-peer.
switch(config-if-Et5)# ptp delay-mechanism p2p
switch(config-if-Et5)#Setting the Delay Request Interval
To set the time for the slave devices to send delay request messages, use the ptp delay-req interval command.
Example
This command sets the time the slave devices to send delay request messages to
the master state to 3 for the
interface.
switch(config-if-Et5)# ptp delay-request interval 3
switch(config-if-Et5)#Setting the Interval for Sending Synchronization Messages
To set the interval (in log seconds) for sending synchronization messages, use the ptp sync-message interval command. Value ranges and defaults vary based on the PTP mode of the switch.
Example
This command configures the interval for sending synchronization messages on the interface to
3 (8
seconds).
switch(config-if-Et5)# ptp sync-message interval 3
switch(config-if-Et5)#Setting the PTP Transport Type
To set the PTP transport type, use the ptp
transport command.
- This command configures the PTP transport type for the interface to IPv4.
switch(config-if-Et5)# ptp transport ipv4 switch(config-if-Et5)# - This command configures the PTP transport type for the interface to IPv6.
switch(config-if)# ptp transport ipv6 switch(config-if)#
Setting the Local Priority of the Clock and Interfaces
To set the local priority of the clock and
interfaces to control the topology, use the ptp local-priority
command.
switch(config)# ptp local-priority 1
switch(config-if)# ptp local-priority 255Setting up as a Slave to another PTP Device
Each interface may be configured with a candidate grantor IP address to send requests and potentially become the slave device to another PTP device. After configuration, the switch starts negotiating with the candidate grantor, and depending on the Announce messages received, it may start requesting Sync and Delay Response to sync the clock. Each grantor may be associated with a unicast negotiation profile. If the configuration omits the profile, the device uses the default interval of one second and a duration of 60 seconds for all message types. If the profile does not exist, the switch uses the default values until the profile gets added.
Use the ptp unicast-negotiation
candidate-grantor command to set up the profile. The following commands
set up the candidate grantor
profile.
switch(config-if)# ptp unicast-negotiation candidate-grantor 10.0.0.1
switch(config-if)# ptp unicast-negotiation candidate-grantor 10.0.0.1 profile fastProfileSetting up as a Master to another PTP Device
Each interface may be configured with a range of IP addresses of remote grantees to grant incoming requests and potentially become a master to another PTP device. By default, the interface denies incoming requests outside the configured range of IP addresses. Each grantee may be associated with a unicast negotiation profile. If the configuration omits the profile, the interface grants incoming requests with an interval of 0 or longer for all message types. If you specify a profile, it compares it to the configured interval. If the profile does not exist, the switch uses the default values until you add the profile.
Use the ptp unicast-negotiation
remote-grantee command to set up the profile. The following commands set
up the remote grantee
profile.
switch(config-if)# ptp unicast-negotiation remote-grantee 10.0.0.1/24
switch(config-if)# ptp unicast-negotiation remote-grantee 10.0.0.1/24 profile fastProfileSetting the masterOnly Flag
For ports that should not be a slave regardless
of other attributes, use the ptp role master command.
switch(config-if)# ptp role masterConfiguring the Unicast Profile
A Unicast negotiation profile may be configured to change message rates and durations. The following tables displays the default value and the configurable range of each value.
| Field | Range | Default |
|---|---|---|
| Announce interval | [-3, 0] | 0 |
| Announce duration | [60, 1000] | 60 |
| Sync interval | [-7, 0] | 0 |
| Sync duration | [60, 1000] | 60 |
| Delay Response interval | [-7, 0] | 0 |
| Delay Response duration | [60, 1000] | 60 |
When you apply a profile to a remote grantee on a Grant port, it uses the profile values to determine if the given request should be granted or denied. If the requested interval is shorter than the profile, the port denies the request. When a profile applies to a candidate grantor on a Request port, it will be requested to the candidate grantor using the values in the profile.
The following configures a typical Unicast
negotiation
profile.
switch(config)# ptp unicast-negotiation profile fastProfile
switch(config-unicast-negotiation-profile-fastProfile)# announce interval -2
switch(config-unicast-negotiation-profile-fastProfile)# announce duration 500
switch(config-unicast-negotiation-profile-fastProfile)# sync interval -3
switch(config-unicast-negotiation-profile-fastProfile)# sync duration 300
switch(config-unicast-negotiation-profile-fastProfile)# delay-resp interval -3
switch(config-unicast-negotiation-profile-fastProfile)# delay-resp duration 300Displaying Unicast Negotiation Configurations
The show ptp unicast-negotiation
profile command displays all user configured profiles and their
values.
(switch)# show ptp unicast-negotiation profile
Unicast Negotiation Profile fastProfile
Announce interval: 0.25 seconds
Announce duration: 500 seconds
Sync interval: 0.125 seconds
Sync duration: 300 seconds
Delay Response interval: 0.125 seconds
Delay Response duration: 300 secondsThe show ptp unicast-negotiation
candidate-grantor command displays all configured candidate grantors,
associated profile name and latest
update.
(switch)# show ptp unicast-negotiation candidate-grantor
Interface Address Profile Grantor Status
----------- ---------- -------------- ------------------
Ethernet1 4::1 fastProfile Master
Ethernet1 4::2 fastProfile Candidate Master
Ethernet2 4::2 fastProfile BlacklistedThe show ptp unicast-negotiation
remote-grantee command displays all configured remote grantees, associated
profile name and latest
update.
(switch)# show ptp unicast-negotiation remote-grantee
Interface Address Profile
------------ ---------- -------------
Ethernet1 4::1/96 fastProfile
Ethernet1 4::2/96 fastProfile
Ethernet2 4::2/96 fastProfileThe show ptp unicast-negotiation
granted command displays to which remote grantees each port has granted
and some
detail.
(switch)# show ptp unicast-negotiation granted
Interface Address Message Interval Duration Expires In
----------- ---------- ------------ -------------- -------------- -------------
Ethernet2 4::1 Announce 0.25 seconds 300 seconds 30 seconds
Ethernet2 4::1 Sync 2.0 seconds 300 seconds 30 secondsThe show ptp unicast-negotiation
requested command displays to which candidate grantors each port has
requested and some
detail.
(switch)# show ptp unicast-negotiation requested
Interface Address Message Interval Duration Expires In
------------ --------- ----------- --------------- -------------- -------------
Ethernet2 4::2 Announce 0.25 seconds 600 seconds 250 seconds
Ethernet2 4::2 Sync 2.0 seconds 300 seconds deniedThe show ptp
local-clock command displays the clock local priority in G8275.2
mode.
(switch)# show ptp local-clock
PTP Mode: Boundary Clock
Clock Identity: 0x00:1c:73:ff:ff:00:72:40
Clock Domain: 44
Number of PTP ports: 64
Priority1: 128
Priority2: 128
Local Priority: 128
Clock Quality:
Class: 248
Accuracy: 0x30
OffsetScaledLogVariance: 0xffff
Offset From Master: -5
Mean Path Delay: 416 nanoseconds
Steps Removed: 1
Skew: 1.00000006399
Last Sync Time: 23:42:33 UTC Nov 01 2018
Current PTP System Time: 23:42:33 UTC Nov 01 2018The show ptp interface command displays the interface local priority in G8275.2 mode.
Note: The Announce, Sync and Delay request message
intervals are for multicast mode. Since G8275.2 operates in unicast mode, those values
should be ignored.
(switch)# show ptp interface Ethernet 42 | nz Interface Ethernet42
PTP: Enabled
Port state: Slave
Sync interval: 1.0 seconds
Announce interval: 2.0 seconds
Announce interval timeout multiplier: 3
Delay mechanism: end to end
Delay request message interval: 0.25 seconds
Local Priority: 128
Transport mode: ipv4
Announce messages received: 2964
Sync messages received: 2558
Follow up messages received: 2558
Delay request messages sent: 2540
Delay response messages received: 2540
Signaling messages sent: 98
Signaling messages received: 101Viewing PTP Settings and Status
The following commands display the status of the switch PTP server connections:
- Displaying General PTP Information
- Displaying PTP Local Clock and Offset
- Displaying PTP Masters Information
- Displaying PTP Clock Properties
- Displaying PTP Information for all Interfaces
- Displaying PTP Interface Counters
- Displaying PTP Foreign Master
- Displaying PTP Monitoring Information
- Displaying PTP Source IP
Displaying General PTP Information
To display general Precision Time Protocol (PTP) information, use the show ptp command.
switch# show ptp
PTP Mode: gptp - Generalized PTP Clock
Clock Identity: 2001:0DB8:73:ff:ff:26:fd:90
Grandmaster Clock Identity: 2001:0DB8:96:ff:fe:6c:ed:02
Number of slave ports: 1
Number of master ports: 6
Slave port: Ethernet33
Mean Path Delay (nanoseconds): 718
Steps Removed: 1
Neighbor Rate Ratio: 1.00000007883
Rate Ratio: 1.00000007883
Interface State ASTime Since LastNeighbor Mean Path Residence
Capable Changed Rate Ratio Delay (ns) Time (ms)
--------- -------- ------- ------------------ ----------- ----------- ---------
Et1 Disabled No Never 1.0 00
Et2 Disabled No Never 1.0 00
Et3 Disabled No Never 1.0 00
Et4 Disabled No Never 1.0 00
Et5 Disabled No Never 1.0 00
Et6 Disabled No Never 1.0 00
Et7 Master Yes 0:21:08 1.000000094200Displaying PTP Clock Properties
To display PTP clock properties, use the Displaying PTP Clock Properties command.
switch# show local-clock time-properties
Current UTC offset valid: False
Current UTC offset: 0
Leap 59: False
Leap 61: False
Time Traceable: False
Frequency Traceable: False
PTP Timescale: False
Time Source: 0x0
switch#Displaying PTP Foreign Master
To display information about foreign masters (PTP sources not designated as the switch's master from which the switch has received sync packets), use the show ptp foreign-master-record command.
switch# show ptp foreign-master-record
No Foreign Master Records
switch#Displaying PTP Information for all Interfaces
To display PTP information for specified interfaces, use the show ptp interface command.
switch# show ptp interface
Interface Ethernet1
PTP: Disabled
Port state: Disabled
Sync interval: 1.0 seconds
Announce interval: 2.0 seconds
Announce interval timeout multiplier: 3
Delay mechanism: end to end
Delay request message interval: 32.0 seconds
Transport mode: ipv4
Interface Ethernet5
PTP: Disabled
Port state: Disabled
Sync interval: 8.0 seconds
Announce interval: 2.0 seconds
Announce interval timeout multiplier: 5
Delay mechanism: peer to peer
Peer delay request message interval: 8.0 seconds
Peer Mean Path Delay: 0
Transport mode: ipv4Displaying PTP Interface Counters
To display PTP interface counters for specified interfaces, use the show ptp interface counters command.
switch# show ptp interface ethernet 5 counters
Interface Ethernet5
Announce messages sent: 0
Announce messages received: 0
Sync messages sent: 0
Sync messages received: 0
Follow up messages sent: 0
Follow up messages received: 0
Delay request messages sent: 0
Delay request messages received: 0
Delay response messages sent: 0
Delay response messages received: 0
Peer delay request messages sent: 0
Peer delay request messages received: 0
Peer delay response messages sent: 0
Peer delay response messages received: 0
Peer delay response follow up messages sent: 0
Peer delay response follow up messages received: 0Displaying PTP Local Clock and Offset
To display the local PTP clock and offset, use the show ptp local-clock command.
switch# show ptp local-clock
PTP Mode: Boundary Clock
Clock Identity: 0x00:1c:73:ff:ff:1e:83:24
Clock Domain: 1
Number of PTP ports: 24
Priority1: 128
Priority2: 128
Clock Quality:
Class: 248
Accuracy: 0x30
OffsetScaledLogVariance: 0xffff
Offset From Master: 0
Mean Path Delay: 0
Steps Removed: 0Displaying PTP Masters Information
To display the PTP clocks master and grandmaster identity and configuration, use the show ptp masters command.
switch# show ptp masters
Parent Clock:
Parent Clock Identity: 0x00:1c:73:ff:ff:00:72:40
Parent Port Number: 0
Parent IP Address: N/A
Observed Parent Offset (log variance): N/A
Observed Parent Clock Phase Change Rate: N/A
Grandmaster Clock:
Grandmaster Clock Identity: 0x00:1c:73:ff:ff:00:72:40
Grandmaster Clock Quality:
Class: 248
Accuracy: 0x30
OffsetScaledLogVariance: 0xffff
Priority1: 128
Priority2: 128Displaying PTP Monitoring Information
To display the list of up to 100 recorded entries of offset from master, mean path delay and skew values, the current PTP mode, whether or not the feature is enabled, the number of entries displayed, and the configured thresholds for each metric, use the show ptp monitor command. Entries are sorted by the system time at which the value was calculated, starting with the most recent data at the top.
switch# show ptp monitor
PTP Mode: Boundary Clock
Ptp monitoring: enabled
Number of entries: 5
Offset from master threshold: 1500
Mean path delay threshold: not configured
Skew threshold: 0.5
Interface Time Offset from Mean Path Skew
Master (ns) Delay (ns)
---------- ----------------------------- ------------ ------------- -----------
Et8 21:23:12.901 UTC Feb 22 2018 71 5849 1.003159918
Et1 21:23:12.901 UTC Feb 22 2018 113 3672 1.004990621
Et2 21:23:12.901 UTC Feb 22 2018 706 7799 1.002744199
Et1 21:23:12.901 UTC Feb 22 2018 803 5861 1.003432049
Et1 21:23:12.901 UTC Feb 22 2018 610 3415 0.998974658Displaying PTP Source IP
To display PTP IP source information, use the show ptp source ip command.
switch# show ptp source ip
PTP source IP: 10.0.2.1Precision Time Protocol (PTP) Commands
PTP Commands
- ptp announce interval
- ptp announce timeout
- ptp delay-mechanism
- ptp delay-req interval
- ptp domain
- ptp enable
- ptp forward-v1
- ptp hold-ptp-time
- ptp local-priority
- ptp mode
- ptp monitor
- ptp monitor threshold mean-path-delay
- ptp monitor threshold offset-from-master
- ptp monitor threshold skew
- ptp pdelay-neighbor-threshold
- ptp pdelay-req interval
- ptp priority1
- ptp priority2
- ptp role
- ptp source
- ptp sync timeout
- ptp sync-message interval
- ptp transport
- ptp ttl
- ptp unicast-negotiation
ptp announce interval
The ptp announce interval command configures the interval at which the configuration mode interface sends PTP announce messages. The no ptp announce interval command resets the announce interval to its default of 1 (2 seconds).
Command Mode
Interface-Ethernet Configuration
Interface-Port Channel Configuration
Command Syntax
ptp announce interval log_interval
no ptp announce interval
default ptp announce interval
Parameters
log_interval The number of log seconds between PTP announce messages (base 2 log (seconds)). Value ranges from -3 (1/8 second) to 4 (16 seconds); default value is 1 (2 seconds).
Examples
- These commands set the interval between PTP announce messages sent by
interface ethernet 5 to
4
seconds.
switch(config)# interface ethernet 5 switch(config-if-Et5)# ptp announce interval 2 switch(config-if-Et5)# - These commands reset the PTP announce interval on
interface ethernet 5 to the default value
of 1 (2
seconds).
switch(config)# interface ethernet 5 switch(config-if-Et5)# no ptp announce interval switch(config-if-Et5)#
ptp announce timeout
The ptp announce timeout sets the timeout multiplier for the configuration-mode interface. The timeout multiplier is the number of announcement intervals that the interface will wait without receiving a PTP announce message before a timeout occurs; the range is from 2 to 255. The default multiplier is 3, which results in a 6-second timeout interval when the announce interval is set to the default of 2 seconds. To configure the announce interval, use the ptp announce interval command.
Command Mode
Interface-Ethernet Configuration
Interface-Port Channel Configuration
Command Syntax
ptp announce timeout multiplier
no ptp announce timeout
default ptp announce timeout
Parameter
multiplier Number of announce intervals after which the interface will time out if it does not receive a PTP announce message. The range is from 2 to 255; default value is 3.
Examples
- This command sets the timeout multiplier for interface ethernet
5 to 5. This means that the
interface will time out if it doesnt receive a PTP announce message
within five announce
intervals.
switch(config)# interface ethernet 5 switch(config-if-Et5)# ptp announce timeout 5 switch(config-if-Et5)# - These commands reset the PTP timeout interval on interface
ethernet 5 to the default value of
3.
switch(config)# interface ethernet 5 switch(config-if-Et5)# no ptp announce timeout switch(config-if-Et5)#
ptp delay-mechanism
The ptp delay-mechanism command configures the delay mechanism in boundary clock mode. The no ptp delay-mechanism command disables the feature.
Command Mode
Interface-Ethernet Configuration
Interface-Port Channel Configuration
Command Syntax
ptp delay-mechanism mech_type
no ptp delay-mechanism
default ptp delay-mechanism
Parameters
mech_type The delay mechanism. Options include the
following:
- e2e end-to-end delay mechanism.
- p2p peer-to-peer mechanism.
Examples
- This command sets the delay mechanism to peer-to-peer in the boundary clock
mode.
switch(config)# interface ethernet 5 switch(config-if-Et5)# ptp delay-mechanism p2p switch(config-if-Et5)# - This command sets the delay mechanism to end-to-end in the boundary clock
mode.
switch(config)# interface ethernet 5 switch(config-if-Et5)# ptp delay-mechanism e2e switch(config-if-Et5)# - This command removes the delay mechanism configuration from
Ethernet
5.
switch(config)# interface ethernet 5 switch(config-if-Et5)# no ptp delay-mechanism e2e switch(config-if-Et5)#
ptp delay-req interval
The ptp delay-req interval command specifies the time in log seconds recommended to the slave devices to send delay request messages. You must enable PTP on the switch first and configure the source IP address for PTP communication. The no ptp delay-req interval command resets the interval to its default of 5 (32 seconds).
Command Mode
Interface-Ethernet Configuration
Interface-Port Channel Configuration
Command Syntax
ptp delay-req interval log_interval
no ptp delay-req interval
default ptp delay-req interval
Parameter
log_interval The range is -1 to 8 log seconds (base 2 log (seconds)). The default is 5 (32 seconds).
Examples
- These commands set the minimum interval allowed between PTP delay request
messages on interface ethernet 5 to
3 (8
seconds).
switch(config)# interface ethernet 5 switch(config-if-Et5)# ptp delay-request interval 3 switch(config-if-Et5)# - These commands reset the minimum interval allowed between PTP delay-request
messages to the default of 5
(32
seconds).
switch(config)# interface ethernet 5 switch(config-if-Et5)# no ptp delay-request interval switch(config-if-Et5)#
ptp domain
The ptp domain command sets the domain number to use for the clock. The no ptp domain command resets or restores the domain to the default number 0.
Command Mode
Global Configuration
Command Syntax
ptp domain domain_number
no ptp domain
default ptp domain
Parameter
domain_number Value ranges from 0 to 255. Default number is 0.
Examples
- This command shows how to configure domain 1 for
use with a
clock.
switch(config)# ptp domain 1 switch(config)# - This command removes the configured domain 1 for
use with a
clock.
switch(config)# no ptp domain 1 switch(config)#
ptp enable
The ptp enable command enables PTP on the interface. The no ptp enable command disables PTP on the interface.
Command Mode
Interface-Ethernet Configuration
Interface-Port Channel Configuration
Command Syntax
ptp enable
no ptp enable
default ptp enable
Examples
- This command enables PTP on interface ethernet
5.
switch(config)# interface ethernet 5 switch(config-if-Et5)# ptp enable - This command disables PTP on Ethernet interface
5.
switch(config)# interface ethernet 5 switch(config-if-Et5)# no ptp enable
ptp forward-v1
The ptp forward-v1 command configures the switch to forward Precision Time Protocol version 1 packets as regular multicast traffic. By default, PTP v1 packets are trapped by the CPU, logged and discarded.
The no ptp forward-v1 and default ptp forward-v1 commands restore the default forwarding behavior by removing the corresponding ptp forward-v1 command from running-config.
Command Mode
Global Configuration
Command Syntax
ptp forward-v1
no ptp forward-v1
default ptp forward-v1
Examples
- This command configures the switch to forward PTP v1 packets as regular
multicast
traffic.
switch(config)# ptp forward-v1 switch(config)# - This command configures the switch to log and discard PTP v1
packets.
switch(config)# no ptp forward-v1 switch(config)#
ptp hold-ptp-time
The ptp hold-ptp-time command configures the PTP offset hold time in seconds. The no ptp hold-ptp-time command resets or restores the PTP hold time to the default value.
Command Mode
Global Configuration
Command Syntax
ptp hold-ptp-time offset
no ptp hold-ptp-time
default ptp hold-ptp-time
Parameter
offset Value ranges from 0 to 86400.
Examples
- This command shows how to configure the PTP offset hold
time.
switch(config)# ptp hold-ptp-time 600 switch(config)# - This command resets or restores the PTP offset hold time to the default
value.
switch(config)# no ptp hold-ptp-time switch(config)#
ptp local-priority
The ptp local-priority command configures the local priority of the clock and interfaces to control the topology.
Command Mode
Interface-Ethernet Configuration
Command Syntax
ptp local-priority PRIORITY_NUM
Parameter
PRIORITY_NUM The priority number from 1 to 255.
Example
This command sets the priority for the
subinterface.
switch(config)# ptp local-priority 1
switch(config-if)# ptp local-priority 255ptp mode
The ptp mode command configures the Precision Time Protocol (PTP) packet forwarding mode for the switch. By default, PTP is disabled globally; the mode must be changed to use PTP on switch interfaces.
The no ptp mode and default ptp mode commands return the forwarding mode to disabled by removing the ptp mode command from running-config.
Command Mode
Global Configuration
Command Syntax
ptp mode mode_name
no ptp mode
default ptp mode
Parameters
mode_name Default mode is
disabled. Options include:
- boundary The device acts as a boundary clock, and
both runs and participates in the best master clock algorithm.
- disabled The default mode. PTP is disabled, and the device forwards all PTP packets as normal traffic.
- e2etransparent The device acts as an end-to-end transparent clock, synchronizing all ports to a connected master clock and updating the time interval field of forwarded PTP packets using switch residence time.
- p2ptransparent The device acts as a peer-to-peer transparent clock, synchronizing all ports to a connected master clock and updating the time interval field of forwarded PTP packets using switch residence time and inbound path delays.
- gptp The device runs generalized Precision Time Protocol (gPTP), participating in the best master clock algorithm but also updating the interval field of forwarded PTP packets using switch residence time and inbound path delays.
Examples
- This command configures the switch to act as a PTP boundary
clock.
switch(config)# ptp mode boundary switch(config)# - This command restores PTP to disabled
mode.
switch(config)# no ptp mode switch(config)#
ptp monitor threshold mean-path-delay
Mean path delay is the mean time in nanoseconds that PTP packets take to travel between PTP master and slave. The ptp monitor threshold mean-path-delay command configures the mean-path-delay threshold in nanoseconds. When this threshold is configured, a Syslog message is generated if the value of the most recently calculated mean path delay is greater than or equal to this value.
The no ptp monitor threshold mean-path-delay and default ptp monitor threshold mean-path-delay commands clear the threshold value and prevent further Syslog messages from being generated for this parameter.
Command Mode
Global Configuration
Command Syntax
ptp monitor threshold mean-path-delay threshold
no ptp monitor threshold mean-path-delay
default ptp monitor threshold mean-path-delay
Parameter
threshold threshold in nanoseconds. Values range from 0 to 1000000000 (1 second).
Example
This command sets a mean-path-delay threshold value of 2000
nanoseconds.
switch(config)# ptp monitor threshold mean-path-delay 2000ptp monitor threshold offset-from-master
PTP offset is the difference in nanoseconds between master and slave time. The ptp monitor threshold offset-from-master command configures the offset-from-master threshold in nanoseconds. A Syslog message is generated if the most recently calculated time offset from the PTP master is outside of the range (-<threshold>, <threshold>). The maximum offset threshold is one second.
The no ptp monitor threshold offset-from-master and no ptp monitor threshold offset-from-master commands clear the threshold value and prevents further Syslog messages from being generated for this parameter.
Command Mode
Global Configuration
Command Syntax
ptp monitor threshold offset-from-master threshold
no ptp monitor threshold offset-from-master
default ptp monitor threshold offset-from-master
Parameter
threshold Offset threshold value in nanoseconds. Values range from 0 to 1000000000.
Example
This command sets an offset-from-master threshold value of
500
nanoseconds.
switch(config)# ptp monitor threshold offset-from-master 500
switch(config)#ptp monitor threshold skew
PTP skew is the clock frequency difference between master and slave. The ptp monitor threshold skew command configures the value of the skew-threshold percentage. A Syslog message is generated if the value of the most recently calculated skew is not in the range (1/(1+threshold), 1*(1+threshold)).
The no ptp monitor threshold skew and default ptp monitor threshold skew commands clear the threshold value and prevent further Syslog messages from being generated for this parameter.
Command Mode
Global Configuration
Command Syntax
ptp monitor threshold skew threshold
no ptp monitor threshold skew
default ptp monitor threshold skew
Parameter
threshold skew percentage threshold represented as a double precision (16 digit) real number ranging from 0 (0%) to 10 (1000%).
Example
This command sets a skew threshold value of 5
(500%).
switch(config)# ptp monitor threshold skew 5
switch(config)#ptp monitor
The ptp monitor command enables and disables PTP monitoring on the switch. When PTP monitoring is enabled, the switch records PTP status and configuration information (which can be viewed using the show ptp monitor command) and generates Syslog messages for metrics whose threshold values have been configured. PTP monitoring is enabled by default.
The no ptp monitor command disables the PTP monitoring and clears all the recorded data from running-config.
Command Mode
Global Configuration
Command Syntax
ptp monitor
no ptp monitor
Related Commands
Example
This command disables ptp monitor PTP monitoring on the switch and clears all the
recorded data.
switch(config)# ptp monitor
switch(config)#ptp pdelay-neighbor-threshold
The ptp pdelay-neighbor-threshold command configures the propagation delay threshold above which the switch will consider the neighbor connected to this port to be incapable of participating in generalized Precision Time Protocol (gPTP).
The no ptp pdelay-neighbor-threshold and default ptp pdelay-neighbor-threshold commands restore the threshold to 100000 nanoseconds by removing the corresponding ptp pdelay-neighbor-threshold command from running-config.
Command Mode
Interface-Ethernet Configuration
Interface-Port Channel Configuration
Command Syntax
ptp pdelay-neighbor-threshold link_prop
no ptp pdelay-neighbor-threshold
default ptp pdelay-neighbor-threshold
Parameter
link_prop Threshold in nanoseconds. Value ranges from 0 to 10000000000 (ten billion). Default is 100000.
Examples
- These commands set the link propagation delay threshold on
interface ethernet 5 to
200000
nanoseconds.
switch(config)# interface ethernet 5 switch(config-if-Et5)# ptp pdelay-neighbor-threshold 200000 switch(config-if-Et5)# - These commands restore the link propagation delay threshold on
interface ethernet 5 to its default value
of 100000
nanoseconds.
switch(config)# interface ethernet 5s witch(config-if-Et5)# no ptp pdelay-neighbor-threshold switch(config-if-Et5)#
ptp pdelay-req interval
The ptp pdelay-req interval command configures the interval between Precision Time Protocol peer delay-request messages. The no ptp pdelay-req interval command removes the configuration.
Command Mode
Interface-Ethernet Configuration
Interface-Port Channel Configuration
Command Syntax
ptp pdelay-req interval log_interval
no ptp pdelay-req interval
default ptp pdelay-req interval
Parameter
log_interval The log interval in seconds (base 2 log (seconds)). Value ranges from 0 to 5.
Examples
- This command shows how to configure the interval allowed between PTP peer
delay request messages on interface Ethernet
5.
switch(config)# interface ethernet 5 switch(config-if-Et5)# ptp pdelay-request interval 3 switch(config-if-Et5)# - This command removes the configure the interval allowed between PTP peer
delay request messages on interface Ethernet
5.
switch(config)# interface ethernet 5 switch(config-if-Et5)# no ptp pdelay-request interval switch(config-if-Et5)#
ptp priority1
The ptp priority1 command configures the priority 1 value for advertising the switchs PTP clock. Priority 1 is the most significant of the six factors used by devices in the selection of a master clock. Lower values indicate higher priority.
The no ptp priority1 and default ptp priority1 commands restore the priority 1 default setting of 128.
Command Mode
Global Configuration
Command Syntax
ptp priority1 priority_rate
no ptp priority1
default ptp priority1
Parameter
priority_rate Value ranges from 0 to 255. Default is 128.
Examples
- This command sets the priority 1 level for the
switchs PTP clock to
120.
switch(config)# ptp priority1 120 switch(config)# - This command restores the default priority 1 level
of
128.
switch(config)# no ptp priority1 switch(config)#
ptp priority2
The ptp priority2 command sets the priority 2 value for the clock. The range is from 0 to 255. Priority 2 is the fifth most significant of the six factors used by devices in the selection of a master clock. Lower values indicate higher priority.
The no ptp priority2 and default ptp priority2 commands restore the priority 2 default setting of 128.
Command Mode
Global Configuration
Command Syntax
ptp priority2 priority_rate
no ptp priority2
default ptp priority2
Parameter
priority_rate Specifies the priority 2 level for the PTP clock. Value ranges from 0 to 255; default value is 128.
Examples
- This command sets the priority 2 level for the
switchs PTP clock to
120.
switch(config)# ptp priority2 120 switch(config)# - This command restores the default priority 2 level
of
128.
switch(config)# no ptp priority2 switch(config)#
ptp role
The ptp role command configures a port to operate either in the master mode or the dynamic mode when it is executed in the interface configuration mode.
The no ptp role command removes the master or dynamic mode if it was previously configured on an interface.
Command Mode
Interface-Ethernet Configuration
Command Syntax
ptp role [dynamic | master]
no ptp role
default ptp role
Parameters
- dynamic the dynamic mode.
- master the master clock mode that has the most precise time.
Related Commands
Examples
- This command configures a port to operate in the master mode for
interface ethernet
1.
switch(config)# interface ethernet 1 switch(config-if-Et1)# ptp role master - This command configures a port to operate in the dynamic mode for
interface ethernet
1.
switch(config)# interface ethernet 1 switch(config-if-Et1)# ptp role dynamic
ptp source
The ptp source command configures the source IP address for all PTP packets. The IP address can be in IPv4 or IPv6 format. The no ptp source ip command removes this configuration.
Command Mode
Global Configuration
Command Syntax
ptp source ip {ip|ipv6} ip_addr
no ptp source ip
default ptp source ip
Parameters
ip specifies an IPv4 source address.
ipv6 specifies an IPv6 source address.
ip_addr the source IP address.
Examples
- This command configures the source IP address
10.0.2.1for all PTP packets.switch(config)# ptp source ip 10.0.2.1 switch(config)# - This command configures the source IP address
2001:db8:ac10:fe01::for all PTP packets.switch(config)# ptp source ip 2001:db8:ac10:fe01:: switch(config)# - This command removes any configured source IP address for all PTP
packets.
switch(config)# no ptp source ip switch(config)#
ptp sync timeout
A PTP synchronization timeout occurs if a sync message is not received for a specified period of time, calculated as a multiple of the PTP sync-message interval. The ptp sync timeout command configures the sync timeout multiplier. The range is 2 to 255, with a default of 20 (20 times the sync interval). To configure the sync interval, use the ptp sync-message interval command.
The no ptp sync timeout and default ptp sync timeout commands restore the PTP sync timeout multiplier to its default value of 20.
Command Mode
Interface-Ethernet Configuration
Command Syntax
ptp sync timeout interval_multiplier
no ptp sync timeout
default ptp sync timeout
Parameter
interval_multiplier The number of sync intervals that must pass without the configuration mode interface receiving a PTP sync message before a timeout occurs. Value ranges from 2 to 255. Default value is 20.
Example
These commands configure the sync timeout on interface ethernet
5 to ten times the configured sync
interval.
switch(config)# interface ethernet 5
switch(config-if-Et5)# ptp sync timeout 10
switch(config-if-Et5)#ptp sync-message interval
The ptp sync-message interval command configures the time for sending synchronization messages by specifying its log2 value. Default values and ranges depend on the PTP mode, which is set using the ptp mode command.
The no ptp sync-message interval and default ptp sync-message interval commands restore the sync interval to its default (1 second in boundary mode, 1/8 second in gptp mode) by removing the corresponding ptp sync-message interval command from running-config.
Command Mode
Interface-Ethernet Configuration
Interface-Port Channel Configuration
Command Syntax
ptp sync-message interval log_interval
no ptp sync-message interval
default ptp sync-message interval
Parameter
log_interval The interval between PTP synchronization messages sent from the master to the slave (base 2 log (seconds)). Values vary according to PTP mode: in boundary mode, the range is from -7 (1/128 second) to 3 (8 seconds) and the default value is 0 (1 second). In gptp mode, the range is from -3 (1/8 second) to 17 (131072 seconds, approximately 36 hours) with a default of -3.
Examples
- These commands set the interval for PTP synchronization messages on
interface ethernet 5 to
3 (8
seconds).
switch(config)# interface ethernet 5 switch(config-if-Et5)# ptp sync-message interval 3 switch(config-if-Et5)# - In boundary mode, these commands restore the interval for PTP
synchronization messages on interface ethernet 5
to its default of 0 (1
second).
switch(config)# interface ethernet 5 switch(config-if-Et5)# no ptp sync-message interval switch(config-if-Et5)#
ptp transport
The ptp transport command configures the PTP transport type for a specific interface. Any values set in interface PTP configuration mode override the settings in the PTP configuration profile associated with the interface. The no ptp transport command removes the stetting from the running-config.
Command Mode
Interface-Ethernet Configuration
Interface-Port Channel Configuration
Command Syntax
ptp transport TRANSPORT_TYPE
no ptp transport
default ptp transport
Parameters
TRANSPORT_TYPE The transport mode in boundary clock mode.
Options include:
- ipv4 The IPv4 address used as the transport type on the interface.
- ipv6 The IPv6 address used as the transport type on the interface.
- layer2 The Layer 2 protocol used as the transport type on the interface.
Examples
- This command overrides the transport type in the profile and sets it to be
IPv4 for the
interface.
switch(config)# interface ethernet 5 switch(config-if-Et5)# ptp transport ipv4 switch(config-if-Et5)# - This command removes the interval for PTP synchronization messages on
interface Ethernet
5.
switch(config)# interface ethernet 5 switch(config-if-Et5)# no ptp transport switch(config-if-Et5)#
ptp ttl
The ptp ttl command configures the Time To Live (TTL) value of the PTP packets. The no ptp ttl resets the TTL value to the default value of 1 hop by removing the ptp ttl command from the running-config.
Command Mode
Global Configuration
Command Syntax
ptp ttl hop_count
no ptp ttl
default ptp ttl
Parameter
hop_count The TTL value measured in hops. Value ranges from 1 to 255, default is 1.
Examples
- This command sets the time to live of the PTP packets to
60
hops.
switch(config)# ptp ttl 60 switch(config)# - This command resets the time to live of the PTP packets to the default value
of 1
hop.
switch(config)# no ptp ttl switch(config)#
ptp unicast-negotiation
The ptp unicast-negotiation command configures the master slave profiles for PTP devices.
Command Mode
Interface-Ethernet Configuration
Command Syntax
ptp unicast-negotiation
ptp unicast-negotiation remote-grantee
Parameters
- candidate-grantor become slave to another PTP device.
- remote-grantee become master to another PTP device.
Examples
- This command sets up an interface as a potential
master.
switch(config-if)# ptp unicast-negotiation remote-grantee 10.0.0.1/24 switch(config-if)# ptp unicast-negotiation remote-grantee 10.0.0.1/24 profile fastProfile - This command sets up an interface as a potential
slave.
switch(config-if)# ptp unicast-negotiation candidate-grantor 10.0.0.1 switch(config-if)# ptp unicast-negotiation candidate-grantor 10.0.0.1 profile fastProfile
show ptp
The show ptp command displays summary Precision Time Protocol (PTP) information and PTP status of switch ports.
Command Mode
EXEC
Command Syntax
show ptp
Example
This command displays summary PTP
information.
switch#show ptp
PTP Mode: gptp - Generalized PTP Clock
Clock Identity: 2001:0DB8:73:ff:ff:26:fd:90
Grandmaster Clock Identity: 2001:0DB8:96:ff:fe:6c:ed:02
Number of slave ports: 1
Number of master ports: 6
Slave port: Ethernet33
Mean Path Delay (nanoseconds): 718
Steps Removed: 1
Neighbor Rate Ratio: 1.00000007883
Rate Ratio: 1.00000007883
Interface StateASTime Since LastNeighborMean PathResidence
Capable Changed Rate Ratio Delay (ns) Time (ms)
--------- -------- ------- ------------------ ----------- -----------
Et1 Disabled No Never 1.0 00
Et2 Disabled No Never 1.0 00
Et3 Disabled No Never 1.0 00
Et4 Disabled No Never 1.0 00
Et5 Disabled No Never 1.0 00
Et6 Disabled No Never 1.0 00
Et7 Master Yes 0:21:08 1.000000094200show ptp foreign-master-record
The show ptp foreign-master-record command displays information about foreign masters (PTP sources not designated as the switch's master from which the switch has received sync packets).
Command Mode
EXEC
Command Syntax
show ptp foreign-master-record
Example
This command displays information about PTP foreign
masters.
switch# show ptp foreign-master-record
No Foreign Master Records
switch#show ptp interface counters
The show ptp interface counters command displays PTP interface counters for all interfaces.
Command Mode
EXEC
Command Syntax
show ptp [INTERFACE_NAME] counters
Parameters
INTERFACE_NAME Interface type and numbers. Options
include:
- no parameter Display information for all interfaces.
- ethernet e_range Ethernet interface range specified by e_range.
- loopback l_range Loopback interface specified by l_range
- management m_range Management interface range specified by m_range.
- port-channel p_range Port-Channel Interface range specified by p_range.
- vlan v_range VLAN interface range specified by v_range.
- VXLAN vx_range VXLAN interface range specified by vx_range.
Valid range formats include number, number range, or comma-delimited list of numbers and ranges.
Example
This command displays the PTP interface
counters.
switch# show ptp interface ethernet 5 counters
Interface Ethernet5
Announce messages sent: 0
Announce messages received: 0
Sync messages sent: 0
Sync messages received: 0
Follow up messages sent: 0
Follow up messages received: 0
Delay request messages sent: 0
Delay request messages received: 0
Delay response messages sent: 0
Delay response messages received: 0
Peer delay request messages sent: 0
Peer delay request messages received: 0
Peer delay response messages sent: 0
Peer delay response messages received: 0
Peer delay response follow up messages sent: 0
Peer delay response follow up messages received: 0
switch# show ptp interface
The show ptp interface command displays PTP information for all the interfaces on the device.
Command Mode
EXEC
Command Syntax
show ptp [INTERFACE_NAME][STATUS_FILTER]
Parameters
- INTERFACE_NAME Interface type and numbers. Options
include:
- no parameter Display information for all interfaces.
- ethernet e_range Ethernet interface range specified by e_range.
- loopback l_range Loopback interface specified by l_range.
- management m_range Management interface range specified by m_range.
- port-channel p_range Port-Channel Interface range specified by p_range.
- vlan v_range VLAN interface range specified by v_range.
Valid range formats include number, number range, or comma-delimited list of numbers and ranges.
- STATUS_FILTER Filters interfaces by their
configuration status. Options include:
- no parameter all interfaces.
- enabled PTP configured interfaces.
Example
This command displays PTP information for all the interfaces on the device.
switch# show ptp interface
Interface Ethernet1
PTP: Disabled
Port state: Disabled
Sync interval: 1.0 seconds
Announce interval: 2.0 seconds
Announce interval timeout multiplier: 3
Delay mechanism: end to end
Delay request message interval: 32.0 seconds
Transport mode: ipv4
Interface Ethernet5
PTP: Disabled
Port state: Disabled
Sync interval: 8.0 seconds
Announce interval: 2.0 seconds
Announce interval timeout multiplier: 5
Delay mechanism: peer to peer
Peer delay request message interval: 8.0 seconds
Peer Mean Path Delay: 0
Transport mode: ipv6
switch#show ptp local-clock
The show ptp local-clock command displays the Precision Time Protocol (PTP) clock information.
Command Mode
EXEC
Command Syntax
show ptp local-clock
Example
This command shows how to display the PTP local clock and
offset.
switch# show ptp local-clock
PTP Mode: Boundary Clock
Clock Identity: 0x00:1c:73:ff:ff:1e:83:24
Clock Domain: 1
Number of PTP ports: 24
Priority1: 128
Priority2: 128
Clock Quality:
Class: 248
Accuracy: 0x30
OffsetScaledLogVariance: 0xffff
Offset From Master: 0
Mean Path Delay: 0
Steps Removed: 0
switch#show ptp masters
The show ptp masters command displays information about the switch's PTP master and grand master clocks.
Command Mode
Privileged EXEC
Command Syntax
show ptp masters
Example
This command displays information about the switchs PTP master and grand master
clocks.
switch# show ptp masters
Parent Clock:
Parent Clock Identity: 0x00:1c:73:ff:ff:00:72:40
Parent Port Number: 0
Parent IP Address: N/A
Observed Parent Offset (log variance): N/A
Observed Parent Clock Phase Change Rate: N/A
Grandmaster Clock:
Grandmaster Clock Identity: 0x00:1c:73:ff:ff:00:72:40
Grandmaster Clock Quality:
Class: 248
Accuracy: 0x30
OffsetScaledLogVariance: 0xffff
Priority1: 128
Priority2: 128
switch#show ptp monitor
The show ptp monitor command to displays the list of up to 100 recorded entries of offset from master, mean path delay and skew values, along with current PTP mode, whether or not the feature is enabled, number of entries displayed and the configured thresholds for each metric. Entries are sorted by the system time at which the value was calculated, starting with the most recent data at the top.
Command Mode
EXEC
Command Syntax
show ptp monitor
Example
This command displays the information recorded by PTP monitoring.
switch# show ptp monitor
PTP Mode: Boundary Clock
Ptp monitoring: enabled
Number of entries: 5
Offset from master threshold: 1500
Mean path delay threshold: not configured
Skew threshold: 0.5
Interface Time Offset from Mean Path Skew
Master (ns) Delay (ns)
---------- ----------------------------- ------------ ------------- -----------
Et8 21:23:12.901 UTC Feb 22 2018 71 5849 1.003159918
Et1 21:23:12.901 UTC Feb 22 2018 113 3672 1.004990621
Et2 21:23:12.901 UTC Feb 22 2018 706 7799 1.002744199
Et1 21:23:12.901 UTC Feb 22 2018 803 5861 1.003432049
Et1 21:23:12.901 UTC Feb 22 2018 610 3415 0.998974658show ptp source ip
The show ptp source ip command displays the PTP source IP for the device.
Command Mode
Privileged EXEC
Command Syntax
show ptp source ip
Example
This command shows the PTP source IP to be
10.0.2.1switch# show ptp source ip
PTP source IP: 10.0.2.1This command shows the PTP source IP to be
2001:db8:ac10:fe01::.switch# show ptp source ip
PTP source IP: 2001:db8:ac10:fe01::show ptp unicast-negotiation
The show ptp unicast-negotiation command displays PTP unicast negotiation information for the switch.
Command Mode
EXEC
Command Syntax
show ptp unicast-negotiation profile
show ptp unicast-negotiation [DETAILS]
Parameters
DETAILS Details requested. Options include:
- candidate-grantor Display all configured candidate grantors, associated profile name and latest update.
- remote-grantee Display all configured remote grantees, associated profile name and latest update.
- granted Display to which remote grantees each port has granted and some detail.
- requested Display to which candidate grantors each port has requested and some detail.
Examples
- This command displays the unicast negotiation profiles configured on the
switch.
switch# show ptp unicast-negotiation profile Unicast Negotiation Profile fastProfile Announce interval: 0.25 seconds Announce duration: 500 seconds Sync interval: 0.125 seconds Sync duration: 300 seconds Delay Response interval: 0.125 seconds Delay Response duration: 300 seconds - This command displays all configured candidate grantors, associated profile
name and latest
update.
switch# show ptp unicast-negotiation candidate-grantor Interface Address Profile Grantor Status ----------- ---------- -------------- ------------------ Ethernet1 4::1 fastProfile Master Ethernet1 4::2 fastProfile Candidate Master Ethernet2 4::2 fastProfile Blacklisted - This command displays all configured remote grantees, associated profile
name and latest
update.
switch# show ptp unicast-negotiation remote-grantee Interface Address Profile ------------ ---------- ------------- Ethernet1 4::1/96 fastProfile Ethernet1 4::2/96 fastProfile Ethernet2 4::2/96 fastProfile - This command displays to which remote grantees each port has granted and
some
detail.
switch# show ptp unicast-negotiation granted Interface Address Message Interval Duration Expires In ----------- ---------- ------------ -------------- -------------- ----------- Ethernet2 4::1 Announce 0.25 seconds 300 seconds 30 seconds Ethernet2 4::1 Sync 2.0 seconds 300 seconds 30 seconds - This command displays to which candidate grantors each port has requested
and some
detail.
switch# show ptp unicast-negotiation requested Interface Address Message Interval Duration Expires In ------------ --------- ----------- --------------- -------------- ------------ Ethernet2 4::2 Announce 0.25 seconds 600 seconds 250 seconds Ethernet2 4::2 Sync 2.0 seconds 300 seconds denied
show ptp unicast-negotiation profile
The show ptp unicast-negotiation profile command displays all user configured profiles and their values.
Command Mode
EXEC
Command Syntax
show ptp unicast-negotiation profile
Example
This command displays the PTP profiles.
switch# show ptp unicast-negotiation profile
Unicast Negotiation Profile fastProfile
Announce interval: 0.25 seconds
Announce duration: 500 seconds
Sync interval: 0.125 seconds
Sync duration: 300 seconds
Delay Response interval: 0.125 seconds
Delay Response duration: 300 secondsSwitch Environment Control
The following sections describe the commands that display temperature, fan, and power supply
status:
The switch chassis, fans, power supplies, line cards, and supervisors also provide LEDs that signal status and conditions that require attention. The Quick Start Guide for the individual switches provides information about their LEDs.
Environment Control Introduction
Arista switching platforms are designed to work reliably in common data center environments.
To ensure their reliable operation and to monitor or diagnose the switch's health, Arista provides a set of monitoring capabilities available through the CLI or SNMP entity MIBs to monitor and diagnose potential problems with the switching platform.