Mct for vll – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual

Page 709

Advertising
background image

Multi-Service IronWare Switching Configuration Guide

679

53-1003036-02

MCT for VLL

18

router mpls

vpls test 10

cluster-peer 12.12.12.12

vpls-peer 21.21.21.21 22.22.22.22 3.3.3.3

vlan 10

tag eth 1/1 eth 1/2

……..

cluster abc 1

rbridge-id 100

l2vpn-peer 12.12.12.12 rbridge-id 101

deploy

client c1

rbridge-id 300

client-interface ethernet 1/1

deploy

Switch PE12:

MLX-PE12#show run

router mpls

vpls test 10

cluster-peer 11.11.11.11

vpls-peer 21.21.21.21 22.22.22.22 3.3.3.3

vlan 10

tag eth 1/1 eth 1/2

……..

cluster abc 1

rbridge-id 101

l2vpn-peer 11.11.11.11 rbridge-id 100

deploy

client c1

rbridge-id 300

client-interface ethernet 1/1

deploy

MCT for VLL

This feature supports dual-homing connectivity of CE devices to PE devices. Dual-homing enables
link level and node level redundancy for CE's connected to PE's.

Figure 184

is a typical topology with MCT end-points for VLL. The VLL end-point connections from a

single CE are dual homed to two PE nodes acting as an MCT cluster. From the CE, it has a LAG
connection between CE and PE and is unaware of the MCT.

•

PE1 and PE2 are two nodes of MCT cluster and work like a single PE. Similarly PE3 & PE4 are
MCT cluster.

•

CE1 is connected to PE1 and PE2 through a LAG.

•

CE2 is connected to PE3 and PE2 through a LAG.

•

PE1 has PW1 and PW3 vll PWs for same instance connected to remote MCT pairs.

•

PE2 has PW2 and PW4 vll PWs for same instance connected to remote MCT pairs.

•

For MCT pair PE1,PE2 PE1 is selected as active for a VLL instance, which it specifies as
Active(A) in pw-redundancy status TLV during PW connection setup to remote PE pair.

•

For MCT pair PE3 and PE4 nodes, PE4 is selected as active, which it specifies as Active(A) in
pw-redundancy status TLV during PW connection setup to remote PE pair.

Advertising