Regarding RSVP-TE: Yes I can confirm that BGP signaled VPLS works with LDP disabled.
The only issue with BGP VPLS (compared to LDP signaled VPLS) is that the PW name is dynamic, and the PW therefore can be used only in the intended full mesh with dynamic addition to a Bridge. At first glance that is all fine, but the effect is that - due to the VPLS PW being dynamically added - it is quite difficult to work with VLANs. Yes, VLAN Filtering can be enabled on the Bridge used by BGP VPLS, but as the dynamically added VPLS PWs change name, keeping VLAN settings up to date would require scripting. Unfortunately it is not possible to add a bridge (e.g. the one used for BGP VPLS, with VLAN filtering off) to an other bridge (that has VLAN filtering on).
Comparably, LDP VPLS PWs appear as L2 interfaces similar to Ethernet, and they can be added to Bridges with no restrictions.
Not sure if I was able to describe the issue above. Anyone sees a workaround?
(a physical loopback using two ethernet ports would probably work, or a tunnel on the router itself. Not pretty.)
What would be needed: A form of Template for dynamically adding a L2 transport to an existing bridge.
The issue is actually broader: Dynamically generated VPLS PW for example have ARP enabled. They themselves require some Template.
a.
The only issue with BGP VPLS (compared to LDP signaled VPLS) is that the PW name is dynamic, and the PW therefore can be used only in the intended full mesh with dynamic addition to a Bridge. At first glance that is all fine, but the effect is that - due to the VPLS PW being dynamically added - it is quite difficult to work with VLANs. Yes, VLAN Filtering can be enabled on the Bridge used by BGP VPLS, but as the dynamically added VPLS PWs change name, keeping VLAN settings up to date would require scripting. Unfortunately it is not possible to add a bridge (e.g. the one used for BGP VPLS, with VLAN filtering off) to an other bridge (that has VLAN filtering on).
Comparably, LDP VPLS PWs appear as L2 interfaces similar to Ethernet, and they can be added to Bridges with no restrictions.
Not sure if I was able to describe the issue above. Anyone sees a workaround?
(a physical loopback using two ethernet ports would probably work, or a tunnel on the router itself. Not pretty.)
What would be needed: A form of Template for dynamically adding a L2 transport to an existing bridge.
The issue is actually broader: Dynamically generated VPLS PW for example have ARP enabled. They themselves require some Template.
a.
Statistics: Posted by azg — Sun Jan 28, 2024 3:56 pm