How Cisco UCS reinvents the datacenter
Encapsulating Cisco's Unified Computing System into a few paragraphs is a daunting challenge. Cisco UCS is quite unlike any other computing platform on the market today, and while there are certainly parallels to existing models, UCS carves a new path through the woods of IT. In order to relay the major differences, it's best to start in familiar territory and compare UCS with a traditional blade infrastructure.
With a "normal" blade infrastructure, you take pieces from every corner of the IT pie -- storage, network, servers, and management -- and put them together. Each blade chassis will have some number of Ethernet and SAN interfaces, either grouped using internal switching with uplinks or dedicated on a per-blade basis, and these interfaces are then connected to a larger Fibre Channel and Ethernet network. Thus, each chassis exists as an island within the datacenter, and each blade exists as an island within the chassis.
[ Peer deep inside the Cisco Unified Computing System in InfoWorld's "Test Center review: Cisco UCS wows." ]
Management frameworks surround these pieces and typically tie them together in some fashion, but the reality is that today's blade infrastructures are more akin to closely grouped banks of separate servers than a bundle or pool. That's where UCS differs significantly.
The UCS model dispenses with fixed ports and internal switching. It removes the smarts from the chassis as well. Each chassis is essentially just sheet metal and a backplane. No switching occurs within a chassis; the chassis is simply an extension of the UCS fabric, which is driven by two redundant Fabric Interconnects. These are not switches, but might be thought of as controllers.
The Cisco UCS 6120XP FI has 20 10Gb Ethernet ports and an expansion slot for 4Gbps Fibre Channel connections to a SAN. Each port can be designated as a server or uplink port, with the chassis connected to the server ports, and the larger LAN connected via the uplink ports. Drop in Fibre Channel connections to your SAN and you're done. Cabling a UCS deployment is extremely simple and requires very few cables per chassis -- up to eight if you need all that bandwidth, but four should be more than enough for most cases.
Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world
On Twitter now
Hardware Systems
Powered by TwitterOn Twitter now
Hardware Systems
Brian Proffitt
Microsoft/Novell: Breaking Down the Coupon Numbers
Esther Schindler
Drupal's Dries Buytaert on Building the Next Drupal
Tom Henderson
Top Ten General Operating Systems Rants
pasmith
PS3 motion controller delayed; goes up against Project Natal
sjvn
Neolithic Windows security hole alive and well in Windows 7
claird
Perl source code comparison makes for good reading
mikelgan
Cell phones don't create stress or interrupt much
Sandra Henry-Stocker
How to: The Unix Interview
Where Google Chrome security fails: the password
I heard mention that the Chrome OS will have some sort of encryption available a la bitlocker. If it's possible to encrypt personal data using another password or key, then it may have potential for very secure data.... And Ubuntu has an 'encrypt home directory' option, perhaps google should follow suit.
- Dann
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
- Ubuntu advances: Why Ubuntu server installations will surge in 2010
- Social media marketing: How to make friends with benefits
- More...
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.






