PCEP
356
MPLS Guide
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com
3HE 18686 AAAB TQZZA
peer
Syntax peer ip-address [preference preference]
no peer ip-address
Context config>router>pcep>pcc
Description This command configures the IP address of a peer PCEP speaker. The address is used as
the destination address in the PCEP session messages to a PCEP peer.
The preference parameter allows the PCC to select the preferred PCE when both have
PCEP sessions successfully established. A maximum of two PCEP peers is supported. The
PCE peer that is not in overload is always selected by the PCC as the active PCE; however,
if neither of the PCEs are signaling the overload state, the PCE with the lower IP address is
selected.
The no form of the command removes the specified peer PCEP speaker.
Parameters ip-address — the IP address of the PCEP peer to be used as the destination address in
the PCEP session
Values a.b.c.d
preference — specifies the preference value of the peer
Values 0 to 100
Default 0
report-path-constraints
Syntax [no] report-path-constraints
Context config>router>pcep>pcc
Description This command enables the inclusion of LSP path constraints in the PCE report messages
sent from the PCC to a PCE.
In order for the PCE to know about the original constraints for an LSP that is delegated but
for which there is no prior state in its LSP database; for example, if no PCReq message was
sent for the same PLSP-ID, the following proprietary behavior is observed:
• the PCC appends a duplicate of each of the LSPA, metric, and bandwidth objects in the
PCRpt message. The only difference between two objects of the same type is that the
P-flag is set in the common header of the duplicate object to indicate that it is a
mandatory object for processing by the PCE.
• the value of the metric or bandwidth in the duplicate object contains the original
constraint value, while the first object contains the operational value. This is applicable
to hop metrics in the metric and bandwidth objects only. The 7705 SAR PCC does not
support configuring a boundary on the path computation IGP or TE metrics.
To Next Page
Loading...
Need help?
General
