Set the Retry Limit

When the ingress LER fails to connect to the egress LER in a signaled LSP, the ingress LER tries indefinitely to make the connection unless the user sets a limit for these connection attempts.

After this limit is exceeded, the ingress LER stops trying to connect to the egress LER over the primary path. When a secondary path is configured for the LSP, it is immediately activated after the primary path fails. After the secondary path is activated, the ingress LER continues to try to connect to the egress LER over the primary path either up to the configured retry limit or indefinitely when no retry limit is set. When a connection over the primary path can be established, the secondary path is deactivated, and traffic for the LSP is again sent over the primary path.

To set the number of collection attempts, complete the following steps.

Configure the device.
```
device# configure
```
Enable the MPLS router.
```
device(config)# router mpls
```
Enable policy parameter configuration.
```
device(config-router-mpls)# policy
```
Configure the retry limit.
```
device(config-mpls-policy)# retry-limit 20
```
In this example, the retry limit is configured to 20.

Example

In the following example, the retry limit is configured with a value of 20.

device# configure 
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# retry-limit 20

Once the connection is established, the retry counter is reset to zero. In the example above, when an LSP needs to be established again, the ingress LER makes 20 attempts to establish a connection to the egress LER.