Juniper Ethernet Switches Review

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: I am a real user, and this review is based on my own experience and opinions.
More Juniper Ethernet Switches reviews from users
...who work at a Comms Service Provider
...who compared it with Cisco Ethernet Switches
Learn what your peers think about Juniper Ethernet Switches. Get advice and tips from experienced pros sharing their opinions. Updated: January 2021.
455,108 professionals have used our research since 2012.
Add a Comment

author avatarit_user4401 (Developer at a transportation company with 1,001-5,000 employees)

Regarding the comparison between Juniper and Cisco Ethernet Switches, what is your opinion about rollbacks? There can be situations when somebody makes a mistake.

author avatarit_user111924 (VP of Network/Comms/Infra at a financial services firm with 10,001+ employees)

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.