HPE Ethernet Switches Reviews

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 work in network operations and have experience as a user of HPE Ethernet Switches. We don't function as the customer, but as the customer's customer. 

The graphical user interface is very good and quite easy to run with. It's quite intuitive.

In terms of product improvement, it's possible that the VLAN tagging could be improved, it's not that straightforward. But I can't really think of other improvements I'd like to see. 

Additional features that could be included in the next release could be the inclusion of further monitoring facilities. 

It's very stable and that's one of the good things about the product. It basically comes with a lifetime guarantee and that was one of the main reasons why I purchased them in the first place.

I haven't had any reason to deal with the technical support people to date.

I would recommend the Hewlett Packard product. They are very, very stable, and for the money it's really good value.

I would rate the product a nine out of 10.

We use this solution for our office network in an on-premises deployment.

It handles only our office traffic, and our main computers are on the cloud.

We use classical features such as trunking and VLAN. We don't really use the fancy stuff like SNMP.

The HPE Ethernet switches have very low latency.

The interface is old in appearance and needs to be modernized.

I would like to see better URL filters and security.

It would be helpful to have training available for this solution.

We have had no problem with respect to stability, and we are very happy.

We have not needed to scale this solution.

We had to contact technical support one time to update the software. It was not easy because this unit is very old. We could not find the current files on the HP support page.

Currently, we do not have a contract with technical support.

We had a NETGEAR solution and it was not stable. I did not like the interface because it was very slow. It was a pain to work with and maintain the configuration. It also had very high latency. After switching to HPE we have had no problem at all.

The initial setup of this solution is straightforward. It has been very easy to change the computers whenever we needed to.

Our deployment took approximately one day. It was easy to get working.

A single technician is enough for deployment and maintenance.

I have also been working with Cisco solutions, which are really great but there is a problem with integration. If everything is Cisco then it is very smooth, but if you mix vendors then it's a problem. This is the reason we did not choose Cisco here.

I have also worked with other kinds of switches like D-Link, but they are not for a business like ours.

I would recommend this product and also a support contract. I don't think that I would pay this price without getting the support.

We are happy with this solution but it is really an old model.

I would rate this solution a six 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.

The primary use case is EdgeSwitches.

The most valuable feature is that they all have PoE. It's one of the most important things that we need in EdgeSwitch.

One of the reasons we keep them alive is because these switches have a lifetime warranty, so it's a major point on their use.

We haven't had any issues with this switch in the past 10 years. That's the reason we're still keeping them alive.

The solution is deployed on-premise.

I have been using this solution for 10 years.

The solution is stable.

It is scalable.

Right now, we have 200 people using this solution. We aren't planning to increase usage in the future because the global solution is appointing another brand of switches that we probably will implement in the next year.

Technical support is quite good, but we haven't needed it.

For an IT network specialist, initial setup is quite simple. There's no problem at all.

We didn't use any consultants or resellers for deployment.

The licensing cost is yearly, and there aren't any additional costs on top of the standard fee.

I would rate this solution 9 out of 10. It's not a 10 out of 10 because of the price.

My advice is to trust the solution. It is a reliable product, and it works well without a lot of attention. We can leave them and almost forget about it.

These are units that are a two or three layer solution. Since it's from HP, we have a lifetime warranty for these switches, unless the product is already phased out. But in most cases it takes a long time before they're out of a cycle. Most of these are quite durable. We are customers of HPE Ethernet Switches and I'm head of technical support. 

I think this solution could be improved if the installation could be made more secure. From our point of view, HP could have SNMP product softwares that would allow us to track all the assets, and then to connect, to identify our equipment. There are options which would allow us to secure the equipment. I think with the enterprise solution, if it's HP, then there is a need to integrate it with an HP product for it to work. The only way to simplify this is with VLANs and then routing, and then let the systems take over when it comes to firewalls and other things. Implementation of those things would allow us to have tighter security.

I've been using this solution for 10 years. 

It's an enterprise solution so it's stable. 

It's mostly quite scalable and quite straightforward. 

If we have problems, we tend to resolve it ourselves. Sometimes there are bugs but it gets sorted out after a while. 

We previously used IBM but they gave up on those products and sold the PC and printer business. We started using HP before that happened. 

The initial setup is quite straightforward. Once we have the manuals, and can enable the VLAN and routing functions, we can set the redundancy, our STP, so that from switch one to switch two, you can set four lines to be redundant. In the event that one line is cut, the others will take over. We can also do a link aggregate where you combine the different lines together to increase the bandwidth. These are mostly the straightforward functions that we use as far as the switches are concerned.

In terms of deployment time, we usually define the IP addresses for the switches so we can access it remotely. Then it's a straightforward thing. There's a plan for us to do some more straightforward definition in the coming months. We do the deployments ourselves. We currently have between 200 - 300 users. I use five or six people and then we can deploy in a week or two.  

There's the familiarity factor for us. It's something that we hold on to. If you know the product is stable, and it's not outdated then you'll continue to use it. I think it's on par with other vendors like Dell. I'm very satisfied with everything. I've been using HP for a long time already and I think it's quite reliable, even my printer is HP.

I would rate this solution a nine out of 10. 

We use the switches to connect end users to the devices. 

We get a lifetime warranty for the solution so whenever the switches get faulty, you can get a replacement. 

The tool should be more stable. 

I have been working with the product for more than ten years. 

The product is scalable. 

I never contact the support since I resolve issues by myself. 

The product is easy to set up. I configure the tool in 5 minutes. 

The tool's pricing is very cheap. 

I would rate the product an eight out of ten. 

We use HPE Ethernet Switches in hospitals and governments.

We have some problems with the performance of our HPE Ethernet Switches because they are old.

I have used HPE Ethernet Switches within the past 12 months.

The solution is highly stable.

We have one client using the solution.

The support of HPE Ethernet Switches is responsive and helpful.

HPE Ethernet Switches are more difficult to implement than other solutions, such as Aruba, because the configuration has to be done one by one, it's not saved centrally. You are not able to automatically configure them across the hardware.

I utilized a significant amount of HP technology in order to create a stacking configuration, incorporating various models as needed. This was because Aruba, which is a well-established brand, is frequently used for stacking purposes. However, in our particular scenario, I utilized HPE Ethernet Switches, despite it being an older technology, and decided to stack them. To provide a specific example, I utilized the HP 2930 model, which is stackable as per the guidelines provided by the model guide. Additionally, I integrated artificial intelligence to further optimize the process. However, for improved results, scaling up is necessary.

I did the implementation of the solution.

The price of the solution is expensive.

I rate the price of HPE Ethernet Switches a ten out of ten.

I would recommend this solution to others who have traditional environments.

I rate HPE Ethernet Switches a ten out of ten.