Import Routes from Other Protocols to BGP

Before importing routes from another protocol to BGP (Border Gateway Protocol), you must first configure both protocols and then verify the independent operation of each. When you import routes from another protocol, the imported routes are limited to those for the respective address family and protocol. For example, you can import IPv4 unicast routes from RIP (Routing Information Protocol) to BGP, but you cannot import IPv6 unicast routes from RIP to BGP. IPv6 routes can be imported only from IPv6 routing protocols; and IPv4 routes can be imported only from IPv4 routing protocols.

You can use route maps to associate BGP attributes including Community, NextHop, MED, Origin, and Local Preference with the routes. Route maps can also be used to filter out exported routes.

For instructions on importing routes from another protocol to BGP, refer to the chapter for the protocol from which you want to import routes.

To configure an import policy to apply to imported routes, use the following command:
configure bgp import-policy [policy-name | none]

For Layer 3 VPNs, a local PE stores the routes received from a remote PE in the VPN-VRF RIB.
To enable or disable export of these routes as IPv4 unicast routes to the CE, use the following command:
enable bgp export remote-vpn {export-policy} policy-name} {address-family [ipv4-unicast | vpnv4]}

disable bgp export remote-vpn {address-family [ipv4-unicast | vpnv4]}

Published March 2020prev | next

Email this topic

Print this page Print this page

Leave feedback Feedback