What is our primary use case?
The use case of this solution depends on our client's environment. Some use HPE Ethernet Switches right out of the box, while some of them use models where the interface can only be opened by Internet Explorer.
The primary use cases would be office interconnection and industrial interconnection. The switches are best suited for our small or medium-sized clients.
What is most valuable?
For me, as an administrator, I value that there is a clear place to find a MAC table with HPE Ethernet Switches.
HPE Ethernet Switches are quite robust. I have not seen them damaged to the level that they are not operable anymore.
The solution has a simple and understandable user interface providing everything I need.
What needs improvement?
In the past, I have encountered configuration problems with the Spanning Tree Protocol. The switches were only handling a single loop. There were quite a few looped switches that could not handle the board blocking, creating the need to manually fight each loop. I have not had the same problems with the newer models of HPE Ethernet Switches.
HPE Ethernet Switches tend to hang from time to time, but all switches do that.
The next release would benefit from adding central management that could be deployable on-premise and allow you to see the layout of topology.
For how long have I used the solution?
I have been working with HPE Ethernet Switches for about one year.
What do I think about the stability of the solution?
The solution is stable. HFE does not fail any more or less often than other switches.
What do I think about the scalability of the solution?
HPE Ethernet Switches, especially the 1820s, are best suited to small or medium-sized organizations, however each case is model dependent. The switches we use, are used in large companies, but they are fractured into smaller layers of three subnets.
The solution is scalable, you can add a switch when you need to, and you can reconfigure it.
How are customer service and support?
I have not had the need to contact customer service and support. Any past issues, we were able to resolve by go through some of our forums.
Which solution did I use previously and why did I switch?
Since our company provides services, we work with the switches that the clients have. Most of the switches we work with are HPE's, Cisco, and UniFi.
I found that when using Aruba or UniFi, you have to search for the MAC table from CLI. This is difficult because when someone calls using a MAC, I will not get the IP address and I need to guess where the user is.
UniFi requires less intervention in configuration, requiring some tune-up support. HPE needs to be configured manually.
How was the initial setup?
The initial setup of HPE Ethernet Switches is straightforward. The time it takes to deploy depends on the overall network configuration, including the number of LAN, number of up links and down links for that switch.
If you only need to connect the switch to the up link and give out for a test for the end devices, it would take a maximum of thirty minutes after installing the switch to its correct place.
In a case where there is a lot of VLAN with some trunking, deployment could take a couple of hours.
I would rate the initial setup of HPE Ethernet Switches a five out of five. They require little to no maintenance and are reliable enough.
What's my experience with pricing, setup cost, and licensing?
As a technician, I am not certain of pricing, but I believe HPE is less expensive than Aruba and UniFi and that is why certain clients have chosen them as their solution.
What other advice do I have?
I would recommend to anyone looking into implementing HPE Ethernet Switches to go for it if the price makes sense for their organization.
Overall, I would rate HPE Ethernet Switches an eight out of 10.
Which deployment model are you using for this solution?
On-premises
*Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator