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

Similar Messages

How to migrate exadata across data centers?

How to migrate exadata across data centers? Is forklift (or lift & shift) only option for this kind of migration since we are talking about migrating appliance?
Any best practices/experiences around such migrations?
Thanks,
Abhi

Hi,
We recently had a data center move and moved some exadata machines to a new location.
There are a few things to consider before move happens;
1) Get the network ready on new Data Center and make sure all connectivity (e.g. you can remote access to it) are working. In our case the new center has same IPs network.
2) Get the Vendor who does transporting of Hardware Machines.
3) On the last day before move, Shutdown the Exadata Machine ( shut down database, RAC, shutdown db nodes, cell nodes, infinity band etc.. )
4) Power off Exadata Machine
5) Unplug all network cables.
6) Let the Hardware cool down.
7) Transport to new location and move the Machines to correct Bay and wait for machines to be acclimatized
8) Plug Network cables.
9) Power On Exadata.
I found a Support note which also you can refer; What Needs to be Done When Moving Cluster Nodes to a New Data Center (Doc ID 1332423.1)
HTH,
Pradeep

Physical connectivity required to support Nexus L2 extension across data centers

my customer requires L2 extension across their data centers using Nexus 5596/Nexus 2248. I'm unable to find documentation to confirm my physical connectivity to confirm the logical requirement. Will the diagram below support the requirement to extend their vlans across the two data centers? Thanks for any help you can provide.

I'm not a Cisco PM, who probably should answer this question; my 2c
Don't know if you have ACI or simply the standalone N9k running NX-OS in mind.
If you don't need/want APIC, I would not go for N9k/ACI Version.
See also the newest information regarding integration of N7k..... into ACI
http://www.networkworld.com/community/node/85429
http://finance.yahoo.com/news/cisco-delivers-aci-vision-adds-120000751.html?.tsrc=applewf
As you said, N9K / ACI doesn't support FCoE (its on the roadmap) and definitely not native FC.
No Fabric Path, all is VXlan based.
On the other hand, VXlan (and Fabric Path) support seems to show up on the N7k family (new line card)
Walter.

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.

How can I move VMs across data centers without changing their IP addresses?

This document is old, but I think will help you:
http://www.sonicwall.com/downloads/VPN_with_Overlapping_Networks.pdf

Hi All,
We have many applications that have been developed that do not use DNS but rather static IP addresses to communicate. Moving the VMs that these applications run on to a different subnet would be a huge project. I’m looking for a service that will allow me to move VMs between sites without the need of changing their IP addresses. I’m also looking to do this without spending very much. Cisco OTV and layer 2 circuits with various ISPs will do what I need, but they can be expensive and will add complexity. I’ve also read about Aryaka and Pertino but I’m not sure if they’ll do what I want.
Is there another option that I’m missing?
This topic first appeared in the Spiceworks Community

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

WAN Vlan optimization between 2 Data Centers - 4451 Router

Hello Group gurus,
I have little odd question
We have 2 Data Centers, we have dedicated 1Gig link across them. we want to optimize certain Vlan traffic across them.
we have 4451 routers installed at each location and OSPF running for end subnets to know each other. but that is routing part completed.
however how can we utilize UCSE chassis of 4451 to optimize vlan traffic across data center is still a query.
I tried to find out document on google but specific to my requirement has not seen on.
if someone already set up this type of scenario, please help.
Thanks in advance

Hi John, I think it's best to use the right equipment for the job. If you've already got a router in place and you're not in a campus/metro/ISP environment, it's not really prudent to use another router. A simple layer 2 or layer 3 switch can accomplish this and give you plenty of ports at a much better price per port.
You may want to look in to the SG300 series switch if you want something that can handle route load and give ample amount of ports.

Server Load-balancing Across Two Data centers on Layer 3

Hi,
I have a customer who would like to load balance two Microsoft Exchange 2010 CAS Servers which are residing across two data centers.
Which is the best solution for this? Cisco ACE or Cisco ACE GSS or both?

