VPLS: bridge-domain o xconnect?

Unanswered Question
Feb 26th, 2007

Hi all,

to attach an interface to a vfi I have seen two kind of possible solution:


L2 vfi <name> manual

Vpn id <VPNid>

bridge-domain <bridge-domain id>

Neighbor <Remote-PE>


interface fastethernetx/y

bridge-domain < bridge-domain id>


interface fastethernetx/y

xconnect vfi <name>

What is the difference between the command bridge-domain o xconnect? When I must use one or the other?

Thanks in advance


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
n.nandrekar Mon, 02/26/2007 - 08:50

hi! I am not entirely sure about it but this is my best shot...

X-connect would be used to establish a pseudo-wire (point-to-point) for an EPL service like EoMPLS. That will just connect the 2 UNI together to the VC created by the X-connect command. In this case ther would be no mac table maintained for the VSI in the router.

Bridge domain can be used so that you create a seperate bridge domain ( like a virtual bridge) and add ports to that and connect it to remote PE so that you create a VPLS connection. The PE will maintain a seperate mac table for the VSI.

So thats what I think - PWE3 v/s VPLS..

Correct me if I am wrong.


cgunawan Wed, 02/28/2007 - 08:36


i tried once that bridge-domain has been used in GSR12000 code (the one i know), the rest like in 7600 newer code (SX or SRA), you will find it as "xconnect vfi ".




This Discussion