[c-nsp] how to accomplish multiple 'native' vlans

[Frank Bulk]

Chris:

Your initial e-mail indicated the tagging opposite to what you said in this
latest e-mail. =)

I think these commands are supported in most switches/software releases.

Frank

-----Original Message-----
From: Chris Hale [mailto:chale99 at gmail.com] 
Sent: Friday, September 12, 2008 8:36 AM
To: Frank Bulk; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] how to accomplish multiple 'native' vlans

Thanks Frank.  This looks almost exactly what I was looking for, but
the VLANs would be switched around: VID 10 would come through tagged
(i.e. equipment mgmt VID) and VID 100/101 (i.e. customer VID) would
come through untagged.

Is this only on the newer switches?  I seem to remember I had to carry
the native vlan throughout the uplinks on an older 3550.

Thanks,
Chris

On Thu, Sep 11, 2008 at 12:54 AM, Frank Bulk <frnkblk at iname.com> wrote:
> Chris:
>
> Each port can be assigned a unique untagged VLAN (switchport trunk native
> vlan xx).  You can limit which VLANs are trunked by assigning the allowed
> VLANs (switchport trunk allowed vlan yy).  You can then create an uplink
> port with all those trunks.
>
> I think this is what you're looking for.
>
> Here's an example:
>
> interface FastEthernet0/1
>  description Customer A
>  switchport mode trunk
>  switchport nonegotiate
>  switchport trunk native vlan 10
>  switchport trunk allowed vlan 100
> !
> interface FastEthernet0/2
>  description Customer B
>  switchport mode trunk
>  switchport nonegotiate
>  switchport trunk native vlan 10
>  switchport trunk allowed vlan 101
> !
> interface FastEthernet0/24
>  description Uplink
>  switchport mode trunk
>  switchport nonegotiate
>  switchport trunk allowed vlan 10, 100, 101
> !
>
> Frank
>
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Chris Hale
> Sent: Wednesday, September 10, 2008 11:35 PM
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] how to accomplish multiple 'native' vlans
>
> All -
>
> We are converting our L2 network from Riverstone to Cisco.  One
> problem I have not been able to solve yet is the way the Riverstone
> and Cisco units handle untagged traffic entering a physical port.  We
> have many connections to customers whereby we have equipment we would
> like to manage with management VIDs inline with untagged customer
> traffic.  When it enters the Ethernet trunk port on the Riverstone, we
> are able to assign the untagged traffic to a VID and it traverses the
> trunk ports where allowed as tagged traffic.  It doesn't seem like the
> Cisco switches have this ability - only one native VLAN per switch.
> Is there some way to accept multiple ports of untagged traffic and tag
> each ports' untagged traffic with separate VIDs?
>
> Example:
>
> fa0/1 - mgmt VID 10, customer traffic untagged (needs to be tagged
> with VID 100 for L3 routing)
> fa0/2 - mgmt VID 10, customer traffic untagged (needs to be tagged
> with VID 101 for L3 routing)
> etc.
> fa0/24 - trunk port to L3 device
>
> We are using 2960 and 3560 switches.  Any other ideas are welcome, but
> we would prefer to minimize any CPE equipment at customer site to tag
> their traffic with the appropriate customer VID.  It's a matter of
> additional cost, additional management devices, and additional points
> of failure.
>
> Thanks,
> Chris
>
> --
> ------------------
> Chris Hale
> chale99 at gmail.com
> _______________________________________________
> 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/
>
>



--
------------------
Chris Hale
chale99 at gmail.com