I would rate the stability as 10 out of 10.

In terms of stability, HPE OneView needs proper communication between customers and HPE. You see, it's a solution that you need time to get used to regarding what's going on and what's required. For example, when my company faced an issue and the team talked to HPE, that was the only time the company learned that an upgrade was needed. HPE didn't send any notification, so out of nowhere, HPE OneView suddenly stopped working or became unstable.

A couple of years ago we faced a lot of issues in HPE OneView with crossover. Since then the firmware has improved a lot and is much more stable.

The solution is stable for the most part however there have been times when both composers went down and you become blind and can't see any management unless you go to the service console, or connect the server by the ILOM.

We've had a few issues. We just upgraded to the 3.9.0 version. We think that now that we are on that version, hopefully a lot of those things are going to go away for us.

The solution is quite stable. I have used the solution for many years so do not have stability comparisons with competitor products. 

There is some dependency because patches and updates are frequently released. It is important to keep things up-to-date for best stability. This is not considered a drawback but rather a standard procedure for most solutions. 

We had one issue a couple of years ago with a slightly older version, where it became incredibly unstable. It took us several days of working with the techs to get it back into a good state, and it required multiple escalations.

Outside of that, it's been very good overall. The main problem that we run into, as far as stability goes, is when something loses its profile. Sometimes it requires jumping through a number of "hoops" to really get it back.

Except for version 3.00.04, stability is very good. That version was only out for about five or six days before they pulled it and I was unfortunately one of those that downloaded it and installed it and rebooted it. It has a tendency to take down your fiber channel connectivity in C7000 with Virtual Connect.

It's stable.

Stability is pretty solid. I couldn't say I've really had any problems with it, aside from the upgrade to 3.0. There was a pretty nasty bug with the first release that they fixed within a week, fortunately. But that caught us and caused some problems. But, aside from that, it's been pretty stable.

It is a stable product, and we will use it for a long time. Around ten people in my company use the solution.

It's definitely very stable. Also, being able to import in all of our existing blade nodes, VMs and the storage was a seamless process. We had no problems with that, i.e., from what I understand and I haven't heard anything that has trickled up to my desk, anyway.

I think it is very stable. We are running version 2 or 3. Version 3 has been really good. We haven't had any issues with it. We had some issues with version 2, but that's just because it was new.

It is a stable solution. Stability-wise, I rate the solution an eight out of ten.

It's been stable so far. Once we got it up and running, we haven't had really any problems with it. We have a single-sign-on implementation for it. Once we got it hooked into our active directory, it has been very stable.

We find it quite stable. Most HPE solutions are stable.

It is certainly a reliable solution. We switched to this solution almost two years ago, and I have not faced any kind of issues.

Stability's been fairly good on OneView, the appliance. In terms of Synergy Composer, which is a OneView central derivative, it is a little slow being on that bare, metal hardware. It would be nice to have one product, OneView, that could manage both Synergy and legacy devices without having two separate products. I understand that's what the dashboard is all about, but it still would be nice to have less components.

Stability's good. It's an appliance, so really you plug it in and it's configured as it is. There is an advantage to the appliances, as we just put it in. We used a VM appliance and that was a pretty easy implementation. We just had to give it a compute and everything else was done for us.

It's stable. It functions. We have no problems whatsoever with stability.

On a scale of 1 to 10, it's about an eight. There are some stability problems. Every once in a while, we'll just have to restart because it's freaking out. For the majority part, really there are no problems.

It's extremely stable. The 3PAR has been rock solid since we put it in. The blades have been a godsend, they're like five hundred times better than the ones that they were using before we transferred over.

No issues.

Since they went to Version 3, it's been excellent. We had a couple of beta versions before that, which kind of just sitting around the office. Nobody was really using them. But then when Version 3 came out, it was so stable that it just started to take off.

Stability is excellent.

HPE OneView is a stable solution.

We've really had very few issues with it. Initially stability, as far the application being up, has been good. We ran into a couple of issues here and there with the baselines for the firmware and not having enough space on the appliance itself to be able to have more than two baselines.

We actually work with HP, they had a way for us to expand that space where we could do more baselines, and so once that happened, we were pretty good.

It was kind of rough around the edges in version 1 but much stabler in 1.2. Version 2 and version 3 are much, much, much better.

