Data Center Core based on EoMPLS ?

Hi,
We've currently a data center based on Layer 2 with many inter building links blocked by STP. To simplify a little bit the layer 2 topology (and improve inter-building link usage) i would like to introduce EoMPLS inside my Data Center core.
Is that a good idea ? or something to rapidly forget ?
regards
Cedric

Hello,
EoMPLS is overkill for the goal presented. Basically you would introduce Layer3 in the core (needed for MPLS) and then use MPLS to make the core look like Layer2 ...
More simple approaches:
Either tune your STP (or better use Rapid Per VLAN STP or MVST) to get some load balancing and also convergence speed.
Or convert to a L3 core - i.e. IP routed. The latter step might require IP readdressing, which can be a major pain. On the other hand you then have separated broadcast (and failure) domains, nice load balancing, fast convergence and no more big STP hassle.
Hope this helps! Please rate all posts.
Regards, Martin

Similar Messages

Data Center Design: Nexus 7K with VDC-core/VDC-agg model

Dear all,
I'm doing with a collapsed VDC-core/VDC-agg model on the same chassis with 2 Redundant Cisco Nexus 7010 and a pair of Cisco 6509 used as a Service Chassis without VSS. Each VDC Core have redundant link to 2 PE based on Cisco 7606.
After reading many design document of Cisco, I'm asking what is the need of a Core Layer in a Data Center especially if it is small or medium size with only 1 aggregation layer and dedicated for a Virtualized Multi-Tenanted environement? What is driving to have a core layer?
Thanx

If your data center is small enough to not require a core, then its fine to run with a collapsed core (distribution + core as the same device). For a redundant design you need to uplink all your distribution switches to each of your cores. If you have no cores, then you need full mess at your distribution layer (for full redundancy).
Lets say you have only 4 distribution pairs...so 8 switches For full redundancy each one needs uplink to each other. This means you need 28 total ports used to connect all the switches together (n(n-1)/2). Thats also assuming 1 link to each device. However if you had redundant cores, the number of links used for uplinks reduces to 21 total links (this includes links between each distribution switch in a site, and link between the two cores). So here you see your only saving 7 links. Here your not gaining much by adding a core.
However if you have 12 distribution pairs...so 24 switches. Full redundancy means you have 276 links dedicated for this. If you add a core, this drops to 61 links. Here you see the payoff.

New Technical Article: Securing a Cloud-Based Data Center

Securing a Cloud-Based Data Center
by Orgad Kimchi, Ron Larson, and Richard Friedman
Orgad, Ron, and Richard and explain the precautions you need to take when deploying a private cloud in a data center, and show you how to employ the security features in Oracle Solaris 11 to protect its infrastructure. Part 2 of a three-part article on cloud deployments that use the Oracle Solaris Remote Lab as a case study.
- Rick

The beautiful curve drawn by LDPC code caught my eyes, but several points hardly built up user confidence.Some details should be submitted carefully, especially comparison with BCH codes. In my opinion, X-axis is exact error bit count and Y axis is frame error rate. Then, BCH comparison is a theoretical vertical line. LDPC code will be well described in a group of points.
Moreover, can Xilinx provide more codes with different rate to support flexible design?

Ask the Expert: Scaling Data Center Networks with Cisco FabricPath

