10-19-2012 02:19 AM - edited 03-01-2019 05:57 AM
Cisco's Nexus switches offer the latest in Next-Generation Data Center switching innovations that enable efficient virtualization, high-performance computing, and a unified fabric. There is a wide range of Cisco Nexus family products that support different features and capabilities. Consequently designing a data center network that uses Cisco’s Next Generation of data center switches (Nexus) requires a very good understanding of the data center network recruitments such as servers’ network connectivity requirements, protocols, layer 2/layer 3 demarcation points, data center interconnect requirements and traffic load.
For more details about Cisco Nexus family products see the following link:
http://www.cisco.com/en/US/products/ps9441/Products_Sub_Category_Home.html
This document will briefly discuss some high level design examples of data center networks that utilise Cisco Nexus Switches with emphasis on the mapping between data center business requirements and the selected hardware and features to meet these requirements, taking into consideration the size of the data center network.
Note:
The bellow design examples can be used as a guide/reference only and are not Cisco’s official best practice solutions
XYZ.com has a small size data center with the following requirements
2x Cisco Nexus 5548 with the following HW specifications per chassis:
Using Cisco nexus 5500 series in a small to medium data cneter can provide a reliable and cost effective data center switching solution. Based on the above requirements nexus 5548 can provide the following:
XYZ.com has a medium size data center with the following requirements
2x Cisco Nexus 7009 with the following specifications per chassis:
XYZ.com has 2x large data centers with the following requirements:
Recommended Hardware per DC:
DC core:
DC aggregation:
DC Access:
The above HW can meet the requirements by providing:
Regards,
Marwan Alshawi
In example 2 can you go with 12 FEX's directly connected to the 7k's? In our PDC we have the 7/5/2k, but in our SDC we're looking to use a scaled down model and remove the 5k (smaller DC and less 10G).
I know it scales to 32 FEX's but the real question is, how does this architecture differ from a 7/5/2 design. What are the implications of this design? Will the 2k interface commands and code upgrade process remain the same? At what point do you need to add a 5k?
Hi Michael,
you are right, you can go up to 32 FEXs, and going to this type of architecture is something depends on your requirements, for example you can check the features and capability supported when using N2K to N5K vs N2K to N2K and see if this is not going to effect your DC requirements, however this design is going to reduce the number of L2 hops but you will need to consider using the collapsed architecture in the N7K with VDCs to help you use vPC(multi-homing) between the access VDC and distribution VDC on both 2K chassis. the FEXs will only extend the access layer for more services to be connected, also the N2K port channel can span several I/O Modules of the 7K for redundancy
Regards,
Nice!
+5
Hi, on Example #2 - Why do we need the Core? What are the benefits? Please elaborate - Thanks
Hi
in example 2 the core function is combined with the distribution to perform L3 routing with the campus core or WAN edge
it is not a pure core like example 3 and again this is a design choice that can change depending on the network
test comment
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: