HPE OneView Reviews

Its simplicity is the most valuable feature.

It is easier to manage and has one central location.

For a code upgrade, there should be more stability in the code.

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.

We're still in the beginning phases of using it, so I don't know how it's going to scale out or not.

The technical support team is okay. They didn't fix the problem at the first time they connected with us, so we're not too impressed, at the moment with them.

This tool was recommended to us by our partners. We then had it included with the service that we bought and implemented it.

Reliability is the most important criteria while selecting a vendor.

Try a PLC first.

The visibility of the status of the IT infrastructure.

The improvement was basically to be more efficient and have a lot of productivity. We are more developed to creation rather than just solving problems.

The possibility to do more analytics regarding the status of the assets.

To improve our political mission process and workflow.

It is very stable.

We can grow according to the needs of the IT and OT requirements.

We needed some support from HPE in Mexico, I think. I would give them a rating of 9/10.

I was not involved in the setup. The management was involved in the setup.

We checked with IBM a little bit. We went back to HPE because most of our infrastructure is HPE service and also cloud solution

It's quite important to improve IT operations to reduce the time IT people devote to solve problems. Instead, we can create valuable position innovation ideas to improve the business.

I have heard of what the benefits are supposed to be and we're trying to get to that state, but we're just not there yet.

Before OneView, for us, we were trying to manage all the separate enclosures with the Virtual Connect tools and it was cumbersome. To be honest, it was never done because it was so cumbersome. So, hopefully, OneView is going to resolve that issue, however, it just hasn't yet for us.

We are just now starting to bring it up, it has taken us around eight weeks and we haven't still been successful to bring it up. We have hardware or blades that can't see themselves within the enclosure of OneView managing them.

Hopefully, it's just going to be more stable and we can get functional, i.e., get up and running quicker than what we've seen.

The product is not stable.

We have used technical support, I would give them a 5/10 rating.

We would like to see quicker times for a resolution. It seems like when you get on the call, the technical support you have is this one level tier, who ask for a bunch of data logs and then, you get to the other technical guys who ask for the same information. You go on with this continual loop for weeks on end.

Previously, we were not using any other solution; it was just managing the virtual connecting individually. We really didn't have a choice in selecting a particular product as such, that was just the direction in which the organization was going.

We looked at CISCO's DCS platform, but we're an HPE shop and there was no major direction to change.

The hardware's reliability and manageability are important criteria while selecting a vendor.

Just make sure you put it through the paces. Again, I don't know what failed in our deployment. I've talked to some of the escalation engineers at the conference and hopefully, they're going to come back and resolve the issue. But, our IT is lean. We don't have time to be beta testers for new products, we need a product that's going to be stable out of the get-go.

The centralized management of the HPE Virtual Connect (VC) is the most valuable feature.

Just having a centralized view, instead of having to go to each chassis for managing Virtual Connect is very helpful; I got it all in one place.

It tends to detect flood conditions on a lot of the networks. I'll have blades that are suddenly offline because it detected a flood condition on that particular NIC. I've called support on that and they're like, "Yeah, we have detected a flood condition, it is a loop." However, I tell them, "We don't have a loop." So, you reset it and reboot the blade; the ESX comes back up and away you go. That has happened to me three or four times now. So, hopefully, we can figure out what's causing this at some point in time.

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

We have six HPE c7000 chassis, across two data centers and everything is good. We have a single OneView product in each location.

I have used technical support. It has been probably a year, but I have used them. They are excellent.

Previously, we were just managing the blades directly through the HPE Onboard Administrator (OA) and Virtual Connect (VC). We were building up brand new data centers, with brand new equipment and we had the choice of doing it the old way, or using OneView; we could just have two places to see it, i.e., one on each data center. So, we decided to combine it, this was a suggestion by one of the partners.

Stability and support are the most important criteria while looking for a vendor.

The setup was straightforward; it was pretty easy. It's a pretty simple setup; you just install your server. It's a virtual appliance and you throw it on there, start it up, add your chassis and away you go.

If you are experienced with OA and Virtual Connect, that it's a completely different animal when you're in OneView; the interface isn't the same. Finally, you figure out how OneView works. It could be that you, maybe, have never used a chassis before and then, finally, you understand this Virtual Connect beast and how to set everything up. Then, you're like, "Let's get OneView!" and you switch to OneView. The theories behind it are the same, but the interface is different and the way you set it up is different. So, I will advise being aware of going in.

What we were looking at originally with OneView was the server profiles. We were looking for:

