Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

Distance VS LinkeState Routing protocols

I don't have much experience with configuring linkstate en distance protocols in real life, just in labs I do it. I am at CCNA2 now. But, what is the main difficulty of linkstate protocols? The configuration is almost the same of distance? right? Or is it the troubleshooting?




Re: Distance VS LinkeState Routing protocols


the the main thing in having a link state protocols is that they are more complex to work with.And They eat up more CPU and memory of your router compare to ditance vector.

The configuration is also some what different than distance vector protocols.

In distance vector protocol each router depends on its neighbors for information, which the neighbours might have learned frm their neighbours, and so on, distance vector routing is osmetimes reffered to as "routing by rumor". Also the distance vector protocols can have routing loops and slow to converge.

In link state protocols each router originates info about itself,its directly connected links(state of those links) & directly connected neighbours.This info is passed around frm router to router,each router making a copy of it, but never changing it.

The link state protocols are loop free and fast to converge.

This is a very short explanation.Hope this helps.



New Member

Re: Distance VS LinkeState Routing protocols

Link-State such as OSPF is almost straight forward for small networks (single area) and you may configure it without the need of giving it alot of design effort. But as you know, OSPF is meant to run over large networks with tens or even hundreds of routers and links. The main issue with link state is that it is router resources intensive in means of memory and CPU because link state routers need to have a full view of all links within the same area. Here comes the need of dividing your networks into multiple OSPF areas and put in mind all related design considerations such defining area borders, neighborship, NBMA, route summaries... etc. This is only a brief overview as link state is a big topic.

Hall of Fame Super Silver

Re: Distance VS LinkeState Routing protocols


As you point out from a configuration standpoint there is much similarity between Link State and Distance Vector protocols. Especially in the fact that both type of protocols use network statements to identify the interfaces to include within the protocol they are similar. The differences appear in the way that the protocols operate and the ways in which you would approach troubleshooting for the various protocols.



Re: Distance VS LinkeState Routing protocols

Configurations: Given a scenario & to configure it for distance & linkstate. There's not much of difference. But yes there are some features supported by Linkstate & are not supported by dsitance vector. Some of these are wild card, stub configs & sumarisation(later on added to ripv2).

Operation: In this aspect, there are many differences:

- Link state are scalable to large boundaries & dont have a hop count limit like distance.

-Triggered updates of link state compared to periodic updates of distance is another advantage.

-hierarchial architecture of link state is another benefit which is not avail with distance protocols.

-Link state are CPU & memory intensive because of the trigered updates. However for stable networks its not an issue.

hope that clarifies.

pls rate all helpful posts.

CreatePlease to create content