Name: Juniper EX Series Ethernet Switches
Brand: Juniper
Rating: 4.1 (73 reviews)

reviewer984912

Service Manager at a energy/utilities company with 1,001-5,000 employees

Oct 14, 2019

Download

Easy to Setup Secured Networks, but local technical support is lacking

Pros and Cons

"What I like most about this solution is that it is secure."
"What I like most about this solution is that it is secure."

"It was very difficult to get technical support, here in Egypt. There is no local support available."
"It was very difficult to get technical support, here in Egypt. There is no local support available."

What is our primary use case?

The primary use case of this solution is for the internal network, covering our entire office.

The deployment model we are using is on-premises.

What is most valuable?

What I like most about this solution is that it is secure.

What needs improvement?

They need to have more marketing in Egypt.

The technical support in Egypt needs to be improved because I was struggling to get technical support.

Having documentation provided in Arabic would be nice, but not necessary, as most everyone speaks and understands English well enough.

I would like to have customer support on the ground.

For how long have I used the solution?

I have been using this solution for two years.

Buyer's Guide

Juniper EX Series Ethernet Switches

April 2026

Free Report: Juniper EX Series Ethernet Switches Reviews and More

Learn what your peers think about Juniper EX Series Ethernet Switches. Get advice and tips from experienced pros sharing their opinions. Updated: April 2026.

DOWNLOAD NOW

893,164 professionals have used our research since 2012.

What do I think about the stability of the solution?

This solution is stable.

What do I think about the scalability of the solution?

This solution is scalable.

We have approximately twenty users, most of them are engineers.

How are customer service and support?

It was very difficult to get technical support, here in Egypt.

There is no local support available.

Which solution did I use previously and why did I switch?

Previously we used Cisco. From my understanding and from what I was told, it was complex, hard to handle, not customer familiar or customer friendly.

How was the initial setup?

The initial setup is straightforward and it's easier than Cisco.

What about the implementation team?

We did not implement this solution through a vendor, we had one of the team members do it. It wasn't that difficult.

What's my experience with pricing, setup cost, and licensing?

I would rate this solution a seven out of ten.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Alejandro Mendez

External Plant Coordinator with 201-500 employees

Feb 4, 2018

Download

Supports all our connectivity infrastructure in our datacenter

Pros and Cons

"Juniper supports all our connectivity infrastructure in our datacenter, supporting optimal availability and performance for services."
"The Virtual Chassis, because you have a centralized administration of a set of switches which makes the operation more efficient."
"Juniper supports all our connectivity infrastructure in our datacenter, supporting optimal availability and performance for services."

"Support prices and licensing scheme need to be improved to allow some features to be purchased at lower costs, for example, RPM."

What is our primary use case?

The primary use is as a datacenter, as aggregation and access switches. They are also used in wireless nodes in the core switch segment receiving all last mile services, as in optical fiber.

How has it helped my organization?

Juniper supports all our connectivity infrastructure in our datacenter, supporting optimal availability and performance for services.

What is most valuable?

The Virtual Chassis, because you have a centralized administration of a set of switches which makes the operation more efficient.

What needs improvement?

Support prices and licensing scheme need to be improved to allow some features to be purchased at lower costs, for example, RPM.

For how long have I used the solution?

Three to five years.

Which solution did I use previously and why did I switch?

We previously used Cisco.

Which other solutions did I evaluate?

We evaluated Brocade.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Buyer's Guide

Juniper EX Series Ethernet Switches

April 2026

Free Report: Juniper EX Series Ethernet Switches Reviews and More

Learn what your peers think about Juniper EX Series Ethernet Switches. Get advice and tips from experienced pros sharing their opinions. Updated: April 2026.

DOWNLOAD NOW

893,164 professionals have used our research since 2012.

it_user101373

Works at a comms service provider with 1,001-5,000 employees

Jul 27, 2014

Download

I'd like to see it's cost go down but it has optimal TCO

Pros and Cons

"We did some prep with the vendor team which was very helpful."

"Stability issues and its cost."

Valuable Features

Optimal TCO

Improvements to My Organization

It's not about improvement, it is more about optimal decision making.

Room for Improvement

Stability issues and its cost.

Use of Solution

Juniper EX series About 2-3 years

Deployment Issues

I haven't seen any issues with deployment.

Stability Issues

Seldom

Scalability Issues

Standard questions about more clients ports on devices.

Customer Service and Technical Support

Customer Service: Good, but not the best.Technical Support: Good.

Initial Setup

We had some questions, but that's it.

Implementation Team

We did some prep with the vendor team which was very helpful.

Other Solutions Considered

Cisco solutions and some others.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

it_user90057

Owner at a tech consulting company with 51-200 employees

Feb 13, 2014

Pros and cons of both Cisco and Juniper configs, but you can see the benefit of why they organized it the way they did

After being primarily a Cisco user for many years, I find the switch to Juniper refreshing. The CLI is intuitive and I appreciate the hierarchy of the various configuration groups to be much more organized. I also think it is better with regard to config checking, and ensuring that the items entered into the config work with the rest of the config. For example if you happen to forget a line in a policy, or make an error in referencing a particular object, it will not let you commit the config. I know there are pros and cons of both configs, but once you get used to Juniper, you can see the benefit of why they organized it the way they did.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