• Something that could provision the server end-to-end with everything configured
• Core management
• Central management
• A way to manage everything
• Have a single plane of glass across all of the server platforms

Those were biggest things that were compelling and drew us to implement OneView.

Central management: That's something we're brand new to at CIBC, i.e., the bank. We never really had a centralized view. We had a very fragmented firmware process across the board with a lot of our hardware. During our refresh cycle, or when trying to keep everything current, that was when we had a real struggle. That's where OneView came into play.

We're still pretty junior into it, so right now our focus with regards to hardware is kind of being displaced now with the cloud. For future releases, it's probably not going to fall into our lap anymore. I probably can't really speak to what we would like to see in future releases, at least not at this point. As much as we've used OneView right now, it's probably not something that we're going to move forward with as a bigger footprint. We're trying to displace ourselves from the hardware platform.

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.

Scalability is good. Right now, we're still at a small footprint. We are expanding over to another side of the bank that is also using OneView, so we're sharing the licenses. But we found that there were options. We sort of designed it so that we could scale out. We are making a central point server with a bunch of OneView nodes, so that we can still talk about everything at one central source, instead of being continually fragmented.

I did not use technical support. Right now, we are still engaged with professional services, so we had the support right on-site.

We knew we needed to invest just because of the fragmentation issue. We noticed that every time there was an incident or occurrence, it was firmware related. Generally, when you open an incident ticket with any hardware vendor, that's usually the first question, as well as any of the stability issues behind it.

We wanted to make sure that we could rule that out on a currency, on a release schedule, so we could say, "Yep. Because the servers are having scope, we're going to release it on this schedule. Once a year, twice a year, whatever it is." We didn't have a platform existing at that time to do that for us, and that's when we looked at OneView.

I was involved in the initial design. So a few things we generally look at from the engineering space are:

• How do we scale?
• How do we manage this?
• How do we manage the currency?
• How do we expand on it if we need to change the footprint and change direction?
• Can we do this easily, or is this a tear down or rebuild?

We didn't evaluate other options for this space. OneView is kind of the direction given by HPE, and we were using HPE servers. We didn't really have any necessity to look at other vendors.

I would definitely consider it for a colleague who had the same challenges as we did. Obviously, different companies have different challenges. But if they are dealing with similar challenges with regards to a fragmented footprint and currency-wise, OneView is a nice choice. It is:

• Visually appealing
• Easy to use
• Easy for managing servers going forward
• Easy for building servers at a profile level, versus going in traditionally and configuring all that stuff. It can automate all that stuff.

So if those were the challenges they are having, I would say OneView is a good place for them to look.

When selecting a vendor, I think relationship is very important. We want to make sure that our vendor is as intimate with us as we are with them. For them to understand our needs, we need to know what they can offer so that they can be transparent on what they can offer or provide partners that could offer the service to help everything we need efficiently. So that's really number one for me.

It's a little bit of unfair analysis. We weren't able to take this solution to the max. We put it in. We did a small footprint. It worked very well. But could I tell you what would happen at 3,000 servers or 5,000 servers? I wouldn't have an answer for you on that one. There is probably the potential, but I don't have an answer.

The single-pane-of-glass and a full view of the environment are the most valuable features.

The single-pane-of-glass, easy to manage, to be able to see the issues/capacities, basic metrics are important features.

I know they're building more product availability within the HPE OneView, so a wider range of products are to be viewable, i.e., you will be able to see within OneView.

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.

We're partners, so we get to see the products, test them, and eventually, promote them. That's really how we work.

I am a vendor, so I get selected; but obviously, knowledge of a product, certifications, partnerships and their levels, etc. are important criteria while selecting a vendor.

I would recommend it. Put a demonstration in, let it show you exactly how it is supposed to work, how it benefits your company; this should convince you that this is what you need.

OneView is the software stack that is running on top of Synergy and on top of the HPE Hyper Converged 380 solution. Customers who buy separate servers can install it, and all the various elements, themselves.

OneView is the one tool where you can manage your build environment, the hyper-converged environment, or the Synergy environment yourself.

The user experience makes it easier for the administrator because new, not so new, and old environments will be managed in the same way. There is an efficiency thing as well because you don't have to be an expert in hybrid IT (private cloud and public cloud). It's the same interface for all of them.

I’d like to see more functionality going towards the hybrid IT. It is cloud economics in which we will see more and more of the private cloud and their own data centers as well.

