Cisco Unified Computing System

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

The Cisco Unified Computing System (UCS) is a data center server computer product line composed of computing hardware, virtualization support, switching fabric, and management software introduced in 2009 by Cisco Systems.[1][2] The products are marketed for scalability by integrating the components of a data center that can be managed as a single unit.[3]

Computing[edit]

Cisco UCS blade servers

The UCS product line was announced in March and first installed in September 2009, at the customer premises of Tutor Perini.[2] They were reported to have the code name "California".[4] The computing component of the UCS is available in two versions: the B-series (a powered chassis and full and/or half slot blade servers), and the C-series for 19-inch racks (that can be used with fabric interconnects). The computer hardware managed by the UCS Manager software on the fabric Interconnects can be any combination of the two. Both form factors use standard components, including Intel x86-64 processors and DIMM memory. The servers are marketed with converged network adapters and port virtualization. Around 2010, an extended memory technology expanded the number of memory sockets that can be connected to a single memory channel in some models.[5][6] A fourth generation was announced in September 2014.[7] It included an additional "M" series, but the M-series was cancelled in 2016 after poor sales.[8]

Virtualization[edit]

Cisco UCS supports several hypervisors including VMware ESXi, Microsoft Hyper-V and Citrix Systems' Xen server.[9] VMware provides a special version of ESXi.

In 2017 Cisco announced a partnership with Docker to include its enterprise software in UCS products to directly provide operating-system-level virtualization (containerization).[10]

Networking[edit]

The Cisco fabric interconnects (FI) provide network connectivity for the chassis, blade servers and rack servers connected to it through different speeds of Ethernet and Fiber Channel over Ethernet (FCoE). The fabric interconnects are derived from the Nexus 5000 series switch and run NX-OS as well as UCS Manager software. FCoE allows connection to storage area network storage, since the UCS system blade servers have very little local storage capacity. Cisco has produced the following series for fabric interconnects: 6100 Series (discontinued), 6200 Series, and 6300 Series. The fabric interconnect can further connect to multiple fabric extenders (FEX), into what they call a "unified fabric".[4]

By 2012, analysts noticed that Fibre Channel vendors such as Brocade Communications Systems had already lost market share to Cisco.[11]

Management[edit]

Management of the system devices is handled by the UCS Manager software integrated with fabric interconnects.[12] Virtual machines can be moved from one physical chassis to another, applications may be moved between virtual machines, and management may even be conducted remotely from an iPhone using SiMU - Simple iPhone Management of UCS. In addition to the embedded software, administrators may also manage the system from VMware's vSphere. The Cisco Integrated Management Controller (CIMC) is used to configure and manage C-Series servers not connected to a manager. The CIMC can also be used to manage B-series blades in addition to the UCS Manager application if configured.

In November 2012, Cisco announced UCS Central which extends management across multiple domains of UCS,[13] and then something called UCS Director. A security flaw in UCS Central was disclosed when it was patched in 2016.[14]

Many configuration details are set up on the UCS manager in a service profile and applied to the servers. Cisco offers a UCSM Platform Emulator, where the full logical configuration of a server can be created from the user interface or the API methods, and later applied to the physical hardware.

References[edit]

  1. ^ "Cisco Unleashes the Power of Virtualization with Industry's First Unified Computing System". Press release. March 16, 2009. Archived from the original on March 21, 2009. Retrieved March 27, 2017. 
  2. ^ a b "Tutor Perini Deploys Cisco's Unified Computing System for Data Center Consolidation". Press release. September 1, 2009. Archived from the original on September 7, 2009. Retrieved March 27, 2017. 
  3. ^ Cisco Product Data Sheet
  4. ^ a b Timothy Prickett Morgan (June 13, 2011). "Cisco gooses switching, virtual I/O for blades: Servers not yet crossing Sandy Bridge". The Register. Retrieved March 27, 2017. 
  5. ^ "Cisco Unified Computing System Extended Memory Technology" (PDF). Cisco Systems. February 24, 2010. Retrieved January 13, 2014. 
  6. ^ Even Solberg (April 27, 2009). "Unified Computing Technical Background" (PDF). Retrieved January 13, 2014. 
  7. ^ Chris Mellor (September 4, 2014). "Blade runner: Cisco ups its UCS server game: Broadens range's appeal to ROBO, clouderati". The Register. Retrieved March 27, 2017. 
  8. ^ Shaun Nichols (June 3, 2016). "Cisco axes unloved M-Series modular servers two years after launch: Nobody wants modules any more, admits Switchzilla". The Register. Retrieved March 27, 2017. 
  9. ^ Nathan Eddy (October 18, 2012). "Cisco, Citrix Extend Partnership on Networking, Cloud, Mobility". e Week. Retrieved March 27, 2017. 
  10. ^ "Cisco and Docker Team to Modernize Cloud and Data Center Application Environments". 2017-03-02. Retrieved 2018-04-30. 
  11. ^ Archie Hendryx Hendryx (March 19, 2012). "Cisco UCS – Undisputed Computing Success". The SANMAN by ZDNet. Retrieved March 27, 2017. 
  12. ^ Ranjit Nayak (September 17, 2013). "Cisco UCS Management". Promotional blog. Archived from the original on October 1, 2015. Retrieved March 27, 2017. 
  13. ^ Timothy Prickett Morgan (November 1, 2012). "Cisco stretches UCS uber-control-freak across larger clouds: How's 10,000 nodes grab ya?". The Register. Retrieved March 27, 2017. 
  14. ^ Shaun Nichols (April 13, 2016). "How to make Cisco UCS servers roll over and obey: Send a HTTP poke". The Register. Retrieved March 27, 2017. 

External links[edit]