Skip to main content

Route This Way: OSPF

 
Something I very recently learned is that routing protocols are learned on Control Planes.

Also, welcome to possibly the last post of 2019. I need a break too! 

There's plenty more coming in 2020. Meanwhile, visit and follow the new LinkedIn Company Page, if you please.





Many of these protocols will have very similar commands - network [network] wildcard [wildcard] - and OSPF has areas.



An area limits the scope of route information distribution. - mainly, less routes to propagate by summarizaton.

Look back at the image; The middle router, 4(2), is what we call a backbone area, that has interfaces in both area 1 (Router 4(1)) and area 2 (Router4).

Area 3 up there is a non-entity.

This is with the left side, area 1, having fully converged with the middle router.

Here are the outputs for show ip ospf for each router: Backbone;


All three areas are acknowledged, even our interfaceless area 3 up there.

Area 1 (left):

Interfaces in the area include its serial link and the Copper ST cable to the LAN.

Area 2 (right):

You may have noticed "Routing Process "ospf 1" and have been confused - processes and areas aren't the same thing. Processes are more for us to know what group of routers we may be working with.
Labels:

Comments

Post a Comment

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H
Post a Comment
Read more

What Do You Need? [List of Offered Services]

2023 Version is here, at this handy Notion Page.
Post a Comment
Read more

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl
Post a Comment
Read more