Tag :: OSPFv3

Add support for configuring admin distance for OSPFv3 external routes, without this OSPFv3 would always install

This feature adds the support for OSPFv3 multi-site domains (currently this feature is added for IPv6 address family only) described in RFC6565 (OSPFv3 as a Provider to Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs) ) and enables routes BGP VPN routes to retain their original route type if they are in the same OSPFv3 domain. Two sites are considered to be in the same OSPFv3 domain if it is intended that routes from one site to the other be considered intra-network routes.

An OSPF router can attract all traffic towards itself from within the OSPF network, by advertising a default route. Often it is desirable to set a route tag in this default route. This feature will add a CLI parameter to default-information originate that allows an external route tag to be set on the default route for both unconditional and conditional modes.

In an OSPFv3 Area Border Router (ABR), area filters may be used to prevent specific prefixes from being announced by an

EOS 4.17.0F adds support for BFD in OSPFv3. BFD provides a faster convergence in scaled deployments where using

OSPFv3 distribute-list is a policy construct to filter out routes received from OSPFv3 LSAs so that they will not be installed on the router even though the routes are resolved and are installable. The filtering is performed after SPF calculation and only on routes from received LSAs, not on self-originated LSAs. This feature does not affect the OSPFv3 protocol behavior of the router. LSAs are exchanged, e.g. flooded, even if the routes are not installed locally on the router.

This feature adds support for making the various OSPFv3 counters accessible via CLI.

A router keeps track of the total number of LSAs for each OSPFv3 instance. The LSA Limit feature provides a mechanism to

Configuring OSPF as PE-CE protocol enables us to distinguish between the “real external routes” and intra network routes between the sites that are stretched across VPN.  But the problem arises when VPN sites are in the same area and have a backdoor connection. With OSPFv3 as PE-CE protocol redistribution, CE routers end up getting inter-area routes (assuming the VRFs on the PE devices that connect the CE sites, are configured with the same OSPFv3 domain id) that actually belong to the same area and just happen to be multihomed to the backbone.

This document describes the feature that allows redistribution of DHCPv6 routes into OSPFv3. This

This document describes the feature that allows redistribution of routes from ISIS to OSPFv3 running on a device.

This document describes the feature that allows the redistribution of VRF leaked BGP routes into OSPFv2 and OSPFv3.

VRF Route leaking can be used when routes from one VRF are required in another VRF (e.g. in case of shared services). If VrfLeak Agent is being used to leak routes, the leaked routes (in destination VRF) can be redistributed into IGPs.

EOS 4.17.0F adds support for IPv4 address family in OSPFv3 (multiple address family support) based on RFC5838.

This document describes the OSPFv2 and OSPFv3 feature that allows enabling or disabling the inclusion of LSAs having “Down” (DN) bit set in SPF calculations. The DN Bit is a loop prevention mechanism implemented when OSPF is used as CE - PE IGP protocol.

This document describes the OSPFv3 feature that allows the setting of “Down” (DN) bit in type-5 and type-7 LSAs. The DN Bit is a loop prevention mechanism implemented when OSPFv3 is used as CE - PE IGP protocol. Its usage in OSPFv3 is explained by RFC4576. By default, OSPFv3 honors the DN-bit in type-3, type-5 or type-7 LSAs in non-default VRFs.