IGP-Interior Gateway Protocol

The CCNA seems to focus primarily on OSPF, but IGP is covered as well.  

No auto-summary command is added because RIP will auto summarize routes, so subnet numbers could be changed.  Setting up the protocol requires the following commands:

After that, we checked to see that all networks are in the routing tables, using the show ip route.  Then we verify PC1 connects with 3 by using ping.  Next we make sure that all routers have a route to the external network, while not advertising internal routes to the service provider.  


After that we create a default static route from R4 to the Internet via SP, and then make sure other routers learn via RIP how to reach Internet.  Finish by checking that each router connects.  




Comments

Post a Comment

Popular posts from this blog

ARP--Address Resolution Protocol

 ARP is a program that helps connect an IP address to a physical address (MAC) over a Local Area Network.   An analogy/pneumonic device.   Apartment's  Real  Person The IP address on a local address is like an apartment's address in a city. It's helpful to get packages delivered, but it doesn't tell the carrier which apartment it is going. ARP helps the packet get from the apartment gate to the apartment door.  Apartment's Real Person.  
Read more

HSRP Configuration

Image
I began by configuring HSRP for the 10.10.10.0/24 using the IP addresses shown in the topology above. My first step was to check to see if G0/1 has been configured on R1 & R2.   It was not on either router, so I configured them and added a virtual IP address.    After that, I checked to see which was the active router (R2). Then, I checked to see that PC2 could ping the default gateway 10.10.10.1, followed by testing upstream connectivity.   I finished this portion of the lab by checking MAC addresses on the active router, the virtual interface, and PCs.  
Read more

OSPF--Load Balancing

Image
The lab configuration entails three network hops from R1 to reach R4, passing through R2, while there are only two hops from R5. As all the interfaces are Fast Ethernet, there would be an excessive load on R5 which could cause issues.  To solve this problem, I configured the links between R1 to R5 and then R5 to R4 at the cost of 1500.   Two hops at 1500 = total cost of 3000. Three hops at 1000 (Previously set at auto-config) = 3000.  So now the traffic should be redistributed evenly. It worked!  
Read more