Hewlett Packard Enterprise, known as a global edge-to-cloud company, concentrates on a range of technology and innovation services to connect, protect, analyze, and act on all data and applications wherever they live, from edge to cloud, focusing on addressing business challenges through technology.
Do You Manage Peer Insights at Hewlett Packard Enterprise (HPE)?
Access Vendor Portal to update and manage your profile.
The EX series switches we use in our core are very stable and have not experienced any failures despite handling very high traffic, as all client syslogs are routed to our SIEM through these devices. They are very useful switches because they are easy to configure when we have physical network probes in the organizations we manage. The virtual chassis and port mirroring configurations on these models are easily configurable, and more importantly, they are very stable; they have never experienced any failures.
* Cheaper than Cisco * Ethernet / Fiber Switchports are physically robust * Rollback function on Firmware is a massive plus to Juniper in general * Juniper Support are quick to respond and dedicated to resolve issues
Stability and reliability, along with advanced network segmentation capabilities using VLANs and Virtual Chassis, make Junos stand out. The Junos CLI is powerful, and performance is robust even under heavy load.
Undoubtedly, the IOS update process for these devices is their biggest problem; it's tedious and slow, and sometimes causes service interruptions despite high availability. In clients who have these switches in their core layer but another manufacturer's operating system in the perimeter firewall or access switches, we've experienced many problems when there's network latency in detecting the point of failure. Therefore, their integration with third-party solutions is far from ideal. In my opinion, they need to invest more in log management and ingestion; they're lagging behind in complex networks.
* Frequent Cold Boots (whether intentional or from an incident) can quite easily cause corruption on the Switch's config - although a majority of software/devices warn this, it seems to be more prevalent here * Power Spikes are the killer of these devices - they seem to be very sensitive in almost any fluctuation of power - goes hand-in-hand with frequent Cold Boots; spikes need to be avoided at all costs * Airflow inside the EX2300 (compared to EX2200) has changed for what seems to be a less-efficient path for hot air removal, and for some could mean a few changes in the Rack * EX2300 model has a power button on the front of it that if held for too long will factory reset the device - as a network engineer, this is no issue but when a non-engineer doesn't know this and tries troubleshooting the device (ie: at a store rack) then this becomes a long night's work very quick * Every firmware revision has a MASSIVE list of bugfixes, and changes, and it's common to find situations where something (eg: Automation) will work with an older version but no longer with a newer version for whatever reason; searching through these changes can be a difficult task to find those nuances
The web management interface is somewhat outdated compared to other vendors. The initial learning curve for Junos OS can be steep for teams accustomed to other platforms.