[c-nsp] VLAN and switch and ?

[Jeff Fitzwater]

Look at layer 2 tunneling for your switches.  You would assign tunnel  
vlan ID and ISP would send tagged traffic into tunnel (Q in Q) and  
traffic would exit tunnel where ever needed.   When you assign a port  
as a tunnel port, it becomes a tunnel-input and tunnel-output.   You  
can have as many tunnel ports as you need.  The ISP can now send what  
ever VLANs they want and you do not need to change anything.
Read the doc and be aware of oversized packet handling within tunnel  
switches.


Jeff Fitzwater
OIT Network Systems
Princeton University

On Mar 4, 2009, at 9:46 AM, Charles Regan wrote:

> Good Morning,
>
> I'll try to explain what I want to do... We are LOCAL NETWORK in  
> this graphic.
> The ISP wants to use our fiber link to connect to his wireless  
> customer.
> We also want internet access from his Wireless Backhaul1.
> ISP also use VLAN on his customer subscriber modules.
>
> How would you configure 2924 Switch and 2960 Switch, so that
> everything is transparent from my side and his side ?
> I don't want him to call me to add a new VLAN on our switch.
>
>
> ISP ---Wireless BackHaul1 -- 2924 Switch ---- FIBER ---- 2960 Switch
> ---- Wireless Backhaul2 ---- Access Point ---- Wireless subscriber
> modules
>                                            |
>             |
>                                            |
>             |
>                                            |
>             |
>                                            |
>             |
>                                            |
>             |
>                             LOCAL NETWORK            LOCAL NETWORK
>
>
> Will something like this work ?
> switchport access vlan 500
> switchport trunk encapsulation dot1q
> switchport mode trunk
> _______________________________________________
> 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/