Layer 3 with MCT Configuration Considerations
The following considerations apply to
Layer 3 behavior with MCT:
Orlando has suggested to replace mangement interface
throughout thi section with session VLAN or session VLAN VE.
- Not all Layer 3 features on MCT session VLANs 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 the MCT management interface, refer to Table 116.
- IPv6 configurations are supported on VEs of member VLANs.
- Route-only ports cannot be used as CCEPs 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 the 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 must not be used for BGP peers on neighboring devices.
- IP addresses on the MCT management interface must not be used for static configurations on neighboring devices.
- For MCT devices configured with VRRP or VRRP-E, track-port features can be enabled to track the link status to the core devices on the VRRP master, so the VRRP or VRRP-E failover can be triggered on the VRRP backup, so as to disable short-path forwarding when it loses its relevance.
- VRRP or VRRP-E must not be used along with OSPF or BGP on the same MCT member VE.