Brocade FastIron Ethernet Switch Platform and Layer 2 Swit Manual de usuario Pagina 189

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 454
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 188
Configuration considerations
MCT devices must obtain complete routing information using static routes for Layer 3 forwarding on
MCT VLANs.
For MCT devices configured with VRRP or VRRP-E, track-port features can be enabled to track the
link status to the core devices so the VRRP or VRRP-E failover can be triggered.
Configuring several Layer 3 features on VE of the session VLAN is not supported. If a VLAN is
already configured with multiple Layer 3 features, it cannot be made the session VLAN.
Configuring UC/MC routing protocols and the IP follow feature on VEs of member VLANs is not
supported. If a VLAN is already configured in this way, it cannot be made a member VLAN.
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 VE on an MCT session VLAN 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.
IP addresses on the MCT management interface should not be used for static configurations on
neighboring devices.
The track port feature should be used for VRRP switchover and controlling the validity of the SPF
feature.
Up to 64 VRRP or VRRP-E instances are supported on an MCT cluster; however, with Jumbo
enabled, a maximum of 32 VRRP or VRRP-E instances is supported on an MCT cluster.
NOTE
To prevent unintended traffic forwarding by the CPU, Brocade recommends disabling ICMP redirect
globally when VRRP or VRRP-E is configured.
Layer 3 traffic forwarding behaviors
When one MCT device acts as a VRRP or VRRP-E master router and the peer device is the VRRP or
VRRP-E backup, the following behavior is observed:
Packets sent to a VRRP-E virtual IP address are Layer 2-switched to the VRRP-E master device for
routing.
The VRRP-E MAC address is learned by the other MCT device that acts as backup router.
Both data traffic and VRRP-E control traffic received by the VRRP backup from an MCT client must
travel through the ICL, unless the short-path forwarding feature is enabled.
When both MCT devices act as the VRRP or VRRP-E backup routers, the following behavior is
observed:
Packets sent to a VRRP-E virtual IP address is Layer 2-switched to the VRRP-E master router for
routing.
The VRRP-E MAC address is learned by both MCT devices acting as backup routers.
Both data traffic and VRRP-E control traffic travels through the links connecting them to the VRRP
master.
Multi-Chassis Trunking
FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide 189
53-1003086-04
Vista de pagina 188
1 2 ... 184 185 186 187 188 189 190 191 192 193 194 ... 453 454

Comentarios a estos manuales

Sin comentarios