The main use cases are hosts and application workloads.
What is our primary use case?
What is most valuable?
The features I appreciate most with Cisco UCS X-Series are profile, profile deployment, and the ability to orchestrate configurations across all of the compute. Instead of doing one-off configurations per server or per host, you can do group deployments and make configurations to all of the hosts at the same time.
An example of how these features have benefited my organization is efficiency and reduction of user error, such as user configuration errors, because it is automated. You can make the change one time and then apply it across the board.
What needs improvement?
I would say a form factor could improve Cisco UCS X-Series. We are in a life cycle replacement phase, and we face a situation where we have to upgrade the hardware, but to get to the next series, you have to upgrade all of it. The chassis, the backbone components, including fabric interconnect components that provide the networking, all have to be replaced at the same time. You cannot mix and match things.
So you get to a situation in your life cycle replacement that you need to upgrade, but it does not make sense economically to just buy a newer blade when the whole life cycle replacement is on the horizon, and you are forced to just replace it all top-down.
I would say a form factor that is more universal and is not going to require an overall hardware refresh would be beneficial.
For how long have I used the solution?
We have been using Cisco UCS X-Series for seven or eight years.
What do I think about the stability of the solution?
I would assess the stability and reliability of Cisco UCS X-Series as really good.
What do I think about the scalability of the solution?
I would say Cisco UCS X-Series scales really well with the growing needs of my organization. It is baked into the solution because of the way the templates and the policies work. If you ever get to a point where you are creeping up on your compute thresholds, you just buy another blade. As long as you have chassis space, you just slot it in, apply the templates, and add it into your virtualization environment, and you are good.
How are customer service and support?
I think in earlier times, the customer service and technical support have been better. It depends on who you get. In many cases, we have engaged with our account representatives to drive the TAC cases if we have issues. Overall, depending on the issue, if it is a real complex problem, those can be difficult to get support on, but overall, support is pretty good.
Which solution did I use previously and why did I switch?
Prior to adopting Cisco UCS X-Series, we were using what they call pizza box setups. Whereas Cisco UCS compiles all that form factor into a chassis that is a lot smaller, traditionally it would be one-off hosts. The space consumption was a lot more with the previous solution because it requires a lot more rack space to get all that compute into a rack.
Whereas with Cisco UCS X-Series, that is why it is really nice; you can shrink down your space consumption because of the chassis and the microblades.
How was the initial setup?
I did not do a chassis deployment, but I do not suspect it would be all that difficult because of the way the templates and the policies work. I have deployed subsequent blades and that is all super seamless.
What other advice do I have?
Cisco optimizes the experience in a hybrid or distributed enterprise setup, though I do not know how that would apply to my environment. I do not know in what way the end-to-end visibility offered by Cisco is referring to.
My experience with pricing, setup, and licensing has been good. The pricing is what it is. If you are committed to a product, in our case Cisco, it would have to be a drastic price increase for us to get off of Cisco because once you get acclimated to a product line, you do not necessarily want to get off unless there is a really good reason. The pricing has been good; I would say it is competitive with other hardware vendors.
I rate this review an 8 out of 10.
Which deployment model are you using for this solution?
On-premises
