Interaction with Other Features Configuring Dynamic Automatic Fabric
page 14-12 OmniSwitch AOS Release 7 Network Configuration Guide June 2013
admin key that both devices will use later for actual LACP communication. This exchange will also
determine the possible ports that can be part of a link-aggregate. This is used only when LACP discov-
ery fails on the port.
• If a neighbor device is manually configured for LACP with lesser ports than the number of connected
ports between devices, then the rest of port in auto discovery enabled device will join/form a back up
LACP configuration.
• If SPB-M is learned on a port, auto fabric LACP can no longer be enabled on the port.
• Upon writing the auto discovered configuration to the configuration file and rebooting, the auto discov-
ered linkagg will become a manually configured linkagg.
SPB
• SPB will apply a set of default SPB backbone port configuration on the port or link aggregate formed.
By default all ports/aggregates are assumed to be a network port. If the port does not join adjacencies in
four hello interval times; the port or link aggregation will be assumed to not be a part of SPB adja-
cency.
• The default configuration that will be applied is:
> BVLANs 4000-4015 are mapped to ECT-IDs 1-16 respectively.
> Control BVLAN will be 4000 on which ISIS-SPB hellos will be sent
> Bridge priority will be 0x8000.
• If there are any BVLANs manually configured that are not in the range of 4000-4015 SPB-M discov-
ery will not run.
• If there are any VLANs configured, except BVLANs, in the 4000-4015 range SPB discovery will not
run.
• SAP information will not be automatically setup for edge/access ports. This applies to core switches or
BCBs and edge switches or BEBs core facing ports.
• SPB-M auto discovery will occur after virtual chassis setup and LACP discovery.
• All ports or auto fabric linkagg will be presumed to be SPB network ports. SPB network ports could be
single ports or link aggregation ports. ISIS IIH (Hello) PDUs will be sent out on all ports to discover
SPB-aware devices. SPB will not operate if LACP aborted discovery because of any reasons.
• At the end of the SPB-M discovery period, all ports that do not have adjacencies will no longer be
considered network (backbone facing) ports and will not be used by ISIS-SPB or be members of the
default BVIDs of auto-fabric.
• When a port that is auto discovery enabled has its first link up event or a new link-agg is formed, SPB
will attempt to form an adjacency. After four Hello periods if no adjacency is found, the port will not
be an SPB-M backbone port unless changed manually configured.
MVRP
• MVRP will be enabled globally after linkagg is formed and SPB configuration exchange is completed
between peer devices. Since this is globally enabled this remains enabled through out. MVRP is
supported only when the switch is operating in flat Spanning Tree mode and it is not supported in the
per-VLAN mode.
To Next Page
Loading...
Need help?
General