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

666 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
L2VPN support for L2 MCT clusters
18
interface ve 10
ipv6 address 10::2/64
ipv6 vrrp vrid 10
backup priority 50
ipv6-address 10::100
activate
!
NOTE
Cluster client-rbridge-id on both switch A and B have to be same value for a given MCT.
Switch S1:
lag "mct_s1" static id 1
ports ethernet 7/1 to 7/2
primary-port 7/1
deploy
!
vlan 200
tagged ethe 7/1
router-interface ve 10
!
interface ve 10
ipv6 address 10::99/64
L2VPN support for L2 MCT clusters
For a L2VPN MCT, L2 MCT peer configuration is not required as it operates independently.
• L2VPN MCT does not require direct ICL as L2VPN may use no-direct MPLS network to the peer
MCT node.
• L2VPN MCT does not require L2’s session VLAN (and have peer in the same subnet as peer) as
peer need not be directly connected.
• L2VPN and L2 MCT can be supported simultaneously
• When L2VPN and L2 needs to be run concurrently, you must configure the L2 peer parameters
(similar to MCT/L2) and also configure L2VPN peer as well. The L2 peer will be used for the
MCT communication.
• When using the L2VPN service, you must configure a L2VPN peer as well.
• MCT L2VPN is HLOS is not supported but compatible.
Support for non-direct ICL
L2VPN MCT functionality supports non-direct ICL functionality apart from the existing direct ICL
requirement that is needed for L2.
A L2VPN MCT session needs to be established or verified at run time so that L2VPN traffic can
traverse the ICL path.
The l2vpn-peer command needs to be configured to support L2VPN over MCT
A l2vpn peer address is required to be on a remote MCT node loopback address on which the
L2VPN sessions is formed.