Back to GIT! Just to have a quick recap of the things we’ve seen in the first part of our GIT deep dive, I am going to create a brand new repo, some files and commit everything:
What is GIT?
GIT is a distributed VCS (Version Control System). In a few words, this means that is a system that allows you to keep track of changes made to a file. The files are stored on a server and each contributor has a local copy of them. Most of the times it’s used when dealing with software development environments, because there is usually a team that works on the same set of files. If it weren’t for GIT (or any other similar tool) everyone would probably overwrite changes that everyone else did to the code and madness would break loose. Still, if you’re not a code developer, you can use GIT to help you keep track of your own files, changes, etc. and keep your head clean!
IS-IS Subnetwork Independent Operation
Continuing our journey through the land of IS-IS and hoping to reach the point where we get to understand how it actually works and the differences between it and OSPF, let’s focus today on how IS-IS is configured and why it uses both Levels and Areas.
After getting familiar with the FA, when it’s set and when not, we’re ready to cook the recipe for chaos: NSSAs, Default Route injection and Forwarding Address.
Everything old is new again. That applies to most industries, trends and businesses, so why wouldn’t it apply to how we use resources and where they are placed.
The theme question is actually quite a good one, because it may seem like the fight has already been won by IS-IS in the Service Provider segment, and by OSPF on the enterprise market. So why ask it then? Well, because I got the following answer one too many times: “IS-IS is awesome, OSPF not so much. I have no idea how IS-IS works but it’s great. OSPF is so complicated and offers so little flexibility…”.