You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have the case that we have several L2VPNs (EPL) and we want to document them. We are transporting VLANs in these L2VPNs to terminate PPPoE customers and now we want to find out at which Router(BNG) the customers terminate, based on the VLAN ID. This is currently only possible if we switch to a VPLS and add the VLANS as terminations, then we see which L2VPN is assigned under VLANS.
My question is, would it make sense to be able to attach a kind of service or VLAN directly to the L2VPN and not only to the terminations? After that you would have the possibility to document the VLAN/s that are transported within the L2VPN.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I would like to discuss the following idea:
We have the case that we have several L2VPNs (EPL) and we want to document them. We are transporting VLANs in these L2VPNs to terminate PPPoE customers and now we want to find out at which Router(BNG) the customers terminate, based on the VLAN ID. This is currently only possible if we switch to a VPLS and add the VLANS as terminations, then we see which L2VPN is assigned under VLANS.
My question is, would it make sense to be able to attach a kind of service or VLAN directly to the L2VPN and not only to the terminations? After that you would have the possibility to document the VLAN/s that are transported within the L2VPN.
Beta Was this translation helpful? Give feedback.
All reactions