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

670 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
L2VPN support for L2 MCT clusters
18
Client Info:
------------
Name Rbridge-id Config Port Trunk FSMState
c1 101 Deployed 1/4 2 Admin Up
c2 102 Deployed 1/2 1 Up
Syntax: show cluster
See “Show commands” for additional information regarding the show cluster output.
Sample Configurations
To support L2VPN services, the cluster with the newly added L2VPN parameters for this feature
must be configured.
Below, the configuration highlighted is the new L2VPN configuration.
Assume: Local MCT node loopback 1.1.1.1; Peer MCT 2.2.2.2; Remote L2VPN Peers: 3.3.3.3,
4.4.4.4;
For L2 operation, the remote peer in direct ICL is assumed to be 10.10.10.2.
Cluster Configuration:
cluster mct_l2vpn 1
rbridge-id 1
[session-vlan 101] // The below configuration is needed only for MCT/L2
[icl interface eth 1/1 icl]
[peer-address 10.10.10.2 rbridge-id ]
l2vpn-peer 2.2.2.2 rbridge-id
[l2vpn-peer 2.2.2.2 timers keep-alive hold-time ]
[l2vpn-peer 2.2.2.2 timers node-keep-alive hold-time ]
deploy
client MCT_CLIENT1
rbridge-id 101
client-interface e 1/1
[vll-pw-redundancy-active]
deploy
Sample MPLS VLL/VPLS Configuration:
router mpls
vpls-policy
[vpls-pw-redundancy-active]
lsp MCT_PEER_LSP
to 2.2.2.2
enable
// Below L2VPN configuration is given just for completion
vll MCT_VLL1 101
vll-peer 3.3.3.3 [4.4.4.4]
[vll-pw-redundancy-active]
vlan 101
tagged eth 3/1