The New Global Language #JUNOS

Originally posted on the Juniper Champion Blog
Secondary post on the Proteus Networks’ Blog

Everyone has always said math is the global language. It’s true. No matter where you go in the world, 1+1=2 is expressed the same way and means the same thing.

After traveling to several continents over the past few years implementing Juniper datacenter, campus, enterprise, and service provider solutions, I’ve found another global language: JUNOS. The phrase “show chassis cluster status” means the same in Singapore, Tel Aviv, Mexico City, Bogota, and Sydney.(Yes, I know they speak English there.)

It’s really quite amazing. I can walk into an office in Israel, having never heard a word of Hebrew, and jump immediately into solving a complex MPLS VPN issue. I can offer class of service configuration advice to engineers from India and set up aggregated Ethernet interfaces for someone who speaks only Chinese.

And the best part is that, when I show them all the solution, they just get it. It’s simple and direct. If you want to configure the OSPF protocol, guess what? You configure it under [edit protocols ospf]. Someone who wants to change the MSS for TCP packets flowing through a secure SRX can configure it under [edit security flow tcp-mss].

Another great thing about a common JUNOS language is the community collaboration it supports and encourages. Partners, customers, and Juniper can communicate with one another around the world. The media are endless — from Twitter, Facebook, and LinkedIn to Juniper’s official community forums, the J-NSP mailing-list, and now The Champion Community.

User groups numbering in the thousands support new configuration, design, and architecture requests across the globe. And widespread adoption of JUNOS has spawned a community of bilingual networking gurus, who speak their native language and JUNOS.

While in other countries, I’ve joked with people that it’s easier to understand their native tongue than it is to understand “the other vendor’s” operating system. In every culture I’ve encountered, the language is direct and to the point. If you want an empanada in Colombia, you simply say, “Yo quiero uno empanada, por favor.” In that “other” OS, to configure OSPF, you have skip back and forth between interface and protocol configuration. And we all know every other vendor out there has copied this awful OS structure.

And don’t get me started on deciphering QoS or MPLS configurations. After 10 years with these things, it still takes me an hour to figure out which packets are classified as EF in that crazy backward OS. I feel like I could decipher Egyptian hieroglyphics faster — without the Rosetta Stone!

Juniper touts its next-generation, high-speed, simply connected network equipment, but in my opinion, it doesn’t put enough emphasis on its awesome OS, JUNOS. Even with all the next-generation features, a beginner can take one look at the hierarchy and generally understand what the device is supposed to do.

JUNOS is truly a global language. A couple billion more Juniper devices out there, and it would give math a run for its money as the global language! Talk to me in JUNOS in the comment space below.


Leave a Reply

There aren't any comments at the moment, be the first to start the discussion!