I would go with source natting the clients ip addresses, so that return traffic from the servers is routed correctly.
It saves you the trouble with maintaining PBR as well.
Source NAT can be done on the ACE, by applying the configuration to either the load balancing policy, or adding the configuration to the class-map entries in the multi-match policy.
Cheers,
Søren
Sent from Cisco Technical Support iPad App

DAG across 2 Data Centers

Looking for pros and cons of 2 potential Exchange 2013 implementations.
ADSite1: 400 users
ADSite2: 100 users
ADSite3: 50 users
Implementation 1: (DAG across two Data Centers without DAC implemented)
ADSite1: ExchSrv1 (MBX/CAS) --- DAG (2 DB) --- ADSite2: ExchSrv2 (MBX/CAS)
ADSite3: FSW
Implementation 2: (DAG across two Data Centers with DAC implemented)
ADSite1: ExchSrv1 (MBX/CAS) ExchSrv2 (MBX/CAS)--- DAG (2 DB) --- ADSite2: ExchSrv3 (MBX/CAS)
Site3: FSW
1. Am I gaining any true benefit from Implementation 2 (additional server in Primary Site)? i.e. Implementation 1 covers me for HA and DR. Would it make sense to consolidate ADSite1 and ADsite2 into a single ADSite for Implementation 1?
2. In either case, is it ok the configure NLB for all the servers (for the CAS role). So, if a user on ADSite2 hits the CAS on ADSite1 they could then be proxied to either ADSite ExchSrv depending on where their MBX is.
3. If all the MBX DBs in ADSite2 are replicas and not active and a user hits the CAS on ADSite2, is this increasing network traffic to then allow ExchSrv3 (CAS) to have to proxy to the ExchSrv1 (MBX). If so, does it not make sense to have the ADSite2
server only hosting replicas?

Hello,
1. I recommend you use Implementation 2. When you enable DAC mode, it will prevent split brain from occurring by including a protocol called Datacenter Activation Coordination Protocol (DACP). After a catastrophic failure, when the DAG recovers, it won't
automatically mount databases even though the DAG has a quorum. Instead DACP is used to determine the current state of the DAG and whether Active Manager should attempt to mount the databases.
2. You can deploy CAS NLB, but you can't depoly DAG+WNLB. If you deploy NLB, the CAS will proxy traffic to the Mailbox servers hosting the active copies.
3. If you deploy NLB, the ExchSrv3 (CAS) may proxy requets to the ExchSrv1 (MBX).
Additional article for your reference.
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Cara Chen
TechNet Community Support

Office Web Apps Farm Across Multiple Data Centers?

I have not been able to find any definitive information about this but the article below seems to suggest what I have in mind is not recommended. I am not sure about supported.
"Stick to one data center. Servers in an Office Web Apps Server farm must be in the same data center. Don’t distribute them geographically. Generally you need only one farm, unless you have security needs
that require an isolated network that has its own Office Web Apps Server farm."
http://technet.microsoft.com/en-us/library/jj219435.aspx#topology
What I have is two very well connected data centers located in the same metro area. We will be deploying a Lync EE pool at each site and use pool pairing for DR. What I am wondering is should I:
Create a single Office Web Apps farm with the server from each data center as members?
Create a farm in each site with a single member, but both farms sharing the same URL?
Create a farm in each site with a single member, but both farms have different names. This seems unnecessarily ugly, but throwing it out there.
Since Lync is using Office Web Apps in read only mode the question is different than if SharePoint were involved. However, I can't rule out this farm also being used for SharePoint down the road.
The LB/RP device of choice is Citrix NetScaler. Another thought I had is can that be configured so incoming requests for Office Web Apps at each data center can prioritize traffic to the server or farm within that data center? If that is unavailable
then switch to the server at the other data center?
Thanks.

Hi,
An Office Web Apps farm can be deployed to provide functionality for multiple sites.
Also you can deploy one Web Apps farm on each site.
So I think you can choose to deploy with the option one and three as you said.
Here is a case about deploying Lync deploy Office Web Apps server may help you:
http://social.technet.microsoft.com/Forums/lync/en-US/7e67bacf-4895-4bdb-95b8-0aff8a0c575f/geographical-placement-of-office-web-app-servers?forum=lyncdeploy
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Requirements about delay and bandwith for using OTV in Nexus 7000 between two data centers separated 25 miles?

