Configuring Dynamic Automatic Fabric Interaction with Other Features
OmniSwitch AOS Release 7 Network Configuration Guide June 2013 page 14-13
• Unlike LACP and SPB auto discovery, MVRP VLANs will not store its configuration in the switch
configuration file. The administrator will have to manually make the dynamically learned VLANs
'static' if necessary.
• MVRP will be enabled when auto fabric is enabled.
• MVRP will operate by default on all auto fabric ports/linkagg and accept registrations on all of them.
MVRP will not operate if LACP was aborted on the port for any reason.
• All VLANs will be eligible for registration by default except for BVLANs with SPB-M enabled. There
is no need to share BVLANs through MVRP as the BVLANs topology is already created via auto
discovery or will be manually configured.
• There are no 'default' MVRP VLANs.
• MVRP does not have an auto discovery time limit. Operation is continuous until the administrator
makes changes.
Virtual Chassis and MC-LAG
• Auto-Fabric cannot be used to create a VFL for a Virtual Chassis or MC-LAG.
• Auto-Fabric will only run after Virtual Chassis setup is complete.
Interfaces
• Once a configuration is detected on a port, though auto fabric will remain globally enabled, the port
state for auto fabric will be disabled so the port will not participate in the next discovery window.
• Whenever a port is brought up the discovery window will be started provided no LACP is discovered,
no SPB-M adjacencies are formed and, if MVRP is enabled, there are no registrations.
• If there is a port up seen in the device, auto-fabric discovery will start for the port in the next discovery
window. If an auto-fabric discovery window is not running, it will start immediately. If it is running, it
will start immediately after completion of the existing run.
To Next Page
Loading...