• Author : Eamon Doyle Doyle


Support for BGP multicast aggregation

BGP address aggregation was previously only supported for IPv4 and IPv6 unicast address families. Equivalent BGP aggregation support has been added for IPV4 and IPV6 multicast address families. Existing aggregation support for IPv4/IPv6 unicast address-families has been preserved. IPv4/IPv6 Multicast aggregation support can be configured and managed through additional CLI commands within the respective multicast address-family configurations. The commands are similar to the existing unicast aggregation. The new multicast aggregation commands support the same configuration options as the equivalent unicast commands. For BGP peers where support for IPv4/IPv6 multicast address-families has been enabled, address aggregation may be performed on advertised...
Continue reading →

Route-Target Membership

Description In a Service Provider (SP) network, a Provider Edge (PE) device learns virtual private network (VPN) paths from remote PEs and uses the Route Target (RT) extended communities carried by those paths to determine which customer Virtual Routing and Forwarding (VRF) the paths should be imported into (from where they can be subsequently advertised to Customer Edge (CE) devices).   In large SP networks, each PE device may learn a significant number of VPN paths even though they might only handle a relatively small number of customer VRFs. In BGP VPN deployments (EVPN, MPLS VPN IPv4 and MPLS VPN...
Continue reading →

Support for BGP Large Community

Description BGP Large Communities, as defined in RFC8092, is now supported within EOS. Both standard (4 octets) and extended (8 octets) BGP communities are unsuitable for 4-octet ASN values due to length restrictions. Large Communities (12 octets)  are a set of values each consisting of a 4-octet ASN value plus two 4-octet local-administrator defined values. Large communities are an optional transitive attribute of variable length. There are no predefined large-community types or values. Large communities may be configured alongside standard and extended communities within route-maps using additional configuration commands. This feature is available with the multi-agent routing protocol model and...
Continue reading →

4-Octet BGP AS Specific Extended Communities

The BGP extended communities support within EOS has been enhanced to include support for 4-octet AS Extended BGP Communities (as per RFC5668). This permits 4-octet AS numbers extended-community values to be used in the same manner as 2-octet AS numbers. BGP Extended communities permit the labelling of BGP routing information, permitting administrators filter and manipulate routes based upon the community values. Each extended communities value includes a type field and a value. For the BGP extended community types ‘Two-Octet Route-target’ and ‘Two-Octet Site-of-origin’ the values specified are a 2-octet AS number and a 4-octet local-admin. Two new BGP Extended Community...
Continue reading →

BGP Fallback AS

BGP Fallback AS offers the ability for BGP peering relationships be established with either the local-as or the router-as. This assists in deployments where the peer AS is expected to change as it avoids the need for concurrent configuration updates. For example, if a service provider is updating their ASN from <old-ASN> to <new-ASN>, peers must make corresponding changes to their eBGP configuration to accept the new value. This will involve configuration updates on both sides of the peering relationship. If the updates are not co-ordinated, connectivity may be lost. With fallback AS, the service provider can configure their BGP...
Continue reading →


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

Join other followers: