Ingress traffic shaping per multicast stream, Implementation considerations – Brocade Multi-Service IronWare QoS and Traffic Management Configuration Guide (Supporting R05.6.00) User Manual
Page 79

Multi-Service IronWare QoS and Traffic Management Configuration Guide
65
53-1003037-02
Egress port and priority based rate shaping
3
Ingress traffic shaping per multicast stream
Internet Protocol Television (IPTV) multicast streams on an individual inbound physical port are rate
shaped to a specified rate and are prioritized over the broadcast or unknown-unicast traffic. Each
IPTV multicast stream is queued separately and is scheduled independently to the outbound ports.
The IPTV rate shaping reduces burstiness in the source stream.
NOTE
The number of active IPTV multicast streams for which per stream ingress shaping can be applied
is limited to 512.
Implementation considerations
The considerations for implementing the multicast rate shaping are as follows:
•
At least the rate or the priority value must be specified.
•
A maximum of 32 profiles and 64 profile-ACL bindings are allowed for multicast traffic.
•
A single profile can be bound to multiple ACLs.
•
An ACL can be associated only to one profile at a time.
•
Either standard or extended ACLs can be used for multicast traffic shaping.
-
When a standard ACL is used, the address specified is treated as a group address and not
as a source address.
-
When an extended ACL is used, the source and the destination addresses are treated as
the source and group address of the multicast stream, respectively.
Figure 1
shows the type of IPTV channels and the bandwidth requirements for each type of
channel. The following conventions are used in the figure:
•
SDTV denotes Standard Definition Television
•
HDTV denotes High Definition Television
NOTE
This feature is supported only on the 4x10 and 24x1 interface modules.