TOI Author :: Eamon Doyle

A fundamental business requirement for any network operator is to reduce costs where possible. For network operators, deploying devices to many locations can be a significant cost as sending trained specialists to each site for installations is both time-consuming and expensive.

A fundamental business requirement for any network operator is to reduce costs where possible. For network operators, deploying devices to many locations can be a significant cost as sending trained specialists to each site for installations is both time-consuming and expensive.

BGP address aggregation was previously only supported for IPv4 and IPv6 unicast address families. Equivalent BGP

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).

BGP Large Communities, as defined in RFC8092, is now supported within EOS. Both standard (4 octets) and

The BGP extended communities support within EOS has been enhanced to include support for 4 octet AS Extended BGP

BGP Fallback AS offers the ability for BGP peering relationships be established with either the local as or the router