Configuring Multi-chassis Link Aggregation Configuring MC-LAG
OmniSwitch AOS Release 7 Network Configuration Guide March 2011 page 8-23
Virtual Fabric Link
• The operational state of the multi-chassis functionality depends on the VFL operational state. You
must explicitly configure the VFL and specify the physical port members.
• VFL should be configured only during the network maintenance or during the initial MC-LAG config-
uration. Changing VFL configuration at runtime can cause undesirable disruption to traffic flows.
• LACP Aggregate ID 128 is reserved and assigned to VFL. For increased resiliency, member ports
should be distributed across different switching ASICs and NI modules
• It is recommended to configure the VFL at the same time as the chassis identifier. This ensures that the
switch reboots with the correct VFL configuration.
• Only physical ports operating at 10-Gbps can be members of a VFL. The VFL is automatically a
member of all VLANs.
• All the member ports must operate at the same speed. If more than one member port is configured, they
will be bundled to form a single logical link.
• The hello interval parameter must match between chassis peers. The hello protocol runs across the
VFL link between the peers.
For more information on Virtual Fabric Link, see “Creating the Virtual Fabric Link (VFL)” on page 8-25
IPC VLAN
• The IPC VLAN ID must match between the two chassis and cannot be disabled.
• Only the VFL link can be configured as a member of the IPC VLAN.
For more information on IPC-VLAN, see “Configuring the IPC-VLAN” on page 8-24
Aggregate Range Identifiers
• The switch must be rebooted after configuring Aggregate Range Identified values.
• The local range configured on Chassis 1 must match the peer range configured on Chassis 2 and vice-
versa.
• Only an aggregate ID in the Multi-chassis range should be used for MC-LAG.
For more information about Aggregate Identifier Ranges, see “Configuring Aggregate Identifier Ranges”
on page 8-24
VIP VLAN
• A chassis identifier must already be configured on the OmniSwitch 10K.
• The only ports that can be configured as members of a VIP VLAN are the multi-chassis link aggre-
gates.
• Routing protocols cannot be configured on IP interfaces assigned to a VIP VLAN.
• VRRP cannot be configured on IP interfaces assigned to a VIP VLAN.
• VIP VLANs must have both a management IP and a virtual IP address.
For more information on VIP VLAN, see “Configuring the VIP VLAN” on page 8-25
To Next Page
Loading...
