Brocade BigIron RX Series Configuration Guide - Manual (Page 660)

582 BigIron RX Series Configuration Guide
53-1002484-04
MCT for VRRP or VRRP-E
20
BigIron RX# Dec 5 16:04:35 CLUSTER MDUP: Received MAC FLUSH message, option:
Flush Client Rbridge, cluster_id: 1, Peer Rbridge: 1, Flush Rbridge: 400, vlan: ,
port_id: 65535
Dec 5 16:04:35 CLUSTER MDUP: Received MAC FLUSH message, option: Flush Rbridge,
cluster_id: 1, Peer Rbridge: 1, Flush Rbridge: 1, vlan: , port_id: 12
Dec 5 16:04:35 CLUSTER MDUP: Received MAC INFO message, Type: Rbridge, cluster:
1, vlan: , Rbridge id: 400
Dec 5 16:04:35 CLUSTER FSM: Received CCRR message from peer when CCP is up (value
= 0190001a)
Dec 5 16:04:35 CLUSTER FSM: cluster id 1, client id 400, old state: Up, event:
Remote Down
Dec 5 16:04:35 CLUSTER FSM: sending EVENT_ID_MCT_REMOTE_CCEP_DOWN event
SYSLOG: <46>Dec 5 16:04:35 Brocade CLUSTER FSM: Cluster MCT-VPLS (Id: 1), client
R4 (RBridge Id: 400) - Remote client CCEP down
Dec 5 16:04:35 CLUSTER FSM: Sending client fsm state to LP, state 3
Dec 5 16:04:35 CLUSTER FSM: new state: Local Up, master: FALSE
Dec 5 16:04:35 CLUSTER FSM: Received CCRR message from peer when CCP is up (value
= 0190001a)
Dec 5 16:04:35 CLUSTER MDUP: Convert CCR to CCL for cluster_id: 1, client rbridge
id = 400
SYSLOG: <41>Dec 5 16:04:37 Brocade DOT1AG: Remote MEP 4000 in Domain VPLS_SP, MA
vpls_420 aged out
SYSLOG: <41>Dec 5 16:04:39 Brocade DOT1AG: Remote MEP 4000 in Domain VPLS_SP, MA
vpls_420 become UP state
Dec 5 16:04:39 CLUSTER FSM: Received CCRR message from peer when CCP is up (value
= 0190001e)
Dec 5 16:04:39 CLUSTER FSM: cluster id 1, client id 400, old state: Local Up,
event: Remote Up
Dec 5 16:04:39 CLUSTER FSM: sending EVENT_ID_MCT_REMOTE_CCEP_UP event
SYSLOG: <46>Dec 5 16:04:39 Brocade CLUSTER FSM: Cluster MCT-VPLS (Id: 1), client
R4 (RBridge Id: 400) - Remote client CCEP up
Dec 5 16:04:39 CLUSTER FSM: Sending client fsm state to LP, state 2
Dec 5 16:04:39 CLUSTER FSM: new state: Up, master: FALSE
Dec 5 16:04:39 CLUSTER FSM: Received CCRR message f
Syntax: [no] debug cluster mdup
MCT for VRRP or VRRP-E
This section describes the support of VRRP or VRRP-E for MCT.
Two-node MCT scenario
Figure 97 shows the two-node MCT scenario in which one MCT switch (Switch A) acts as the VRRP-E
master router and the other MCT switch (Switch B) acts as a VRRP-E backup router. S1 is the
MCT-unaware switch connected over MCT to the two MCT peer switches. The two MCT peer
switches connected through an ICL act as a single logical switch. E1 and E2 are CCEP-connected
end stations, which are connected through an IEEE 802.3ad LAG across the MCT pair.