Basic Connectivity Troubleshooting

 Ping Responses

Uses ICMP: Internet Control Message Protocol

Tests two way connectivity.  



Today's lab had the scenario of PC 1 not being able to reach P3.  We started by testing the connection from PC1 to P2 using the Command Prompt.  


Now that the problem is verified, we use traceroute to investigate the source. Control C stopped the process.


The hop stopped at 10.1.0.1, which is R3. So from here we check to see if R3 has a route to PC3, which requires us to jump back into R3's CLI.  

PC3's network, 10.1.2.10 is not on the routing table, so we should manually add it! Back to the the CLI.  


Now it's time to test it out the connectivity by pinging PC3 from PC1.  Success!  
































































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