Hi, I would like to know if anyone was able to successfully configure BGP signaled VPLS on ROSv7?
In the documentation there is a reference to Cisco Style BGP VPLS (https://help.mikrotik.com/docs/display/ROS/VPLS), but the sub-menu “/interface cisco-bgp-vpls” it is not present in RouterOS 7.3beta37.
Hi,
IIRC BGP signaled VPLS is under
/interface/vpls/bgp-vpls/add
It should be BGP signaled if you using site-id instead of cisco-id.
for example if your AS is 65535 and RD is 111:
/interface/vpls/bgp-vpls/add disabled=no rd=65535:111 import-route-targets=65535:111 export-route-targets=65535:111 site-id=1 name=BGP_signaling_VPLS1
Hi oreggin, thanks for your attention.
On ROSv6 I use “/interface vpls cisco-bgp-vpls”, but I don’t find that option on ROSv7.
I take this opportunity and ask you if you have tested the operation of “/interface/vpls/bgp-vpls”.
ROS v7 does not separate cisco style and other style in different menus. Type of the tunnel is determined by the parameters you set.
As for BGP signaled VPLS it may not work properly in versions up to beta37. Next beta will have the fix.
Thanks mrz for the info. Then I will wait for the next beta to perform new tests.
Fixed in 7.3beta40?
I don’t think so. We are seeing strange behavior. A vpls interface is created against the route reflector, it disappears, it is recreated and it disappears again. This behavior is permanent.
However, I am not sure if we are configuring the service correctly. The configuration we use in ROSv6 is as follows:
/interface vpls cisco-bgp-vpls
add bridge=bridge-vpls-test bridge-cost=1 bridge-horizon=1 export-route-targets=65000:100 import-route-targets=65000:100 l2router-id=192.168.1.2 name=vpls-test route-distinguisher=65000:100 vpls-id=65000:100
On ROSv7 we try to replicate the configuration with the following command:
/interface vpls bgp-vpls
add bridge=bridge-vpls-test bridge-cost=1 bridge-horizon=1 cisco-id="" disabled=no export-route-targets=65000:100 import-route-targets=65000:100 name=vpls-test rd=65000:100
Update:
With the help of Support, I was able to successfully set up Cisco VPLS BGP-based auto-discovery in ROS 7.3rc1.
I needed to correctly configure the cisco-id parameter, which comes from a merge of l2-router-id and route-distinguisher ROSv6 parameters.
/interface vpls bgp-vpls
add bridge=bridge-vpls-test bridge-cost=1 bridge-horizon=1 cisco-id=192.168.1.2&65000:100 disabled=no export-route-targets=65000:100 import-route-targets=65000:100 name=vpls-test rd=65000:100
Update 2:
When I enable Cisco VPLS BGP-based auto-discovery, the CPU goes up to 100%, mostly due to the routing process.
I’m seeing this interface creation and deletion behaviour on v7.4.1 with BGP VPLS (Non-Cisco). Was there any special configuration that you had to apply to resolve or was it just fine in v7.3rc1?
We were able to successfully configure BGP VPLS on ROSv7.5. The configuration is as follows:
/routing bgp vpls add bridge=bridge=bridge-vpls-test bridge-cost=1 bridge-horizon=1 export-route-targets=65000:100 import-route-targets=65000:100 name=vpls-test rd=65000:100 site-id=18
Hi, we have set up same BGP VPLS config and still same problem on ROS 7.5, BGP vpls subinterfaces go up and down and are not BGP signaled, can you tell us how have you configured BGP on the router reflector and nodes? We use ibgp rr role for RR and ibgp for nodes, but something should be missing. When router reflector is using ROS6.48, all nodes using ROS6.8 have BGP VPLS signaled interfaces running, but those ones with ROS 7.5 remain stable and active but not BGP signaled. When we upgrade Router reflector to ROS 7.5 all the problems of unstability start.
Hi, below route reflector client configuration (running ROS 7.5):
/routing bgp connection add address-families=l2vpn as=65000 disabled=no local.address=192.168.1.10 .role=ibgp name=RR remote.address=192.168.1.20
/routing bgp vpls add bridge=bridge=bridge-vpls-test bridge-cost=1 bridge-horizon=1 export-route-targets=65000:100 import-route-targets=65000:100 name=vpls-test rd=65000:100 site-id=18
Route reflector configuration (running ROS 6.47.10):
/routing bgp peer add address-families=l2vpn name=ros7_test remote-address=192.168.1.10 remote-as=65000 route-reflect=yes update-source=loopback
Ok, well understood, that’s why I was so confused, apart from that I received this update from Mikrotik support:
“There is an issue with ibgp rr role. We have managed to reproduce the issue locally in our labs and look forward to fixing it on upcoming RouterOS versions, unfortunately, I cannot provide a release date now.”
So It’s not possible to have a fully working BGP signaled VPLS scenario on ROS 7.5. Also I noticed that if I use the ROS 7.5 in a node and 6.48 in router reflector, all devices with ROS 6.48 bring up the BGP signaled VPLSs, but in those running ROS 7.5, these BGP-VPLS are running, but not BGP signaled, and in MPLS LDP neighbors appear as “Invalid” due to the problems of BGP with ROS7.5, so I guess that this is not fully working and ROS 7.5 needs more work.
Thank you so much for your help and quick responses. Hope a new version comes up soon fixing this issue.
Has any progress been made toward fixing BGP route reflectors in v7? BGP VPLS won’t work for our setup until that’s fixed in v7, so our entire network is stuck on v6. 
hi, is there any news on solving the route reflector problem? thank you
they just patched routeros 7.7rc for the route reflector
Could you please tell us your ticket ref for this? Some script reading joker in support told us to upgrade to v7 for a related issue we’re having (as if the lack of BFD wasn’t already a big no from us) 
v7.18 , still not fixed