Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 698)

668 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
L2VPN support for L2 MCT clusters
18
• This timer is to quickly detect CCP communication between the MCT peers and to failover
quickly. This failure can happen due to route flaps or congestion in the network or in the MCT
peer nodes. (Compared to L2 or MCT peer, this is similar to ICL link down).
L2VPN peer with a L2 peer
The CCP comes up if the following is TRUE:
• Peer normal CCP session comes up
The CCP goes down if the following is TRUE:
• L2 peer CCP session goes down
The remote node down event is generated if the following condition is TRUE:
• L2 CCP session is down and keepalive VLAN does not respond
NOTE
CCP is dependent only on L2 in such a configuration
NOTE
The behavior for L2 peer only case will be similar to the original L2/MCT implementation.
Handling L2VPN spoke down
For L2VPN/MCT services to function, you must establish a spoke PW between two MCT peers for
each L2VPN service instance. This spoke PW will be used for sending traffic from standby MCT
node to the remote PE devices and also in failover scenarios. This spoke PW is like any other PW
session between 2 peers and will be established using LDP and can use any MPLS tunnel transport
mechanism (RSVP or LDP tunnel).
If the CCP is UP and L2VPN MCT Spoke PW is down, either for all L2VPN Instances or some of the
instances then,
• For the L2VPN Instances which are down, a list MCT CCEP clients are collected and trigger the
MCT infrastructure to do Master/Slave selection for those MCT clients. This ensures that for
each MCT Client only the links connected to one of the MCT node will be UP (Master) and the
other MCT node will be down (Slave).
• This ensures that if MCT Client Ports are NOT shared by L2 and L2VPN then MCT Spoke
PW going down will not affect L2.
• If there are any MCT client ports which are shared by L2 and L2VPN then the MCP Spoke
PW going down will affect both L2 and L2VPN.
• When MCT Spoke PW is down and comes up later, it will revert back to active/active MCT
clients.
CCP down handling when both L2 and L2VPN exist
When no keep-alive VLAN is configured,
• Client links status will be controlled based on loose and strict configurations. Both links can
stay up OR both links can go down OR one of them can stay up and one of they can stay down.
• There is no change in L2 behavior in this release.