Nexus 5K - Data Center to Data Center

Hi All,
A scenario was recently presented to me that involved connecting two SANs between two Data Centers. One of the Data Centers is existing and utilizes Nexus 5K switches while the other Data Center will be greenfield and is currently just a shell.
From what I've been reading the Nexus 5K does not support FCIP and I have some concerns regarding the feasibility to perform SAN to SAN over a Service Providers WDM infrastructure; mainly due to cost. More reading suggested that this could not be done with FCoE.
Just wanted to pick everyones brain regarding what solutions are available to interconnect two SANs between Data Centers. The solution would involve using a Service Provider, Ethernet and WDM services are available to both locations.

You can add a pair of MDS9222i in the middle. This will take care of FCIP, DWDM traffic.

Similar Messages

New Galaxy Nexus Release Date Rumor

So maybe we won't have to wait until after Thanksgiving
http://www.androidcentral.com/galaxy-nexus-set-verizon-nov-17-well
Please, let it be so. My old Droid is on life support. I need them to release this phone.

Rumor Update: This article says the release will happen on November 21st. No answer if that means it will be available for purchase on the 21st or available for order.
http://www.androidcentral.com/nov-21-enters-galaxy-nexus-date-grab-bag

Nexus 9396PX Data centre switch not booting.

Nexus 9300 switches are not loading with code and getting the below error.
Loader> prompt and i tried with boot command and no luck.
Do we need crossover cable for netboot from tftp server?
Configured the IP setting in the nexus through Set command.
PC-------------Nexus9300(mgmt0) port.

Thanks Colin,
I was thinking towards a 6500
For a small setup with currently about 20 clients, and looking towards increasing that to about 50 in the next year, would a single / pair of 6500's be a suitable core.
Is there any benefit in setting up an MPLS core with routers etc, I have done it in labs but can't see how to scale it for a real world implementation.
I am thinking the VRF separation on the 6500 is going to be sufficient and forget MPLS?
Roger

Galaxy Nexus Data Issues

So, I have no 3g/4g data connection. Went to the Verizon store and they went as far as replacing my SIM card and even the phone. Still no data. I can text and make calls just fine and WiFi works. So they had to open a trouble ticket with support. Seems other phones are working fine (lg, motorola, HTC), just not my Nexus.
Anyone else using the Galaxy Nexus having data problems?
thanks

budone wrote:
techbeck wrote:
So, I have no 3g/4g data connection. Went to the Verizon store and they went as far as replacing my SIM card and even the phone. Still no data. I can text and make calls just fine and WiFi works. So they had to open a trouble ticket with support. Seems other phones are working fine (lg, motorola, HTC), just not my Nexus.
Anyone else using the Galaxy Nexus having data problems?
thanks
Where are you located?
Freeport IL I have a trouble ticket opened and was just curious if I was the only one. I had a 1x connection for about 10min.

Data Center Aggregation/Access SW Nexus

i have a design scinario for backup email data center, some difficulties faced when trying to match the requirements to Boxes.
the design required a Nexus 5548UP with addition to 2x Virtualized Data center switches, also it required 12 x CPU license for VM Virtual Network Switch. i suggested to add Nexus 1000 series but the consern is can i use it without adding Nexus 2k . if i have to use N2k and N1k what is the best configuration scinario?

Hi Shakeeb,
I don't understand your question very well, but I will try clarify some points.
You don't need a Nexus 2000 if you have enough ports available in your Nexus 5500, even if you will use nexus 1000v.
In this scenario what I recommend to you is connect the both Nexus 5548 each other and create a vpc with upstreams routers and downstream blades and storage.
Richard

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.

Data Center Hall Temperature for Cisco Nexus 7010

Hi,
I Have a Nexus 7010 that sometimes raise an alarm about temperature thresholds that are being exceeded.... I was wondering if Cisco has a recommendation (or best practice) about the correct temperature that the Nexus need in the cold and hot hall of the data room. I know that the operative temperature of nexus is 0 - 40°C but i´m not sure if my halls are in the best temperature.

Hi Salvador,
As long as you keep your Data Center environment in this operative range your N7K will be fine.
The usual is around 18°C and 24°C.
Richard

Data Center - Nexus, UCS, ASA and SAN

Does anyone have a logical diagram showing the relatioship between Cisco products in the Data Center.

You can read through the Design Guides-
http://www.cisco.com/en/US/netsol/ns743/networking_solutions_program_home.html

Welcome to the Solutions and Architectures Data Center & Virtualization Community

Welcome to the Solutions and Architectures Data Center & Virtualization Community. We encourage everyone to share their knowledge and start conversations related to Data Center and Virtualization Solutions and architectures.All topics are welcome, including Servers – Unified Computing, Data Center Security, Data Center Switching, Data Center Management and Automation, Storage Networking, Application Networking Services and solutions to solve business problems.
Remember, just like in the workplace, be courteous to your fellow forum participants. Please refrain from using disparaging or obscene language or posting advertisements.
Cheers,
Dan Bruhn

Hi,
I have a question...
I going to install two Nexus 7009 with three N7K-F248XP-25 modules on each one, I am planning to create 3 VDC, but at the initial configuration the system does not show the ethernets ports of these modules, even with the show inventory and show module I can see tah the modules are recognized and its status is OK. There is something that I have to do before start to configure these modules...? enable some feature or license in order to see the ports with show running CLI...?

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

