
Configuring IP Multicasting Services
6-8 114064 Rev. B
You can select a priority queuing algorithm to schedule reserved traffic ahead of
nonreserved traffic.
Set the Traffic Queuing Algorithm to None (best-effort scheduling for reserved
traffic) or Priority (reserved traffic ahead of nonreserved) for this interface.
Specifying the Policing Algorithm
By default, the Resource Manager does not check ST2 packets against the
flowspec (policing). This assumes that an upstream router is policing traffic, or the
applications generating the reserved traffic consistently adhere to the flowspec and
do not require policing.
When using the Leaky Bucket policing algorithm for reserved traffic, the
Resource Manager makes sure that all ST2 packets using reserved bandwidth
follow the flowspec that appears in the ST2 connect request. The Resource
Manager discards any packets that do not adhere to the flowspec. Note that Leaky
Bucket policing requires additional processing by the router.
For more information about Leaky Bucket policing, see “Specifying the
Unreserved Policing Algorithm,” later in this chapter.
You can set the Policing Algorithm for this interface.
Setting the Bandwidth Interval
By default, the Resource Manager measures instantaneous bandwidth over a 10
second interval. If 10 seconds is not sufficient, you can specify a different
bandwidth interval for this interface, from 1 to 214748364 seconds.
Site Manager: Traffic Queuing Algorithm parameter: page A-28
Site Manager: Policing Algorithm parameter: page A-28
Site Manager: Bandwidth Interval (Secs) parameter: page A-29
Comentarios a estos manuales