Enables redistribution of routes to OSPFv3.
| direct | Specifies direct routes. |
| ripng | Specifies RIPng 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. |
| host-mobility | Specifies host-mobility routes. |
| cost | Specifies a cost metric. |
| ase-type-1 | Specifies AS-external type 1 routes. |
| ase-type-2 | Specifies AS-external type 2 routes. |
| tag number | Specifies a tag value. |
| policy_map | Specifies a policy. |
The default tag number is 0. The default setting is disabled.
The cost metric is inserted for all RIPng-learned, static, and direct routes injected into OSPFv3. If the cost metric is set to 0, the cost is inserted from the route. The tag value is used only by special routing applications. Use 0 if you do not have specific requirements for using a tag. The tag value in this instance has no relationship with 802.1Q VLAN tagging.
Note
Setting the tag value is not supported in this release.The same cost, type, and tag values can be inserted for all the export routes, or a policy can be used for selective insertion. When a policy is associated with the export command, the policy is applied on every exported route. The exported routes can also be filtered using a policy.
Any other policy attribute will not be recognized and will be ignored.
The following is an example OSPFv3 export policy file:
Print
this page
Email this topic
Feedback
View PDF
Download EPUB
entry first {
if match any{
nlri 2001:db8:200:300:/64;
nlri 2001:db8:2146:23d1::/64;
nlri 2001:db8:af31:3d0::/64;
nlri 2001:db8:f6:2341::/64;
} then {
deny;
}
}
entry second {
if match any{
nlri 2001:db8:304::/48;
nlri 2001:db8:ca11::/48;
nlri 2001:db8:da36::/48;
nlri 2001:db8:f6a6::/48;
} then {
cost 220;
cost-type ase-type-2;
permit;
}
}
The following command enables OSPFv3 to export RIPng-related routes and associates a policy redist:
enable ospfv3 export ripng redist
This command was first available in ExtremeXOS 11.2.
The tag keyword was removed in ExtremeXOS 11.4.
This command is available on platforms with an Advanced Edge or Core license as described in the Feature License Requirements document.