L2 VPN (VLAN rewrite?)

Unanswered Question
Jun 25th, 2007

We have a requirement to provide L2 Ethernet "VPNs" to our clients(Historically, we have only provided L3 MPLS VPNS) - Our clients ethernet Tails are presented to us over GBIC Trunks from our various Ethernet Providers....the providers control the VLAN Id presented to us for each client tail.

Is there anyway to "rewrite" or "map" multiple vlan id's to one?(Without bringing the vlans up into our Routers, and adding each dot1q Int. into a bridge group?)


Client A has 4 ethernet tails presented to us from 2 providers(Both providers terminate on the one Switch):

Provider 1 presents VLAN 501 and VLAN 502

Provider 2 presents VLAN 601 and VLAN 602

Is there any way to rewrite the 4 vlans to VLAN 50, so that all 4 tails are in a flat L2 network(Client has full control over IP addressing) - If so, at a minimum, what Switch would be required?(3750?)

VPLS would be the most obvious solution, but we currently only have 7200's at the core, connected to 2950's(L2 Ethernet has not been a focus until now ;) )

All suggestions are greatly appreciated.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Anonymous (not verified) Fri, 06/29/2007 - 11:49

To provision L2VPN using the Cisco IP Solution Center (ISC) API, you need an L2VPN service policy of a specific subtype and an L2VPN service request.

The service policy (defined in a service definition) specifies the attributes common to the end-to-end wires and attachment circuits (ACs).

The service request defines the device interfaces for each end-to-end wire connection (called link endpoints in the GUI), and can optionally override policy attributes in each end-to-end wire link and AC. When you deploy an L2VPN service request using a service order, the attributes specified in the service definition are applied to the devices and interfaces listed in the service request, along with the attributes for each end-to-end wire link and AC.



This Discussion