TOI Author :: Josh Pfosi

SWitch Aggregation Group (SWAG) is a feature in EOS that supports combining multiple physical switches into a single logical system with shared control plane and distributed data plane, simplifying network management and increasing scalability. This document describes how to configure and troubleshoot a SWAG.

This feature implements RFC3107 that allows carrying a label stack with BGP route updates, using multi protocol BGP.

This feature adds support for CPU traffic policy capable of matching and acting on IP traffic which would otherwise hit the CPU. This policy is capable of permitting traffic from trusted sources, while rejecting untrusted traffic. It supports matching on a variety of IP packet header information such as DSCP, L4 port values, fragmentation bits, etc. as well as a number of actions such as permit, deny, and police. To prevent a malicious source from overloading the CPU, this traffic policy will take effect in the switching hardware, before the traffic is processed by the kernel. This feature provides a shorthand syntax for securing L3 protocol peers, in particular, BGP neighbors.

This feature adds support for "sequential" processing of route-map 'set ext/community' clauses. This feature is enabled via a configuration knob and there is no change in behavior without enabling this knob. The default route-map processing behavior can be summarized as "add then delete".

This feature adds support for BGP peering over IPv6 link local addresses. As defined in RFC 4007, IPv6 addresses have

This feature adds support for a 'match route type' route map match clause in release 4.20.1F. This clause allows