HPE Ethernet Switches Reviews

We use HPE Ethernet Switches to connect access devices. 

We were able to onboard HPE Ethernet Switches easily to the cloud. It was fast and took only five minutes to complete. 

HPE Ethernet Switches must ensure that the updates and patching are done regularly. When we have new software updates, we can resolve issues quickly. 

I have been using the solution for ten years. 

HPE Ethernet Switches is stable. 

The solution is scalable. 

Aruba's technical support is good and cooperative. 

I used Cisco before HPE Ethernet Switches. We chose HPE because of our company's single-vendor policy. 

The tool's deployment is straightforward and takes less than five minutes. To deploy the solution, you need to know the site's size and number of users. This is important since you need to know the model that needs to be purchased. 

I rate HPE Ethernet Switches a ten out of ten. You must understand the product well so you won't waste money. You need to know the deployment to purchase the suitable model. There are different products which can result in high costs. 

We primarily use the solution for data communication, the data center, and wireless. All of our switches are HP.

The switches offer simple management. I can control what I need using CLI. CLI commands are very simple and are somewhat similar to Cisco CLI. We can manage them, we can update them freely, and the warranty is unlimited. This is the solution's most valuable feature.

The solution uses a single interface and that interface contains everything.

The stability is very good on this solution. There have been no bugs, glitches or crashes.

Scalability on the solution is easy. It's not too difficult. Right now, we have about 150 users on the solution.

We've contacted technical support many times. They are quick to respond. We're satisfied with them.

I have used Cisco switches before. Cisco updates are more difficult on switches. Also, the initial setup is more difficult.

The initial setup is easy. Deployment only takes a few minutes.

I handled the installation myself.

The pricing is a bit lower than Cisco switches.

We use the 2500 PoE switches.

I have a lot of experience with HP switches. They're very reliable and are implemented easily. The features that they offer are more than enough for our hospital. There are other features on solutions like Cisco and Juniper, but for what we need, this solution is perfect.

I'd rate the solution eight out of ten.

The primary use case of this solution is for the customer's assurances in medium-size businesses.

The deployment model that we are using is on-premises, but it is going more and more in the cloud direction.

The most valuable feature is the IRF. It is very good, it has a multi-connection that you can do with multiple aggregation protocols to different chassis and this is a very valuable feature.

It's easy to stack more switches together if you need more ports.

Technical support needs improvement.

Customer awareness, as in the availability of the products, needs to be improved through marketing or other information.

Currently, we haven't seen any new switches and we don't know if there will be others.

In the next release, I would like to see them include more features like the Aruba solution, to have more possibilities concerning the software design.

This solution is very stable. It's a very good solution.

This is a scalable solution. With the IRF you can stack the switches willfully together locally or geographically. You can have the same switch even if you have a switch ten kilometers away from your location.

Technical support needs improvement.

The initial setup is straightforward and easy.

The time it takes to deploy depends on if the customer. An SD solution that will use management to configure the switches automatically will take minutes. If you have to configure a stand-alone switch it can take half an hour.

For ten customers there may be one person to deploy the switch and maintain it. You would rarely have to replace a switch.

There is no license for this solution.

We need a license for having a management solution, but the switch does not need a license. There are free software updates and there is a lifetime warranty for a few of the switch series.

If a customer has an issue with a switch and has to return to HPE, they can have it replaced within thirty days.

To our customers, we offer a contract service to have an exchange within the next day.

I would suggest not to invest in this switch. Aruba, which is also HPE, has a great switch. Aruba is taking over these types of switches because of the DLAN and WLAN. 

I agree that HPE provides good products but I would go with Aruba OS.

I would rate this solution a six out of ten.

HPE is very reliable because it has a lifetime warranty, so the switches didn't give us any problems. We were planning on replacing our switches with new HP ProCurve switches.

The solution is very straightforward for HPE users. It is not difficult to configure.

The pricing could be better.

