Virtualization, Private Cloud, Big Data, HPC, etc. have been steadily changing the landscape of data center architectures. Lower latency and higher performing server-to-server data traffic (East-West) have become key discussion points as customers look to modernize their infrastructures. Cisco specifically designed UCS unified fabric for this type of traffic to create a highly-available infrastructure with reduced latency and unmatched consistency as the solution scales. Without providing any supporting data, HP and IBM have been incorrectly asserting that Cisco UCS unified fabric would increase latency and slow blade-to-blade traffic. Cisco ran the tests, and the results were simply amazing.
We are living in arguably the most exciting time in human history, and I’m mesmerized by how fast our world is evolving thanks to brilliant technologies and the sheer volume of inanimate objects that are connecting to the internet on a daily basis, forming the internet of everything (IoE).
As much as it seems everything is digital these days, our world is almost entirely analog. However, digital technology (and its massive potential to revolutionize our world) is trending toward mainstream popularity, in spite of traditionally being relegated to the minds of the ‘geeky’ few. The reason for this trend is simpler than it might initially appear and it’s the topic of this post. Read More »
Complexity and Cost Comparison: Cisco UCS vs. IBM Flex System is report recently published by Principled Technologies.
They evaluated both the technologies and costs of each solution and found a UCS solution is both less expensive to deploy and less complex to manage than an IBM Flex System.
Off all the ways Principled Technologies shows how UCS is a superior solution, I wanted to touch on just one: highly available and scalable management. A UCS management domain consists of a pair of Fabric Interconnects and supports up to 160 blade and/or rack servers. In contrast, IBM is limited to 54 blade servers plus a non-redundant Flex System Manager node. Quoting from the paper:
Because IBM Flex System Manager nodes do not failover automatically like the Cisco UCS solution, administrators must manually connect to a backup node and bring it online. Each target system has an OS agent that remains registered to the original FSM node and does not recognize the new FSM. Admins must manually unregister each of these agents from the failed node and then register the new FSM node. [page 7]
Read the full report to learn the many additional ways which UCS is shown to be superior solution and why Cisco has leapt ahead of IBM and is now the #2 blade server vendor worldwide1
Would like to learn more about how Cisco is changing the economics of the datacenter, I would encourage you to review this presentation on SlideShare or my previous series of blog posts, Yes, Cisco UCS servers are that good.
- Source: IDC Worldwide Quarterly Server Tracker, Q1 2013 Revenue Share, May 2013
Tags: 2208XP, 6248UP, 6296UP, B200 M3, blade server, capex, Cisco, CMM, CN4093, Fabric Interconnect, fex, Flex System, FSM, G8264R, IBM, patterns, Principled Technologies, rack server, ROI, service profile, tco, UCS, UCS Manager, x240
As we continue to expand on the conversation of the Cisco Open Network Environment (Cisco ONE), this week provides yet another educational opportunity (Register here) to discuss a topic that has become some what top of mind to customers, partners and even investors alike. This is the topic of open source in networked environments. While Cisco has always been known for open standards, it has now stepped up into the open source conversation in a fairly big way over the couple of years with its contributions to both OpenStack and the more recent OpenDaylight project under the Linux foundation.
This week kicked off with a trip to Boston and Red Hat Summit where Cisco is talking about our partnership with Red Hat on open source projects including OpenStack, and the Kernel-based Virtual Machine (KVM) hypervisor. I’m here to highlight some of our Nexus 1000V virtual networking innovations that involve Red Hat open source distributions of red Hat Enterprise Linux (RHEL), KVM and OpenStack.
As you probably know, Cisco started shipping the Nexus 1000V virtual switch for Microsoft Hyper-V this month (and it won a Best of TechEd Show award at Microsoft’s TechEd conference). But open source virtualization and cloud infrastructure platforms continue to be an important strategy for our entire data center portfolio here at Cisco. KVM will be the next hypervisor that we’ll ship our Nexus 1000V virtual switch on, and the rest of the Red Hat open source cloud infrastructure will be an important part of our open strategy, and that includes Red Hat Linux and their Red Hat OpenStack distribution.