Brocade Multi-Service IronWare QoS and Traffic Management Configuration Guide (Supporting R05.6.00) - Manual (Page 146)

132 Multi-Service IronWare QoS and Traffic Management Configuration Guide
53-1003037-02
Egress port and priority based rate shaping
4
Configuring multicast flow control
Flow controls are available from egress to Ingress, and from fabric to Ingress. At the egress of each
Traffic Manager, there are pre-determined thresholds for consumed resources and available
resources and separate thresholds for guaranteed multicast or broadcast traffic and best-effort
multicast or broadcast traffic. When a threshold is crossed, flow control can be triggered and
multicast or broadcast traffic of the corresponding class is stopped at Ingress until resources are
below the threshold again. Flow control is disabled by default and can be enabled on an interface
using the command shown in the following.
Brocade(config)# interface ethernet 2/2
Brocade(config-if-e10000-2/2)# qos multicast flow-control
Syntax: [no] qos multicast flow-control
This command changes the flow control setting on the Traffic Manager where the interface resides.
Configuring multicast rate shaping
You can specify either guaranteed or best effort multicast rate shaping for a port in Kilobits per
second. Multicast rate shaping is configured per-port to the Ingress port.
The following example changes the best-effort multicast traffic rate to 10 Mbps.
Brocade(config)# interface ethernet 2/2
Brocade(config-if-e10000-2/2)# qos multicast shaper best-effort rate 10000
Syntax: [no] qos multicast shaper [guaranteed | best-effort ] rate bandwidth
The guaranteed option specifies that the multicast or broadcast shaper applies only to internal
multicast priority 3 (the highest multicast priority) traffic.
The best-effort option specifies that the multicast or broadcast shaper applies to internal multicast
priority 0, 1 and 2 traffic only.
The bandwidth variable specifies the maximum bandwidth in Kbps for best effort or guaranteed
multicast traffic scheduled by the Traffic Manager across the switch fabric.
Configuration considerations for multicast rate shaping
When applied to a port, the qos multicast shaper configuration is applied to all ports on the
Interface module that use the same Traffic Manager as the configured port. This is unlike the
behavior of rate shaping applied for unicast traffic. The relationship between ports and Traffic
Managers is defined in the following tables:
“Ethernet ports per traffic manager” on page 141.
Example 1
In the following example, multicast rate shaping is applied to port 1/18 on a 20-port,
10/100/1000 Copper Ethernet Interface module (NI-XMR-1Gx20-GC).
Brocade(config)# interface ethernet 1/18
Brocade(config-if-e1000-1/18)# qos multicast shaper best-effort rate 10000
In this example, the configuration will apply to Ingress traffic that arrives on any port of the
Interface module.
Example 2
In the following example, multicast rate shaping is applied to port 1/1 of a 4-port, 10 GbE Ethernet
Interface module (NI-XMR-10Gx4).