Table of Contents
Advertisement
Configuring MC-LAG
Configuring MC-LAG
This section describes commands to configure MC-LAG on a switch.
•
"MC-LAG Configuration Guidelines" on page 8-22
•
"Configuring the Chassis-ID" on page 8-24
•
"Configuring the IPC-VLAN" on page 8-24
•
"Configuring the Hello-Interval" on page 8-24
•
"Configuring Aggregate Identifier Ranges" on page 8-24
•
"Creating the Virtual Fabric Link (VFL)" on page 8-25
•
"Configuring MC-LAG Aggregates" on page 8-25
•
"Configuring the VIP VLAN" on page 8-25
Note. See
"Quick Steps for Configuring MC-LAG" on page
parameters on an OmniSwitch 10K.
MC-LAG Configuration Guidelines
The following sections provide configuration guidelines to follow when configuring MC-LAG on an
OmniSwitch 10K.
General
•
A VLAN that performs IP routing cannot span several switches throughout the entire network if any of
its member ports is a multi-chassis aggregate.
•
The Spanning Tree protocol can run on MC-LAG chassis peers, however STP is disabled on MC-LAG
ports.
•
One of the MC-LAG 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 MC-LAG ports.
•
There is no synchronization of routing information between MC-LAG peers.
Chassis-ID
•
Each chassis requires a globally unique chassis ID within the allowed range (1-2).
•
If a duplicate chassis ID is detected, then the operational state of the chassis will remain down.
•
Chassis ID information is distributed to all NIs to allow NI software to program the underlying ASICs
with the correct module ID derived from the chassis ID.
•
The switch must be rebooted after configuring the chassis ID.
For information about configuring the Chassis-ID, see
page 8-22
8-5" for a brief tutorial on configuring these
"Configuring the Chassis-ID" on page 8-24
OmniSwitch AOS Release 7 Network Configuration Guide
Configuring Multi-chassis Link Aggregation
March 2011
Advertisement
Table of Contents