Please shed some light on Data Center design

Hi,
    I want you guys to recommend what the design should be. I'm familiar with HP blade system. Let me clarify the existing device.
1. HP Blade with Flex Fabric. It supports FCOE.
2. MDS SAN switch for the storage
3. Network Switch for IP network.
4. HP Storage.
    HP Blade has 2 interface types for IP Network(Network Switch) and Fiberchannel(SAN).
   What is the benifit for using Nexus switch and FCOE for my exising devices. What should be a new design with Nexus switch? Please guide me ideas.
THX
Toshi

Hi, Toshi:
Most of these chat boards have become quite boring. Troubleshooting OSPF LSA problems is old news. But I do pop my head in every now and then. Also, there are so many other companies out there doing exciting things in the data center. You have Dell, Brocade, Arista, Juniper, etc. So one runs the risk of developing a myopic view of the world of IT by lingering around this board for too long.
If you want to use the new B22 FEX for the HP c7000 blade chassis, you certainly can. That means the Nexus will receive the FCoE traffic and leverage its FCF functionality; either separate the Ethernet and FC traffic there, or create a VE-port instantiation with another FCF for multihop deployments. Good luck fighting the SAN team with that one! Another aspect of using the HP B22 is the fact that the FEX is largely plug and play, so you dont have to manage the Flex Fabric switches.
HTH

Ask the Expert: Data Center Integrated Systems and Solutions

Welcome to this Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about utilizing Cisco data center technology and solutions with subject matter expert Ramses Smeyers. Additionally, Ramses will answer questions about FlexPOD, vBlock, Unified Computing Systems, Nexus 2000/5000, SAP HANA, and VDI.
Ramses Smeyers is a technical leader in Cisco Technical Services, where he works in the Datacenter Solutions support team. His main job consists of supporting customers to implement and manage Cisco UCS, FlexPod, vBlock, VDI, and VXI infrastructures. He has a very strong background in computing, networking, and storage and has 10+ years of experience deploying enterprise and service provider data center solutions. Relevant certifications include VMware VCDX, Cisco CCIE Voice, CCIE Data Center, and RHCE.
Remember to use the rating system to let Ramses know if you have received an adequate response.
Because of the volume expected during this event, Ramses might not be able to answer every question. Remember that you can continue the conversation in the Data Center Community, under the subcommunity Unified Computing, shortly after the event. This event lasts through August 1, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hi Ramses,
I have dozen questions but will try to restrain myself and start with the most important ones :)
1. Can cables between IOM and FI be configured in a port-channel? Let me clarify what I"m trying to achieve: if I have only one chassis with only one B200M3 blade inside, will the 2208 IOM and FI6296 allow me to achieve more than 10Gbps throughput between the blade and the Nexus 5k? Of course, we are talking here about clean ethernet environment.
B200M3 --- IOM2208 --- 4 links --- FI6296 --- port-channel (4 links) --- Nexus5548
2. Is it possible to view/measure throughput for Fibre Channel interfaces?
3. Here is one about FlexPod: I know that in case of vBlock there is the company that delivers fully preconfigured system and offers one universal support point so customer don't have to call Cisco or VMware or storage supports separately. What I don't know is how it works for FlexPod. Before you answer that you are not sales guy, let me ask you more technical questions: Is FlexPod Cisco product or is NetApp product or this is just a concept developed by two companies that should be embraced by various Cisco/NetApp partners? As you obviously support Datacenter solutions, if customer/partner calls you with are FlexPod related problem, does it matter for you, from support side, if you are troubleshooting fully compliant FlexPod system or you'll provide same level of support even is the system is customized (not 100% FlexPod environment)?
4. When talking about vCenter, can you share your opinion about following: what is the most important reason to create the cluster and what will be the most important limitation?
5. I know that NetApp has feature called Rapid Clones that allows faster cloning than what vCenter offers. Any chance you can compare the two? I remember that NetApp option should be much faster but didn't understand what is actually happening during the cloning process and I'm hoping you can clarify this? Maybe a quick hint here: seems to me it will be helpful if I could understand the traffic path that is used in each case. Also, it will be nice to know if Vblock (i.e. EMC) offers similar feature and how it is called.
6. Can I connect Nexus 2000 to the FI6xxx?
7. Is vBlock utilizing Fabric Failover? Seems to me not and would like to hear your opinion why.
Thanks for providing us this opportunity to talk about this great topic.
Regards,
Tenaro

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

Data center design guide

Hi all,
does anybody familiar with good design guide of Cisco data center design evolving nexus 2000, 5000 & 7000 with FCoE ?
thanks,

Hi all,does anybody familiar with good design guide of Cisco data center design evolving nexus 2000, 5000 & 7000 with FCoE ?thanks,
Hi ,
Check out the below link on Data center design with Nexus switches
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/C07-572831-00_Dsgn_Nexus_vPC_DG.pdf
Hope to Help !!
Ganesh.H
Remember to rate the helpful post

Nexus 5K - Data Center to Data Center

Similar Messages

Maybe you are looking for