• IP addresses on the MCT management interface should not be used for static congurations on neighboring devices.
• For MCT devices congured 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 and on the VRRP backup, so as to disable
short path forwarding when it loses its relevance
• VRRP or VRRP-E shouldn't be used along with OSPF or BGP on the same MCT member VE.
NOTE
To prevent unintended trac forwarding by the CPU, Brocade recommends disabling ICMP redirect globally when VRRP or
VRRP-E is congured.
MCT conguration examples
The examples in this section show the topology and
conguration for a single-level MCT deployment, VRRP/VRRP-E over MCT, OSPF
over MCT and BGP over MCT.
MCT
conguration for a single-level MCT deployment
The following gure shows a sample conguration for a single-level MCT. The associated conguration follows.
FIGURE 41 Sample Conguration for a single-level MCT
Router A - MCT conguration
This example presents the MCT conguration for Router A cluster device.
!
lag lag_routera static id 55
ports ethernet 1/1/1 to 1/1/2
primary-port 1/1/1
deploy
!
port-name "ICL-To_routerB_eth1/1/1" ethernet 1/1/1
port-name "ICL-To_routerB_eth1/1/2" ethernet 1/1/2
!
!
vlan 110 name Member-vlan by port
tagged ethernet 1/1/1 ethe 1/1/2 to 1/1/4
router-interface ve 110
!
vlan 1000 name ICL-Session-vlan by port
tagged ethernet 1/1/1 to 1/1/2
Layer 3 behavior with MCT
FastIron Ethernet Switch Layer 3 Routing
576 53-1003627-04
To Next Page
Loading...
Need help?
General
