RSVP supports multiple path protection mechanisms and facility backup is one of them. With facility backup protection, N number of LSPs sharing the common path can be protected using one bypass tunnel which leads to resource utilization.

As shown in Figure 2-18, we have four routers R1, R2, R3, and R4.

Refer the topology defined above.

Suppose we have two primary tunnels P1 (100mbps) and P2(20mbps) ingressing from R1 and egressing at R3 (path R1->R2>R3) and asking for BW protection and we have two Bypass tunnels bp1 (120mbps) and bp2( 80mbps) type dedicated with same ingress and egress router taking Path R1->R4->R3. Below are the two cases defined in which we can observe different kinds of behavior.

1. Let the primary P1 and P2 come up.

CASE 1:

i) If the bypass bp1 (120mbps) comes up first it will give protection to both the primaries P1 and P2. bp2 should remain idle and will not give protection if there are no other primary tunnels asking for it.

CASE 2:

i) If the bypass bp2 (80mbps) comes up first it will give protection to only the primary P2 (20mbps) that will have satisfied protection which will not be changed until the bypass will go down.

ii) After that if bp1 (120mbps) comes it will provide protection to primary P1 (100mbps).

So in the CASE 1 after the protection has been provided to both the primary tunnels P1 and P2 by bypass bp1 if new primary tunnel P3 comes up with BW protection of 80mbps it would be given by bp2 (80mbps).

But in the CASE 2 as bp2 has only 60mbps left (20mbps is being used by P2) and it would not give protection to P3 tunnel and it will remain unprotected. To get the protection new tunnel has to have setup and hold priorities higher than other tunnels which are already been served with the bypass protection.

Suppose we have primary tunnel P1 (100mbps) ingressing from R1 and egressing at R3 (path R1->R2>R3) and asking for BW protection and we have Bypass tunnel bp1 (120mbps) type dedicated with same ingress and egress router taking Path R1->R4->R3. Then Bypass will start providing protection to primary P1.

If the primary went down it will start using the local protection.

After that if the secondary tunnel is provisioned, primary LSP, which is in using backup state shall continue to use backup path and will not shift over to secondary path.

This section contains a complete Facility Bypass with Ring Topology configuration.

During facility bypass integration to OcNOS SP, few issues were reported when upstream and downstream interfaces of a session happens to be same (i.e. protection path is same as upstream path) and also CSPF most likely had some issues where LSP path used to formed by crossing the head node of the path.

Considering the information available in RSVP to impose restriction, bypass tunnel path crossing primary LSP node anywhere in between merge point were not considered for mapping.

Below assumption point was added in ERD and documents were updated on the line.

If protection is requested by primary session, then initial bypass matching criteria will be to ensure egress (merge point) node of bypass will be one of the nodes of primary LSP and bypass never intersect any node of primary LSP until the merge point.

The facility bypass method takes advantage of the MPLS label stack. Instead of creating a separate LSP for every backed-up LSP, a single LSP is created that serves to back up a set of LSPs. We call such an LSP tunnel a bypass tunnel. The bypass tunnel must intersect the path of the original LSP(s) somewhere downstream of the PLR. Naturally, this constrains the set of LSPs being backed up via that bypass tunnel to those that pass through some common downstream node. All LSPs that pass through the point of local repair and through this common node that do not also use the facilities involved in the bypass tunnel are candidates for this set of LSPs.

By multiple facility bypass tunnels, we mean that multiple facility bypass tunnels can be created to the same egress/MP. For a protected LSP there could be multiple candidates available. The mapping of the LSP to one of the backup tunnels has to be efficiently done so that we can extract the maximum benefit out of those backup tunnels available

Figure 2-19 displays a sample Facility Bypass with Ring topology.

All configuration commands in the table below should be followed for each router.

Validate that the RSVP Session is up.

Validate that the RSVP bypass session is up.

To validate RSVP bypass session details:

To validate RSVP bypass Protected-lsp-list: