enable bgp export vr
For IPv4 and IPv6 routes, this command enables the PE router to export and redistribute local VRF routes to remote PE routers through BGP.
|vr||Specifies the source VPN VRF of the exported routes .|
|vr_name||Specifies the name of the source VPN VRF.|
|route_type||Specifies the source or origin of the route types to be exported to remote PE routers. Valid Types: blackhole, direct, and bgp, and static .|
|address-family||Specifies the address family for the exported routes. Valid types are vpnv4.|
(Optional) The export policy can be specified when you enable bgp export.
Specifies that routes from the VRF are exported as vpnv4 routes over MPBGP.
|policy_name||Name of export policy to be associated with export of VRF routes into BGP‘s VPN-IPv4 domain for advertisement to other PE routers.|
Usage GuidelinesThis command enables a PE router to advertise learned routes from CE routers to remote PE routers in a Service Provider's backbone. Executing this command allows the PE router to convert VRF native IPv4 routes into VPN-IPv4 route,s and advertise to all remote PE BGP neighbors as VPN-IPv4 routes.
- This export command is applicable in Parent VR context only. If you execute it in a VRF context, an error message is returned.
- The source VPN VRF must be a child of the Parent VR.
- BGP need not be added to a VPN VRF to export routes from a VPN VRF.
- The direction of where the redistribution is targeted is implicit on the keywords used. Similarly bgp only applies to EBGP routes from CE exported as VPN routes, hence we use it only with address family vpnv4. Other sources such as “static” and “direct” are redistributed both ways.
- Use show vr parent_vr_name to check routes exported from various VPN VRFs into the MBGP‘s VPN-IPv4 domain.
- Use show vr vpn_vrf_name to check routes exported from a VPN VRF into the MBGP‘s VPN-IPv4 domain.
The following command enables BGP to advertise a vpnv4 route named "corp1_vpn_vrf":
switch 19 # enable bgp export "corp1_vpn_vrf" bgp address-family vpnv4
This command was first 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.2 Feature License Requirements document.