The solution is pretty stable. We are in revision 3. It has been over three years now, and every revision has gotten better. One of the advantages of OneView is that even if something happens, it doesn't affect the work.

So far, it's been rock-solid. No problems whatsoever. It's run. Every update is applied, no issues. It just works.

It is stable if you are able to understand how it works. You can’t pretend to come to this new style of IT and have it work the way you did with old technologies. If you can make sure that you understand the workarounds for your challenges, then OneView is very stable.

Stability is a hit and miss.

The product is really pretty stable now, pretty good. We've had minor issues, so if I were going to rate it either a 4/5 or 5/5, I'd go for a 4/5. We've had some bugs in terms of things not quite working when we've done upgrades. But we've had good support from HPE.

So far, so good. We had a couple issues with the earlier version, but I do not think those issues will occur now.

It is really stable. In two years, I have had only one crash and it was my fault. However, we use it for really small options. We don't use it like other companies do, i.e., for zoning, server profiles, patch management, etc. We use it only for the small things such as monitoring purposes.

It is very stable. We have had no downtime nor issues in approximately a year. 

The product has good stability.

It's very stable. It's fine. Never had an issue.

It has been stable, I haven't had any problems with it at all.

I never faced any stability issues.

At the scale we're using it, which is not much, I don't think stability is something we could comment on, really. It's fine for what we've been using it for.

The stability of the solution is unfavorable. We have had some struggles with OneView. We have seen a lot of errors and a lot of open cases. We are progressively seeing text that says “Upgrade! Upgrade! Upgrade!”. That is not what I want to hear when I have a production issue. I can't just take down a production server to upgrade. They need to fix the problem rather than constantly chasing our tails to upgrade.

The product is really stable.

We have had different stability issues. We have experienced a lot of downtime on it. We have used this product from the first version up until what is available right now and have noticed that a lot of the functions have stopped working suddenly with no reason. This was now in version 2.0.7. Then we maxed out the amount of alarms and after that the system crashed. However, HPE has cleaned this out.

For the last four weeks or so, we have had no issues. We still have version 2.7 but we are planning to upgrade to version 3.0.

It has improved over time. It has become significantly better.

It's a stable product, it's working fine. 

We've had no issues whatsoever, so far.

It is very stable.

I have experience with Versions 1.0, 1.1, and 2.0. I have seen the evolution. Version 3.0 is a major step forward. Of course, Versions 4.0 and 5.0 will be better as well. That's the way it works in software.

It's very stable.

Stability has been really great, we don't have any issues with stability at all.

It's definitely a stable product.

Stability-wise, it is okay. It suits us well.

I know there is a new version (v.4), but we are using v.3.1, which is pretty stable. We have not had any downtime in our six months of use.

I haven't had any real downtime. I have experienced when it hangs for a couple of seconds, or minutes, but no downtime. When it hangs it's quite annoying, everything should happen immediately.

The stability is very good. We usually run it beyond the specs. We usually find the limits and then we have to go to more solutions, which we still turn to HPE for. We are going to more SSD disks and we went to a newer 3PAR. That's where we really pushed our storage.

Stability seems fine. I haven't had any down time.

It's stable. The real pain is in support.

It's stable. For us, it's the first step of integration as we are young. 

The restful APIs were very useful and helped us to integrate easily with the solution.

It seems to be a very stable product for us.

It is very stable. There is no downtime.

It's been there for ages now. Every new iteration that comes in is stable. There are no issues with it.

Regarding stability, there have been no problems, there have been no crashes with it whatsoever.

It is very stable.

The product is not stable.

I haven't seen many issues with it running in the environments. We run it personal here and run it within our environment as well, but I don't deal with it day in and day out.

The stability of this product is good.

The stability is fair.

It is very stable. No problems.

Every product has it's bugs, but they are getting fixed.

We haven't had any issues with it. We have only had it for a few months now, but we haven't had any issues. It works fine.

We don't have that much history yet. But the HPE technician who implemented it, he says it is very stable and recommended us to it. Normally he's right.

It is very stable.

The stability is very good. I have never had an issue with it over the three years that I have been using it.

Stability is very good.

It's quite stable. There’s been no down time.

It's pretty stable.

To be honest, we've been having some issues with the stability of the product. We're working with the support to get it more stabilized. We did a code upgrade and the whole thing just fell. Our guys back home are still working on fixing it.