GMPLS
7450 ESS MPLS Guide Page 441
If a path (also refer to the description of a GMPLS path configuration, below) without an
explicit te-link for the first hop is configured, the system will automatically select a TE Link to
use for a gLSP path based on the lowest available TE Link ID with a matching bandwidth (if a
bandwidth is configured for the gLSP). During a data-bearer link allocation request, an RSVP
-requested gLSP BW could be either a non-zero value as per RFC 3471 signal-type (see
below), or it could be zero. There are the following cases
Case 1: Requested BW is non-zero as per RFC 3471 Signal-type configuration
• When a TE (or TE/DB) link is configured in the related hop LMP checks whether the
related port BW is the same (exact match) as the requested BW, and allocates the port
(provided any other checks are successful).
• When the related Hop is empty, LMP finds a db-link port to the peer with a matching
the requested BW, and allocates it.
Case 2: Requested BW is Zero
• When TE (or TE/DB) link is configured in the related hop, LMP allocates the port
(provided the other checks are OK), and provides the port BW to RSVP to use in
signaling.
• When the related Hop is empty, LMP finds the first available db-link to the peer
(based on lower db-link Id), and allocates it and provides the port BW to RSVP to use
in signaling.
To Next Page
Loading...
