[no] pcep
config>router
This command enables the Path Computation Element Communication Protocol (PCEP) and enters the context to configure PCEP parameters.
The no form of the command disables PCEP.
[no] pcc
config>router>pcep
This command enables the context to configure PCC parameters.
dead-timer seconds
no dead-timer
config>router>pcep>pcc
This command configures the PCEP session dead timer value, which is the amount of time a PCEP speaker will wait after the receipt of the last PCEP message before declaring its peer down.
The dead timer mechanism is asymmetric, meaning that each PCEP speaker can propose a different dead timer value to its peer to use to detect session timeout.
The no form of the command returns the dead timer to the default value.
120
the dead timer value, in seconds
keepalive seconds
no keepalive
config>router>pcep>pcc
This command configures the PCEP session keepalive value. A PCEP speaker must send a keepalive message if no other PCEP message is sent to the peer at the expiry of this timer. This timer is restarted every time a PCEP message or keepalive message is sent.
The keepalive mechanism is asymmetric, meaning that each peer can use a different keepalive timer value at its end.
The no form of the command returns the keepalive timer to the default value.
30
the keepalive value, in seconds
local-address ip-address
no local-address
config>router>pcep>pcc
This command configures the local address of the PCEP speaker.
The PCEP protocol operates over TCP using destination TCP port 4189. The PCE client (PCC) always initiates the connection. When the user configures the PCEP local address and the peer address on the PCC, the PCC initiates a TCP connection to the PCE. When the connection is established, the PCC and PCE exchange OPEN messages, which initializes the PCEP session and exchanges the session parameters to be negotiated.
By default, the PCC checks first to determine if the remote PCE address is reachable out-of-band via the management port. If the remote address is not reachable, the PCC will check if the remote PCE address is reachable in-band. The local address configured by the user is only used for in-band sessions and is otherwise ignored. When the session comes up out-of-band, the system IP address is always used as the local address. Use the route-preference command to configure the PCC to use only out-of-band or only in-band instead.
The no form of the command removes the configured local address of the PCEP speaker.
the IP address of the PCEP speaker to be used for in-band sessions
peer ip-address [preference preference]
no peer ip-address
config>router>pcep>pcc
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.
the IP address of the PCEP peer to be used as the destination address in the PCEP session
specifies the preference value of the peer
redelegation-timer seconds
no redelegation-timer
config>router>pcep>pcc
This command configures the redelegation timer for PCE-initiated LSPs.
The no form of this command sets this value to the default.
90
route-preference {both | inband | outband}
no route-preference
config>router>pcep>pcc>peer
This command configures the route preference that PCC uses to reach the remote PCE address, which allows you to restrict the PCC to using only out-of-band or only in-band for reachability. By default, the PCC checks first to determine if the remote PCE address is reachable out-of-band via the management port. If the remote address is not reachable, the PCC will try to reach the remote PCE address in-band.
The no form of this command resets the route preference to the default behavior.
both
the PCC uses the out-of-band routing table to reach the PCC; if unsuccessful, it then uses the in-band routing table
the PCC uses only the in-band routing table to attempt to reach the PCE
the PCC uses only the out-of-band management router routing table to attempt to reach the PCE
[no] report-path-constraints
config>router>pcep>pcc
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.
the path computation on the PCE must use the first set of objects when updating a path if the PCRpt message contained a single set. If the PCRpt message contained a duplicate set, PCE path computation must use the constraints in the duplicate set.
The no form of the command disables the above behavior in case of interoperability issues with third-party PCE implementations.
report-path-constraints
[no] shutdown
config>router>pcep>pcc
config>router>pcep>pcc>peer
This command administratively disables the PCC process.
The following PCC parameters can be modified without shutting down the PCEP session:
report-path-constraints
unknown-message-rate
The following PCC parameters can only be modified when the PCEP session is shut down:
local-address
keepalive
dead-timer
peer
shutdown
tls-client-profile profile-name
no tls-client-profile
config>router>pcep>pcc>peer
This command configures a TLS client profile on the PCC. When the TLS client profile is configured, the PCC tries to establish a PCEP connection with the PCE over TLS. If the PCE sends an Open message or does not send back a StartTLS message within the time set by the tls-wait-timer command, the connection is not accepted and the TCP connection is closed and a new connection is tried within 60 s
The no form of the command removes TLS encryption from the communication between the PCC and the PCE.
no tls-client-profile
the TLS client profile name, up to 32 characters in length
tls-wait-timer [60..255]
no tls-wait-timer
config>router>pcep>pcc>peer
This command configures the time that the PCC waits before declaring a TLS handshake failure if the handshake is not established.
The no form of the command reverts to the default.
tls-wait-timer 60
the wait time in seconds
unknown-message-rate msg/min
no unknown-message-rate
config>router>pcep>pcc
This command configures the maximum rate of unknown messages that can be received during a PCEP session.
When the rate of received unrecognized or unknown messages reaches the configured limit, the PCEP speaker closes the session to the peer.
The no form of the command returns the unknown message rate to the default value.
10
the rate of unknown messages, in messages per minute