OmniSwitch os6900 Network Configuration Manual page 253

Configuring Multi-chassis Link Aggregation
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
Aggregate Range Identifiers
•
The switch must be rebooted after configuring Aggregate Range Identifier 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 MCLAG.
For more information about Aggregate Identifier Ranges, see
on page 10-31
VIP VLAN
•
Although VIP VLANs are identified as a special VLAN type for MCLAG purposes, assigning non-
MCLAG ports to this type of VLAN is supported. In addition, assigning MCLAG ports to standard
VLANs (non-VIP VLANs) is supported.
•
There are two IP addresses associated with a VIP VLAN IP interface: a management address and a
virtual IP address.
>
The management address is a unique IP address used by each switch within a multi-chassis system
to provide management services. Each peer switch must have a unique management IP address.
>
The virtual IP address is used to route packets that terminate on the multi-chassis peer switches.
Unlike the management address, the VIP address must be the same on each peer switch.
•
The IP interfaces configured on a VIP VLAN cannot be bound to any routing protocols or establish
routing adjacencies.
•
VRRP is not supported on VIP VLAN IP interfaces. IPv6 interfaces cannot be configured on a VIP
VLAN at this time.
•
The VIP VLAN routes are propagated to L3 networks via route redistribution. OSPF is the recom-
mended routing 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 to:
>
Eliminate STP on uplinks.
>
Provide Robust failover.
>
Load balance upstream traffic.
For more information on VIP VLAN, see
OmniSwitch AOS Release 7 Network Configuration Guide
"Configuring the IPC-VLAN" on page 10-31
"Configuring Aggregate Identifier Ranges"
"Configuring the VIP VLAN" on page 10-32
June 2013
Configuring MCLAG
page 10-29