I’ve decided to jump head-first into JUNOS. My short(ish) term goal is to find a position with a service provider. I’ve read that Juniper owns a very significant portion of the SP core, so any exposure to JUNOS can only be a good thing (or so I hope). JUNOS is (obviously) very different from IOS. This is mainly about my experience as an IOS guy starting out with JUNOS.


  • JUNOS is modular, which means more process separation and stability.
  • JUNOS has less versions (no ipbase, advanced enterprise, etc.
  • Commit feature – This allows you to input multiple commands before making them active.
  • Rollback feature – JUNOS saves the last 50 committed configs, allowing you to revert to an old config.
  • Command completion is a little better in JUNOS, you can use spacebar or tab. It will also pick up things that IOS wouldn’t, like user-set variables in the config.
  • The ability to use CIDR notation in JUNOS, this is very, very nice.
  • JUNOS has better pipe functionality than IOS with show commands


  • It’s not IOS :-)
  • Simple things (NAT, static routing, IGP, BGP, etc) can become very complex due to the hierarchical nature of JUNOS.
  • Show command outputs. It’s harder for me to find information in some of the outputs. This one doesn’t count really as it’s mainly because I’m so used to IOS

So far, I don’t hate JUNOS, which surprises me a little. Once you get the basics worked out it’s not so bad and JUNOS definitely has some features I wish the traditional IOS had. I don’t see myself becoming a total Juniper zombie yet, but I will definitely keep playing with it. I plan on making a post or two about the simple stuff like basic setup and OSPF configuration.


Colby Glass has been in IT since 2002. He is currently a Systems Engineer (presales) with a Cisco Gold partner and holds the CCNP R/S, CCNP DC, CCDP, CCIP, JNCIA-ER.

More Posts