OmniSwitch os6900, Руководство по настройке сети, Страница: 246 / 942

Interaction with Other Features Configuring Multi-chassis Link Aggregation
page 10-22 OmniSwitch AOS Release 7 Network Configuration Guide June 2013
•
A loop within the MCLAG setup may occur when one end of a static MCLAG aggregate is configured
on the core peer switches before the other end is configured on the edge switches. The following
configuration options will help to prevent loops from occuring:
>
Configure the static MCLAG aggregate on the edge switches first, then configure the other end on
the core peer switches.
>
If possible, use dynamic (LACP) aggregates instead of static aggregates.
>
Disable all ports that will serve as members of the static MCLAG aggregate, configure the aggre-
gate on both ends (core and edge), then enable the member ports.
Multicast
•
DVMRP is not supported with MCLAG.
•
PIM-DM and PIM-SM are supported over MCLAG, with the exception that PIM-DM is not supported
in a back-to-back MCLAG network configuration.
•
The Designated Router should be configured on the primary MC-LAG chassis.
•
IP Multicast Switching (IPMS) does not allow routing into MCLAG VFL ports. As a result, there is no
way for multicast data traffic to be inserted into the MCLAG IPC-VLAN, which is only present on
VFL ports.
•
Enabling IPMS on the IPC-VLAN is not recommended, but doing so will only cause a slight increase
in the amount of control traffic that is sent over the VFL on the IPC-VLAN. There is no benefit to
enabling IPMS on an IPC-VLAN.
Source Learning
MCLAG is supported only when the switch is operating in the centralized source learning mode, which is
the default mode for the switch.
Server Load Balancing
•
MCLAG supports the use of Server Load Balancing (SLB) in a multi-chassis configuration. However,
only the SLB VIP Layer 3 method for directing traffic to cluster servers is supported; the QoS policy
condition method is not supported.
•
The SLB configuration must be the same on both MCLAG peer switches. Any inconsistencies in the
configuration between the two switches could impact the flow of traffic, especially in a failover
scenario.
•
The SLB feature does not perform any automatic consistency checks; it is up to the administrator to
make sure the SLB configuration is the same on both peer switches.
•
There is no synchronization of the SLB operation between the two peer switches. This means that as
servers become reachable or are unreachable, a period of time may occur during which the hashing is
different on each peer switch.
•
Even though they use the same name, the MCLAG VLAN Virtual IP (VIP) address and the SLB VIP
address must be different on the MCLAG setup.
>
The MC-LAG VLAN VIP is used to create a common IP address for both multi-chassis peer
switches.
>
The SLB VIP is used to create a common IP address for the SLB servers.