HPE Ethernet Switches Reviews

These access layer switches are used by our branches for user LAN connectivity.

These are the basic access layer switches used for connectivity among users, and they are cost-effective.

We sometimes have issues with the stability of our POE switches. If there is any fluctuation in power then we will face an outage with our POE switches, so this is something that should be improved.

We have been using these switches for between four and five years.

These switches are partly stable but we do sometimes face issues with them. We do plan to continue using them in the future.

We have these switches deployed in different branches and in many cities.

In our office, we have between 10 and 12 users.

We are only using this product for basic purposes, so we do not require technical support from HPE.

We were using Cisco Ethernet switches before we switched to HPE. The HPE switches are almost the same and we switched because they are more cost-effective.

The installation and initial setup are straightforward. The minimum time required is half an hour.

Our in-house team is responsible for deployment. We have five or six team members who are engineers.

There are no licensing costs for this solution.

This is a product that I can recommend.

I would rate this solution an eight out of ten.

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 are a solution provider and the HPE Ethernet Switches are one of the network infrastructure products that we implement for our customers.

They are used from edge to core and I usually implement them for storage traffic and IP over ethernet, like NFC, iSCSI, or SAS. 

Our customers' needs are simple and not very sophisticated, and these switches allow us to set up the solution and forget about it. As much as possible, we isolate subnets or infrastructure to ensure that the frontend network is separate from the backend network storage. This helps to reduce problems.

HPE is very good for cases where you use storage for server networking

The product's stacking technology is stable and works well.

Authentication and other security features are not easily satisfied using the lower-end switches. For better security, you need to implement enterprise-level hardware and software.

I have been working with the HPE Ethernet Switches for six years.

Our clients for this product range in size from small businesses to university campuses. In a small business, they might have 200 to 300 users with perhaps between 500 and 1,000 endpoints. The scale for a campus would be in the area of 3,000 to 5,000 endpoints.

When we or our partners sell this product, it usually sells only with a hardware warranty. It does not come with software support. When there is an issue, we normally just update the switch or try to find out what version or what configuration is suitable for the product.

Ideally, once we install and configure it, we can forget about it. This is our motto.

The Comware version from H3C was very useful for our customer base, but the product line is changing and the customers are changing. Some of our customers use Cisco, HPE, or other products, and I have to configure them. I recommend products to customers, although it often depends on what they already have in their environment.

In cases such as Comware, where the line no longer exists, I recommend new products.

With Cisco Switches, you cannot buy them without the support and a license.

This is an expensive product. Some features can be added after purchase, which comes at an additional cost.

Overall, the product works very well, we don't have any problems, and I can recommend it. 

Although people can have a lot of trouble with these switches, they are human management issues. This is why we are careful to choose the correct products and to do the implementation and integration correctly.

I would rate this solution a seven out of ten.

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.

We primarily use this solution for video surveillance.

The best part about this solution is the price.

This solution is easy to use.

The technical support for this solution has improved from what it was.

We have had some rare occasions with glitches, so the stability can be improved.

This solution is stable, but on the rare occasion, we have had glitches like dropped packets.

We do not tolerate serious issues in the backbone or infrastructure. We do not go for something cheap and hoping that it will work, especially when it comes to networking.

I cannot comment on the scalability because it is not something that we consider. When we decide on a solution, we go for it completely, from the beginning to the end. We start with the complete solution on day one, as opposed to starting small and then looking to scale it later on.

The number of users for each of our switches depends on the circumstances. In some sites, we have ten or twenty users. In other sites, depending on how big it is, like an industrial facility or a hotel, we do not know. Many of our solutions are used in retail or hospitality environments.

We do not speak with HPE technical support because everything has to go through the distributor.

Most of the time, we use solutions from Cisco. They are well supported in Egypt. However, new regulations in Egypt require that if we are buying a product from abroad then we have to be a partner, and have a letter from the vendor to indicate this. Is has to do with the ability to provide local support.

Because we are not a partner with Cisco, we need to purchase equipment from the local partner. This means that we have to work with their fees and time schedule. Paying in advance is not a problem, but you have to wait for an unspecified period of time to receive your equipment. They won't give you an estimate as to the duration.

We switched to HPE simply because they are easier to get than Cisco or Sophos.

Our deployment took a couple of days.

We have not had to maintain our switches, except for one time when we had a bad experience. It was a long time ago, and we had HPE switches from a system integrator. One had a problem and it was under warranty, but instead of replacing the switch, they started swapping pieces one at a time. This switch was in a very crucial data center and it was very difficult to get there.

Ultimately, we lost the customer and the system integrator lost their reputation. I think that HPE lost a lot because it was much easier to replace the entire unit instead of replacing one piece at a time. They ended up replacing entire modules. Since that time, we don't rely on local partners. We talk to HPE directly or we collect the whole unit and send it to HPE.

Our in-house team handled the implementation.

Licensing fees are on a yearly basis.

These switches are not as stable as those from Cisco.

We were looking at some switches from Alcatel-Lucent, but they are not popular in Egypt.

This is a solution that I recommend.

My advice to anybody researching this type of solution is to not go for the cheap solution. Go for the right one. You get what you pay for.

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

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.

We use HPE Ethernet Switches for network switching. 

This solution is deployed on-premise. 

The most valuable features of this solution are the interface and configuration. It's very easy to use. 

The only improvement I can think of is that it could be better with less updates. 

I have been working with HPE Ethernet Switches for more than 10 years. 

The performance is fine. 

This solution is easily scalable. 

In my organization, there are maybe 200 end users of this solution. 

The technical support is really good. They're fast, knowledgeable, and customer-ready. 

The installation took one hour, and I was involved in the process. For deployment, we had a team of two engineers. 

We implemented this solution through an in-house team. 

There are no licensing costs for this solution. It's lifetime, so it's okay. 

I rate HPE Ethernet Switches a 10 out of 10, and recommend this solution to others. To those considering implementation, I would say: if you want a lifetime solution, then go with HPE.