Table of Contents
Advertisement
MPLS Guide
In order to indicate the path diversity and bidirectionality constraints to the PCE, the
user must configure the profile ID and path group ID of the PCE path that the LSP
belongs to. The CLI commands for this are described in
with PCEP Using the
as part of the path profile configuration and identifies implicitly the set of paths that
must have the path diversity constraint applied.
The user can only associate a single path group ID with a specific PCE path profile
ID for an LSP. However, the same path group ID can be associated with multiple
PCE profile IDs for the same LSP.
The path profiles are inferred using the path ID in the path request by the PCC. When
the PE router acting as a PCC wants to request path diversity from a set of other
LSPs belonging to a path group ID value, it adds a new PATH-PROFILE object in the
PCReq message. The object contains the path profile ID and the path group ID as
an extended ID field. In other words, the diversity metric is carried in an opaque way
from the PCC to the PCE.
The bidirectionality constraint operates the same way as the diversity constraint. The
user can configure a PCE profile with both the path diversity and bidirectionality
constraints. The PCE will check if there is an LSP in the reverse direction that
belongs to the same path group ID as an originating LSP it is computing the path for,
and will enforce the constraint.
In order for the PCE to be aware of the path diversity and bidirectionality constraints
for an LSP that is delegated but for which there is no prior state in the NRC-P LSP
database, the PATH-PROFILE object is included in the PCRpt message with the P-
flag set in the common header to indicate that the object must be processed. This is
proprietary to Nokia.
Table 35
Table 35
Note:
3HE 18686 AAAB TQZZA
CLI. The path group ID does not need to be defined in the PCE
describes the new objects and TLVs introduced in the PCE path profile.
PCEP Path Profile Extension Objects and TLVs
TLV, Object, or Message
PATH-PROFILE-CAPABILITY
TLV
PATH-PROFILE Object
1. Nokia proprietary
Use subject to Terms available at: www.nokia.com
Contained in Object
OPEN
N/A
© 2022 Nokia.
Configuring RSVP-TE LSPs
Contained in Message
OPEN
1
PCReq, PCRpt
PCEP
335
Advertisement
Table of Contents