We've used HPE Ethernet Switches for about ten years.

The switches have been stable since we put them in there. HPE gives a lifetime warranty on their switches because they know they're reliable. We have never had a single issue with HPE switches being offline or being upgraded and not working again.

The solution is very scalable.

We've used D-Link switches for smaller offices.

It's a very straightforward solution because it is not that difficult to configure. HPE was much simpler to set up than FortiGate. It didn't take a long time to set up.

We implemented the solution in-house.

The product's pricing is high, but you always get your ROI. It has served me for ten years without trouble.

We transitioned to Fortinet due to a company policy that came in to change from HPE to Fortinet. However, at the HPE level, I don't think Fortinet is on the same level. You won't compare HP with Fortinet. If you're going to compare HPE, then you have to go to Cisco Enterprise. But we try to stay just a little bit below the very high-level enterprise systems that HPE and Cisco have.

I rate HPE Ethernet Switches a ten out of ten. I recommend the product to everybody who wants to use it. HPE gives you a lifetime warranty on their switches, promising to fix them any time they break down. That tells you the product is reliable.

The pricing could be better, but I don't blame them for their price. HPE is not a small-business switch, especially the ProCurve switches, which are a bit expensive. Cisco prices are also not cheap, so I'm sure it's because of the competition. If HPE should make their prices a bit cheaper while Cisco keeps their price up there, it implies that Cisco is much more reliable than HPE. For competition's sake, reducing their price might not be something that can be done unless it can still be competitive at that level.

The primary use case of this solution is for the office network connection.

What I like the most is the management system integrated with the HP system. Our server is HPE and we have the management system to supervise. Now it is our system, but at the same time, it is the HPE because it is integrated into our system.

I am now using a new model because we had a problem with the speed, but the problem was with the network infrastructure, not with the HPE. We did not have the fiber backbone in our company.

We need more support to fix simple issues. For example, to find a problem in the LAN or why the systems speed is slow.

When we have a lot of clients on the system, we lose signal and have to restart our antenna. 

It would be better to be able to provide my number and have the information needed in regards to the equipment when a change is proposed.

You will need the assistance of a technician because the implementation is not that easy.

If you change your old equipment then it will be replaced but you have the same issues in five years' time because HPE does not have the equipment to solve my issues.

In the next release, I would like to see technical support for simple issues and to simplify the implementation.

I have been using this solution for six years.

This solution is stable. 

The switches have been installed for a minimum of five years, and have never been switched off. The problem is the cable or the rack gripped the cable, not the switch.

The switches are old, but there are components available that are not too expensive.

We have fifty users. This includes a technical and IT office with three people, a mechanical office with ten engineers, and an electronic office with three engineers.

This solution is scalable.

In our company, we want to change to a Fiber backbone and the switches we have are too old and only have STF ports with a maximum speed of one gigabit. The network needs ten gigabits to scale one gigabit for the client.

The technical is okay for our system. With the issue we have now, we contacted web support. We were satisfied with the support that we received. 

We had a problem with the shipment being lost, and they had to ship another one, but that was a problem with the shipper and not HPE.

The support not only solves my problems but they try to solve future problems that may occur.

Previously we used Cisco Atlantis. We switched to HPE because we had a good impression of this solution and good experience with the switches. Our network system was also older, with older equipment.

I find the setup in Cisco to be more difficult than HPE, but I know HPE better than Cisco.

If you use the web interface, the GUI interface, you need to have a basic knowledge to manage the network, it's easy. If you use the command line interface it's not as easy.

The time it takes to deploy really depends on the complexity of the network. If, for example, you have one HPE switch without a VLAN system, it's not easy. A network deployment can take a week with ten switches and to set up every port.

To implement this solution to make a separate VLAN for the CMC or to deploy the VPN connection we used an external technician. The technician, in this case, was HPE certified.

There were three options, but we prefer HPE, it was our first choice.

