Data centers are undergoing a major transition to meet higher performance, scalability, and resiliency requirements with fewer resources, smaller footprint, and simplified designs. These rigorous requirements coupled with major data center trends, such as virtualization, data center consolidation and data growth, are putting a tremendous amount of strain on the existing infrastructure and adding complexity. MDS 9710 is designed to surpass these requirements without a forklift upgrade for the decade ahead.
MDS 9700 provides unprecedented
Performance - 24 Tbps Switching capacity
Reliability -- Redundancy for every critical component in the chassis including Fabric Card
Flexibility -- Speed, Protocol, DC Architecture
In addition to these unique capabilities MDS 9710 provides the rich feature set and investment protection to customers.
In this series of blogs I plan to focus on design requirements of the next generation DC with MDS 9710. We will review one aspect of the DC design requirements in each. Let us look at performance today. A lot of customers how MDS 9710 delivers highest performance today. The performance that application delivers depend
Imagine that you head the leading telecommunications provider in Italy and you are watching traditional service and revenue streams struggle under intense competitive pressure. Customer retention is a major issue because the types of services required by your residential and business clients are changing. Clearly, you need to retain customers and do so by offering new services. It is a generally known business fact that often it is more cost effective to invest in retaining customers than trying to get new ones in such competitive industries.
So, how would you do it?
FASTWEB, a Swisscom company, asked Cisco exactly that question. FASTWEB’s analysis indicated that offering cloud-based service delivery would be an excellent opportunity to retain existing business while capturing new revenue streams from Italian businesses looking for new IT solutions. But FASTWEB struggled with execution due to insufficient resources to develop and deliver these new services.
So, FASTWEB adopted Cisco’s Unified Data Center architecture which includes Cisco UCS Blade Servers and Intelligent Automation for Cloud (IAC). Cisco UCS servers were selected for performance, reliability, and the ability to integrate smoothly with other heterogeneous elements in their solution stack. They thoroughly analyzed cloud management solutions, and Cisco IAC scored the highest in their evaluation for:
• Openness and flexibility
• Ease of use by users and administrators
• Single management console access to the entire cloud service lifecycle
• Ability to build services without deep technical skills
Teaming with Cisco Services, FASTWEB implemented cloud service delivery across six distinct use cases. Because of UCS they did so with minimum server hardware, gaining a complete cloud infrastructure that consumes only a few racks. With this Cisco Unified Data Center strategy and solution, FASTWEB estimates their customers can save around 50 percent over three years utilizing FASTWEB services compared to on-premises infrastructure.
What’s more FASTWEB relies on Cisco IAC to offer customers a portal that is intuitive with fast delivery thanks to strong automation and orchestration of all cloud elements, including network. None of their competitors in the Italian marketplace has an offering equal to this unified solution from Cisco.
Now FASTWEB’s cloud services are growing smoothly thanks to technology that scales as quickly as their business does. FASTWEB plans to expand its use of Cisco IAC to offer new services as such PaaS and SaaS for their customers.
Do you have a need for automated provisioning of your data center? Cisco Prime Data Center Network Manager (DCNM) might just provide that solution.
DCNMis designed to help you efficiently implement, visualize, and manage the Cisco Unified Fabric. The need today in the datacenter is for a comprehensive management platform that delivers visibility as well as control of all elements within the Unified Fabric which in turn significantly simplifies troubleshooting, maintenance and provisioning of the entire fabric in a fast and efficient way.Watch the video below to find out more.
In one of my earlier blogs, -- “How to get more SAN mileage….” -- I had highlighted how one can deploy End-to-End FCoE using a converged Director-class platform, like Nexus 7000, connected directly from the converged access switch, like UCS FI, in order to get the utmost agility. Well, this is how ITOCHU Techno-Solutions Corporation (CTC), a Cloud Service provider, deployed its network to get significantly higher mileage.
CTC provides a wide range of IT services for business customers in Japan. The company’s Cloud Platform Group recently launched its innovative ElasticCUVIC shared private cloud service, which helps customers reduce infrastructure cost and management complexity. With large numbers of VMs, CTC wanted to simplify its data center architecture and IT management while optimizing scalability. The challenge was to deliver high-performance, easy-to-manage cloud services at scale.
The company evaluated several storage networking solutions and turned to Cisco for Fibre Channel over Ethernet (FCoE) solutions, which greatly simplify the infrastructure and management. CTC built its two newest data centers in Yokohama and Kobe with ultra-high performance and flexibility in mind. CTC implemented an End-to-End FCoE architecture using Cisco Nexus 7000 Series Switches, Cisco UCS servers, and FCoE connections between the switches, servers, and FCoE storage arrays.
With the converged FCoE architecture, ElasticCUVIC is enabling CTC customers to gain Read More »
Mileage (miles per gallon) is one of the important criteria while buying any automobile and once bought, it is highly desirable to hit the maximum advertised mileage withoutsignificantly changing the driving habits or the routes (highway vs city mpg). Well, I have not been able to achieve that yet, so being a geek, I focused my attention on a different form of mileage (throughput per switch-port) that interests me at work. So in this blog, I would explore a way to get more SAN mileage from the Cisco UCSFI (Fabric Interconnect)without significantly affecting the SAN admin’s day-to-day operations.
Just a bit of background before we delve into the details -- The I/O fabric between the UCS FI and the UCS Blade Server Chassis is a converged fabric, running FCoE. The usage of FCoE within the UCS fabric is completely transparent to the host operating system, and any Fibre Channel block storage traffic traverses this fabric as the FCoE traffic. So, a large number of over 20,000+ UCS customers, using Block Storage, are already using FCoE at the access layer of the network.
Now, the key question is what technology, FC or FCoE, to use northbound on the FI uplink ports to connect to an upstream Core switch for the SAN connectivity. So, what are the uplink options? Well, the FI has Unified ports and the choice is using the same uplink port as either 8G FC -or- 10G FCoE. [Note that when using the FCoE uplink, it is not a requirement to use a converged link and one can still use a dedicated FCoE link for carrying pure SAN traffic].
1) Bandwidth for Core Links: This is a very important aspect for the core part of the network. It is interesting to note that 10G FCoE provides almost50% more throughput than the 8G FC. This is because FC has a different bit encoding and clock-rate than Ethernet, and so 8G FC yields 6.8G throughput while 10G FCoE yields close to 10G throughput (post 1-2% Ethernet frame overhead)
2) Consistent Management Model: FCoE is FC technology with same management and security model, so it will be a seamless transition for a SAN admin to move from FC to FCoE with very minimal change in the day-to-day operations. Moreover, this FCoE link is carrying dedicated SAN traffic without requiring any convergence of LAN traffic. To add to that, if the UCS FI is running in the NPV mode, then technically the FCoE link between the UCS FI and the upstream SAN switch does not constitute a Multi-Hop FCoE design, as the UCS FI is not consuming a Domain-ID, and the bulk of SAN configurations like zoning etc. need to happen on only the Core SAN switch, thus maintaining the same consistent SAN operational model as with just the FC.
3) Investment Protection with Multi-protocol flexibility: By choosing FCoE uplink from the converged access layer, one can still continue to use the upstream core SAN Director switch as-is, providing the connectivity to existing FC Storage arrays. Note that Cisco MDS 9000 SAN Director offers Multi-protocol flexibility so that one can Interconnect FCoE SANs on the Server-side with the FC SANs on the Storage-side.