I am often asked by customers why UCS has been so successful in such a short amount of time. My response is always the same in that it comes down to two things – 1) Cisco and our partners’ ability to understand and execute against customer needs and 2) A fundamental difference in the underlying architecture.
You may know that Cisco invented UCS service profiles and built the entire system around the notion of hardware state abstraction. Cisco’s approach has been so successful because every element of the system was designed from the beginning to have its configuration set through software, without any licensing requirements. Whether customers are running bare-metal, virtualized, or any combination therein, Cisco UCS service profiles have revolutionized computing and have challenged competitors to try and replicate the simplicity and increased productivity that UCS Manager policies and templates provide. It’s no secret that Cisco UCS Manager has revolutionized the way customers deploy and manage servers, but here are a few things about UCS Manager that you may not be aware of.
Did you know that Cisco UCS Manager is embedded software running within the Fabric Interconnects in a highly available clustered configuration? This is an important distinction from traditional architectures as Cisco UCS Manager is a fully redundant management engine right out of the box the moment the system receives power, without special clustering software or additional licensing fees. Read More »
Tags: blades, Cisco UCS, Cisco UCS Manager, Cisco Unified Fabric, Dell Active System Manager, Dell ASM, HP, HP blade management, HP c-class bladesystem, HP OneView, IBM, IBM Flex System, IBM Flex System Manager, IBM FSM, service profile, UCS Manager
Almost a year ago, I wrote my first blog post detailing what customers have been saying about their UCS experiences in our Case Studies, Solution Briefs, etc.
The findings have been updated with the latest studies. While the percentages haven’t changed much, the number of customers reporting similar results (like Cisco’s market share) has gone up dramatically.
These results are limited to where the customers specifically stated a savings or where the savings is easily derived from the numbers stated.
- 61% reduction of ongoing administrative/management costs based on 27 customers.
- 54% reduction in power & cooling based on 44 customers.
- 77% reduction in cabling with an average cost savings of 71% based on 21 & 6 customers respectively.
- 41% reduction in other operations costs based on 13 customers
- 84% reduction in provisioning times based on 71 customers.
To help explain how customers achieved these results, the Cisco Unified Computing System (UCS): Changing the Economics of the Datacenter presentation walks you through UCS technology innovations and how they lead to TCO improvements. Along with this data, the presentation has been updated with current cost comparisons as well as third party deployment test reports.
Would you like to learn more about how Cisco UCS can help you? There are more than 270 datacenter case studies currently on Cisco.com. Additionally, there is a TCO/ROI tool that will allow you to compare your existing environment to a new UCS Solution. For a more in-depth TCO/ROI analysis, contact your Cisco partner.
Tags: B-Series, blade server, C-Series, cabling, capex, Cisco, HP, opex, ProLiant, rack server, ROI, server provisioning, tco, UCS
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.
Cisco UCS Outperforms HP Blade Servers on East-West Latency
Cisco UCS Outperforms IBM Flex System Blades on East-West Latency
Read More »
Tags: blades, Cisco UCS, Cisco UCS Performance, Cisco Unified Fabric, Fabric Interconnect, HP, HP c-class bladesystem, IBM, IBM Flex System
It’s great to see Cisco and many companies across the industry make a major change in the use of Open Source via the newly form project hosted by the Linux Foundation called OpenDaylight. This consortium is an industry-wide, open and transparent effort to catalyze innovation and accelerate an application ecosystem for software-defined networking. With all the partners involved we are working to not only further development and adoption of SDN but also to foster a new developer community. A consortium like this has been long overdue and it’s great to finally see it come to fruition.
We are incredibly pleased to partner with Arista, Big Switch Networks, Brocade, Citrix, Dell, Ericsson, Fujitsu, HP, IBM, Intel, Juniper Networks, Microsoft, NEC, Nuage Networks, PLUMgrid, RedHat and VMware on the Project. This is the largest effort to date to drive Software-Defined Networking across the industry and into new markets. While the initial goal is to build a common, industry backed SDN Platform, the broader objective is to give rise to an entire ecosystem of developers that can freely utilize the code, contribute to the project and commercialize the offerings. I further expect the ecosystem to expand into areas like tools and services.
Cisco has donated our core “Cisco ONE” controller code to the project and has officially open sourced the code under the Eclipse Public License. The community has come together around this code to form the architecture (see below) for the Open SDN Framework. Beyond donations of code, Project members are supporting the project via both financial investment and via developers we are committing to work full-time on the project overall. Donations from other members of the Project can be seen here and we expect this list to only grow.
As Open Source increasingly becomes a standard for customers and developers, we look at this as a new way to meet our customer needs and also help developers innovate in new ways without the barriers of vendor lock-in. Open Source is increasingly important for our customers and developers as well and as they evolve, we evolve. Cisco to date has supported Open Source through efforts such as OpenStack and now OpenDaylight and we look at Open Source as a critical pillar in our software strategy moving forward. By allowing developers to freely use these solutions we hope to enable a new developer ecosystem for software-defined networking and more. We are fully committed to enabling developers, both current and new, to deliver innovating applications and services that will help customers across the board realize the value of SDN faster than before.
The OpenDaylight architecture and code offering to date includes a modular southbound plugin architecture for multi-vendor environments. In addition, OpenDaylight offers an extensible northbound framework with both Java & REST APIs to ensure multiple developer skill-sets can build applications to the platform. We are also planning to build a onePK plugin for OpenDaylight to enable multiple users to drive network intelligence into their SDN applications. As you can see from below we will also be supporting key standards with this effort, including OpenFlow.
It’s important to note that you don’t launch a community; you build one. By investing in OpenDaylight we hope that our customers, partners and developers across multiple industries will now have the ability to build applications that frankly make the network easier to use and more automated. As an industry we are moving in a new direction and further up the stack and OpenDaylight offers new opportunities for application creation and monetization beyond the networking layer.
It’s a true rarity when you see both partners and competitors come together for the good of the community, and contribute code for the universal good of the customer. All OpenDaylight participants have committed to open source guidelines that include open communication, ethical and honest behavior, code and roadmap transparency and more. An Open Source project is only as successful as the community of developers and the level of code quality, and OpenDaylight’s Board of Directors (which includes multiple parties cross-industry) will be ensuring that partners, code contributors and project committers all abide by the same guidelines for the success of the project over the success of their own company’s offerings.
For more information, please see www.opendaylight.org. Code will be available for download soon, and we are looking for interested individuals for commitments across the board – from technical offerings to application development, and we welcome contributions from both individuals and other organizations. All ideas are welcome, and we look forward to multiple new innovative solutions coming from this.
Congratulations to all our partners and individuals who helped to make this happen, including the hard work done by the Linux Foundation. It’s truly an amazing accomplishment and we expect to see much more in the near future.
Tags: arista, big switch networks, Brocade, Cisco SDN Controller, citrix, dell, ericsson, Fujitsu, HP, IBM, Intel, juniper, Microsoft, NEC, Nuage, open source, opendaylight, PLUMgrid, RedHat, SDN, VMware
In my last blog, I wrote about HP’s disturbing pattern of suing non-California employees under ‘non compete’ clauses, often imposed years after employment began. Apparently it’s relatively recently that HP decided to abandon its Silicon Valley roots and tie up its non-California employees in legal knots. HP is in fact the only large Silicon Valley-based company to have two classes of employees and try to impose mobility restrictions on those who live outside California. HP’s efforts have gone so far as to sue an employee who took a buyout after having his salary cut, and one who didn’t even work in an area related to HP’s products that compete with Cisco’s.
Two recent actions since that blog posting are stunning. First, HP renewed legal action in Texas, where one of the employees used to live, trying to get a judge there to schedule a court date on a day’s notice and to apply Texas law even though the California judge in the case is going to hold a hearing, as is certainly appropriate, to verify that the employee has in fact moved to California. (Yes, he came to work for Cisco after he arrived in California, rented an apartment, got a drivers license, etc.) Once again the Texas court refused to intervene, and in fact effectively “stayed” HP’s legal actions indefinitely. HP also tried in Texas to raise another bar to employee freedom, claiming that the employee would ‘inevitably’ use HP’s trade secrets to do his job at Cisco, and therefore should be barred from continuing his new job. Just as California law bars enforcement of non-compete clauses, California courts won’t recognize this doctrine either, seeing it for what it is — an effort to impose de facto non competition clauses.
Read More »
Tags: employee mobility, employment law, general counsel, HP, innovation, legal