[nsp] remapping VLAN IDs between .1q trunk ports on the 3550?

[Andrew Fort]

Sean Mathias said the following on 21/09/2003 10:06 AM:
> Well, I don't believe the 3550 has precisely what you are looking for.
> The best/closest it can offer from my understanding would be
> double-tagging in 802.1q tunneling.  I understand your dilemma and
> scenario, but this really is an access switch, not what I expect to be
> used as a PE/PE device.
> 
> However, as new as this platform is, the code is being enhanced fairly
> regularly.
> 
> Sean

The other responses I've had off-list sofar have all been of the order 
of "we had to use a bunch of access ports and physical patches between 
PE switches", which is of course the way we have to do this now.

Does anyone know a way to remap VLANs other than physical patches and 
access ports (on any platform)?  802.1q tunneling isn't an option as it 
doesn't fit with the architecture available to us.

-afort

> -----Original Message-----
> From: Andrew Fort [mailto:afort at choqolat.org] 
> Sent: Thursday, September 18, 2003 11:25 PM
> To: Sean Mathias
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [nsp] remapping VLAN IDs between .1q trunk ports on the
> 3550?
[snip]
> 
> What I'm talking about is having two (ethernet) SPs connecting via a 
> switch (in this case, a c3550-EMI).  They might connect because one 
> provider (A) can provide physical tails where the other provider cannot 
> (B), so they enter into an agreement where (A) provides (B) with tails 
> for customers of (B) to use (so that (B) can get greater customer
> reach).
> 
> For the case of the example, one provider (lets say, B) uses VLAN ranges
> 
> 100-200 for their customers, but those VLAN numbers are already in use 
> at (A), so they will be using 1500-1600 for (A)'s customers.