Layer 3 With Mct Configuration Considerations - Brocade Communications Systems FastIron SX 800 Configuration Manual

In such a deployment, the MCT clients and the devices behind them form separate protocol adjacencies with each MCT cluster device.
These multiple L3 next hops can be utilized by deploying ECMP on the MCT client device.
NOTE
The MCT failover will not be a hitless one for layer 3 traffic since each MCT cluster device forms an independent adjacency.
When one of the MCT devices goes down, a layer 3 re-convergence is required and traffic loss is expected during this time.
FIGURE 40 OSPF and BGP configuration in an MCT-enabled network

Layer 3 with MCT configuration considerations

The following configurations apply to layer 3 behavior with MCT.
• Not all layer 3 features on MCT management interface are supported. If a VLAN is already configured with these Layer 3
features, it cannot be made the session VLAN. To see the list of unsupported features on MCT management interface, refer to
Layer 3 behavior with MCT
• IPv6 configurations are not supported on VEs of session or member VLANs.
• Route-only ports cannot be used as CCEP or ICL ports.
• Global route-only configuration and MCT cluster configuration are mutually exclusive.
• Using MCT management interface IPs for a tunnel source is not supported.
• Configuring static and policy-based routes using MCT management interface is not supported.
• Configurations to redistribute connected routes will not advertise IP addresses on an MCT management interface
• IP addresses on the MCT management interface should not be used for BGP peers on neighboring devices.
FastIron Ethernet Switch Layer 3 Routing
53-1003627-04
on page 571.
Layer 3 behavior with MCT
575