
Configuring IP Multicasting Services
A-28 114064 Rev. B
Parameter: Traffic Queuing Algorithm
Path: Configuration Manager > XCVR, HSSI, MCT1, or COM Connector configured
for the ST2 protocol > Edit Line Resources > Edit Line Resources
Default: None
Options: None
| Priority
Function: Specifies the queuing algorithm for all reserved traffic.
Instructions: Select None to use best-effort scheduling. Use best-effort scheduling if you
want to use the resource reservation protocol (ST2) to control admission of
flows to the network, but do not want to explicitly schedule each flow’s packets.
MIB Object ID: 1.3.6.1.4.1.18.3.5.16.2.1.3.1.5
Parameter: Policing Algorithm
Path: Configuration Manager > XCVR, HSSI, MCT1, or COM Connector configured
for the ST2 protocol > Edit Line Resources > Edit Line Resources
Default: None
Options: None
| Leaky Bucket
Function: Specifies whether or not to use the Leaky Bucket policing algorithm for
reserved traffic. With Leaky Bucket policing, 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 such policing requires additional
processing by the router.
Instructions: Select None to bypass policing if an upstream router is policing traffic, or if the
applications generating the reserved traffic consistently adhere to the flowspec
and do not require policing.
Enter Leaky Bucket to apply a Leaky Bucket policing algorithm to reserved
traffic.
MIB Object ID: 1.3.6.1.4.1.18.3.5.16.2.1.3.1.6
Kommentare zu diesen Handbüchern