Comments on: Weekly Open Ended Question #6 http://blog.alwaysthenetwork.com/open-ended-questions/weekly-open-ended-question-6/ Just another Cisco blog Mon, 23 Jan 2012 23:37:03 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Weekly Open Ended Question #7 | AlwaysTheNetwork http://blog.alwaysthenetwork.com/open-ended-questions/weekly-open-ended-question-6/comment-page-1/#comment-566 Weekly Open Ended Question #7 | AlwaysTheNetwork Tue, 09 Mar 2010 13:02:26 +0000 http://blog.alwaysthenetwork.com/?p=750#comment-566 [...] answer to the sixth question has been added to the [...] [...] answer to the sixth question has been added to the [...]

]]> By: Jared http://blog.alwaysthenetwork.com/open-ended-questions/weekly-open-ended-question-6/comment-page-1/#comment-542 Jared Thu, 04 Mar 2010 06:12:57 +0000 http://blog.alwaysthenetwork.com/?p=750#comment-542 SIA is caused when a route to a network goes down (with no feasible successor), causing the router to recursively query it's neighbours (setting a timer for 3 minutes) for a new route to the network, but no reply returns to the router. This can be caused by a large network, congestion, or loops in the network. It effects EIGRP (can also affect BGP I believe as well). To prevent SIA from happening route summarization and stub networks can be used. SIA is caused when a route to a network goes down (with no feasible successor), causing the router to recursively query it’s neighbours (setting a timer for 3 minutes) for a new route to the network, but no reply returns to the router. This can be caused by a large network, congestion, or loops in the network.

It effects EIGRP (can also affect BGP I believe as well).

To prevent SIA from happening route summarization and stub networks can be used.

]]> By: Daniel http://blog.alwaysthenetwork.com/open-ended-questions/weekly-open-ended-question-6/comment-page-1/#comment-541 Daniel Thu, 04 Mar 2010 05:57:25 +0000 http://blog.alwaysthenetwork.com/?p=750#comment-541 stubs will also contain it it won't use a diffrent route till it's heard back from all it's neighbors, so even if it does get a good one untill it hears back from every single neighbor it will just sit on it's hands (with it's thumbs oddly absent) waiting for ~3 min, at that point it will kill all neighbor relationships and reform them stubs will also contain it

it won’t use a diffrent route till it’s heard back from all it’s neighbors, so even if it does get a good one untill it hears back from every single neighbor it will just sit on it’s hands (with it’s thumbs oddly absent) waiting for ~3 min, at that point it will kill all neighbor relationships and reform them

]]> By: Stuart Howlette http://blog.alwaysthenetwork.com/open-ended-questions/weekly-open-ended-question-6/comment-page-1/#comment-540 Stuart Howlette Thu, 04 Mar 2010 04:31:29 +0000 http://blog.alwaysthenetwork.com/?p=750#comment-540 It's where query messages from an originating router are propogating around the network, and no reply is coming back (either due to loops or just a massive network). Usually set off by a network going down. It affects EIGRP. It can be prevented with summarization, as routers shall reply with indication that the route comes from a summarization elsewhere. It’s where query messages from an originating router are propogating around the network, and no reply is coming back (either due to loops or just a massive network). Usually set off by a network going down.

It affects EIGRP.

It can be prevented with summarization, as routers shall reply with indication that the route comes from a summarization elsewhere.

]]>