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

Multi-Service IronWare Switching Configuration Guide 667
53-1003036-02
L2VPN support for L2 MCT clusters
18
• This configuration is not mandated by configuration but is required for MCT operation to
support L2VPN services.
• A cluster L2 peer address configuration is not required to support L2VPN over MCT.
NOTE
For MCT L2VPN services to function, you must configure an operational MPLS tunnel (RSVP or LDP)
between the MCT peers.
L2VPN timers
Following optional timers are needed when using MCT L2VPN.
Keep-alive timer: This is used to detect a CCP that is down. The default is 300 miliseconds with
hold time of 900 miliseconds. This timer cannot be changed dynamically once the cluster is
deployed.
Node-Keep-Alive timer: This is used to detect whether the peer MCT node is down. The default is 2
seconds with hold time of 6 seconds. This timer cannot be changed dynamically once the cluster is
deployed. 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).
Cluster CCP session rules
NOTE
CCP (Cluster Communication Protocol) can run either on L2VPN peer (in cases where only l2vpn peer
configured) or on L2 configured peer (in cases where L2 and L2VPN services need to coexist).
NOTE
If using a L2VPN peer in conjunction with L2 Peer, the L2VPN keepalive timers are not used and we
will rely on MCT L2 peer for MCT communication. Additionally, for L2VPN peer case, these timers
need to match on both nodes. If not, the CCP using L2VPN will not come up.
L2VPN peer only configurations
The CCP comes up only if:
• CCP session to L2VPN peer has to come up using regular TCP session.
The CCP goes down if either of the below conditions is TRUE:
• L2VPN CCP is down (TCP shuts down the CCP session for some reason).2VPN-CCP-timer
expires.
The remote node down event is generated if both scenarios below are TRUE:
• L2VPN-CCP keepalive timer expires. This will indicate route failure (300 milliseconds * 3 ~ 900
milliseconds).
• L2VPN-node keepalive timer expires. This timer is to detect the reachability of the remote
node. (Compared to MCT or L2 peer, this is similar to remote MCT node down or not
reachable).
NOTE
It does not need to be route failure for the timer to expire.