Welcome back, friends!
I’m pleased to announce the newest and the last version of Juniper Service Provider Lab that covers even more JNCIP-SP topics.
Moreover, all devices now exist in a single vMX device, so an amount of RAM your station needs to start exploration is about 2,5 GB (2GB for vMX + 512MB for UNL Linux host).
The comprehensive bunch of information to help with a journey presented below.
Speaking of centralized management of network devices would be a great idea to demonstrate some possibilities to use NETCONF and open-source software.
Under the hood, we are going to use Ansible and “Juniper.junos” library to manage Juniper vMX 14.1 and SRX 12.1 from GNU/Linux Debian CLI.
This note is the first one in a small bunch of articles about SDN-sided tendencies already affecting networking or will affect soon.
A lot of network engineers are still thinking that practical SDN as far away from networking as far IS-IS from to be called “simple”. But in reality, networking SDN is almost knocking on the door and looks like there is no way to evade tentacles.
In the previous part, we had configured all service provider devices and got our first part of control plane information, populated by BGP.
This time, we are going to configure the rest: provider tunnel, PIM, start on a p-multicast source and request some groups by customers.
How about a short break for a humor?
Dive under the cut to find some hilarious moments from the long story between Juniper and Cisco.
Few days ago, at March 14 to be precise, my Juniper Service Provider path had received another one pleasant milestone – JNCIP-SP exam has been passed!
As always, my thoughts and a short overview of the exam are presented.
As deeper I dived in Junos OS CLI as better I understood that a full list of available commands would be one the best way to be familiar with features.
Fortunately, Junos OS CLI divided to a huge amount of stanzas, so it’s not a big deal to get that list as a continuous hierarchy of available commands.
Furthermore, that job is done already by Juniper documentation team!
Go inside to get some of them and an information how to find more.