With Hatim Badr and Iqbal Syed
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about the Cisco FabricPath with Cisco technical support experts Hatim Badr and Iqbal Syed. Cisco FabricPath is a Cisco NX-OS Software innovation combining the plug-and-play simplicity of Ethernet with the reliability and scalability of Layer 3 routing. Cisco FabricPath uses many of the best characteristics of traditional Layer 2 and Layer 3 technologies, combining them into a new control-plane and data-plane implementation that combines the immediately operational "plug-and-play" deployment model of a bridged spanning-tree environment with the stability, re-convergence characteristics, and ability to use multiple parallel paths typical of a Layer 3 routed environment. The result is a scalable, flexible, and highly available Ethernet fabric suitable for even the most demanding data center environments. Using FabricPath, you can build highly scalable Layer 2 multipath networks without the Spanning Tree Protocol. Such networks are particularly suitable for large virtualization deployments, private clouds, and high-performance computing (HPC) environments.
This event will focus on technical support questions related to the benefits of Cisco FabricPath over STP or VPC based architectures, design options with FabricPath, migration to FabricPath from STP/VPC based networks and FabricPath design and implementation best practices.
Hatim Badr is a Solutions Architect for Cisco Advanced Services in Toronto, where he supports Cisco customers across Canada as a specialist in Data Center architecture, design, and optimization projects. He has more than 12 years of experience in the networking industry. He holds CCIE (#14847) in Routing & Switching, CCDP and Cisco Data Center certifications.
Iqbal Syed is a Technical Marketing Engineer for the Cisco Nexus 7000 Series of switches. He is responsible for product road-mapping and marketing the Nexus 7000 line of products with a focus on L2 technologies such as VPC & Cisco FabricPath and also helps customers with DC design and training. He also focuses on SP customers worldwide and helps promote N7K business within different SP segments. Syed has been with Cisco for more than 10 years, which includes experience in Cisco Advanced Services and the Cisco Technical Assistance Center. His experience ranges from reactive technical support to proactive engineering, design, and optimization. He holds CCIE (#24192) in Routing & Switching, CCDP, Cisco Data Center, and TOGAF (v9) certifications.
Remember to use the rating system to let Hatim and Iqbal know if you have received an adequate response.
They might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Data Center sub-community Unified Computing discussion forum shortly after the event. This event lasts through Dec 7, 2012.. Visit this support forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hi Sarah,
Thank you for your question.
Spanning Tree Protocol is used to build a loop-free topology. Although Spanning Tree Protocol serves a critical function in these Layer 2 networks, it is also frequently the cause of a variety of problems, both operational and architectural.
One important aspect of Spanning Tree Protocol behavior is its inability to use parallel forwarding paths. Spanning Tree Protocol forms a forwarding tree, rooted at a single device, along which all data-plane traffic must flow. The addition of parallel paths serves as a redundancy mechanism, but adding more than one such path has little benefit because Spanning Tree Protocol blocks any additional paths
In addition, rooting the forwarding path at a single device results in suboptimal forwarding paths, as shown below, Although a direct connection may exist, it cannot be used because only one active forwarding path is allowed.
Virtual PortChannel (vPC) technology partially mitigates the limitations of Spanning Tree Protocol. vPC allows a single Ethernet device to connect simultaneously to two discrete Cisco Nexus switches while treating these parallel connections as a single logical PortChannel interface. The result is active-active forwarding paths and the removal of Spanning Tree Protocol blocked links, delivering an effective way to use two parallel paths in the typical Layer 2 topologies used with Spanning Tree Protocol.
vPC provides several benefits over a standard Spanning Tree Protocol such as elimination of blocker ports and both vPC switches can behave as active default gateway for first-hop redundancy protocols such as Hot Standby Router Protocol (HSRP): that is, traffic can be routed by either vPC peer switch.
At the same time, however, many of the overall design constraints of a Spanning Tree Protocol network remain even when you deploy vPC such as
1.     Although vPC provides active-active forwarding, only two active parallel paths are possible.
2.     vPC offers no means by which VLANs can be extended, a critical limitation of traditional Spanning Tree Protocol designs.
With Cisco FabricPath, you can create a flexible Ethernet fabric that eliminates many of the constraints of Spanning Tree Protocol. At the control plane, Cisco FabricPath uses a Shortest-Path First (SPF) routing protocol to determine reachability and selects the best path or paths to any given destination in the Cisco FabricPath domain. In addition, the Cisco FabricPath data plane introduces capabilities that help ensure that the network remains stable, and it provides scalable, hardware-based learning and forwarding capabilities not bound by software or CPU capacity.
Benefits of deploying an Ethernet fabric based on Cisco FabricPath include:
• Simplicity, reducing operating expenses
– Cisco FabricPath is extremely simple to configure. In fact, the only necessary configuration consists of distinguishing the core ports, which link the switches, from the edge ports, where end devices are attached. There is no need to tune any parameter to get an optimal configuration, and switch addresses are assigned automatically.
– A single control protocol is used for unicast forwarding, multicast forwarding, and VLAN pruning. The Cisco FabricPath solution requires less combined configuration than an equivalent Spanning Tree Protocol-based network, further reducing the overall management cost.
– A device that does not support Cisco FabricPath can be attached redundantly to two separate Cisco FabricPath bridges with enhanced virtual PortChannel (vPC+) technology, providing an easy migration path. Just like vPC, vPC+ relies on PortChannel technology to provide multipathing and redundancy without resorting to Spanning Tree Protocol.
Scalability based on proven technology
– Cisco FabricPath uses a control protocol built on top of the powerful Intermediate System-to-Intermediate System (IS-IS) routing protocol, an industry standard that provides fast convergence and that has been proven to scale up to the largest service provider environments. Nevertheless, no specific knowledge of IS-IS is required in order to operate a Cisco FabricPath network.
– Loop prevention and mitigation is available in the data plane, helping ensure safe forwarding that cannot be matched by any transparent bridging technology. The Cisco FabricPath frames include a time-to-live (TTL) field similar to the one used in IP, and a Reverse Path Forwarding (RPF) check is also applied.
• Efficiency and high performance
– Because equal-cost multipath (ECMP) can be used the data plane, the network can use all the links available between any two devices. The first-generation hardware supporting Cisco FabricPath can perform 16-way ECMP, which, when combined with 16-port 10-Gbps port channels, represents a potential bandwidth of 2.56 terabits per second (Tbps) between switches.
– Frames are forwarded along the shortest path to their destination, reducing the latency of the exchanges between end stations compared to a spanning tree-based solution.
    – MAC addresses are learned selectively at the edge, allowing to scale the network beyond the limits of the MAC addr

MB1A and Cost Center (KOSTL) based on Order (AUFNR)

Hello,
I have a requirement, where i must make a modification in transaction MB1A in the following way:
On the second screen "Enter Goods Issue: New items" i must fill automatically the Cost Center field, based on the Order number (after the Enter).
How can I do this?
I've tried with a substitution in GGB1 but it didn't worked:
select single kostv from coas into cobl-kostl where aufnr = cobl-aufnr.
Thanks in advance !
Tohi

HI
Can you check the below exits
Transaction Code - MB1A                     Goods Withdrawal
Enhancement/ Business Add-in            Description
Enhancement
MBCF0002                                Customer function exit: Segment text in material doc. item
MBCF0005                                Material document item for goods receipt/issue slip
MBCF0006                                Customer function for WBS element
MBCF0007                                Customer function exit: Updating a reservation
MBCF0009                                Filling the storage location field
MBCF0010                                Customer exit: Create reservation BAPI_RESERVATION_CREATE1
MBCF0011                                Read from RESB and RKPF for print list in MB26
MB_CF001                                Customer Function Exit in the Case of Updating a Mat. Doc.
BADI
MB_MIGO_BADI                            BAdI in MIGO for External Detail Subscreens
MB_MIGO_ITEM_BADI                       BAdI in MIGO for Changing Item Data
MB_PHYSINV_INTERNAL                     Connection: Core Inventory and Retail AddOn
MB_QUAN_CHECK_BADI                      BAdI: Item Data at Time of Quantity Check
MB_RESERVATION_BADI                     MB21/MB22: Check and Complete Dialog Data
MB_RESERVATION_SCR                      Screen BAdI for Retrofit DFPS
MB_RESERVATION_UPCHD                    BAdI for Creation and Changing of Manual Reservations
MB_RES_BAPI_CHANGE                      BAdI: Execution of Changes to Reservation Fields
MB_RES_BAPI_CREATE1                     BAdI: Adoption of Customer's Own Fields as Reserv. Fields
MB_RES_BAPI_DETAIL1                     BAdI: Display of Customer's Own Fields in Reservations
MB_STOR_LOC_BADI_GTS                    BADI to Check and Change Storage Location (GTS Fct. Only)

Recommended Design for WAAS in both Data center and Branch Offices

Hi All,
I need to purchase different appliances for WAAS, but before I decide what to purchase, I need to know exactly how I am going to put these devices so that I can know which one to purchase and how the designs will be.
My environment is as follows:
I have two core routers (ASR 1000 series) at Data center, two 6509 switches (expecting to insert the ACE module, and FW module) and the I have access switches which connects servers.
At the branch offices, I am expecting to place ASR1000 series also.
Now, I need to know the recommended designs for these WAAS appliances so that, I can know in advance what to purchase(i.e. how many WAAS CM, Core WAE, and Edge WAE).
Any input will highly be appreciated.
Thanks,

If you purchase the Standard Edition, your license supports:
One installation of Cisco Security Manager on one Windows-based server.
The configuration or management of 5 devices (in the Standard-5 option) or 25 devices (in the Standard-25 option). This excludes Catalyst 6500 and 7600 Series devices and their associated service modules.
If you purchase either the Standard-5 or Standard-25 license, you cannot purchase an incremental device license. Your license is fixed at either 5 or 25 devices.

Collapsed Data Center Tier - Best Practice

Hey guys,
I'm working with a company who's doing a Data Center build-out. This is not a huge build out and I don't believe I really need a 2 tier design (access, core/aggregation). I'm looking for a 1 tier design. I say this because they only really have one rack of hosts - and we are not connected to a WAN or campus network - we are a dev shop (albeit a pretty damn big dev shop) who hosts internet sites and web applications to the public.
My network design relies heavily on VRF's. I treat every web application published to the internet as it's town "tenant" with one leaked route which is my managment network so I have any management servers ( continues deployment, monitoring, etc...) sitting in this subnet that is leaked. Each VRF has their own route to a virtual firewall context of their own and out to the internet.
Right now we are in a managed datacenter. I'm going to be building out their own switching environment utilizing the above design and moving away from the managed data center. That being said I need to pick the correct switches for this 1 tier design. I need a good amount of 10gbe port density (124 ports minimum). I was thinking about going with 4 5672UP or 4 C3064TQ-10GT - these will work as both my access and core (about 61 servers, one fiber uplink to my corporate network, and one fiber uplink to a firewall running multiple device contexts via multiple vlans)
That being said - With the use of VRFs, VLAN, and MP-BGP (used to leak my routes) what is the best redundancy topology for this design. If I was using catalyst 6500's I would do VSS and be done with it - but I don't believe vPC on the nexus switches traffic and is really more for a two tier model (vPC on two cores, aggregation/access switch connects up to both cores but it looks like one.) What I need to accomplish sounds to me that I'm going to be doing this the old fashion way , running a port channel between each switch, and hopefully using a non STP method to avoid loops.
Am I left with any other options?

ISP comes into the collapsed core after a router. A specific firewall interface (firewall is in multi context mode) sits on the "outside" vlan specific to each VRF.

Layer 2 connect - data center web hosting

hi, i need your help!!
i have data center with the nexus 7000 , i have servers connecting to the cisco 7000 with web servers. my company do hosting for customers.
the poing that we have shared resources like vmwares on blades and so on.. mean that the ports of the blade are connecting physically to the nexus 7000 with trunk and vlans for every customers.
my nexus connecting to FW than to WAN stiches than to Routers connecting to the internet so if i asked to to hosting from the internet its easy.
the problem is now i have cusomer that wants to connect his switch over the wan directly to his area at my datacenter.... we make for him servers that are the same like his servers with the same subnet and he makes replications...
he dont have router, he connect his switch over wan provider at layer 2 to me..
should i connect him direcly to my nexus??? with his vlan?? should i need other solution like eompls??? what is the safest way to connect him with layer 2.. and i repeat the problem that our servers are shared between many customers - the same nexus ports, please help!!

Hello,
1.PIX is the precursor to the ASA so at this point the ASA is probably a better choice since it'll be around longer plus I'm sure they have beefed up the base hardware compared to the pix.
2.Your external router is dependant on how much traffic your going to be dropping into your hosting site. A 7200 series router is a fairly beefy router and should be able to handle what you need if your looking.
3.One of the nice things about the 6500 is you can put a FWSM and segment all your different hosting servers to provide a more granular network control.
I don't have any case studys but will look around and post them if I find some.
Patrick

Single CAS NameSpace in Multi-Data Center Model With Exchange 2013

Hi
We are in process of transitioning from Exchange 2007 to Exchange 2013. Our Exchange 2007 infrastructure is as follows:
2 Data centers (DC 1 and DC 2). Both with active user population. Both have their own direct Internet Connectivity
Standalone Exchange 2007 mailbox servers in each data center
Load Balanced CAS (HT co-located) servers using Hardware Load Balancers in each data center. Load balancers are configured with VIP and FQDNs (LoadBalancer1.Com and LoadBalancer2.com)
Currently No access allowed from Internet except ActiveSync (No OWA or OA)
Outlook anywhere is disabled in Exchange 2007 organization but once mailboxes will be moved to Exchange 2013, OA will definitely be used – we will provide OA on Intranet as well as Internet
All the internal URLs including Autodiscover point to VIP (Load Balancer IP)
Autodiscover is not currently published on Internet, but we have a plan to publish it now once Exchange 2013 is introduced
We want to keep a single CAS NameSpace BYOD.ABC.Com for our ActiveSync and OA (and not going to allow OWA) access from Internet. We want to have Split-DNS for our new Exchange 2013 infrastructure due to
the simplicity it brings. So we are going to use one name BYOD.ABC.Com from the Internet. We have GSLB that provide Fault Tolerance and Geo-Load Balance to external requests coming from Exchange clients, between two data centers. When we will
install new Exchange 2013 servers, they’ll be part of new VIP so:
In a 2 data center model, can we name our internal VIPs same in both data centers (i:e BYOD.ABC.Com) as we have decided to go with Split-DNS? Do you see any caveats to this strategy
If the above strategy will not work, what are the alternate approach(es).
If we configure same names for the VIPs in both data centers, it will mean that the Autodiscover SCPs for all the Exchange 2013 CAS objects (and Exchange 2007 CAS objects during co-existence) will point to BYOD.ABC.Com. This should not be a problem for
AD joined systems as they’ll find and contact Autodiscover endpoints in their own sites (based on Keywords attribute that tells which AD site SCP belongs to) –
Please correct me if this is wrong.
If we configure same names for the VIIPs in both data centers, this also means that we have to configure BYOD.ABC.Com on External as well as Internal URLs on all the Exchange 2013 servers across both the data centers – Wouldn’t that be a problem – in terms
of loops during CAS-CAS Proxy/Redirection?
If we configure different names of the VIPs (say BYOD1.ABC.Com and BYOD2.ABC.Com), how will the Outlook Anywhere requests be handled in both data centers. The OA requests from DC1 will expect the Certificate Principle Name to be BYOD1.ABC.Com and requests
from DC2 will expect the Certificate Principle Name to be BYOD2.ABC.Com. How to get this stuff working. As far as I know, OA expects CPN to match with it’s name.
Thanks
Taranjeet Singh
zamn

Any comments/suggestions from community......
Thanks
Taranjeet Singh
zamn

Wireing Question for Data Center

I work in what I would consider to be a small/mid sized data center. We use two 6513 as the core/distribution for ~25 racks of servers.
My question comes in the way of cabling the servers to the core. Currently they are using long patch cords between the 6513 and each server. Well its a mess, functional but messy.
I'm trying to figure out the best way to clean up the mess and make it look professional.
Most people seem to suggest 2 different ways to accomplish this:
1) Install switches in each rack and run fiber from the core to the rack. Wire each server to the switch in the rack.
2) Install 24/48 port patch panels between the core area and the racks.
I'm wondering what people think of these ideas and if there are any other suggested ways of accomplishing this?
Andy

