rift
Syntax
rift {
capabilities;
default-prefixes;
default-prefixes-advertisement;
export;
external-preference external-preference;
interface interface-name;
level;
lie-receive-address;
lie-receive-port port-number;
name name;
node-id (node-id | auto);
overload timeout seconds;
preference route-preference;
proxy-process traceoptions (file | flag | no-remote-trace);
tie-authentication (loose | none | permissive | strict);
tie-origination-key tie-origination-key;
traceoptions (file | flag | level | peer-prefixes);
}
Hierarchy Level
[edit protocols]
Description
Enabling tracing can adversely impact scale and performance and may increase security risk. We strongly recommend using the trace, tracing, or traceoptions commands only under the guidance of a JTAC support engineer. After collecting the debug information, immediately disable tracing to minimize risk and restore normal system performance.
Configure the Routing in Fat Trees (RIFT) protocol for IP abrics that have CLOS-based and fat tree model topologies.
The RIFT protocol enables:
Automatic disaggregation of prefixes on link and node failures.
Minimal storing of routing state information at every level.
Zero-configuration capabilities with automatic pruning.
Load balancing of traffic towards the spine based on available bandwidth.
Synchronization of a limited key-value data-store that can be used after protocol convergence.
Options
| capabilities | Enable the RIFT capability of reducing flooding globally. See capabilities for more information. |
||||||||
| deafult-prefixes | Explicitly specify default prefixes generated in southbound direction. See default-prefixes for more information. |
||||||||
| default-prefixes-advertisement (always | never) | (Optional) Enable default route generation strategy.
|
||||||||
| export | Enable exporting of routes from other protocols into the RIFT protocol. See export for more information. |
||||||||
| external-preference external-preference | —(Optional) External route preference for the RIFT protocol. The external preference configured is analogous to the OSPF configuration. This value is shown when RIFT installs the preference as static route values.
|
||||||||
| interface | (Optional) Configure the interfaces for the RIFT protocol. See interface for more information. |
||||||||
| level | (Optional) Configure the level to identify the role of node in the RIFT topology. See level for more information. |
||||||||
| lie-receive-address | (Optional) Configure the address on which the link information elements (LIEs) should be received. See lie-receive-address for more information. |
||||||||
| lie-receive-port port-number | (Optional) Port on which link information elements (LIES) should be received.
|
||||||||
| name name | (Optional) Name of the node for identification. |
||||||||
| node-id (node-id | auto) | (Optional) ID of the configured node, or enable zero touch provisioning where the node ID is configured automatically. |
||||||||
| overload | (Optional) Configure the overload bit that takes the node out of traffic bearing paths.
|
||||||||
| preference route-preference | (Optional) Route preference for the RIFT protocol.
|
||||||||
| proxy-process | (Optional) Configure the proxy process options for the RIFT protocol. |
||||||||
| tie-authentication (loose | none | permissive | strict) | (Optional) Configure the method to authenticate received TIEs (inner fingerprint).
|
||||||||
| tie-origination-key tie-origination-key | (Optional) Configure the key ID used to protect self-originated TIEs (inner key).
|
||||||||
| traceoptions | (Optional) Enable traceoptions for the RIFT protocol. |
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 19.4R1.