15 mins read

RSVP – Secondary Paths

1. Intro

In the previous example we tested link coloring with multiple LSPs to the same destination, which is not ideal. In this post we will configure Secondary paths.

By default, when network failures occur along the path of RSVP signaled LSPs, traffic will be dropped. The ingress LSR continues to send traffic until a PathTear message arrives. Then the ingress LSR will try to signal new path if possible. RSVP provides different traffic protection mechanisms, which can significantly improve network restoration.

Secondary paths are established only if the primary path fails. After failure the ingress router always tries to establish the primary path again. An LSP can only have one primary path, but multiple secondary paths are allowed. Secondary paths are signaled in the order they appear in the configuration.

Specifying standby under the secondary path forces the LSR to signal the path even though the primary has not failed yet. The Ingress router pushes traffic only to the primary path. The secondary path will already be established, but still waits until the primary fails. This reduces failover times as the secondary path is pre-established, but also requires additional state in the LSRs for the standby LSPs. 

It is recommended for the primary and secondary path to have constraints (ERO or link coloring) defined so that it is sure that they pass different LSRs in the network.

If a secondary path is configured the ingress LSR fails over to it even though there is another physical path that complies the primary path constraints. When the ingress LSR signals the primary path on different physical path, traffic is reverted back from the secondary path to the new primary path.

By default, the minimum time that the primary path must be UP before the traffic to revert to it is 60 seconds. By configuring that timer to 0 ensures the LSP will not revert back to the primary path. Another way to disable the revert-timer is to configure two secondary paths instead of configuring a primary and a secondary path.

WE will use the same topology.

2. Primary and Secondary paths

Instead of having 2 LSPs to R7, we will configure one LSP with a Primary and Secondary paths:

So, this time we saw one LSP with 2 different paths, if one fails the other is established. But, we will have some packet loss during the switchover from Primary to Secondary path; it takes time for the Secondary path to be signaled.

3. Standby path

There is a solution to this, we can configure the Secondary path as hot standby:

4. No constraints

Let’s see what happens if we have a Primary and Secondary path defined with constraints:

Even with no constraints, JunOS will try to establish non overlapping paths.


External Resources:

Leave a Reply