Hi Andy,
Here's something that we used to do where I worked:
We had 6509's with three/four 48 port blades servicing between 150 and 200 phones roughly. I had four total switches, one on each of four floors. So this would be roughly similar to your DC environment, only we're servicing longer horizontal runs and phones, not servers -- but the idea is the same (i.e. high density cabling issues).
Lord knows that when you're plugging in 48 cables into one of those blades, it can get pretty crowded. And since we don't yet know how to alter the laws of physics that determine space requirements, we have to search for alternatives.
Back to my environment: On three of the four floors, we just wired straight from the patch panel (that ran to floor locations) to the switch. Quite a mess when you're running in 48 cables to one blade! However, this is traditional and this is what we did. My cabling guy (very smart fella) suggested something else. At the time I was too chicken to do it on the other floors, but I did agree to try it on one floor. Here's what we did:
He ran Cat5 (at the time, that was standard) connections in 48 cable bunches from an adjacent wall into the switch. They had RJ-45 connections so that they could plug in, and they were all nice and neat. On the other end, they plugged in to a series of punch down blocks (kind of like you see in a phone room for telephone structured cabling). These, in turn, were cross connected to floor locations on another punch down block that went to the floor locations. Now, whenever we wanted to make a connection live, we simply had to connect the correct CAT5 jumper wire from one punch down block to the other. You never touch the actual ports in the switch. They just stay where they are. All alterations are done on the punch down blocks. This keeps things nice and neat and there's no fiddling with cables in the switch area. Any time you need to put in a new blade, you just harness up 48 more cables (we called them pigtails) and put them in the new blade.
NOTE: You could do the exact same thing with patch panels instead of punch down blocks, but with higher densities, it's a bit easier to use the blocks and takes up much less space.
ADVANTAGES:
* Very neat cable design at the switch side.
* Never have to squeeze patch cables in and out.
* Easy to trace cables (but just better to document them and you'll never have to trace them).
* Makes moves, adds, and changes (particularly adds) very easy.
DISADVANTAGES:
* Not sure that you can do it with CAT6.
* You have to get a punch down tool and actually punch cables (not too bad though after you do a few).
* You need to make sure that you don't deprecate the rating on the cable by improperly terminating it (i.e. insufficient twists)
Anyway, I haven't had a need to do this in a while and I no longer work at the same place, but my biggest concern would be if that meets with the CAT6 spec. Not sure about that, but your cabling person could probably tell you.
I'm not a big fan of decentralizing the switches to remote locations. It can become cumbersome and difficult to manage if you end up with a lot of them. Also, it doesn't scale well and can end up with port waste (i.e. you have 24 servers in one cabinet on one switch and then along comes 25; you now have to buy another 12 or 24 port switch to service the need with either 11/23 ports going to waste -- not good).
Good luck. Let us know how you make out. I'd be glad to go in to more detail if the above isn't explained well enough.
Regards,
Dave

Data Center Connection using ONS 15530

Hi!
1. I am connecting 2 Data Center using DWDM on ONS 15530. The client is GE and planning on running Gigabit Etherchannel.
2. My question is, whish one is better? Using the multirate transponder or GE aggregation card to connect to GE client?
3. Either way, how does client and ONS component interconnect?
- If transponder is used, how does the OADM, OSC, trunk card and transponder connect to each other?
- If muxponder is used, what component is needed ad how does it connect?
4. FYI, I come from ONS 15540 ESPx background where everything connect externally. Apreciate you guys expert response. Thanks.
Rgds
Helme

You have three options:
1/ Use 8 port aggregation card (15530-FCGE-8P) together with 10G ITU card (4 port aggregation card is not cost effective if you are carrying only GE traffic). 10G ITU is the expensive part.
This 8 port aggregation module is connected to 10G ITU module via ONS15530 electrical backplane (not optical); 10G ITU and 8 port module both have 4x 2,5G backplane connections. 10G ITU is connected OADM using external MU-MU optical patch cords.
You can also use 2,5G ITU card but then you can only use 2 ports of the 8 port module card.
2/ Use 8 port multiservice muxponder (15530-MSMP-xxxx), this card has 2,5G capacity and card is SDH/SONET based. DWDM laser is embedded in the card, so this card is connected directly to OADM using external MU-MU optical patch cords (no backplane connections). Remember that this card is 2,5G so if you plan to use only GE you can utilize only 2 ports from the module.
3/ Use Transponders (15530-TSP1-XXX2) as you do in ONS15540. One Transponder - one client signal - one lambda. Transponder is connected directly to OADM using external MU-MU optical patch cords (no backplane connections).
What solution fits best for you depends on how many GE connections you need, what are future needs for more ports, what is your optical power budget, do you need high availability (no single point of failure) etc. Cheapest way to run only 2x GE is using option 2 above.
rgds,
Jp

Data Center Interconnect using MPLS/VPLS

We are deploying a backup data center and need to extend couple of Vlans over the backup data center.These two DC's which are interconnected by a fibre link which we manage and terminates on the ODC2MAN and ODCXMAN.We run MPLS on these devices ODC2MAN and ODCXMAN(Cisco 6880) as PE routers. I configured OSPF between these devices and advertised their loopbacks.
I need configuration assistance on my PE (odcxman and odc2man) to run the VFI and the VPLS instances.The vlans on the ODCXAGG need to extend to the ODC2AGG.
Also, I am looking for the configuration assistance such that each core devices should have 3 eigrp neighbors.
For example:
ODC2COR1 should have Eigrp neighbors with ODCXCOR1, ODCXCOR2 and ODC2COR2 and my VPLS Cloud should be emulated as a transparent bridge to my core devices such that it appears that ODC2COR1 is directly connected to ODCXCOR1 and ODCXCOR2 and have cdp neighbor relation. I have attached the diagram.Please let me know your inputs.

Hello.
If you are running Active/Backup DC scenario, I would suggest to make network design and configuration exactly the same. This includes platforms, interconnectivity types and etc.
Do you know what is the latency on the fiber between these two DCs?
Another question: why do you run 6880 in VSS, do you really need this?
Q about the diagram: are you going to utilize 4 fibers for DC interconnection?
PS: did you think about OTV+LISP instead of MPLS?

Scheduled system maintenance on US data center - November 23rd 2014

To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our US data center. To minimize the customer impact, the upgrade is scheduled at the most convenient hours and will take up to 8 hours to complete. During the maintenance procedure, creating and updating content, Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available. Additionally, during the 8 hours maintenance procedure, all sites on the US data center will experience 4 sessions of 15 minutes downtime. Except for the 4 scheduled downtime sessions, the website front-ends will not be impacted by the maintenance.
Maintenance schedule:
Start date and time: Sunday, November 23rd, 3:00 AM EST (check data center times)
Duration: We are targeting a 8 hours maintenance window
Customer impact:
Partner registration, Trial site creation, Adobe Muse publish, APIs, FTP and some admin section will not be available through the entire maintenance window on all data centers
All websites and services on US data center will experience 4 sessions of 15 minutes downtime sometimes within the maintenance window
Creating or updating content on sites located on US data center will be unavailable during the maintenance procedure
For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
Thank you for your understanding and support,
The Adobe Business Catalyst Team

agents will be online for update from console.
Method 1: Update the protection agents from the Data Protection Manager Administrator Console
Open the Data Protection Manager Administrator Console.
Click the Management tab, and then click the
Agents tab.
In the Protected Computer
list, select a computer, and then click Update on the Action pane.
Click Yes, and then click
Update Agents.
Note You may have to restart the computer after you install the agent upgrades.
Method 2:Update the protection agents on the protected computers
Obtain the update protection agent package from the following directory on the System Center 2012 R2 Data Protection Manager server:
<var>Data_Protection_Manager_installation_location</var>\DPM\DPM\Agents\RA\4.2.1217.0
The installation packages are as follows:
For x86-based updates: i386\1033\DPMAgentInstaller_KB2904687.exe
For x64-based updates: amd64\1033\DPMAgentInstaller_kb2904687_AMD64.exe
Run the appropriate DPMAgentInstaller.exe package on each protected computer, based on the architecture of the agent.
Open the Data Protection Manager Administrator Console on the System Center 2012 R2 Data Protection Manager server.
Click the Management tab, and then click the
Agents tab. Select the protected computers, update the information, and then verify that the agent version number is 4.2.1217.0
Have a nice day !!!

WAN Router Connection to Data Center

We have a WAN router that needs to connect to our Data Center network. The Data Center consists of two N7K core switches, with a pair of N5K switches as aggregation, and each N5K has twelve N2K fabric extenders. The N2Ks are single-homed to the N5Ks. The N5Ks are vPC connected to the N7Ks.
We would like to attach the WAN router to both N7K switches in the Data Center. The N7K switches only have 10G ports in them, so we can't terminate the WAN router directly to the N7Ks.
I was considering creating one dedicated VLAN on each N7K, and assigning an SVI to each VLAN, to correspond to the L3 connections between the N7Ks and the WAN router. Then, we could trunk these VLANs to each of the N5Ks, and configure one 1G port on each N5K for the VLAN, and connect the WAN router to the N5Ks.
Two questions regarding this design:
1) Is there a problem in connecting the L3 WAN router to the N7K via the N5K?
2) Does vPC connectivity between the N7K and N5K pose a problem for the proposed WAN connectivity?
Thanks in advance for any feedback.
-rb

