Behaviors and Limitations of TI-LFA
The TI-LFA behaviors and limitations are listed below:
-
IGP directly programs a TI-LFA backup path requiring three or fewer labels, including the label of the protected destination prefix.
-
Programming of TI-LFA backup paths requiring more than three labels is not supported.
TI-LFA Functionality | IS-IS1 | OSPFv2 |
---|---|---|
Protected Traffic Types | ||
Protection for SR labeled traffic | Supported | Supported |
Protection of IPv4 unlabeled traffic | Supported (IS-ISv4) | Supported |
Protection of IPv6 unlabeled traffic |
Unsupported |
N/A |
Protection Types | ||
Link Protection | Supported | Supported |
Node Protection | Supported | Supported |
Local SRLG Protection |
Unsupported |
Supported |
Weighted Remote SRLG Protection |
Supported |
Supported |
Line Card Disjoint Protection |
Unsupported |
Unsupported |
Interface Types | ||
Ethernet Interfaces | Supported | Supported |
Ethernet Bundle Interfaces | Supported | Supported |
TI-LFA over GRE Tunnel as Protecting Interface | Unsupported |
Unsupported |
Additional Functionality | ||
Maximum number of labels that can be pushed on the backup path (including the label of the protected prefix) |
3 |
3 |
BFDv4-triggered |
Unsupported |
Supported |
BFDv6-triggered |
Unsupported |
N/A |
Prefer backup path with lowest total metric |
Unsupported |
Unsupported |
Prefer backup path from ECMP set |
Unsupported |
Unsupported |
Prefer backup path from non-ECMP set |
Unsupported |
Unsupported |
Load share prefixes across multiple backups paths |
Supported |
Supported |
Limit backup computation up to the prefix priority | Supported | Supported |