VLANs across EoMPLS

Hi there
I wonder if it possible to transport a QinQ across an EoMPLS connection, so the EoMPLS is transparent to the QinQ (ie. transport a trunk of VLANs across the EoMPLS connection)?

Hi there,
It is possible to transport QinQ across EoMPLS.
EoMPLS can operate in two modes: port-tunneling mode and VLAN-tunneling mode.Port-tunneling is also referred to as port-to-port transport which supports QinQ.
Here are some more details.This type of transport defines one of the Metro Ethernet Services called Ethernet Wire Service (EWS).
EWS is a non-multiplexed point-to-point service.It is P2P as it resembles a PVC.It is a wire service as a port does not have multiplexing. A customer port connects to a single remote customer port. This is similar to a leased line.
EWS counterpart is Ethernet relay service which is VLAN multiplexed P2P service.In ERS service multiplexing is available based on VLAN, such that different customer VLANs within a customer port can connect to different sites. This is similar to a Frame Relay port.
EWS being a transparent services use QinQ facing the customer to provide "VLAN bundling" in a port-based service and achieve transparency for customer bridge protocol data units (BPDUs).
An example of QinQ transport over EoMPLS would be Switch to Switch Port-based EoMPLS transport.
Hope it helps.
Cheers
Zeshan

Similar Messages

VLANS across WANS

I am working on a project for CCNA class. I want to maintain VLAN identities across multiple WAN sites...i.e. My central Core will be in LA, remote offices at Dallas and St Louis. If I define VLANs 10, 20,30, and 40 at LA for 4 departments, with network 10.0.10.0/22, 10.0.20.0/22 etc..I have considered using EoMPLS to maintain the VLAN structure and the ability to not have to change or reassign different network address at the remote sites. In essence, I wish to have the same subnets at all sites for all VLANS and implement NMC from the LA office. I want to have VLAN 10, with 10.0.10.0/22 at all 3 sites. Is this possible and maintainable from a management standpoint using EoMPLS. What am I missing here? Other posts I have researched state that this is not possible and not recommended. The objective is to maintain VLANs across all 3 sites.
If not, then how do we maintain VLAN identities and membership across all 3 sites with different Subnets? I am just looking for ideas, not solutions. Just some guidance, since I am a student.

I haven't personally used EoMPLS, but it seems a viable option. The other L2 extension technologies to consider are:
VPLS
OTV (ASR1k or CSR1k)
L2TPv3 (can use regular IOS routers)
Typically you'd only consider extending L2 VLANs across a WAN for DCI (data center interconnect) and not branch to branch.
L2TPv3 is a neat feature that can be done cheaply using 800-series routers. It does transmit all L2 traffic so it's possible to have spanning tree loops over the WAN (fun in the lab, but not in production).

How to span vlans across core layer in core/distribution/access campus design?

Hi,
I studied Cisco Borderless Campus Design Guide 1.0 (http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Campus/Borderless_Campus_Network_1-0/Borderless_Campus_1-0_Design_Guide.html) last week because we plan to redesign our campus backbone to a three tier Core/Distribution/Access Design.
Today we use a collapsed backbone where a lot of vlans are spanned across the backbone because they are needed in different buildings.
Could anybody give me a hint how Cisco recommends to deal with that kind of vlans in the multi-tier design?
In my eyes between core and distribution layer there is only routing functionality and no l2 transport of vlans.
So using the same vlan in different buildings seems not to be supported?
Best Regards,
Thorsten

Thorsten
Just to add to Joseph's post.
It is quite common for a vlan to be spanned when it doesn't actually need to be ie. the network has evolved that way.
Most things do not need L2 adjacency, they can happily use L3. Servers sometimes do but in the campus design your servers are usually located in one site so you don't need to extend vlans to other sites in your campus.
Not suggesting this is the case for you but it may be worth checking whether you really do. (apologies if you already have)
As Joseph mentioned you really want to avoid it if at all possible ie. ideally all connections to the core switches are L3 ie. no need for vlans at all in the core.
If you need to extend a few vlans then you can do this but still route for all other vlans ie. you would configure your distribution to core connections as trunks and then allow the vlans you need to extend plus one other vlan, unique per distribution pair, to route all other vlans. So per site your distribution switches route all vlans except the extended vlans and of they need to route to a vlan in another site they use that unique vlan.
But this is not ideal because you then need to extend certain vlans across the core and because you are using L2 connections STP could come into it although that does depend on your core switch selection eg. 4500/6500 VSS etc. would alleviate this.
There are ways to extend vlans across a L3 network but the solutions available are very much dependant on the kit you use and their capabilities so if you do need multiple vlans in multiple sites but still want to keep a L3 core you may want to investigate some of those before purchasing kit (unless of course you have already purchased it).
What you do really depends on just how many vlans you actually need to extend between sites.
Jon

