As you know , mikrotik mpls implementation only binds one label for ECMP routes, with that, mpls forward using multiple path is broken as only one path is used to forward traffic. As our network have a lot of ECMP paths , we had to disable LDP.
The workaroud to use VPLS tunnels is without ldp is using bgp based VPLS and TE tunnels to generate the MPLS labels.
The problem is that its a pain to configure a lot of TE tunnels like a mesh , as that is the only way , all routers have mpls labels to its loopback addres, and vpls tunnels get running.
imagine having to configure 30 routers with 30 mpls te tunnels to another 29 routers?
an easy ways is to fix mpls to bind labels for all ecmp routes, and enable BGP to work with LDP.
Cisco routers have a feature called AUTOTUNNEL, that automaticaly create TE tunnels between all routers that participate in the ospf-te opaque area.
http://www.cisco.com/en/US/docs/ios/mpl ... unnel.html
http://www.cisco.com/en/US/docs/ios/mpl ... _mesh.html
http://www.juniper.net/techpubs/softwar ... nfig5.html
MPLS supports equal-cost multipath (ECMP) labels. A nonconfigurable maximum of 16 MPLS paths is supported. On LERs, MPLS ECMP next hops can be used in the IP routing table for non-VPN and VPN routes. On LSRs, an incoming label can point to either an MPLS ECMP next hop or an IP ECMP.
The signaling protocol determines whether ECMP next hops are used. For example, LDP can learn multiple labels for a route from different downstream peers (or one label from a downstream peer that has parallel connections to the router). LDP then creates an MPLS ECMP next hop that can be used in the IP routing table. If LDP also advertises a label, then a forwarding entry is added to the MPLS forwarding table with the ECMP next hop.