ISP redundancy issue

We have two internet link in a Router.

When one link fails automatically second link also getting down.

We have deployed IPSLA to track the interface..

Wil share the config shortly

Regards
Ram
LVL 1
RAMU CHAsked:
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.

MiftaulCommented:
Do you use Routing protocol on the router or use static default routes pointing to ISP next-hop.

Which router are you using to connect to ISP.

If it is Cisco, Floating static route with IPSLA can work out here.
R1(config)# ip route 0.0.0.0 0.0.0.0 1.1.1.1 track 1
R1(config)# ip route 0.0.0.0 0.0.0.0 2.2.2.2 10
IPSLA commands varies with CISCO Router IOS version. We can give you exact config as we know about your router IOS.

In SonicWall, you need to go to Network - > FailOver and load balancing.  You can set Failover type here.
RAMU CHAuthor Commented:
Regret that not shared needful details:

Here are the details :

Device is Cisco

Model : 2800 series

version 15.0

Scenario :


         ISP1                    ISP2
                               
                \                  /
              cisco 2800 router
                       |
                    LAN




On Cisco 2800 series Router

Primary ISP details  :

Interface :  GigabitEthernet0/0
Ip address :  10.224.47.33

Secondary ISP details :

Interface :  GigabitEthernet0/0
Ip address :  10.224.47.33


About Routes are in the attached config fie.


My requirement is simple :

If primary ip fails , second isp should take care and onc eprimary comes back then traffic shouls pass over Primary ISP


Attached config file and SH version output

Regards
Ram
changed-Router-cofig.log
MiftaulCommented:
You have a typo, your both ISP address seems to be same.
I believe the second link is at FastEthernet0/0/1 with next-hop 10.205.120.2  

You already have two IP SLA object configured
ip sla 111
 icmp-echo 10.224.47.37 source-ip 10.224.47.33
ip sla schedule 111 life forever start-time now

Open in new window

We could make it little smarter.
R1(config)# ip sla 111
R1(config)# icmp-echo 8.8.8.8 source-interface GigabitEthernet0/0
R1(config)# timeout 1000
R1(config)# threshold 2
R1(config)# frequency 3
R1(config)# ip sla schedule 111 life forever start-time now

Open in new window

It is always good to set the icmp-echo to some remote IP, not the ISP next-hop IP. Because it might be that the ISP link is up as we have connectivity but ISP might not have their upstream connectivity still showing our lin kas up.

The default route should look something link this.
R1(config)# #Static Default route to Primary ISP next hop 10.224.47.34. Due to track
R1(config)# ip route 0.0.0.0 0.0.0.0 10.224.47.34 Track 111
R1(config)# 
R1(config)# #Static Default Route to second ISP next-hop 10.205.120.2, we increased the metric to 10 to make it floating
R1(config)# ip route 0.0.0.0 0.0.0.0 10.205.120.2 10

Open in new window

You need to look into the many static routes that are there, some don't seem necessary

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
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

RAMU CHAuthor Commented:
Thanks fot the solution

 but it makes ISP as active /standby

 but in my scenario ,

ISP links  should be Active/Active

Regards
Ramu
MiftaulCommented:
Proper load sharing doesnt smartly work using static route, it works some sort using ip cef. If our intention is to keep both the links active, we could keep the above default routes. And use Policy Based Routing to route some interesting traffic over the second link.
Bgp could do that but thats not feasible here.
RAMU CHAuthor Commented:
Tks
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.