[no] pcep
config>router
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12
This command enables the Path Computation Element Communication Protocol (PCEP) and enters the context to configure PCEP parameters.
The no form of this command disables PCEP.
[no] pcc
config>router>pcep
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12
Commands in this context configure PCC parameters.
The no form of this command disables PCC.
dead-timer seconds
no dead-timer
config>router>pcep>pcc
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12
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, which means that each PCEP speaker can propose a different dead timer value to its peer to use to detect session timeout.
The no form of this command returns the dead timer to the default value.
dead-timer 120
Specifies the dead timer value, in seconds.
keepalive seconds
no keepalive
config>router>pcep>pcc
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12
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, which means that each peer can use a different keepalive timer value at its end.
The no form of this command returns the keepalive timer to the default value.
keepalive 30
Specifies the keepalive value, in seconds.
local-address ip-address
no local-address
config>router>pcep>pcc
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12
This command configures the local address of the PCEP speaker.
The PCEP 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.
The PCC always checks first to determine if the remote PCE address is reachable out-of-band through the management port. If the remote address is not reachable, the PCC checks if the remote PCE address is reachable in-band. If the session comes up out-of-band, the system IP address is always used. The local address configured by the user is only used for in-band sessions and is otherwise ignored.
The no form of this command removes the configured local address of the PCEP speaker.
Specifies the IP address of the PCEP speaker to be used for in-band sessions.
[no] peer ip-address
config>router>pcep>pcc
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12
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 no form of this command removes the specified peer PCEP speaker.
Specifies the IP address of the PCEP peer to be used as the destination address in the PCEP session.
[no] report-path-constraints
config>router>pcep>pcc
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12
This command enables the inclusion of LSP path constraints in the PCE report messages sent from the PCC to a PCE.
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 7210 SAS 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 this command disables the preceding 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
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12
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
The no form of this command administratively enables the PCC process.
shutdown
When the no shutdown command is issued in the configure>router>pcep>pcc context, resources are allocated to enable processing of the protocol by the node. When you issue the configure>router>pcep>pcc>shutdown command, the resources are deallocated.
unknown-message-rate msg/min
no unknown-message-rate
config>router>pcep>pcc
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12
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 this command returns the unknown message rate to the default value.
unknown-message-rate 10
Specifies the rate of unknown messages, in messages per minute.