EIGRP router failure

In the scenario where I have EIGRP Successor Router on the Data Center, the Feasible Successor Router on the Disaster Site and all other EIGRP Routers on Remote Sites, now if a Router in remote site crashes for instance looses power, will that impact other routers ?

Thank you
jskfanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JustInCaseCommented:
Not sure that I understand topology (drawing would be nice), but typically, if you have Feasible Successor route in EIGRP topology database impact should be under 1 second. As soon as connection to Successor is lost route to Feasible Successor will be placed in routing table as new Successor route. This is the fastest convergence time that you can get with almost no impact on network at all (especially with bfd configured).
0
jskfanAuthor Commented:
In This case R1 is at the Data Center , R3 is at the Disaster Recovery Site, the rest of the routers at the remote site
First , I want to know if best practice is to make R1 as Successor and R3 Feasible Successor.
Then if any of Remote Sites router crashes, whether it will impact the Data Center

EIGRP
0
jskfanAuthor Commented:
First , I want to know if best practice is to make R1 as Successor and R3 Feasible Successor. and how to do it ?

Then if any of Remote Sites router crashes, whether it will impact the Data Center. I mean most our servers  are in the Data Center
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

JustInCaseCommented:
if best practice is to make R1 as Successor and R3 Feasible Successor
Sure it is. You can manipulate routes by changing bandwidth and delay to adjust route costs, or you can use offset-lists to make routes more or less attractive.
0
jskfanAuthor Commented:
What about this ?

Then if any of Remote Sites router crashes, whether it will impact the Data Center. I mean most our servers  are in the Data Center
0
JustInCaseCommented:
If you have Feasible Successor for every significant route on your routers, you can route around anything under 1 second. if I remember correctly that fastest reroute time was around 200 ms (including dead neighbor detection with bfd). So, if configured properly there should be no significant impact.
0
jskfanAuthor Commented:
I thought if he remote site fails completely..it will not impact other sites especially the Data Center ?
0
JustInCaseCommented:
If you can change routing around currently used route fast enough (and there is no NAT) traffic path is typically not important at all. And Feasible Successor should give you "fast enough" switch to other path to location. The thing is - feasible successor is already in topology, but path is just not in use (by default). So router will just switch to that route - that is the reason for minimal impact in this case.
0
jskfanAuthor Commented:
All our servers are in the DataCenter (behind Router 1), I do not see in which case the  Failure on remote sites will impact the Data Center.
0
JustInCaseCommented:
In your topology that you provided there should be no problem, but in some cases you can have problem with EIGRP Stuck in active. That is situation when router loses path to some network and looses connection to that network. If there is many routers and answer from neighbors is not back fast enough (either alternative path provided to network or network is lost), in that case all neighbor relationships gets broken and are reestablished again. However - that problem is not solved by having feasible successor ready. :)
Looks like I went in wrong direction - fastest way to reroute by usage of feasible successor.
0
jskfanAuthor Commented:
I believe an Outage on the remote site, will still cause EIGRP recalculation on all routers if they are in the same AS
Probably that time of recalculation can impact the servers.
I would like to know if there is a  way to isolate the remote sites failures from impacting the Datacenter...
0
JustInCaseCommented:
I believe an Outage on the remote site, will still cause EIGRP recalculation on all routers if they are in the same AS
Most likely it will not happen in so small topology. Also, we are talking about EIGRP here, not OSPF, calculations are not so intensive in the case of EIGRP.
Also, there are typically two ways to avoid SIA (to reduce waiting time on answer to query message):
- configure summary routes
- configure EIGRP stub routing
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jskfanAuthor Commented:
Thanks Jovic
0
JustInCaseCommented:
You're welcome.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Routers

From novice to tech pro — start learning today.