x86 Blade Shares CQ2’13 - WW: HP 43.1%, Cisco 21.5%, IBM 16.3%, Dell 9.7%, Hitachi Ltd. 1.4%, NEC 1.3%, Fujitsu 1.3%, Oracle 0.8%x86 Blade Shares CQ2’13 - Americas: HP 42.2%, Cisco 31.1%, IBM 11.8%, Dell 11.2%, SGI 1.4%, Oracle 1.0%X86 Blade Shares CQ2’13 – N. America: HP 42.7%, Cisco 32.9%, Dell 11.1%, IBM 9.6%, SGI 1.4%, Oracle 0.9% X86 Blade Shares CQ2’13 – US: HP 41.9%, Cisco 33.9%, Dell 11.5%, IBM 9.0%, SGI 1.5%, Oracle 0.9%X86 Blade Shares CQ2’13 – EMEA: HP 54. 1%, IBM 16.1%, Cisco 12.6%, Dell 8.6%, Groupe Bull 2.9%, Fujitsu 1.8%, SGI 0.9%, Oracle 0.8%X86 Blade Shares CQ2’13 – Asia Pacific (APJC): HP 30.5%, IBM 27.2%, Cisco 10.7%, Dell 7.7%, NEC 6.2%, Fujitsu 2.6%
Graph shows vendor revenue shares for three quarterly periods: Q2CY11, Q2CY12,Q2CY13.Since UCS first recorded IDC vendor revenue in Q3CY09, HP has lost 7.1% in share (50.3% in Q3CY09 to 43.1% in Q2CY13) and IBM has lost 12.8% (29.1% to 16.3%).Cisco has gained 20.2% (1.2% in Q3CY09 to 21.5% in Q2CY13).
Virtualized workloads need both File and Block storage capabilities. In a traditional deployment these are often separate networks, which limits workload mobility since administrators have to plan in advance whether or not the new server has enough connectivity to network and specific type of storage. Unified Fabric with its "wire-once" capability standardizes the infrastructure, where every server is connected to the network and has access to both File and Block types of storage devices. This provides administrators with un-precedented flexibility for workload mobility.
Multi-tier architectures across one resource poolOnly vendor on the planet to provide management parity across both blade and rack form factor
Place correct imagesPlace correct imagesRename the row from Mezz cards to I/O Options, Place1240 as the first mLOMMove the 1280 underneath the capitola launchExplicitly call out Modular LOM option instead of
There needs to be speaker notes for the UPC and VIFs
What does HI and NI mean
We expect to keep the WHIPTAIL product family but migrate the platforms to be UCS-based, and to migrate the cluster connect from Infiniband to 40Gb ultra-low latency ethenet.
Symmetrical I/O occurs because we take random data and we actually make it sequential. By making it sequential, you make it highly efficient for flash. A few things occur. We can write to the media very, very quickly while protecting it. We also reduce what's referred to as wear on the media because we're not really allowing the flash itself to be involved and determining how that information will be written. We handle all of that.Many of our competitors don't directly manage the flash. They allow the actual local flash media to make all kinds of decisions about how the data should be applied, which is not very efficient at all.
So how does it all come together?With UCS Management Pack for System Center Operations Manager you can:monitor the health of Cisco UCS by using Microsoft System Center Operations Manager. It monitors Cisco UCS devices such as Cisco UCS blades, chassis, and rack servers. In addition, the management pack enables correlation of faults and events between Cisco UCS infrastructure and both bare-metal and virtualized operating systems that you manage withMicrosoft System Center Operations Manager.The Cisco UCS Management Pack for Microsoft System Center Operations Manager simplifies management byenabling IT personnel to:● View Cisco UCS hardware, service profiles, operating systems, and virtual machines on a single interface● View the health of Cisco UCS hardware and subsystems in the native Microsoft System Center OperationsManager format● Visually correlate blades, service profiles, and host operating systems by using Microsoft System CenterOperations Manager status views to quickly determine how an event will affect the overall systemCisco UCS Management Pack for Microsoft System Center Operations Manager graphically depicts Cisco UCShardware, service profiles, host operating systems, and virtual machines. Correlation of events with the blades and service profiles that they affect simplifies identification of root causes, accelerating problem resolution.With UCS Integration Pack for System Center Orchestrator you can:Automate UCS managementImprove predictability and reduce manual errors with UCS integration packReduce delivery time Deliver Scalable and Reliable UCS management through orchestrated workflowsDeliver consistent service across multiple systems and departmentsUCS XML API (UCS Manager) provides a powerful, supported interface for Orchestrator workflow operationsOptimize and extend UCS capabilitiesIntegrate with 3rd party tools using Cisco UCS integration packIn working with deeply with the MS engineering organizations, we have been told time and time again that our integration is the best that they have seen to date.-------------------------------------------------------Cisco UCS Integration Pack for Microsoft System Center Orchestrator: Automate and StandardizeUCS ManagementThe Cisco UCS Integration Pack for Microsoft System Center Orchestrator exposes prebuilt runbook actions thatcover every management aspect of Cisco UCS, as shown in Figure 3. It is built on the same Cisco UCS ManagerXML API framework as Cisco UCS Manager and enables runbook actions designed in Microsoft System CenterOrchestrator to connect to Cisco UCS. This integration pack enables IT administrators to:● Automate Cisco UCS management, improving predictability, expediting delivery, and reducing humanerrors● Deliver scalable and reliable Cisco UCS management through orchestrated workflows, to provideconsistent service across multiple systems and departments; the Cisco UCS Manager XML API provides apowerful, supported interface for workflow operations in Microsoft System Center Orchestrator● Optimize and extend Cisco UCS capabilities, enabling integration with third-party management tools
Build Node , Controller Node & Compute UCS nodes Integration of bare metal bring up and the subsequent setup Applications (like Openstack, cobbler, etc). 2 stages:1. Apply configuration of the UCS baremetal using the Python SDK2. Start the event listener that listens for the change events of service-profile. Based on the event type, automatically update OR remove the host details in integration application The integration script quickly configures UCS Manager with required policies so that it automatically discovers chassis, servers and creates and associates service profiles with the servers. This script also starts the event listener program in the integration application. The event listener automatically adds the UCS servers to application cluster after it receives the association complete event from UCS Manager.1) If the Application is Openstack, Then it also does ‘puppet apply’ with the updated conf file.2) If the Application is Cobbler, Then it also does ‘cobbler sync’ to reflect new configuration changes. So the servers can automatically PXE boot from the Host (Build-node in case of Openstack, or DHCP server used with Cobbler setup).
Ucs clle 2014-v6
Cisco Unified Computing
Todd Rodgers – CCNP Datacenter
Consulting Systems Engineer