Creating multiple vlans across multiple switches

Hi All,
How should I create multiple vlans across multiple switches?
For instance, I have two (primary/redudant) layer 3 (core) switches and four layer 2 access switches (Cisco 2960) for the hosts, and given these are the vlans/subnets to be created. Should I do it in the core switches only and it would just propagate through the access via VTP? Just trying to practice and learn.. Any help will be greatly appreciated:)
VLAN 100: [DHCP-workstations]
172.26.4.0/24
172.26.5.0/24
VLAN 200: [Servers]
172.16.1.0/24
172.16.2.0/24
VLAN 300: [Printers]
192.168.129.0/24
192.168.130.0/24
VLAN 800: [Management for switches/routers]
10.160.1.0/24

Hi
You will have the SVI on the core. Set a VTP domain, make one of the cores as VTP server and rest of the switches as VTP clients. Once you do this, you won't have to login into each switch and create a vlan locally. The vlans will be automatically advertised from the VTP server to all the VTP clients.
Thanks
Ankur
"Please rate the post if found useful"

Extending VLAN across Data centers

I hope you can help, I have 2 data centers connected via a L3 10gb (dark fiber) now I have a few more fiber strands available between the 2 data centers; so for Disaster Recovery and server clustering (requiring same subnet) does it make sense to extend certain vlans across using these extra fiber strands or is it best practice to keep the layer 3 separation, thanks in advance!

Borman
It does make sense in terms of clustering. Not sure exactly what you mean in terms of disaster recovery, that really depends on your topology/addressing.
Basically i would route where you can and extend L2 when you have to. Be aware you are extending L2 between data centres and tha brings STP issues. Obvioulsy make sure you only allow the vlans you need on this link and route all else.
There are other ways to extend a L2 vlan across a L3 link - L2TPv3 springs to mind.
Jon

Extending VLANs across routed interfaces

Hello;
I'm trying to create a L3 core network. The core equipment will be Cisco 3750 enhanced. My idea is make each link between core 3750 a routed interface, with /30 IP addresses.
The problem is the customer needs some VLANs extended across the full enterprise. Is there any way to encapsulate the VLAN inside routed interface?
Thanks in advance.

I realize this thread is 5+ years old, but I feel like commenting anyway.
If you want to encapsulate the vlan across that link, you won't be able to use routed interfaces. You will need to use a layer 2 trunk(dot1q). Therefore, I wouldn't bother with the /30 addresses unless you want to monitor that specific link by IP. In that case, use a special VLAN just for those two interfaces and put your /30 addresses on the vlan interfaces.
If you want fast fail over on a layer 2 link, well then, use Rapid STP. The goal should be to get rid of those flat VLANs that span the core and switch to your original plan of routed interfaces using EIGRP or OSPF.

Spanning vlans across access switches in distribution block.... please help

Hi All
Can someone please explain why Cisco states that in a Campus Hierarchical modle if Vlans are spanned across Access switches in a distribution block, then the Distrubution to distribution link should be Layer 2. Is this really necesary or just a recommendation, and if so why? Can't this link be a L3 link when spanning vlans across Access switches in distribution block, as I understand the benefit of having a L3 distribution to distribution link so that SPT is avoided.
Please help

Hello,
The cisco recommended design is L3 links, but these is only possible if you have no vlans you need to span over the hole network.
It depends on your topology or what you want achieve.
If you need for one or more vlan's spanned the LAN, you need to use a layer 2 connection between all switches and between distribution too.
In my company we have for example a few vlans for restricted areas, like device management or else, so we can't use L3 Links in the distribution area because these vlan's are terminated at the firewall. I think these is good thing.
I would recommend you if you don't have to span one or more vlan's across the network to use L3 Links, specially in the case of redundancy way's. So you need no spanning-tree, but need to use other protocols like GLBP or else. The works faster and are not so confusing (for some people) as STP.
best regards,
Sebastian

Span VLANs across switches

VLANs are new to me so please forgive me -
We have 5 Cisco sg500x switches. We need to create two vlans across some or all of the switches.
I have been successful in creating vlan1 on one switch and excluding and including ports to segregate traffic. My problem is I can’t get the other switches to see vlan1 that was created on the original switch. I have enabled gvrp on all switches and ports assigned to the vlan but no luck in getting vlan1 devices to communicate across switches. How do I make this work? I think my main problem is creating uplink ports between the switches to carry the vlan across.
How do I go about spanning vlans across the switches?
Many thanks

