Enables RIP to redistribute routes from other routing functions.
|bgp||Specifies BGP routes.|
|direct||Specifies interface routes (only interfaces that have IP forwarding enabled are exported).|
|e-bgp||Specifies E-BGP routes.|
|i-bgp||Specifies I-BGP routes.|
|ospf||Specifies all OSPF routes.|
|ospf-extern1||Specifies OSPF external route type 1.|
|ospf-extern2||Specifies OSPF external route type 2.|
|ospf-inter||Specifies OSPF-inter area routes.|
|ospf-intra||Specifies OSPF-intra area routes.|
|static||Specifies static routes.|
|isis||Specifies IS-IS routes.|
|isis-level-1||Specifies ISIS Level 1 routes.|
|isis-level-1-external||Specifies ISIS Level 1 External routes.|
|isis-level-2||Specifies ISIS Level 2 routes.|
|isis-level-2-external||Specifies ISIS Level 2 External routes.|
|cost number||Specifies the cost metric, from 0-15. If set to 0, RIP uses the route metric obtained from the route origin.|
Specifies a tag number.
Specifies a policy.
This command enables the exporting of BGP, static, direct, and OSPF-learned routes into the RIP domain. You can choose which types of OSPF routes are injected, or you can simply choose ospf, which will inject all learned OSPF routes regardless of type.
The cost metric is inserted for all RIP-learned, static, and direct routes injected into RIP. If the cost metric is set to 0, the cost is inserted from the route. For example, with BGP, the cost could be the MED or the length of the BGP path. The tag value is used only by special routing applications. Use 0 if you do not have specific requirements for using a tag.
Each protocol can have a policy associated with it to control or modify the exported routes.
The following command enables RIP to redistribute routes from all OSPF routes:
# enable rip export ospf cost 0
This command was first available in ExtremeXOS 10.1.
This command is available on all platforms with an Edge or Base license or higher as described in the ExtremeXOS 32.2 Feature License Requirements document.