Link-State Protocols

Weeks ago and maybe months :) , I talked about distance vector protocols and with that you probably got the feeling that when using a distance vector protocol it does not give a full network graphical representation of the entire network. Only the directly connected routes can’t remember? Check out this post Distance Vector Routing. Link state protocols are faster to converge network changes compared to distance vector however when compared to distance vector setup they can be harder to set up, maintain, and troubleshoot when problems arise. Continue reading

About these ads

The Codes of ICMP

In today’s post I wanted to talk about the widely used Ping command. Which is one of the best methods (I think) to begin network troubleshooting. When part of the network goes down it is sometimes hard to figure out why? When you issue the ping command or the extended ping command in a Cisco router several ICMP codes can come up on the router. Let’s discuss them! Continue reading

The Beginnings of Layer Two Redundancy

In a perfect world we would never need redundancy on a network infrastructure, but as you know as well as I know we don’t live in a perfect world. Hardware will eventually fail, bottlenecks will appear, and the speed of our network will become slower when we max the bandwidth on links. So having redundancy in routers, connections, and having a hierarchy network is one of best choices to make when improving the efficiently of the network. But in the OSI model there is one layer that can’t have redundancy at least logically and that is Layer two of the OSI model. Continue reading