Omniswitch Aos Consistency Recommendations - OmniSwitch os6900 Network Configuration Manual

Interaction with Other Features
•
The VIP routes are propagated to L3 networks via route redistribution. OSPF is the recommended rout-
ing protocol to interoperate with VIP VLANS.
•
Configuring and enabling IP route-maps to redistribute local (VIP) routes to OSPF is required. OSPF
interfaces in the forwarding path will dynamically update and propagate VIP routes upstream to the
core routers and onwards, effectively providing visibility and bidirectional communication between
MCLAG subnets and L3 networks.
•
ECMP to upstream L3 networks is highly recommended:
>
Eliminates STP on uplinks.
>
Robust failover.
>
Load balances upstream traffic.

OmniSwitch AOS Consistency Recommendations

In addition to ensuring that the MCLAG configuration is the same between peer switches, configuring the
same values for the following non-MCLAG features is highly recommended:
•
MAC address aging timer
•
MCLAG member ports: port speed and duplex
•
Static MAC entries
•
QoS configuration
•
Port Security configuration
•
IGMP Snooping configuration
•
PIM configuration
•
IP interface configuration
•
Routing protocols configuration
•
VRRP configuration
For more information, see
OmniSwitch AOS Release 7 Software
Both peer switches operating in a multi-chassis domain must run the same version of the OmniSwitch
AOS Release 7 software.
OmniSwitch AOS Release 7 Hardware
MCLAG is not supported between two different type of OmniSwitch models. For example, only two
OmniSwitch 10K or two OmniSwitch 6900 switches can serve as peers within the same multi-chassis
domain. Mixing model types is not supported at this time.
page 10-26
"Recommended Configuration Parameters" on page
OmniSwitch AOS Release 7 Network Configuration Guide
Configuring Multi-chassis Link Aggregation
10-33.
June 2013