A few years ago, we were one of the first/early adopters of UCS. At that time, it was clearly in it’s infancy and not ready for prime time, our local Cisco guys didn’t even know anything about it. If you care to read those previous posts, they can be found here: Part 1, Part 2, and Part 3. I was fairly bitter when I wrote those, but with good reason. I ‘wasted’ a lot of time (read weeks or months) jacking with it and had nothing but problems.
I forget the firmware of the original chassis, something like 1.0-something. It should have been 0.-something. That original chassis is still around, but being physically moved to a different datacenter, so I can’t check the actual version. It really seemed like a beta product and shouldn’t have been released yet.
So, why am I writing this? We got a new chassis running on version 1.4(3q) and none of the issues I had previously are there, in regards to the hosts dropping offline.
I hammered it as hard as I could and the blades are 100%. I felt it was only right to provide an update and give my ‘stamp of approval’. When I get the original chassis back online, I’ll update the firmware and see how it goes…
Hey man, I’m a Cisco UC engineer(CCNP-VOICE) and I wanted to thank you for writing about your experience. I’m working a virtualization issue right now and came across your article as I was searching for answers. My issue stems from non-Cisco hardware with ESXi 5.0.0. I have a XP VM, CUCM 8.6.2a, and UCON 8.5 co-resident and running fine, but I get some strange behavior on the network side.
I don’t want to derail your post by talking about my issue, so I’ll just say it was good to read someone coming back and giving an updated opinion.
-Regards