User guide

Configuring Automatic Fabric Automatic Fabric Discovery Examples
OmniSwitch AOS Release 7 Switch Management Guide March 2015 page 14-17
Automatic Fabric Discovery Examples
This section contains the following Automatic Fabric discovery examples:
• “Automatic Fabric Configured in the Network Core” on page 14-17.
• “Manual Configuration of the Network Core for LACP, SPB, and MVRP” on page 14-18.
• “Automatic Fabric Process for Automatic IP Configuration” on page 14-19.
Automatic Fabric Configured in the Network Core
In this example, the network core is manually configured to be in Automatic Fabric mode on a subset of
ports. When user enables the discovery window, auto discovery is triggered for discovery time window.
Automatic Fabric in the Core
1 OS6900 with no boot.cfg configuration file, Automatic Fabric enabled by default. The switch has
multiple connections to the core (which has Automatic Fabric enabled on the connected ports).
2 LLDP exchanges port properties and automatically discovers LACP ports.
3 LACP with the same admin key is exchanged. Multiple ports with the same admin key are detected and
a link aggregate is formed and configured on both the core and edge switches.
4 After the LACP discovery window expires, the SPB discovery starts. SPB BVLANs and control
BVLANs are exchanged and adjacencies are saved.
5 MVRP control frames are exchanged for all non-BVLANs. VLANs received through MVRP frames
are associated with the ports on which MVRP frames are received.
6 The automatically discovered configuration remains in switch memory on the OS6900 as well as on
the core switches, but a manual write memory command must be entered to make it permanent in the
boot.cfg file and saved across switch reboots if the auto-fabric config-save admin-state is not enabled.
Ports which already have a configuration are not eligible for automatic discovery on the next reboot.
Virtual Chassis in core with
auto fabric enabled on a
subset of ports.
OS6900
LAG
1
2
3
6
4
5
VC - VFL