To Next Page

To Previous Page

When a PCEP session terminates, the PCC starts two timers without immediately

deleting the PCE-initiated LSPs – delegation cleanup timeout and lsp cleanup timer –

to avoid disruption of services. During this time, an active stateful PCE can acquire

control of the LSPs provisioned by the failed PCE, by sending a create request for the

LSP.

Control over PCE-initiated LSPs reverts to the PCC at the expiration of the delegation

cleanup timeout. When the delegation cleanup timeout expires, and no other PCE has

acquired control over the LSP from the failed PCE, the PCC takes local control of the

non-delegated PCE-initiated LSP. Later, when the original or a new active stateful

PCE wishes to acquire control of the locally controlled PCE-initiated LSPs, the PCC

delegates these LSPs to the PCE and the lsp cleanup timer timer is stopped.

A PCE may return the delegation of the PCE-initiated LSP to the PCC to allow LSP

transfer between PCEs. This triggers the lsp cleanup timer for the PCE-initiated LSP.

The PCC waits for the LSP cleanup timer to expire before removing the non-delegated

PCE-initiated LSPs from the failed PCE.

When the lsp cleanup timer expires, and no other PCE has acquired control over the

LSPs from the failed PCE, the PCC deletes all the LSPs provisioned by the failed PCE.

3. LSP signaling—On receiving one or more LSP parameters from the main active stateful

PCE, the PCC re-signals the TE LSP based on the PCE provided path. If the PCC fails

to set up the LSP, it notifies the PCE of the setup failure and waits for the main PCE

to provide new parameters for that LSP, and then re-signals it.

When the PCE specifies a path that is incomplete or has loose hops where only the

path endpoints are specified, the PCC does not perform local constraint-based routing

to find out the complete set of hops. Instead, the PCC provides RSVP with the PCE

provided path, as it is, for signaling, and the path gets set up using IGP hop-by-hop

routing.

Considering the topology used in Figure 37 on page 695, Figure 39 on page 701 illustrates

the partial client-side PCE implementation in the MPLS RSVP-TE enabled network. The

ingress routers A and G are the PCCs that are configured to connect to the external

stateful PCE through a TCP connection.

The PCE has a global view of the bandwidth demand in the network and performs external

path computations after looking up the traffic engineering database. The active stateful

PCE then modifies one or more LSP attributes and sends an update to the PCC. The PCC

uses the parameters it receives from the PCE to re-signal the LSP.

ACX Series Universal Access Router Configuration Guide

Juniper ACX2000 Configuration Guide

Other manuals for Juniper ACX2000