We have two Nexus 7000, and I need use them with OTV between two data Centers separated 25 miles, but I don´t know what are the optimal values about bandwidth and delay (ms) for extended VLANs IDs (production and DAG replication) for Microsoft Exchange environment. Can somebody tell me please which are the values required for operate OTV in optimal conditions in this case? We have about 35 000 users that will use that platform of email. Thanks a lot for your comments. Regards.

We have two Nexus 7000, and I need use them with OTV between two data Centers separated 25 miles, but I don´t know what are the optimal values about bandwidth and delay (ms) for extended VLANs IDs (production and DAG replication) for Microsoft Exchange environment. Can somebody tell me please which are the values required for operate OTV in optimal conditions in this case? We have about 35 000 users that will use that platform of email. Thanks a lot for your comments. Regards.

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).

Unable to create extended vlan

Dear All,
Is there anyway to create extended vlan(from 1006 to 1010) on my cisco 7604? These are existing customer vlan which I planned to move to this 7604 but unfortunately cant. I believe only FDDI and Token ring vlan unable to remove. Expert please advice.
PBR#sh ver
Cisco Internetwork Operating System Software
IOS (tm) s3223_rp Software (s3223_rp-IPSERVICES_WAN-M), Version 12.2(18)SXF17, R
ELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by cisco Systems, Inc.
Compiled Fri 25-Sep-09 06:10 by ccai
Image text-base: 0x40101040, data-base: 0x42A509B0
ROM: System Bootstrap, Version 12.2(17r)SX3, RELEASE SOFTWARE (fc1)
BOOTLDR: s3223_rp Software (s3223_rp-IPSERVICES_WAN-M), Version 12.2(18)SXF17, R
ELEASE SOFTWARE (fc1)
PBR uptime is 11 weeks, 1 day, 21 hours, 33 minutes
Time since PBR switched to active is 11 weeks, 1 day, 21 hours, 33 min
utes
System returned to ROM by power cycle (SP by power on)
System image file is "sup-bootdisk:s3223-ipservices_wan-mz.122-18.SXF17.bin"
cisco CISCO7604 (R7000) processor (revision 2.0) with 458752K/65536K bytes of me
mory.
Processor board ID FOX1340GBXD
R7000 CPU at 300Mhz, Implementation 0x27, Rev 3.3, 256KB L2, 1024KB L3 Cache
Last reset from power-on
SuperLAT software (copyright 1990 by Meridian Technology Corp).
X.25 software, Version 3.0.0.
Bridging software.
TN3270 Emulation software.
18 Virtual Ethernet/IEEE 802.3 interfaces
57 Gigabit Ethernet/IEEE 802.3 interfaces
1915K bytes of non-volatile configuration memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
PBR#
PBR#sh vlan
VLAN Name Status Ports
1 default active Gi3/14, Gi3/44
2 HPeP_Terrestrial_Side active
3 HPeP_Satellite_Side active Gi3/23, Gi3/24
5 Management active Gi3/1, Gi3/2, Gi3/3, Gi3/4
Gi3/5, Gi3/6, Gi3/7, Gi3/8
Gi3/9, Gi3/12, Gi3/13, Gi3/15
Gi3/31, Gi3/35
6 Customer_Traffic active Gi3/11, Gi3/37, Gi3/38
8 GCU active Gi3/33, Gi3/34
20 SIME active
45 Petrofac active
51 140.176.51.0/24-client-vlan active
101 Internet_Connection active Gi1/1, Gi1/2, Gi3/16, Gi3/26
190 BUK_FVSB active
201 Customer_VLAN_201 active
202 GITNS2A active
203 Internet_Connection_New active Gi3/17, Gi3/48
204 Sports_Toto_Malaysia active
205 XOM_EXXONMOBIL active
206 PCSB active
990 Unused_Ports active Gi1/3, Gi1/4, Gi1/5, Gi1/6
Gi1/7, Gi1/8, Gi1/9
999 RSPAN active
1002 fddi-default act/unsup
1003 token-ring-default act/unsup
1004 fddinet-default act/unsup
1005 trnet-default act/unsup
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
1 enet 100001 1500 - - - - - 0 0
2 enet 100002 1500 - - - - - 0 0
3 enet 100003 1500 - - - - - 0 0
5 enet 100005 1500 - - - - - 0 0
6 enet 100006 1500 - - - - - 0 0
8 enet 100008 1500 - - - - - 0 0
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
20 enet 100020 1500 - - - - - 0 0
45 enet 100045 1500 - - - - - 0 0
51 enet 100051 1500 - - - - - 0 0
101 enet 100101 1500 - - - - - 0 0
190 enet 100190 1500 - - - - - 0 0
201 enet 100201 1476 - - - - - 0 0
202 enet 100202 1500 - - - - - 0 0
203 enet 100203 1500 - - - - - 0 0
204 enet 100204 1500 - - - - - 0 0
205 enet 100205 1500 - - - - - 0 0
206 enet 100206 1500 - - - - - 0 0
990 enet 100990 1500 - - - - - 0 0
999 enet 100999 1500 - - - - - 0 0
1002 fddi 101002 1500 - - - - - 0 0
1003 tr 101003 1500 - - - - - 0 0
1004 fdnet 101004 1500 - - - ieee - 0 0
1005 trnet 101005 1500 - - - ibm - 0 0
Remote SPAN VLANs
999
Primary Secondary Type Ports
PBR#
PBR# sh vlan internal usage
VLAN Usage
1006 online diag vlan0
1007 online diag vlan1
1008 online diag vlan2
1009 online diag vlan3
1010 online diag vlan4
1011 online diag vlan5
1012 PM vlan process (trunk tagging)
1013 Control Plane Protection
1014 L3 multicast partial shortcuts for VPN 0
1015 Egress internal vlan
1016 Multicast VPN 0 QOS vlan
1017 GigabitEthernet3/27
1018 GigabitEthernet3/47
1029 IPv6 Multicast Egress multicast
1030 L3 multicast partial shortcuts for VPN 1
1031 Multicast VPN 1 QOS vlan
1032 L3 multicast partial shortcuts for VPN 3
1033 Multicast VPN 3 QOS vlan
1034 L3 multicast partial shortcuts for VPN 5
1035 Multicast VPN 5 QOS vlan
1036 L3 multicast partial shortcuts for VPN 6
1037 Multicast VPN 6 QOS vlan
PBR#