Thanks Robert I think that has got me a bit further in that I'm not getting VLAN MISMATCH error any more. I believe it was because the trunk ports were marked as untagged. I still don't feel I understand the NATIVE VLAN concept or how to set it. If I have the default VLAN(1) and I have the VLAN I am trying to span across two switches (VLAN2) do I then need a 3rd VLAN to be the native for either end of the trunk between the two switches? Anyway this what I've done in more detail -
On Switch 1
Create VLAN 2: VLAN ID 2
Set port 2 as follows: Default VLAN1 = forbidden, VAN2 = trunk, tagged
Set port 3 as follows: Default VLAN1 = forbidden, VAN2 = access, untagged
On Switch 2
Create VLAN 2: VLAN ID 2
Set port 2 as follows: Default VLAN1 = forbidden, VAN2 = trunk, tagged
Set port 3 as follows: Default VLAN1 = forbidden, VAN2 = access, untagged
With rj45 connect port 2 on both switches to each other. Clients connected to port 3 on both switches cannot ping each other across the trunk.
Seeing this in the logs:
Warning: %STP-W-PORTSTATUS:gi1/1/2: STP status Forwarding
IP info:
Default VLAN1 on 172.16.1.0/21
VLAN2 on 172.16.40.0/21
Any suggestions or areas to investigate would be helpful however obvious they may seem to anyone as this is my first effort with a Cisco. Thanks

Sending specific Vlan across wireless bridge

Hello All,
I would like to know how I can send a specific VLAN across a wireless bridge. Currently, we have a building across the street from our main office that's connected via a wireless bridge (no physical cabling). One of the switches in building 1 has a port in VLAN 206 (10.20.6.0/24) which connects to the wireless bridge (10.20.6.3) on that building. The wireless bridge in building 2 is 10.20.6.4 and connects to a router on the same subnet. So both bridges, the switch in building 1, and the router in building 2 are all on the same subnet. I need to send VLAN 60 across this wireless bridge so that the workstations in building 2 can go out to the Internet. As a side note, VLAN 60 is unrouted and is it's own subnet which has it's own firewall and web filter. My thought on this is that if I can get the wireless bridges to send VLAN 60 to building 2, then all I would need to do is add the workstations to that VLAN on the switch in that building and all should be well. I'm just not sure what I need to configure on the bridges and how building 2 should be configured seeing that the 2nd bridge connects to a router instead of a switch. Any tips, suggestions, and help would be great!
Thanks,
Terence

assume that i have two bridges Br-root , and Br-nonroot and i want to send traffic from multiple vlans across the wireless link, all you need to have is infrastructure-ssid on the native vlan. Then define the required subinterfaces on both radio and ethernet of root and non-root.
Example: ( vlan 1 , 2 , and three )
Root(config)#dot11 ssid test
                 #authentication open
                 #vlan 1
                 #infrastructure-ssid
                #exit
Root(config)#interface dot11radio 0
                 #ssid test
                 #station-role root bridge
                 #no shut
                #exit
Root(config)#interface dot11rdio0.1
                 #encapsulation dot1q 1 native
                #bridge-group 1
               #exit
Root(config)#interface dot11rdio0.2
                 #encapsulation dot1q 2
                #bridge-group 2
               #exit
Root(config)#interface dot11rdio0.3
                 #encapsulation dot1q 3
                #bridge-group 3
               #exit
Root(config)#interface fa0.1
                 #encapsulation dot1q 1 native
                #bridge-group 1
               #exit
Root(config)#interface fa0.2
                 #encapsulation dot1q 2
                #bridge-group 2
               #exit
Root(config)#interface fa0.3
                 #encapsulation dot1q 3
                #bridge-group 3
               #exit
for the non-root , same config but the station-role should be non-root
Enjoy

Private vlan across switches in NX-OS

Hi,
I'm trying to make a scenario to span private vlan across multiple switches but I couldn't get this to work in NX-OS N7K.
My topology is similar to the one in the picture attached.
I tried to ping from isolated host vlan 201 in switch A to isolated host vlan 202 in switch B. Promiscuous trunk port has been configured to upstream router in Switch A. From switch a to switch b is a normal trunk port.
But still, I can't establish any connectivity from host vlan 201 to host vlan 202.
Any suggestion?
thanks

