In a previous blog post, I elaborated on the general rules about fabric, how it works, and the protocols used. We already know that services like VLANs inside the fabric are propagated automatically, with no configuration needed within the fabric. Services should only be created at the edge of the fabric—this can be done manually or automatically. Let’s now explore the automation options.
Auto-sense
The Fabric Engine (VOSS) operating system can be used not only at the core/distribution level but also at the access layer. The biggest benefit of fabric at the edge is complete automation. VOSS supports a feature called Auto-sense, where the switch can automatically configure a port depending on the connected device (based on the LLDP protocol):
- Switch with Fabric Engine: The port will be automatically configured as NNI, and the new switch will join the fabric.
- Device with Fabric Attach support (switch or AP): Fabric Attach will be configured.
- IP Phone: A voice VLAN will be configured.
- End host with RADIUS configured on the switch: The port will be configured with 802.1x authentication.
- End host without RADIUS configured on the switch: A guest VLAN/I-SID will be assigned
Fabric Attach
Fabric Attach is also based on the LLDP protocol, similar to Auto-sense. Fabric Attach is supported by access points and switches running Switch Engine (EXOS). As mentioned in a previous blog post, in fabric services, L2VSN and L3VSN have to be mapped to an I-SID. Using Fabric Attach, a switch or access point can notify the fabric to assign a VLAN to an I-SID. Then, the VLAN will be created on the access switch, the end host port, the uplink port, and on the fabric switch. Additionally, the VLAN I-SID mapping will be created automatically.
ExtremeCloud IQ Site Engine
What are the management software tasks to achieve end-to-end automation? One of the modules of ExtremeCloud IQ Site Engine is Extreme Control, which is a NAC solution. During the authorization of an end host, NAC can also send information about VLAN to I-SID mappings. When the whole solution is used, there is no need to configure VLANs on the switches manually. By using NAC along with other capabilities like Auto-sense and Fabric Attach, everything is created automatically.
This is the third blog post about Extreme Automated Campus. Of course, it is not completely covered here—there are more advanced capabilities, but those discussed are the most commonly used in real life. In the next blog post, I will show you some practical examples and demonstrate how beautiful the whole solution is. 🙂