As Cisco Freak said, those vlans are being allocated for internal use
Layer 3 LAN ports, WAN interfaces and subinterfaces, and some software features use internal VLANs in the extended range. You cannot use an extended range VLAN that has been allocated for internal use.
In order to use them, you will need to use a descending vlan allocation option, to start allocation from vlan 4094 and down, to do this you will need to apply the command:
vlan internal allocation policy descending
And then reboot your switch, so the internal vlans get reallocated
For more info refer to this configuration guide:
http://www.cisco.com/c/en/us/td/docs/routers/7600/ios/15S/configuration/guide/7600_15_0s_book/vlans.html#pgfId-1038695

OTV-Extended VLAN Gateway

I am working on this design where the DC VLANs that need to be extended to DRC via OTV have their gateways as SVIs on a server agg VSS. So there is no FHRP in DC. The other side (DRC) server aggregation is a pair of VDCs on N7K. See figure for connectivity summary.
I need to maintain the gateway IP address on both sides for each extended VLAN. So for VLAN100 the gateway in DC is SVI-100 on the VSS pair with IP address 10.0.0.254 while in the DRC side it is an HSRP VIP address of 10.0.0.254. This is required to maintain the server network card configuration once it is moved from DC to DRC.
In order to avoid tromboning traffic destined across VLANs and prevent it from traversing the OTV link, what possible solutions are available? I have been reading OTV design and best practices documentation and I think FHRP isolation is irrelevant, or is it?

Although FHRP is not issue here, but you still need to block 'ARP for default gateway' and 'MAC address of default gateway' which is advertised by IS-IS.
you can refer this link for more details:
http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Data_Center/DCI/whitepaper/DCI3_OTV_Intro.pdf

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

Extending VLAN across Data centers

Similar Messages

Maybe you are looking for