• Author : Sharad Birmiwal


EOS default route preferences

Description The document captures the default preference value (between 0 and 255) for routes from various supported protocols. Note that some the preference value may be overridden by configuration in the respective source protocols. Route Protocol/Source Default Route Preference Connected 0 Static 1 VxLAN Control Service 1 DHCP IPv6 Prefix Delegation 15 Kernel 40 OSPFv2 110 OSPFv3 110 IS-IS 115 RIP 120 iBGP 200 eBGP 200 BGP Aggregate 200 Dynamic Policy 240 Routes leaked across VRFs retain the route preference from the source VRF. Show commands The show ip route and the show ipv6 route commands show the route preference...
Continue reading →

Routing Control Functions

Description Routing control functions (RCF) is a new language that can be used to express BGP route filtering and attribute modification logic in a powerful and programmatic fashion. It supports a new set of workflows to define and apply these functions in EOS. The broader feature set includes: The base RCF language framework; Support for RCF function application to BGP neighbors; Support for matching and modifying BGP protocol attributes; Workflows to define and apply routing control functions; CLI commands to provide visibility into operational status. The following points of application are supported: Point of application Supported since Inbound BGP neighbor...
Continue reading →

Pseudowire Resolution Over User-defined Tunnel RIBs

Description This feature allows configuring user-defined tunnel RIBs for the resolution of LDP pseudowire endpoints. User-defined tunnel RIBs were introduced in EOS 4.22.0F.   Applications can have different requirements and preferences for the tunnel protocols they use. This necessitates the use of separate tunnel RIBs for specific requirements. Pseudowires, too, can be configured to be resolved over user-defined tunnel RIBs. Platform Compatibility Resolution of LDP pseudowires over user-defined tunnel RIBs is available on all platforms supporting LDP pseudowires. For the full list of supported platforms, please see LDP pseudowires. Configuration The tunnel RIB used by pseudowires is configured by the...
Continue reading →

Disabling local interface in raw mode LDP Pseudowires, when remote side is not forwarding traffic

EOS 4.20.5F introduces support for disabling local interface, when a fault is signaled by the remote peer. The Pseudowire agent will honor Pseudowire Status TLVs (type 0x096A), when received from an LDP peer, notifying that it is not forwarding traffic. On receiving any reason for the remote peer to not forward traffic, the local interface is error disabled with the error reason explained as “pseudowire.” Supported platforms The feature is supported on all platforms supporting LDP Pseudowires. Details RFC4446 defines status codes (a bit mask) for signalling the state of a pseudowire at one end. These are summarized below. 0x00000000...
Continue reading →

BGP selective route download

The BGP selective route download feature allows learning and advertising BGP prefixes without installing them in the hardware. The filtering for installation in hardware is through the route-map semantics and filtered out routes are flagged as inactive in the RIB (Routing Information Base). With the feature enabled, BGP is no longer constrained by the platform’s hardware limit and can relay much larger number of prefixes to its peers. The route-map is applied only for BGP learned paths and not on locally originating routes (e.g. BGP aggregates) or redistributed routes. BGP routes filtered out by selective route download are not used...
Continue reading →


Get every new post on this blog delivered to your Inbox.

Join other followers: