disable bgp export vr
For IPv4 and IPv6 routes, this command disables 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.|
|address-family||Specifies the address family for the exported routes. Valid types are ipv4-unicast, vpnv4.|
|vpn4||Specifies that routes from the VRF are exported as vpnv4 routes over MPBGP.|
Usage GuidelinesThis command disables 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.
- For Layer 3 VPNs, you must enter the disable bgp export vr command in the context of the VRF that supports the Layer 3 VPN.
- When the export source is the Layer 3 VPN, you can specify direct, or remote-vpn to disable route export to the VRF. The destination address family must be ipv4‑unicast.
- 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, For eg:- remote-vpn only applies to remote routes from PE redistributed to CE, hence we cannot use it with address family vpnv4. 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.
The following command disables BGP to advertise a vpnv4 route named "corp1_vpn_vrf":
disable bgp export "corp1_vpn_vrf" bgp address-family vpnv4
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.2 Feature License Requirements document.