I had been busy with the demo on Cisco UCS with VMware and EMC recently. 1 of the key features I had tested was about the Stateless Computing claim by Cisco. As a server or system guys, we all know that the ability to maintain the system state with UUID, Firmware, BIOS, LAN & SAN are important during a hardware changes. Honest speaking, the demo performed last week was my 1st experience on the stateless computing. The outcome was impressive.


To enjoy the benefit of stateless computing, you must ensure that the server or system are boot from SAN. We simulated the blade failure during the demo, and we re-associated the service profile to any of the available blade within the UCS cluster, and power it on. The entire servers are back online which maintain all the necessary system state and no re-configuration was required include LAN, SAN, Hostname and etc. The entire process took less than 20 mins and the system was back online. We simulated few round with different blade but same images and profiles, and it work exactly as it promises. Stateless computing are the key features which meant for the IT administrator to minimize the system down time in the event of hardware failure & system compatibilities.

If you have a hardware failure on the current blade server, which the hardware will be replaced in the next 4 hours,  nothing much could be done on the system administration to resume the production system without stateless computing. With stateless computing in place, you can easily shutdown any of your test & Development systems, and transfer the service profiles to allow the production system back online in less than 20 mins. This will be helpful to improve the SLA and system uptime in the event of hardware failure.