User guide

Automatic Fabric Discovery Examples Configuring Automatic Fabric
page 14-18 OmniSwitch AOS Release 7 Switch Management Guide March 2015
Manual Configuration of the Network Core for LACP, SPB, and
MVRP
In this example, the network core is not configured for Automatic Fabric. The LACP, SPB, and MVRP
protocols have been manually configured on the core.
No Automatic Fabric in the Core - To Be Updated
1 OS6900 with no boot.cfg configuration file, Automatic Fabric is enabled by default. The switch has
multiple connections to the core and the core has LACP, MVRP, and SPB manually configured, no
Automatic Fabric is enabled on the core switches.
2 LLDP runs on the edge switch, the core may or may not have LLDP enabled.
3 LACP is manually configured on the core and sends LACP frames to the OS6900. The OS6900 honors
the LACP frames since it is running Automatic Fabric and forms a link aggregate of ports with the same
admin key. There could be multiple or single link aggregate groups based on the admin key advertised.
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, 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
LACP, SPB, and MVRP
protocols manually
configured.
OS6900
LAG
1
2
3
6
4
5
VC - VFL