it_user111924VP of Network/Comms/Infra at a financial services firm with 10,001+ employees

Report as inappropriate

Nov 11, 2014

Hi, well to your point about rollbacks, the benefits of this feature are quite obvious in that they provide a fail safe mechanism should your changes inadvertently isolate you from a remote device due to some unforeseen error/mistake (it happens!).
I often hear people compare this age old Junos feature to Cisco's "reload in|at x" command, however if the difference isn't already obvious, that command results is a device reload, whereas Junos rollbacks do not. Picture a scenario whereby your action isolates you from a remote device yet that device is still carrying production traffic loads. In this scenario, the user of rollback would be able to regain access to the device without impact to traffic through the device, whereas the user of the reload command would see an outage. Consider a worst case scenario whereby the device fails to complete its boot cycle and there my friend you have hell on your hands. May as well pack your stuff into a box and grab your coat at that point.

See all 2 comments

it_user82779

Engineer at a comms service provider with 10,001+ employees

Jan 29, 2014

Benefits of Juniper vs Cisco

Both are decent products. I prefer Juniper for the following reasons:

1) Cleaner separation of data plane from control plane. Higher end Cisco devices are better at this but most of the lower end products still seem to be more integrated than I like.

2) The Hierarchical config design means I can make changes only in areas that concern me without necessarily impacting other areas.

3) Easier rollback when one makes mistakes

4) I think there are less bugs/vulnerabilities in Junos vs IOS.

5) iOS has too many flavors leads to confusion with deployment.

One more advantage of junos over iOS. Juniper adheres closer to the standards than Cisco. Epigraph is nice, auto rp is cool, but with the less protocols in the standards it's much earlier to configure junos.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

it_user111156Consultant

Report as inappropriate

May 6, 2014

Either vendor has a switch that will do the job. However I perferer Juniper due to

a. rollback is quick and easy in the event of issues arising from chnages
b. easier fault finding (once you get your head around how its implemented)
c. no need check the switch to find which OS feature set is installed and if memory / flash upgrade is required - its all in the OS with very few licenses (usually none) required to get full functionality if you have select the correct product in the first place
d. Hierarchical config is much easier to follow - great concept that most programmers can pickup quickly
e. don't need to learn different variants of the CLI as is required on IOS (even HP manage to stay relatively consistent there)
f. decent speed stacking interfaces on enterprise grade switches (particular 4x00 series)
g. more function for $ (at retail prices)
h. closer to standards than Cisco - easier interoperability in multi vendor environment
i. does not have legacy protocols that are not used or so rarely used that they don't matter in the day and age

Purchase and implementation of Cisco maintenance process is MUCH simpler to the end customer

Worked on both brands for a number of years.

it_user5700

Engineer with 501-1,000 employees

Apr 4, 2013

I found it to be difficult to make the transition from Cisco to Juniper as far as the CLI goes.

Overall, the equipment is pretty good and more affordable than some other solutions. I found it to be difficult to make the transition from CISCO to Juniper as far as the CLI goes, maybe thats just me. I also had more than one instance where a switch would just stop working and I would have to reload the firmware on it and reconfigure it to get it back up and running. This caused me to purchase backup devices to minimize downtime and really cut into the cost savings over CISCO.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

it_user88422Network Engineer at a comms service provider with 1,001-5,000 employees

Report as inappropriate

Feb 13, 2014

There's a learning curve for sure but it's definitely a better CLI and it appears Cisco agrees going by the changes in IOS-XR. Once you get your heard round using a tiered structure it just makes more sense. Config tools that JunOS offers like copy, replace and move are really handy if you learn how to use them. These can save you a lot of time. What else...

Commit check / confirm / comment
rollback
traceroute monitor
monitor interface
stacking of pipe "|" commands for example: show interface | match xe | match error
Show configuration | display set

I strongly advise you start looking at and backing up configs using the later format. Sometimes the standard hierarchical display can be easier to read and spot mistakes but for copy and pasting config it's much easier to use the "set" display format. Avoiding using "load merge terminal" will save you headaches IMHO.

Once you learn the power of all the show and config command options start looking at JunOS Scripts - then you'll be blown away.

Also if you have access Juniper offer a IOS to JunOS conversion tool... i2j.juniper.net/release/index.jsp

it_user2589

IT Administrator at a tech consulting company with 51-200 employees

Oct 27, 2012

Download

Impressive features but switches are facing tough competition

Pros and Cons

"From the technology point of view quality, design, and look-and-feel is good."

"I felt that on-site and telephone support is not satisfactory."

Valuable Features:

From the technology point of view quality, design, and look-and-feel is good. Network administrators can easily manage and configure these network switches. I have easily configured an L3 switch to create a network campus backbone. Low maintenance required. No certification (CCNA, CCIE) is required to become a network administrator to set up a Juniper network.

Room for Improvement:

During price negotiation we found that price is high compared to other switches. High price is obstructing sales in market. I felt that on-site and telephone support is not satisfactory.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.