enable ripng export

enable ripng export [direct | ospfv3 | ospfv3-extern1 | ospfv3-extern2 | ospfv3-inter | ospfv3-intra | static | isis | isis-level-1| isis-level-1-external | isis-level-2| isis-level-2-external | bgp | e-bgp i-bgp] [cost number {tag number} | policy policy-name]


Enables RIPng to redistribute routes from other routing functions.

Syntax Description

direct Specifies interface routes (only interfaces that have IP forwarding enabled are exported).
ospfv3 Specifies all OSPFv3 routes.
ospfv3-extern1 Specifies OSPFv3 external route type 1.
ospfv3-extern2 Specifies OSPFv3 external route type 2.
ospfv3-inter Specifies OSPFv3-inter area routes.
ospfv3-intra Specifies OSPFv3-intra area routes.
static Specifies static routes.
isis Specifies IS-IS routes.
isis-level-1 Specifies IS-IS Level 1 routes.
isis-level-1-external Specifies IS-IS Level 1 External routes.
isis-level-2 Specifies IS-IS Level 2 routes.
isis-level-2-external Specifies IS-IS Level 2 External routes.
bgp Specifies BGP IPv6 routes
e-bgp Specifies EBGP routes.
i-bgp Specifies IBGP routes.
cost number Specifies the cost metric, from 0-15. If set to 0, RIPng uses the route metric obtained from the route origin.
tag number Specifies a tag number.
policy-name Specifies a policy.


Disabled. However, direct routes will always be advertised for all the interfaces where RIPng is enabled. For those interfaces where RIPng is not enabled, the corresponding direct route could be redistributed if direct route export is enabled through this command.

Default tag is 0.

Usage Guidelines

This command enables the exporting of static, direct, IS-IS, and OSPFv3-learned routes from the routing table into the RIPng domain. You can choose which types of IS-IS or OSPFv3 routes are injected, or you can simply choose isis or ospfv3, which will inject all learned routes (of all types) for the selected protocol.

The cost metric is inserted for all RIPng-learned, static, and direct routes injected into RIPng. If the cost metric is set to 0, the cost is inserted from the route table. 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 is sample policy file which modifies the cost of redistributed routes from OSPFv3 and statically configured routes:

entry filter_rt {
	If match any {
		Route-origin ospfv3;
		Route-origin static;
	then {
		cost 10;


The following command enables RIPng to redistribute routes from all OSPFv3 routes:

enable ripng export ospfv3 cost 0


This command was first available in ExtremeXOS 11.2.

Platform Availability

This command is available on platforms with an Edge, Advanced Edge, or Core license. For licensing information, see the ExtremeXOS and Switch Engine 31.7 Feature License Requirements document.