4 Cool Things About Juniper Networks That Set Them Apart

One of the questions customers often pose is...“Why go with Product A over Product B?”

You can always go with the stats on Manufacturer A’s Switch and match them up to Manufacture B’s Switch. Instead of doing that, you might find it helpful to highlight the perks of a manufacture and what sets them apart from other companies. Let's do this for Juniper Network

Here are 4 cool things that set Juniper Networks apart from other manufacturers.

All for Junos and Junos for All

For the most part all of Juniper’s products (switches, routers, firewalls) run the exact same modular operating system at the same code version. That operating system is JUNOS.  What that means is that a customer does not need to learn multiple operating systems to configure different types of products within the same product line.

Save the Date

To add on to the joy of JUNOS, Juniper has only 4 software release upgrades a year; one every quarter.  Unlike many manufactures who have random updates to code with no set schedule, this is simpler and much easier to plan for.  If you have a complete Juniper network you can upgrade your software on your switches, routers, and firewalls all at the same time and since they all run the same code they will all be at the same code version.

Here's an example using professional baseball and football. With baseball, if asked when the next 3 gameswill be played you would have to look it up and plan things accordingly. On the other hand, with  professional football it's well known that game day is Sunday. Sure, there are the occasional games on Monday, Thursday and sometimes Saturday, but you get my point.  Much easier to plan for football.

A Likely Candidate

When configuring Juniper product you have what they call the Candidate Config. When you enter in a series of commands they are not executed immediately. They do not go into effect until you type the command “commit”. This gives you time to look over your work and check for errors that could potentially harm your network. And even if there is a potential error it will in some cases tell you when you try to commit it.

Fall Forward, Rollback

By default, Juniper automatically saves your last 50 configuration changes.  Why is that important? Because at any time you can roll back to one of them.  In a situation where it takes a time to see changes in your network (such as waiting for OSPF convergence) this is a life saver.

You make a change, commit it, and everything seems fine. Then 5 minutes later a quarter of your network is down. You just type the command to rollback to a previous working configuration before you made the changes and you are up and running again. Now you can go back and try to figure out what went wrong in your changes.