Configuring Multi-chassis Link Aggregation
Configuring MCLAG
OmniSwitch AOS Release 7 Network Configuration Guide
June 2013
page 10-27
Configuring MCLAG
This section describes commands to configure MCLAG on a switch.
•
“MCLAG Configuration Guidelines” on page 10-27
•
“Configuring the Chassis ID” on page 10-30
•
“Configuring the Group ID” on page 10-30
•
“Creating the Virtual Fabric Link (VFL)” on page 10-30
•
“Configuring the Hello Interval” on page 10-31
•
“Configuring the IPC-VLAN” on page 10-31
•
“Configuring Aggregate Identifier Ranges” on page 10-31
•
“Configuring MCLAG Aggregates” on page 10-31
•
“Configuring the VIP VLAN” on page 10-32
Note
. See
“Quick Steps for Configuring MCLAG” on page 10-5
” for a brief tutorial on configuring these
parameters on an OmniSwitch.
MCLAG Configuration Guidelines
The following sections provide configuration guidelines to follow when configuring MCLAG on an
OmniSwitch.
General
•
MCLAG functionality is only active for switches on which an MCLAG chassis ID is configured.
•
The Spanning Tree protocol can run on MCLAG chassis peers, however STP is disabled on MCLAG
ports.
•
One of the MCLAG chassis peers should be the root bridge so that the VFL is always in forwarding
mode.
•
Due to the MG-LAG loop avoidance feature, non-unicast traffic received on the VFL is never flooded
on local MCLAG ports.
•
There is no synchronization of routing information between MCLAG peers.
Chassis ID
•
Each peer switch requires a chassis ID number that is unique within the multi-chassis group. The
MCLAG feature currently supports two peer switches per multi-chassis group, so ID 1 or 2 is used.
•
If a duplicate chassis ID is detected within the group, then the operational state of the chassis will
remain down.
•
A switch reboot is required after the chassis ID is configured.
For information about configuring the Chassis ID, see