The vPC between N5K and N7K is the catch here. Layer-3 routing over vPC member ports is currently not supported so I will advise you to stay away from this approach.
Atif

Need helip for data center designing

Sir ,
I am going to design a data center where the following equipments are the
1. one router 7609
2. two core switch (WS-C6509-E)
3. two firewall (WS-C6506-E, with Firewall blade)
4. one VOICE ROUTER (CISCO2821with PVDM2-64, VWIC2-2MFT-T1/E1, PVDM2-32)
5. one Remote Access Server (AS5400XM, AS5000XM 60 Dial Port Feature Card, AS5400 Octal E1/PRI DFC card)
6. two CALLMANAGER-5.1
7. multiple no of Cisco IP Phone 7940G with Video Advantage with VT Camera II
8. one Gatekeeper (2811)
9. one Internet Router (3845)
10. one Authentication, Authorization and Accounting (AAA) System
11. one ISDN RAS 2811 with2-Port Channelized E1/T1/ISDN-PRI Network Module with video conferencing (polycom)
12. one Network Intrusion Detection/ Prevention System (NIDS)
13. one NMS
14. one Content Switch for Server Load Balancing
15. multiple Video Phone
16. lots of sever ( mail. Web, storage, etc )
17. polycom MGC 100
18. polycom 7000
also 20 no of 7206 VXR will be connect with 7609 router through lease line
so.. if u send me some link or some sample design and share some advice where I can gather some idea to design this data center in a proper way
thanks
tirtha

IMO opinion the best place to start is by reading the SRNDs. They can be found here-
http://www.cisco.com/en/US/netsol/ns656/networking_solutions_design_guidances_list.html
Hope that helps.

Data Center Core based on EoMPLS ?

Similar Messages

Maybe you are looking for