The connection with Azure Stack, which was recently announced, demonstrates the connection between the local data center and Microsoft Azure. I see more and more features that will come together.

Can't be easier: eploy the OVA file, boot the appliance and enter the IP address and password... That's it!

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.

I've been in IT a long time, so I realize that by attending conferences, such as a recent one, it’s not just for the announcements. For me, it's more of a networking thing, shaking hands, and getting to know people. At these events, you can meet the developers and the product managers. It opens up doors so you can become more independent of that one phone number. It’s quite important knowing people.

If you do the networking, you feel that the service you get is top notch. You get even more service. It makes it easier to get to the second and third line of support because you know what you're talking about. You get more information than just the marketing fluff. I know what it's about because I'm able to communicate directly with the hardware and software guys and the product managers.

One of my things I do in my company is publish a technology blog which is quite technical for the type of audience that I have. OneView is a simple installation. My nine-year-old daughter can do it.

In my pre-sales role, I see other customers looking at competitive solutions, be it Intel, EMC, or Nutanix. They all have some strengths.

The Nutanix solution is cool, because it's simple. But it's software and I'm not convinced about any of the hardware underneath it. Some people say, "Yeah, the hardware's not important." However, I have some real-life scenarios, cases with customers, in which it was proven that they had the software, they had the hardware, but they had a hardware issue and the software screwed up.

I prefer to go for the HPE solution. This is not because Nutanix is bad, but they are just a software company, independent of the hardware. I feel more confident with HPE because I know they build the hardware and the software. If I have a problem, I can contact one person with one phone number and I can make contact. I know the hardware guy and I know the software guy.

With Nutanix, for instance, this is not the case. They also say, “we have one phone number," but if they have a problem with the rate controller in their server, they have to call Dell or Lenovo. They have to escalate the case. They are not going to be able to solve my problem. They are going to escalate it. I'm with HPE. I know that HPE will solve my problem directly.

You know all the good stuff and the not so good stuff about software, but OneView 3.0 is there now.

It enables you to view the entire infrastructure. If you have blades, storage, or any HPE environment, it enables you to manage it in a single pane. That's the best. It is easy to manage.

Although the product is meant only for HPE, it would be great if they were to incorporate functionality from non-HPE components.

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.

Scalability is good.

When you log a case, technical support works quite well.

I was not involved in the initial setup. That was taken care of by the services team, but it is fairly straightforward.

We did not actually decide to buy the product. When you buy an HPE kit, HPE OneView comes with it. That’s how we got started with that.

I’m at a system integration company, so we work with HPE. We are partners with them. The ease of doing business with the company is the number one criteria when you select a vendor. The technical capability to solve a particular issue is also important, of course. This is followed by value for your money in terms of how much you spend on the infrastructure.

It's a product with which you can automate, manage, and monitor your devices.

It improves our productivity, because we can use OneView for more than just servers. We can use it for storage on some of the networks as well. So it's quite good.

With every new version, new devices are supported in OneView, but we are still missing support for some HPE products. I hope they will be supported soon.

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

It's easy to scale, but we are not a huge company. We're not GE.

We haven't been using technical support. We have not had any issues.

We were using Insight Manager, which was the product before OneView's conception. Therefore, we heard about OneView, and started using it instead.

Initial setup was quite straightforward.

We were not really looking at other vendors, because OneView is for HPE products. You couldn't use another product. We want OneView because we want to automate things and to manage our systems easier.

It should be easy to use and easy to manage things. You don't need a couple of different products to manage. Now you can use OneView for everything.

It provides a good view of the whole infrastructure. It makes it easy to manage the infrastructure, including the server infrastructure and firmware updates.

It keeps our costs down and improves the time it takes to manage our infrastructure and deploy.

We have different operations teams managing the servers. It should be segregated more in terms of which operation team is managing which group of servers.

I never faced any stability issues.

It is easier and faster to integrate a new BladeSystem, new servers, and a new chassis into an existing HPE OneView instance.

We have a good relationship with HPE. It is not really with technical support, but more with presales for defining the cost of features and services.

Previously, we managed the servers manually.

I was involved with the initial setup with the engineering and the operations team. It was quite easy.

I would advise colleagues to look into using this solution. Now we know that HPE OneView is the future and an important the layer of synergy management; so we need to use it right now.

When we evaluate vendors, we want a good explanation of the product and a good understanding of how the support will be. A good relationship with the vendor is important, as well as a lower price. Even if we know that this product is technically the best, the manager won’t want to select it if it is more expensive than others.