53-1003093-03 15 April 2014 FastIron Ethernet Switch Traffic Management Guide Supporting FastIron Software Release 08.0.
Contents Preface..................................................................................................................................... 5 Document conventions......................................................................................5 Text formatting conventions.................................................................. 5 Command syntax conventions.............................................................. 5 Notes, cautions, and warnings....................................
Trust DSCP for the SX-FI48GPP, SX-FI-24GPP, SX-FI-24HF, SX-FI-2XG, and SX-FI8XG modules........................................... 32 Configuring QoS mapping configuration....................................................... 33 Default DSCP to internal forwarding priority mappings.....................33 Changing the DSCP to internal forwarding priority mappings...........34 Changing the VLAN priority 802.1p to hardwareforwarding queue mappings...............................................................
ACL-based adaptive rate limiting configuration...................................66 Specifying the action to be taken for packets that are over the limit... 69 ACL statistics and rate limit counting.............................................................. 70 Enabling ACL statistics....................................................................... 70 Enabling ACL statistics with rate limiting traffic policies......................71 Viewing ACL and rate limit counters...............................
4 FastIron Ethernet Switch Traffic Management Guide 53-1003093-03
Preface ● Document conventions......................................................................................................5 ● Brocade resources............................................................................................................ 7 ● Getting technical help........................................................................................................7 ● Document feedback...................................................................................................
Notes, cautions, and warnings Convention Description value In Fibre Channel products, a fixed value provided as input to a command option is printed in plain text, for example, --show WWN. [] Syntax components displayed within square brackets are optional. Default responses to system prompts are enclosed in square brackets. {x|y|z} A choice of required parameters is enclosed in curly brackets separated by vertical bars. You must select one of the options.
Brocade resources Brocade resources Visit the Brocade website to locate related documentation for your product and additional Brocade resources. You can download additional publications supporting your product at www.brocade.com. Select the Brocade Products tab to locate your product, then click the Brocade product name or image to open the individual product page. The user manuals are available in the resources module at the bottom of the page under the Documentation category.
Preface • • Through the online feedback form in the HTML documents posted on www.brocade.com. By sending your feedback to documentation@brocade.com. Provide the publication title, part number, and as much detail as possible, including the topic heading and page number if applicable, as well as your suggestions for improvement.
About This Document ● About This Document........................................................................................................9 ● What’s new in this document.......................................................................................... 10 ● How command information is presented in this guide.....................................................10 About This Document Introduction This guide includes procedures for configuring the software.
What’s new in this document What’s new in this document This document includes the information from FastIron software release 08.0.10b. TABLE 1 Summary of Enhancements in FastIron release 08.0.10b Feature Description Location A new command has been added: The store-and-forward command See store-and-forward on page changes the switch mode to store-and- 94. forward. store-and-forward. Support for Outbound rate shaping. Outbound rate shaping is supported on ICX 7750 devices.
Quality of Service ● Supported Quality of Service features............................................................................ 11 ● QoS overview..................................................................................................................12 ● QoS for Brocade stackable devices................................................................................ 19 ● QoS queues................................................................................................................
QoS overview Feature ICX 6430 ICX 6450 FCX ICX 6610 ICX 6650 FSX 800 FSX 1600 ICX 7750 User-configurable scheduler profiles 08.0.01 08.0.01 08.0.01 08.0.01 08.0.01 No 08.0.10 QoS overview Quality of Service (QoS) features are used to prioritize the use of bandwidth in a switch. When QoS features are enabled, traffic is classified as it arrives at the switch, and processed through on the basis of configured priorities.
Quality of Service NOTE The Determining a packet trust level - FSX devices figure is not applicable to the third generation FSX interface modules. To determine the trust level of a packet for the SX-FI48GPP, SX-FI-24GPP, SXFI-24HF, SX-FI-2XG, and SX-FI-8XG modules, refer to the Determining a packet trust level - SXFI48GPP, SX-FI-24GPP, SX-FI-24HF, SX-FI-2XG, and SX-FI-8XG modules figure.
Quality of Service The Determining a packet trust level - SX-FI48GPP, SX-FI-24GPP, SX-FI-24HF, SX-FI-2XG, and SXFI-8XG modules figure illustrates how the SX-FI48GPP, SX-FI-24GPP, SX-FI-24HF, SX-FI-2XG, and SX-FI-8XG modules determine the trust level of a packet. The marking process for these modules is similar to the marking process for other FastIron SX modules. However, there are major differences between these modules and other FastIron SX modules.
Quality of Service FI48GPP, SX-FI-24GPP, SX-FI-24HF, SX-FI-2XG, and SX-FI-8XG modules. Therefore, configuring a static MAC with a priority of 0 has no effect on QoS marking. FIGURE 2 Determining a packet trust level - SX-FI48GPP , SX-FI-24GPP, SX-FI-24HF, SX-FI-2XG, and SX-FI-8XG modules The following figure illustrates how FCX, and ICX series devices determine the trust level of a packet.
Quality of Service classified with the ingress port default priority. then DSCP/ToS value, then 802.1p CoS value, and finally the default priority of zero (0).
Quality of Service Once a packet is classified, it is mapped to a forwarding queue. For all products except the SXF148GPP interface module and ICX 6430 switch, there are eight queues designated from 0 through 7. The internal forwarding priority maps to one of these eight queues. For the SX-Fl48GPP interface module and ICX 6430 switch, internal forwarding priority maps to four forwarding queues. The mapping between the internal priority and the forwarding queue cannot be changed.
Quality of Service TABLE 2 Default QoS mappings for FCX platforms, columns 0 to 15 (Continued) DSCP value 0 1 2 3 4 5 6 7 8 9 10 11 12 12 14 15 DSCP value 0 1 2 3 4 5 6 7 8 9 10 11 12 12 14 15 Internal forwarding priority 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 Forwarding queue 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 TABLE 3 Default QoS mappings for FCX platforms, columns 16 to 31 DSCP value 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
QoS for Brocade stackable devices • level is DSCP. Refer to Changing the DSCP to internal forwarding priority mappings on page 34. VLAN priority (802.1p) to hardware forwarding queue - You can change the mapping between the 802.1p value and hardware forwarding queue from the default value. Refer to Changing the VLAN priority 802.1p to hardwareforwarding queue mappings on page 35. QoS for Brocade stackable devices Brocade FastIron units in a traditional stack support QoS.
QoS behavior for 802.1p marking in a traditional stack When stacking is not enabled on a device, all priorities are mapped to their corresponding queues without restrictions. QoS behavior for 802.1p marking in a traditional stack By default, 802.1p marking is not enabled in a traditional stack. Outgoing tagged traffic will not be marked based on the hardware queue into which ingress traffic was classified. 802.1p marking can be achieved using ACL.
Queues for the SX-FI-8XG interface module one 1-GbE port in the back-end NP. The two network ports share the same hardware queues, and therefore they have the same buffer and descriptor limits and scheduling algorithm for transmission. Ingress packets are classified into eight QoS priority levels at the front-end NP of the SX-FI48GPP module. The eight priorities are mapped into four hardware queues based on the priority queue configuration in the following table.
Queues for the ICX 6430 switch Queues for the ICX 6430 switch For the ICX 6430 switch, ingress packets are classified into eight QoS priority levels. These are mapped internally to four hardware forwarding queues or traffic classes as shown in the following table. QoS priority 7 is the highest priority, and QoS 0 is the lowest QoS priority (qosp) level.
User-configurable scheduler profile TABLE 10 Default QoS mappings for ICX 6430, columns 16 to 31 (Continued) DSCP value 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Forwarding queue 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 TABLE 11 Default QoS mappings for ICX 6430, columns 32 to 47 DSCP value 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 802.
User-configurable scheduler profile configuration On Brocade ICX 7750 devices, scheduler profiles are applied at the port, rather than at the device (port region), level. See the description of the scheduler-profile command for more information. User-configurable scheduler profile configuration Configuring a user-configurable scheduler profile involves, selecting a proper mechanism and appropriate weights for the traffic classes (TCs) corresponding to that mechanism.
Quality of Service To display all the scheduler profiles configured in the runtime configuration for the system, use the show scheduler-profileall command. FCX and ICX 6450 platforms The following tables show the default values for the scheduling type for stacking and stand-alone FCX and ICX 6450 platforms. TABLE 13 Default values for scheduling type for stacking systems (for FCX and ICX 6450 platforms).
Quality of Service ICX 6650 platforms The following tables show the default values for the scheduling type for ICX 6650 platforms.
QoS priorities-to-traffic assignment TABLE 16 Default values for scheduling type for stacking systems (for ICX 6430 platforms) (Continued) QSP Level SP SP Jumbo WRR WRR Jumbo Mixed Mixed Jumbo QSP7 SP SP SP SP SP SP TABLE 17 Default values for scheduling type for stand-alone systems (for ICX 6430 platforms) SP SP Jumbo WRR WRR Jumbo Mixed Mixed Jumbo QSP0 SP SP 3 8 15 15 QSP1 SP SP 3 8 15 15 QSP2 SP SP 3 8 15 15 QSP3 SP SP 3 8 15 15 QSP4 SP SP 3 8 40 40
Assigning static MAC entries to priority queues The device assigns priority 7 to untagged switched traffic received on port 1/1. Use the following command to assign priority levels. Syntax: [no] priority num The num variable can be from 0 through 7 and specifies the IEEE 802.1 equivalent to one of the eight QoS queues listed in the QoS queues table. Assigning static MAC entries to priority queues By default, all MAC entries are in the best-effort queue.
Configuration notes and feature limitations Note that the original 802.1p priority in the packet will be retained. This feature does not re-mark the 802.1p value. Configuration notes and feature limitations • • 802.1p priority override is supported on physical ports and trunk ports. When applied to the primary port of a trunk group, the configuration applies to all members of the trunk group. This feature is not supported together with trust dscp . Enabling 802.1p priority override To enable 802.
Configuration considerations and limitations Prior to 08.0.00, the only way to prevent such threats was to mark all packets using ACLs. Beginning with 08.0.00, the internal forwarding priority can be set using an ACL only for flows that require preferential QoS treatment. For all other flows, you can remark DSCP and CoS fields globally. Traffic marked by the ACL method always has a higher priority than the global marking.
Enabling CoS marking The following example shows how to set the DSCP value to 4 of all IP packets on a specific port: device(config)# interface ethernet1/1/1 device(config-if-e1000-1/1/1)# ip dscp-remark 4 Enabling CoS marking To enable CoS marking globally, use the ip pcp-remark command in global configuration mode. To enable CoS marking on a port, use the ip pcp-remark command in interface configuration mode.
Using ACLs to honor DSCP-based QoS Using ACLs to honor DSCP-based QoS This section shows how to configure Brocade devices to honor DSCP-based QoS for routed and switched traffic. FCX and ICX devices Brocade FCX, ICX 6430, ICX 6450, ICX 6610, and ICX 6650 devices support DSCP-based QoS on a per-port basis. DSCP-based QoS is not automatically honored for switched traffic. The default is 802.1p to CoS mapping. To honor DSCP-based QoS, enter the following command at the interface level of the CLI.
Configuring QoS mapping configuration Each port on the supported modules corresponds to a front-end panel port. By default, trust VLAN priority is enabled. NOTE For all ports in the other FastIron SX modules, ACL should be used to implement the trust DSCP mode. For example, to enable trust DSCP on interface ethernet 1/48 on the SX-FI48GPP module, enter the following command. Syntax: [no] trust dscp To disable the configuration, use the no form of the command.
Changing the DSCP to internal forwarding priority mappings On FCX and ICX devices, you can use QoS queue 1 for priority traffic, even when sFlow is enabled on the port. This differs from the FastIron X Series devices, which support seven priorities for user data instead of eight when sFlow is enabled. QoS queue 1 is reserved for sFlow and not used by other packets. Any non-sFlow packets assigned to QoS queue 1 will be directed to QoS queue 0. Note that the ICX 6430 does not support sFlow.
Changing the VLAN priority 802.1p to hardwareforwarding queue mappings Following is an example of using this command. qos-tos map dscp-priority 1 2 3 4 5 6 7 8 to 6 Following is output displayed from using the show qos-tos command as a result of issuing the preceding command. device#show qos-tos Portions of table omitted for simplicity.
Default scheduling configuration for the SX-FI48GPP module Default scheduling configuration for the SX-FI48GPP module The default scheduling configuration for Weighted Round Robin (WRR), Strict Priority (SP), and mixed WRR and SP mode for the eight QoS priority (qosp) queues mapped to the four hardware queues is described in the following table.
Scheduling QoS information The above table includes values for default, non-jumbo mode WRR for a stand-alone system.
Quality of Service NOTE Queue cycles on the Brocade FastIron devices (except on ICX 6650) are based on bytes. These devices service a given number of bytes (based on weight) in each queue cycle. The QoS WRR on ICX 6650 is configured to operate in packet count mode. • Strict Priority (SP) - SP ensures service for high-priority traffic. The software assigns the maximum weights to each queue, to cause the queuing mechanism to serve as many packets in one queue as possible before moving to a lower queue.
Selecting the QoS queuing method Selecting the QoS queuing method By default, Brocade devices use the WRR method of packet prioritization. To change the method to SP, enter the qos mechanism strict command at the global CONFIG level of the CLI. device(config)#qos mechanism strict To change the method back to WRR, enter the qos mechanism weighted command.
Quality of Service TABLE 24 Default minimum bandwidth percentages on Brocade devices Queue Default minimum percentage of bandwidth Without jumbo frames With jumbo frames qosp7 75% 44% qosp6 7% 8% qosp5 3% 8% qosp4 3% 8% qosp3 3% 8% qosp2 3% 8% qosp1 3% 8% qosp0 3% 8% When the queuing method is WRR, the software internally translates the percentages into weights.
Configuration notes for changing the bandwidth for each priority. When jumbo frames are enabled, the minimum bandwidth requirement is 8 percent. If these minimum values are not met, QoS may not be accurate. Configuration notes for changing the bandwidth • • The total of the percentages you enter must equal 100. FastIron devices do not adjust the bandwidth percentages you enter.
Viewing DSCP-based QoS settings The following example shows the output on an FSX device.
Quality of Service TABLE 25 DSCP-based QoS configuration information (Continued) Field Description d1 and d2 The DSCP to forwarding priority mappings that are currently in effect. NOTE The example shows the default mappings. If you change the mappings, the command displays the changed mappings Traffic class to 802.1 priority map Traffic Class and 802.1p Priority The traffic class to 802.1p priority mappings that are currently in effect. NOTE The example shows the default mappings.
Quality of Service TABLE 26 8 to 4 queue mapping configuration information Field Description 8 to 4 queue mapping Priority and Hardware Queue The priority to hardware queues that are currently in effect for 8 to 4 queue mapping.
Rate Limiting and Rate Shaping on FastIron X Series and FCX and ICX Series Switches ● Supported Rate Limiting and Rate Shaping features on FastIron X Series and FCX and ICX Series Switches.............................................................................................. 45 ● Rate limiting overview..................................................................................................... 45 ● Rate limiting in hardware......................................................................
Rate limiting in hardware specify in the policy, but drops additional bytes (packets in the case of ICX 6650). Unused bandwidth is not carried over from one interval to the next. NOTE Port based Rate Limiting affects only known-unicast traffic. Broadcast, Multicast and Unknown-unicast (BUM) is not affected by this rate. To rate limit the BUM traffic, use BUM rate limiting as described in chapter BUM Rate Limiting.
Configuration notes for rate limiting (packets in ICX 6650) in each interval. However, the port receives more than 500000 bits (packets in ICX 6650) during the third and fourth one-second intervals, and consequently drops the excess traffic. FIGURE 5 Fixed rate limiting NOTE The software counts the bytes (packets in ICX 6650) by polling statistics counters for the port every 100 milliseconds, which provides 10 readings each second.
Configuring a port-based rate limiting policy Configuring a port-based rate limiting policy To configure rate limiting on a port, enter commands such as the following. device(config)#interface ethernet 24 device(config-if-e1000-24)#rate input fixed 500 These commands configure a fixed rate limiting policy that allows port 24 to receive a maximum of 500 kbits (500 packets in ICX 6650) per second.
Rate Limiting and Rate Shaping on FastIron X Series and FCX and ICX Series Switches 5/2 5/6 230432 234113 230000 234000 Syntax: show rate-limit input The command lists the ports on which fixed rate limiting is configured, and provides the information listed in the following table for each of the ports. TABLE 27 CLI display of fixed rate limiting information Field Description Total rate-limited interface count The total number of ports that are configured for fixed rate limiting. Port The port number.
Rate shaping overview Rate shaping overview Outbound Rate Shaping is a port- level feature that is used to shape the rate and control the bandwidth of outbound traffic on a port. This feature smooths out excess and bursty traffic to the configured maximum limit before it is sent out on a port. Packets are stored in available buffers and then forwarded at a rate no greater than the configured limit. This process provides for better control over the inbound traffic of neighboring devices.
Configuring outbound rate shaping for a port TABLE 29 Output rate shaping on FastIron devices (Continued) Device Module Minimum Maximum ICX 6450 All 73 999868 ICX 6650 40 Gbps ports 20 80000000 ICX 6650 10 Gbps ports 20 20000000 ICX 7750 10 Gbps ports 128 kbps 10,000,000 kbps ICX 7750 40 Gbps ports 8 kbps 40,000,000 kbps FCX 1 Gbps ports 89 999666 FCX 10 Gbps ports 3388 9996513 FSX SX-FI48GPP module 51 999485 FSX SX-FI-24GPP module 51 999485 FSX SX-FI424P module 65
Configuring outbound rate shaping for a LAG port Syntax: [no] rate-limit output sharingvalue priority priority-queue Specify 0-7 for priority-queue Configuring outbound rate shaping for a LAG port This feature is supported on individual ports of a LAG group. To configure the maximum rate at which outbound traffic is sent out on a LAG port, enter the following on each LAG port where outbound traffic will be shaped.
Limiting Broadcast, Multicast, and Unknown Unicast Traffic ● Supported Limiting Broadcast, Multicast, and Unknown Unicast Traffic Features..........53 ● Configuration notes and feature limitations.....................................................................53 ● Command syntax for packet-based limiting ................................................................... 54 ● Command syntax for byte-based limiting........................................................................
Command syntax for packet-based limiting ‐ • Unknown unicast limiting is independent of broadcast and multicast limiting. To enable multicast limiting, enable it after enabling broadcast limiting. Multicast limiting uses the limit defined in broadcast limiting. You cannot set a separate limit for multicast limiting. ‐ FastIron X Series devices support packet-based and byte-based limiting per port, as well as simultaneously on the same port.
On Brocade FCX Series, ICX 6430 , and ICX 6650 devices device(config-if-e1000-1)# unknown-unicast limit 65536 The combined number of inbound Unknown Unicast packets permitted for ports 1 to 12 is now set to 65536 device(config-if-e1000-1)# NOTE On the SX-FI48GPP module, multicast and unknown-unicast limiting use the value defined in broadcast limiting. You cannot set a separate limit for unknown-unicast limiting and multicast limiting.
Command syntax for byte-based limiting To include unknown-unicast limiting, enter the unknown-unicast limit command after enabling broadcast limiting. device(config-mif-e1000-1/1/1-1/1/8)# unknown-unicast limit To include multicasts limiting, enter the multicast limit command after enabling broadcast limiting.
Viewing broadcast, multicast, and unknown unicast limits Syntax: [no] unknown-unicast limit num bytes The num variable can be any number that is a multiple of 65536, up to a maximum value of 2147418112. If you enter the multicast limit command, multicast packets are included in the limit you specify. If you specify 0, limiting is disabled. If you specify a number that is not a multiple of 65536, the software rounds the number to the next multiple of 65536. Limiting is disabled by default.
Limiting Broadcast, Multicast, and Unknown Unicast Traffic interface management 1 ip address 10.21.113.7 255.255.248.
Limiting Broadcast, Multicast, and Unknown Unicast Traffic Syntax: show rate-limit unknown-unicast Use the show rate-limit broadcast command to display the broadcast limit or broadcast and multicast limit for each port to which it applies. NOTE For ICX 7750, this command shows only the broadcast limit.
Viewing broadcast, multicast, and unknown unicast limits 60 FastIron Ethernet Switch Traffic Management Guide 53-1003093-03
Traffic Policies ● Supported Traffic Policies............................................................................................... 61 ● Traffic policies overview.................................................................................................. 61 ● Maximum number of traffic policies supported on a device............................................ 63 ● ACL-based rate limiting using traffic policies..................................................................
Configuration notes and feature limitations for traffic policies Brocade devices use traffic policies for the following reasons: • • To rate limit inbound traffic To count the packets and bytes per packet to which ACL permit or deny clauses are applied Traffic policies consist of policy names and policy definitions: • • Traffic policy name - A string of up to eight alphanumeric characters that identifies individual traffic policy definitions.
Maximum number of traffic policies supported on a device TABLE 30 CoS parameters for packets that use rate limiting traffic policies Packet conformance level Packet DSCP value Traffic class and 802.
Setting the maximum number of traffic policies supported on a Layer 3 device can be applied, in the hw-traffic-conditioner section of the results. The configurable tables and their defaults and maximum values can be obtained using the show default command. Setting the maximum number of traffic policies supported on a Layer 3 device NOTE This configuration is supported on FastIron devices with the exception of the FCX and ICX 6650 platforms.
Support for fixed rate limiting and adaptive rate limiting You can configure ACL-based rate limiting on the following interface types: • • • • • Physical Ethernet interfaces Virtual interfaces Trunk ports Specific VLAN members on a port (refer to "Applying an IPv4 ACL to specific VLAN members on a port (Layer 2 devices only)" section in the FastIron Ethernet Switch Security Configuration Guide ).
ACL-based adaptive rate limiting configuration Syntax: [no] ip access-group num in NOTE For brevity, some parameters were omitted from the access-list syntax. The software allows you to add a reference to a non-existent TPD in an ACL statement and to bind that ACL to an interface. The software does not issue a warning or error message for nonexistent TPDs. Use the no form of the command to delete a traffic policy definition.
Configuring ACL-based adaptive rate limiting TABLE 31 ACL based adaptive rate limiting parameters (Continued) Parameter Definition Committed Burst Size (CBS) The number of bytes per second (packets per second in ICX 6650) allowed in a burst before some packets will exceed the committed information rate. Larger bursts are more likely to exceed the rate limit. The CBS must be a value greater than zero (0).
Inspecting the 802.1p bit in the ACL for adaptive rate limiting NOTE For brevity, some parameters were omitted from the access-list syntax. The software allows you to add a reference to a non-existent TPD in an ACL statement and to bind that ACL to an interface. The software does not issue a warning or error message for nonexistent TPDs. Use the no form of the command to delete a traffic policy definition. Note that you cannot delete a traffic policy definition if it is currently in use on a port.
Specifying the action to be taken for packets that are over the limit Specifying the action to be taken for packets that are over the limit You can specify the action to be taken when packets exceed the configured CIR value for fixed rate limiting, or the CIR, CBS, PIR, and PBS values for adaptive rate limiting. You can specify one of the following actions: • • Drop packets that exceed the limit. Permit packets that exceed the limit and forward them at the lowest priority level.
ACL statistics and rate limit counting The command configures an adaptive rate limiting policy that enforces a guaranteed committed rate of 10000 kbps (10000 pkts/s in ICX 6650) and allows bursts of up to 1600 bytes (1600 packets in ICX 6650). It also enforces a peak rate of 20000 kbps (20000 pkts/s in ICX 6650) and allows bursts of 4000 bytes (4000 packets in ICX 6650) above the PIR limit.
Enabling ACL statistics with rate limiting traffic policies Syntax: [no] traffic-policy TPDname count Syntax: ip access-list extended 101 Device (config-std-nacl)# { permit | deny } protocol source destination traffic-policy TPDname Syntax: [no] ip access-group num in NOTE For brevity, some parameters were omitted from the access-list syntax. The software allows you to add a reference to a non-existent TPD in an ACL statement and to bind that ACL to an interface.
Traffic Policies NOTE In the SX-FI48GPP module only, the outputs of these commands are identical with one exception. When ACL counting is shown by show statistics traffic-policy , the Packet Count is not supported and displays "N/A". The following example shows the output from the show access-list accounting command.
Clearing ACL and rate limit counters TABLE 32 ACL and rate limit counting statistics Parameter Description Traffic Policy The name of the traffic policy. General Counters Port Region # The port region to which the active traffic policy applies. Byte Count The number of bytes (packets in ICX 6650) that were filtered (matched ACL clauses). Packet Count The number of packets that were filtered (matched ACL clauses).
Traffic Policies Metering Enabled, Parameters: Mode: Adaptive Rate-Limiting cir: 100 kbps, cbs: 2000 bytes, Counting Not Enabled Number of References/Bindings:1 pir: 200 kbps, pbs: 4000 bytes Sample output from an ICX 6650 device: device#show traffic-policy t_voip Traffic Policy - t_voip: Metering Enabled, Parameters: Mode: Adaptive Rate-Limiting cir: 100 Pkts/s, cbs: 2000 Pkts, pir: 200 Pkts/s, pbs: 4000 Pkts Counting Not Enabled Syntax: show traffic-policy TPDname To display all traffic policies, ent
CPU rate-limiting CPU rate-limiting Unnecessary traffic to the switch CPU lowers the efficiency of the CPU and delays handling of other traffic that requires processing. CPU rate limiting is a CPU protection scheme which limits certain traffic types. CPU rate limiting identifies the traffic type and assigns a maximum rate limit to the traffic type.
CPU rate-limiting 76 FastIron Ethernet Switch Traffic Management Guide 53-1003093-03
ICX 7750 Flow control and buffer management ● Priority flow control .........................................................................................................77 ● Configuring priority flow control.......................................................................................78 ● Packet buffer management.............................................................................................
Configuring priority flow control NOTE Enabling flow control on ports that have auto-neg enabled causes flap because the port pause capabilities must be advertised and negotiated again with peer. Ports that have auto-neg disabled do not experience flap. Configuring priority flow control Enables PFC globally and for a priority group. 1. 2. Enable priority flow control (PFC)globally. Device(config)# priority-flow-control enable Enable PFC for priority group (PG) 0.
ICX 7750 Flow control and buffer management sharing pool. For example, if queue 4 is at level4, queue 4 is entitled to use up to 1/9 of total sharing buffers in the sharing pool. You can configure eight levels of sharing. The actual number of buffers a queue can use depends on the current available buffers in the system. See the description of the qos egress-buffer-profile command for more information on egress buffer profiles.
Packet buffer management 80 FastIron Ethernet Switch Traffic Management Guide 53-1003093-03
Traffic Management Commands ● egress-buffer-profile........................................................................................................ 81 ● ip dscp-remark ............................................................................................................... 82 ● ip pcp-remark ................................................................................................................. 82 ● priority-flow-control.................................................................
ip dscp-remark The following example shows how to attach an egress buffer profile named egress2 to multiple ports: Device(config-mif-1/1/2-1/1/16)# egress-buffer-profile egress2 The following example shows how to remove an egress buffer profile named user2 from multiple ports: Device(config-mif-1/1/2-1/1/16)# no egress-buffer-profile egress2 History Release version Command history 8.0.10 This command was introduced. ip dscp-remark Enables remarking of the DSCP field for all IPv4 packets.
priority-flow-control Usage Guidelines The no form of this command removes PCP remarking. In the interface configuration mode, the command enables PCP remarking for each port. The command can be configured only on Layer 2 ports. The configuration can be done on a physical port, LAG, and VE port.
priority-flow-control enable priority-flow-control enable Enables priority flow control (PFC) globally. Syntax priority-flow-control enable no priority-flow-control enable Command Default Modes Usage Guidelines PFC is globally disabled. Global configuration mode The no form of this restores the default flow-control settings. To enable global PFC, symmetrical-flow-control must be disabled. You must enable PFC globally before you configure it for priority groups. Priority flow control and 802.
Traffic Management Commands You can attach an egress buffer profile to a port. You must configure the no qos egress-buffer-profile command to detach a profile from any ports that are using it before you can configure the no qos egress-buffer-profile command to delete it. The higher the sharing level, the better the port absorb micro-burst. However, higher sharing level of 7 and 8 may compromise QoS functions and create uneven distribution of traffic during congestions.
qos priority-to-pg Examples The following example shows how to create an egress buffer profile named port-40G.
qos scheduler-profile Configures the internal priority based on classification in the range 0 to 7. priority-PG-map Specifies the internal priority-to-PG mapping. The range is 0 to 3. Modes Usage Guidelines Global configuration mode The no form of this command restores the default priority-to-PG map. You must configure the priority-flow-control enable command to enable PFC globally before you configure priority-to-PG mapping.
Traffic Management Commands no qos scheduler-profile user-profile-name Command Default Parameters A user scheduler profile is not configured. user-profile-name Specifies the name of the scheduler profile to be configured. mechanism scheduling-mechanism Configures the queue assignment with the specified scheduling mechanism . The following scheduling mechanisms are supported: mixed-sp-wrr Specifies mixed strict-priority (SP) and weighted scheduling. strict Specifies SP scheduling.
Traffic Management Commands Per-queue Details Bandwidth Percentage Class 1 3 Class 2 3 Class 3 3 Class 4 3 Class 5 3 Class 6 7 Class 7 75 The default qos-profile weights for each queue using a mixed QoS mechanism are as follows: Per-queue Details Bandwidth Percentage Class 0 15 Class 1 15 Class 2 15 Class 3 15 Class 4 15 Class 5 25 Class 6 sp Class 7 sp The total weight (wt0-wt7) in both weighted and mixed mechanism must be 100%. The minimum value for any weight is 1.
scheduler-profile The following example shows how to configure a QoS scheduler profile named user3, with mixed SP and weighted scheduling: Device(config)# qos scheduler-profile user3 mechanism mixed-sp-wrr The following example shows how to remove a QoS scheduler profile named user3: Device(config)# no qos scheduler-profile user3 History Release version Command history 8.0.10 This command was introduced. scheduler-profile Attaches a scheduler profile to one or more ports.
show priority-flow-control show priority-flow-control Displays the priority flow control (PFC) on the system.
show qos priority-to-pg History Release version Command history 8.0.10 This command was introduced. show qos priority-to-pg Displays priority-to-priority-group (PG) mapping for priority flow control (PFC).
show qos scheduler The following example enables flow control on all priorities and shows the priority-to-PG mapping .
store-and-forward The following example displays information for all the scheduler profiles configured in the system: Device(config)# show qos scheduler-profile all User Scheduler Profile: user1 Scheduling Option: Weighted round-robin Ports attached: 1/1/1 Per Queue details: Bandwidth% Traffic Class 0 1% Traffic Class 1 1% Traffic Class 2 10% Traffic Class 3 10% Traffic Class 4 10% Traffic Class 5 10% Traffic Class 6 20% Traffic Class 7 38% User Scheduler Profile: user2 Ports attached: -- Scheduling Optio
symmetrical-flow-control enable and store-and-forward mode. The store-and forward command changes the switching methodology to store-and-forward. A store-and-forward switch makes a forwarding decision on a data packet after it has received the whole frame and checked its integrity, a cut-through switch engages in the forwarding process soon after it has made the forwarding decision of an incoming frame. With cut-through switching, a packet may start to forward before the entire packet has been received.
Traffic Management Commands Modes Usage Guidelines Global configuration mode The no form of this restores the default flow-control settings. By default, the system runs in tail-drop mode, with all ports honoring 802.3x flow control and disabling 802.3x transmit. The symmetrical-flow-control enablecommand enables transmission of 802.3x pause frames. Configuring the symmetrical-flow-control enable command changes priority-to-PG mapping.
Index A D ACL enabling statistics 70 ACL-based rate limiting clearing counters 73 configuring 65 specifying action to be taken for packets that are over the limit 69 statistics 70 using traffic policies 64 viewing counters 71 DSCP and CoS global remarking 29 F feature support Quality of Service 11 rate limiting and rate shaping on FastIron X series and FCX and ICX series switches 45, 53 traffic policies 61 B I broadcast, multicast, and unknown traffic Interface broadcast limit 54–56 ip access-gr
802.1p priority override 28 assigning static MAC entries to priority queues 28 behavior for Layer 2 (802.
