There should be a message digest post, but as I and a few of my colleagues (@hellt_ru and @syncromechanica) decided after a short discussion – the best place to post links will be a dedicated Telegram channel instead of someone’s blog.
So, here we go. Join us at https://telegram.me/networklsa.
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.