For IPv4 and IPv6 routes:
enable bgp export route_type {{address-family} address_family} {export-policy policy-name}For VPNv4 routes:
enable bgp export remote-vpn {{address-family} ipv4-unicast} {export-policy policy-name}For IPv4 and IPv6 routes, this command enables the export of routes learned from BGP peers to the specified protocol.
For VPNv4 routes, this command enables the exchange of routes between a BGP PE router and a CE router.
| bgp | For Layer 3 VPNs, this specifies that BGP routes learned from CE routers are to be exported to remote PE routers. |
| route_type | Specifies the BGP export route type. Valid route_type values are: blackhole; direct; isis; isis-level-1; isis-level-2; isis-level-1-external; isis-level-2-external; ospf; ospf-extern1; ospf-extern2; ospf-inter; ospf-intra; rip; static; ospfv3; ospfv3-extern1; ospfv3-extern2; ospfv3-inter; ospfv3-intra; ripng; |
| address-family | Valid address_family values are: ipv4-unicast; ipv4-multicast; ipv6-unicast; ipv6-multicast |
| remote-vpn | For Layer 3 VPNs, this specifies that BGP routes learned from remote PE routers are to be exported to the local VRF. |
| policy-name | Name of policy to be associated with network export. Policy can filter and/or change the route parameters. |
Disabled.
If no address family is specified for an IPv6 protocol, the default IPv6 unicast family applies; otherwise if no address family is specified, IPv4 unicast is the default.
The exporting of routes between any two routing protocols is a discrete configuration function. For example, you must configure the switch to export routes from OSPF to BGP and, if desired, you must configure the switch to export routes from BGP to OSPF. You must first configure both protocols and then verify the independent operation of each. Then, you can configure the routes to export from OSPF to BGP, and the routes to export from BGP to OSPF.
You can use a policy to associate BGP attributes including Community, NextHop, MED, Origin, and Local Preference with the routes. A policy can also be used to filter out exported routes.
Using the export command to redistribute routes complements the redistribution of routes using the configure bgp add network command. The configure bgp add network command adds the route to BGP only if the route is present in the routing table. The enable bgp export command redistributes an individual route from the routing table to BGP. If you use both commands to redistribute routes, the routes redistributed using the network command take precedence over routes redistributed using the export command.
Note
For this command to execute, the specified protocol must support the specified address family. For example, the command fails if you specify OSPF and the IPv6 unicast address family. You can specify blackhole, direct, static, and IS-IS routes with IPv4 or IPv6 address families.
The following command enables BGP to export OSPF routes to other BGP routers:
enable bgp export ospf
The following command enables export of Layer 3 VPN Routes recevied from the PE Core in a VPN-VRF to its CE peers:
enable bgp export remote-vpn address-family ipv4-unicast
This command was first available in ExtremeXOS 10.1.
This command required a specific license in ExtremeXOS 11.1.
The blackhole option was added in ExtremeXOS 12.1.3.
Support for IPv6 was added in ExtremeXOS 12.6 BGP.
Support for Layer 3 VPNs was added in ExtremeXOS 15.3.
This command is available on platforms that support the appropriate license. For complete information about software licensing, including how to obtain and upgrade your license and which licenses support the BGP feature, see the ExtremeXOS 32.1 Feature License Requirements document.