HPE ProCurve Reviews

I have used S3 bucket to save files. I used the SQL database from AWS. We use AWS Relational Database Services (RDS) and EC2, which is Elastic Cloud Compute. These are the three services I have used from Amazon.

S3 Simple Storage Service is used for sharing videos and photos. We created a system where we process and comment on content. For the backend, we save the files in S3 bucket, and provide that link to the frontend for displaying images. That is what we use S3 bucket for, as it is a simple storage solution.

I have been using Amazon RDS database service for 4-5 years. It is a normal Postgres installation, which we use for storage purposes.

Amazon RDS itself is a product offering different relational database services. It includes DynamoDB for NoSQL databases, as MySQL and Postgres for relational databases. I have used relational database services in Amazon which provides backup capabilities. If we miss anything, we can immediately restore from a backup to retrieve the data.

We use DigitalOcean mostly for RDS services and cloud-related systems where we deploy codes and run them using Nginx, as it is more economical. We also use it to extract data and manage Linux-related schedulers.

Amazon RDS is easy to use. It is somewhat pricier but manageable. It has easy tasks and integrates smoothly with frontend components. When using IDE services such as PgAdmin, the installation steps are straightforward. The availability is also high, which is why we use it.

It offers easy scalability and migration between different configurations.

RDS performs well overall. The main consideration is pricing, which is higher compared to alternatives such as DigitalOcean. For backup and restore operations, it takes slightly longer - approximately 2-3 minutes compared to 2 minutes with other providers. There are also more steps to follow compared to other service providers.

The installation process is straightforward with no complex requirements. Users can directly select their desired database, memory requirements, and port numbers without complications.

I use the solution in my company for ToR switching in the data center.

Frankly speaking, the switches are very good and have been running without any shutdowns for more than a year. HPE's team has already monitored the switches.

Network performance-wise, it is a good product. The network performance can be made simpler. A few areas included in the network performance managers can be integrated into the solution's dashboard since it is the only area with a few concerns. The network performance manager should be integrated with the dashboard.

We wanted a faster and more reliable network. While Cisco might have some advantages in complex switch management, HPE, and specifically ProCurve, offered easier configuration, deployment, and overall performance.

At the time we switched to ProCurve, segmentation was critical for us. It was easy to configure VLANs for network isolation and was straightforward with ProCurve.

It has supported our network expansion.

The user interface (UI) could be better. Sometimes navigating through the switch interface to find specific features wasn't very intuitive. As an administrator, the layout could make it difficult to quickly locate settings. You might end up searching through various menus, which takes time. This gets easier with familiarity, but it can be challenging initially.

The command structure wasn't always as straightforward as something like Cisco. 

We use the product to connect our headquarters with 32 branches in the country.

Inter-VLAN is a great feature. It makes restrictions for spoofing in certain ports. We also get very good logs about flapping ports that cause the network to hang up.

We use the solution for networking access. We need to connect, for example, every user in the building to the network. Generally, the users are not using more cables. They are just using Wi-Fi. We connect the users via Wi-Fi to the network of the company, and we also have this network access control which is one appliance that can verify the current situation of the endpoints. For example, if the device has the correct credentials to access the networking, if the device, for example, has the latest Windows updates, the latest antivirus updates, you can create your own routes to let the device in and access the network, or deny it, or put it in quarantine. You'll be able to access some remediation networks.

The network management solutions that they have is great. They use a multi-vendor approach. For example, you don't have to buy their equipment or their devices. You can buy from another vendor and then try to integrate with the network management system. The same is true for ClearPass. It's network access control. It's multi-vendor, and it's prepared to integrate with a lot of things. That this is the main advantage of the product. 

In our organization, we might have up to 20,000 people who need to connect to the network and access Wi-Fi. And not just inside the buildings, as they have remote access points, for example, that we can put in a home to provide the same or almost the same access to the network that you can get when you are in the office.

The solution is scalable.

It is a stable product.

We've found the setup to be pretty straightforward. 

The solution is very secure. This year, they may have only been one issue, whereas, for example, Cisco had maybe ten. It's very secure. 

Our entire network is controlled by HPE ProCurve. Essentially, we have an MPLS as part of our MPLS network. There are numerous use cases I can describe, but there is nothing I can say in detail right now.

We have a huge network with a lot of servers. Our operation is small but we need the network infrastructure.

It has valuable features. It has an excellent menu system where you can use both the CLI and a menu system and the GUI version. They have three options for manipulating, updating, and changing the switch, which we like.

In general, the CLI functions similarly to the Cisco iOS. Except for a few core Cisco proprietary functions, they have most of the functions.

If you're familiar with Cisco iOS, you won't have to worry about their ProCurve. That's what we like about it. Also, it basically controls, layer three and layer two, we use both functions on it, and it has a lot of routing for us as well.

It does a good job for us. ProCurve CLI is very similar to what Cisco allows you to do with their CLI on iOS.

It is not difficult to work on the transitions or if someone is working on both. The commands don't differ all that much.

We use the product for VLAN configuration.

The product is robust. Once I get it working, I'm good to go.

The HPE ProCurve, we've used mostly with businesses, either enterprise networks and/or some manufacturing. We've worked and used the solution in a core setup and edge switches.

One of the biggest things in HPE ProCurve that I like, though not necessarily a feature, is the HPE warranty because it's probably better than any of the other vendors that we deal with, as it has a lifetime replacement. Feature-wise, the web interface of HPE ProCurve is typically pretty good and I like that as well.