My advice would be to draw the network system before calling a technician. It's necessary to do a good job.

The price is not the only thing to consider when making your decision.

The switches are guaranteed for life, it's a great solution.

I would rate this solution an eight out of ten.

We use the solution for a small network and a small data center.

The solution is very stable and easy to use.

I would like to see more updates for the solution.

I have been using HPE Ethernet Switches for a couple of years.

I rate the solution ten out of ten for stability.

More than 250 users use HPE Ethernet Switches regularly in our organization.

I rate the solution’s scalability ten out of ten.

The solution’s technical support was good.

The solution’s initial setup is very easy.

The solution can be implemented through an in-house team. The solution's deployment process is very easy and includes designing the network and configuring VLAN.

The solution's security features are very good, and I rate them ten out of ten. Two people are needed for the solution's deployment and maintenance. I would recommend the solution to other users. I rate the solution ten out of ten for ease of management and configuration.

Overall, I rate the solution ten out of ten.

We use HPE Ethernet Switches for access control or access switches.

HPE Ethernet Switches have helped us build ACLs and VLANs.

They are effective. 

We have some fairly simple requirements, we can do the things that we need to do, it gets the job done. The interfaces are more user-friendly than they were ten years ago. 

It is simple to operate, and they have the feature sets that we require.

It's fairly lightweight, they don't require a lot of maintenance.

In general, the web GUI, or web interface, requires improvement.

Interface, and the ability to do things that are only possible through the command line, which seems pointless because there is no reason to have a command line for many of the functions.

The ability to stack, as well as a unified operating system, would be extremely beneficial. It isn't there. They are budget switches.

I have been using HPE Ethernet Switches for 15 years.

We use several versions of this solution, ranging from the most recent to some that are over ten years old. We have a full spectrum of switches.

We have no issues with the stability of HPE Ethernet Switches. It is stable and it works.

Scalability is determined by a pricing decision. HPEs are not at all a Juniper or anything like that, but for a budget shop like ours, they are adequate.

Our company has 250 users who use this product extensively.

I have never contacted technical support.

Previously, we had not used another solution. We started with HPE Ethernet switches.

The initial setup is relatively straightforward.

It took a couple of hours to get it set up and configured.

I am responsible for the maintenance of the product.

We did not use a consultant or integrator to assist us with the configuration, we did it ourselves.

There are no licensing fees, the price of the product is all that is required.

It is what it is and can be used by anyone; no expertise or prior knowledge is required.

I would rate HPE Ethernet Switches a seven out of ten.

I would say, to start with, the most valuable feature is that HP is not too different from existing systems. You don’t have to change too much the mode of operation that the ops teams are used to, and the command interfaces are workable.

We’re still in the implementation phase.

We’ve been getting fixes for things that were missing initially, but v6 support is there and has everything we need.

Because this is a modular device, we feel we can use scale in the future. The IRF is also important to us.

Overall good. We’re running into some issues when looking at beta code, something HP isn't focused on. The support people don’t want to talk too much about that.

We’re basically trying to look at an openstack infrastructure solution. We’re using it on a voice-over-infrastructure, supporting IMS. We’re using a Cisco solution right now.

I would say it’s no more complex than anything else, so we’re learning that people are protecting systems a bit differently.

We looked at -

• Cisco
• Juniper
• Alcatel Lucent
• HP
• Aresta
• Erickson

We chose HP because they met most of the criteria that we were looking at, and they were able to come up with some solutions that were a little outside of the box when things didn’t quite fit. They were more proactive on the sales/engineering side and with pre-solution support.

You should look for high performance, low maintenance, open flow, and XLAN when choosing a solution. Compatibility with other products is also very important. Some routing protocols were required.

Overall, the solution is a little more complicated than we initially wanted, but it’s pretty good. It’s going to be a learning and teaching experience for service providers. Solutions are there, but they’re not always the same methodologies for the same businesses.