Auto-peering Introduction

Auto-peering is a network of cooperating interconnected devices that create an AutoBGP for any topology, providing fully redundant, multipath routing. The fabric grows dynamically and freely, not bound to any well-known topology such as Clos or Leaf/Spine.

Auto-peering nodes build a secure network by running the very scalable Border Gateway Protocol (BGP) to exchange topology and host information about IP networks. It uses IPv6 as the network layer to transport IPv4 and IPv6 traffic.

Any device connecting to an auto-peering device is an attachment point to the network. This network provides the underlay for services such as VXLAN, policy, VRF, and Fabric Attach. The AutoBGP device applies policy rules as it discovers external devices. These devices can be any IP host, LAG-attached servers and bridges, or gateway routers. By default, auto-peering allows connectivity for all attached hosts, allowing for a controller-less operation. However, interconnection (trunk ports) between fabric nodes should not be LAG ports; you should not enable port sharing on trunk ports.

Auto-peering uses a combination of the Link Layer Discovery Protocol (LLDP) and external BGP over an IPv6 Transport Layer to create the network. Auto-peering uses LLDP to discover surrounding nodes and the node‘s capabilities. LLDP is extended to advertise networking capabilities.

ExtremeXOS 31.1 introduces explicit CLI commands to configure OneConfig, which allows for ExtremeCloud IQ support for BGP Auto-peering (see Configuring BGP Auto-peering).