Jerry -
Any idea why? This breaks the ability to use moderately complex ACLs. For example - how would you configure scavenger class traffic to ignore some traffic, and mark other?
Carole

GE cards supported for port- vlan based EoMPLS on 7600/sup720

Hi,
Can anyone explain/point where I can find de proper documentation where I can find the support for port- vlan based EoMPLS support cards on a 7600 with a sup720 engine on the CCO site ?
WHich GE port cards are supporting EoMPLS and which GE cards will support it not.

try
www.cisco.com/go/fn
-Waris

SPAN for vlan across Nexus vPC

Dear Team,
Anyone have the experience for monitor the vlan traffic across 2 Nexus 6k switches? My scenario are 1 of the monitor server are direct attached to the 1st unit of N6k intend to monitor 2 vlans, but this 2 vlans are span across vPC where it can be transit across both units of N6K according to the vPC traffic flow methodology. I can easily span the local N6K from the 2 vlan to the destination (monitor server) ports, but how I could monitor the traffic (for that 2 vlans) arrived on 2nd unit of N6K?
I try searching for N6K doc there is no RSPAN feature but now introduce ERSPAN, but ERSPAN got limitation stated •A destination port can only be configured in one SPAN session at a time.
Meaning I can't configured both local SPAN and ERSPAN at N6K unit 1 to the same destination port to monitoring server?!!!
Just wish to know is any experts came across this scenario and have experience on alternative solution, would like to hear from your expert advice, thanks in advance.
Regards
Chong

Hi chuck_113th,
Did you manage to fix the problem?

VLANs across switches without trunking

Assuming that you only have one VLAN, is it possible to have that single VLAN reach across multiple switches without trunk ports? I've inherited a network of a handful of Cat 6506s, and Cat4006's, which have one big flat /22 in a single VLAN. I'd like to break it up into smaller chunks and seperate VLANs, but I'm rather suprised that it appears to be working with one VLAN but without trunks.

Actully you can run seperate access port links per vlan, chewing up a seperate physical port per vlan on each switch. There was a 2900 series switch I had a long time ago that supported vlans but not trunks.
It had a feature called multi vlan that you could add to a port, but this was a way of letting one port talk to all vlans and was messy.
But you could run a seperate cable for each vlan. if you have 5 vlans then 5 cables between switch A and switch B, port 1 vlan 1, port 2 vlan2, port 3 vlan3, etc...

Need consistant management vlan across mesh

Attached is "Figure 1" which depics a worst case but working multi-vlan configuration which includes the use of the "native vlan" 240 at each point.
This works with version 7.035.3 and older covering the last 3 years of use. Here we turn on "VLAN Transparency" under the Controller>Mesh> tab with Ethernet Bridging normal at both ends.
This DOES NOT work with versions 7.2 and up. Apparently, we cannot trunk the native vlan 240 past the 1st Mesh Access Point (MAP). We need to maintain a consistant native vlan to manage all network equipment. See anything or can you offer any help?

So, you use indoor APs in bridge mode (indoor mesh). right?
If VLAN transparency is enabled you'll not be able to use tagging. So, does that mean you need only to enable the native vlan (no other tagged vlans?) across the mesh APs?
If VLAN transparent is enabled you can not use tagged VLANs on a mesh trunk. Strange if it was working with you this way.
Please go to the wireless -> All APs -> AP name -> mesh tab.
What is the configuration of "Ethernet bridging"? Enabled or disabled?
If enabled, from the listed wired interfaces on same page click on interface name and let us know what is the configuration of tha tinterface (normal, access or trunk).
Regards,
Amjad
Rating useful replies is more useful than saying "Thank you"

Configure VLANs across multiple switches

Hi.
I'm trying to configure a segregated network using a VLAN. There are 5 switches on the site (all SG200). A router with 2 interfaces - one for the normal network and for the segregated network - is connected and located at switch 1. The network which needs to be segregated and the PCs on it are connected to a port on switch 5. Switch 1 is connected to switch 2, 2 to 3, 3 to 4 and 4 to 5.
I have created a VLAN but can't get the network to talk to the first switch over the link. I have created a VLAN ID 10 on each switch. Do the switches have to be linked together logically in some way to get this to work.
Thanks.

Hi,
Try to create the VLAN 5 in all switches.I have assumed that Management VLAN for all switches are VLAN 1.Kindly configure Trunk between switch 1 to S2 ,S2 to S3,S3 to S4,S4 to S5, S5 to S1.Allow the VLAN's 1U,10T.
regards
Moorthy

VLANs across EoMPLS

Similar Messages

Maybe you are looking for