[c-nsp] vlan translation

[Murphy, William]

We use VLAN translation to create virtual segments through a security device.  When it's untagged it's simple, each end is an access port in a different VLAN and you can force traffic through by placing hosts in one VLAN and their gateway in the other.  When it's a trunk you have to use VLAN translation to pair up the VLANs across the trunk...  It works great...  Only gotcha I experienced is the default interface command removed the translation from like 8 ports.  My line card only allows unique translations per bank of like 8 ports and the default interface command applied to a single interface affected all 8 interfaces...  I called it a bug but Cisco didn't agree...

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of chris stand
Sent: Friday, September 30, 2011 2:30 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] vlan translation

Are many ( any ) of you using vlan translation on trunk ports ?

Legacy networks integrating into new number schemas ?
Allowing similar vlans to live at multiple remote locations but be seen uniquely at "core"
Part of an 802.1X / radius auth vlan scheme ?

6500 or 7K ?

Thank you,
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/