3Com CoreBuilder 3500, Implementation Manual, Page: 517 / 592

RSVP 517
To use RSVP, you must be routing. (RSVP operates at Layer 3 for IP-based
data flows.) Endstations in the configuration must support RSVP in order
to request the reservation of bandwidth through the network.
By default, RSVP is disabled on the system. If you decide to use RSVP, it is
recommended that you use the default RSVP settings.
RSVP Terminology Familiarize yourself with the following RSVP terms:
■
RSVP flow — A data stream that operates in simplex, going one way
from the origin to multiple destinations. The flows go from a set of
senders to a set of receivers.
■
Reservation style — The types of multicast flows that RSVP installs:
■
Fixed filter (distinct) style — A flow originating from one sender
only (for example, a video application). This style requires a
separate reservation per sender on each transmission type.
■
Shared explicit — A shared-reservation flow originating from a
limited number of senders (for example, an audio application). This
style identifies the flows for specific network resources. A single
reservation can be applied to all senders in the set.
■
Wildcard filter — A shared-reservation flow from all senders.
■
Total reservable bandwidth percentage — Controls the admission
control policy. RSVP begins to refuse reservations when the requested
bandwidth on an output link exceeds the total reservable bandwidth.
You specify a percentage of the output link (a value of from
0 to 200,
with 50 as the default). This is the amount of bandwidth that you
allow RSVP to reserve in the system. You can over-subscribe (over 100)
and specify a value up to 200.
■
Maximum per-reservation bandwidth
— The largest reservation
that RSVP attempts to install. Specify this bandwidth using a
percentage of the output link (a value of from
0 to 100; 50 is the
default).