# Profile 27 w/ FRR

Coming from the previous lab, configure the Tree SID to use FRR TI-LFA.

## Answer <a href="#fd8b9b3e-1815-4cb1-a576-b0e022e929b4" id="fd8b9b3e-1815-4cb1-a576-b0e022e929b4"></a>

```
#XR9
pce
 segment-routing
  traffic-eng
   p2mp
    policy Tree-SID-Pol1
     fast-reroute lfa

#XR1-XR8
group ISIS
 router isis '1'
  interface 'Gigabit.*'
   address-family ipv4 unicast
    fast-reroute per-prefix
    fast-reroute per-prefix ti-lfa
```

## Explanation <a href="#id-0406bf94-d2d1-45e7-831e-a2f9d3a1fdb1" id="id-0406bf94-d2d1-45e7-831e-a2f9d3a1fdb1"></a>

To be able to use LFA with P2MP Tree-SID policies, we must first enable TI-LFA everywhere. This is done easily using the above group configuration. TI-LFA is added to every Gigabit interface.

```
#XR1-XR8
group ISIS
 router isis '1'
  interface 'Gigabit.*'
   address-family ipv4 unicast
    fast-reroute per-prefix
    fast-reroute per-prefix ti-lfa
```

Next we simply enable FRR LFA on the policy. Since this is a static policy, we do this on the PCE.

```
#XR9
pce
 segment-routing
  traffic-eng
   p2mp
    policy POL1
     fast-reroute lfa
```

Let’s look at a transit node such as XR1. Before making this change, the outgoing interface is explicit. The nexthop is the router’s IP address on the link. These are both signs that FRR is not in use for this P2MP policy.

<div align="left"><figure><img src="https://3072390383-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkUz2C3GqnZcWhoVL6jfk%2Fuploads%2FrLJ1L7qEQcDenMQAB3Sh%2Fimage.png?alt=media&#x26;token=23d41321-c318-438c-b951-77e53175db7a" alt=""><figcaption></figcaption></figure></div>

\
After making the change, we can see on the PCE’s policy that FRR is enabled. All of the nexthops now have an exclamation point, indicating that FRR is in use.<br>

<div align="left"><figure><img src="https://3072390383-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkUz2C3GqnZcWhoVL6jfk%2Fuploads%2F6FEB66coslXtV5ZUHK99%2Fimage.png?alt=media&#x26;token=c0aa4cc4-37d5-409c-a416-48238eb99a86" alt=""><figcaption></figcaption></figure></div>

On XR1, we now see no outgoing interface. The nexthop is now the node’s RID, and it has an exclamation point. This indicates that the IP FRR for the nexthop dictates the outgoing interface now.

<div align="left"><figure><img src="https://3072390383-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkUz2C3GqnZcWhoVL6jfk%2Fuploads%2F5lLZLNp7BgIvnrhZXUtw%2Fimage.png?alt=media&#x26;token=ef679250-b186-4902-b67d-50780b8143ca" alt=""><figcaption></figcaption></figure></div>

Under normal circumstances, the direct link to R3 is used. But under FRR protection conditions, the multicast traffic is tunneled to R3 via the link to R2 (Gi0/0/0/0.3012).

<div align="left"><figure><img src="https://3072390383-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkUz2C3GqnZcWhoVL6jfk%2Fuploads%2FDw0Z5NigQAMNUFng08qB%2Fimage.png?alt=media&#x26;token=b59e2d48-7e6c-4d52-b53c-24bf3642b4c2" alt=""><figcaption></figcaption></figure></div>

The backup path will push two labels on top of label 15001: {16004/16003}.

<div align="left"><figure><img src="https://3072390383-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkUz2C3GqnZcWhoVL6jfk%2Fuploads%2FAkOKkXlxbeDr4wS8xtfG%2Fimage.png?alt=media&#x26;token=d2422f4a-0d8c-4903-8a49-a756f44436f9" alt=""><figcaption></figcaption></figure></div>
