My friend, M. Sean McGee, wrote up a great blog post in April that deserves revisiting titled, “The State of Statelessness: Cisco UCS vs. HP Virtual Connect“. In the write-up, he discusses Cisco how Unified Computing System (UCS) blade servers are “stateless” and use “UCS Service Profiles”. He identifies 96 server settings that can be handled via the UCS Service Profile vs 12 server settings with HP’s Virtual Connect Server Profile. It is a great read, so I encourage you to take a few minutes and see if you agree with what he writes.
eWeek recently posted snapshots of Cisco’s Unified Computing System (UCS) Software on their site: http://www.eweek.com/c/a/IT-Infrastructure/LABS-GALLERY-Cisco-UCS-Unified-Computing-System-Software-199462/?kc=rss
Take a good look at the software because the software is the reason this blade system will be successful because they are treating the physical blades as a resource – just CPUs, memory and I/O. “What” the server should be and “How” the server should act is a feature of the UCS Management software. It will show you the physical layout of the blades to the UCS 6100 Interconnect, it can show you the configurations of the blades in the attached UCS 5108 chassis, it can set the boot order of the blades, etc. Quite frankly there are too many features to mention and I don’t want to steal their fire, so take a few minutes to go to: http://www.eweek.com/c/a/IT-Infrastructure/LABS-GALLERY-Cisco-UCS-Unified-Computing-System-Software-199462/?kc=rss.