Route Leaking Overview

Route leaking involves exporting a route from one routing instance to another routing instance.

As shown in the figure below, RBFS allows importing routes from the RIB of one instance to another instance. Additionally, the routes can be selectively imported based on the associated policy.

Route Leaking Across Instances

Route Leaking Across Instances

Guidelines and Limitations

  • Currently, the route leaking “import-rib” feature is limited to importing only IPv4 and IPv6 unicast routes.

Supported Platforms

The Route Leaking feature is supported by the Multiservice Edge images for the following Q2A and Q2C hardware platforms.

Q2A:

  • Edgecore CSR440 (AS7535-28XB)

  • UfiSpace S9510-28DC

Q2C:

  • Edgecore AGR420 (AS7946-74XKSB)

  • UfiSpace S9600-72XC

  • UfiSpace S9600-102XC

Route Leaking Policy Attributes and Match Types

The following table provides all the supported route leaking policy attributes and match types.

Attribute Type Match Types Supported

ipv4-prefix

regex
exact
longer
or-longer
prefix-length-exact
prefix-length-greater
prefix-length-greater-or-exact

ipv6-prefix

regex
exact
longer
or-longer
prefix-length-exact
prefix-length-greater
prefix-length-greater-or-exact

community

regex
exact
exists

extended-community

regex
exact
exists

large-community

regex
exact
exists

source

regex
exact