better off using BGP and tie

brijendrasaini · ‎08-10-2017

DEAR TEAM,

I HAVE TWO LOCATION IN WHICH ONE LOCATION IS HYD AND SENCOND LOCATION DLI.

BOTH LOCATION SAME TWO DIFFERENT ISP AIRCEL AND RELIENCE.WE CURRENTLY USING STATIC ROUTES FOR EACH ISP.

PROBLEM OCUURS WHEN AIRCEL DOWN THEN WE HAVE TO CHANGE MANUALLY IN BOTH ROUTERS.

I M HEARD IP SLA BUT HOW IT WORK I DONT KNOW.

PLEASE HELP ME OUT

Dennis Mink · ‎08-13-2017

If you have layer 2 between sites, really any dynamic routing protocol would be better than static routes. I suggest OSPF.

Please remember to rate useful posts, by clicking on the stars below.

brijendrasaini · ‎08-14-2017

hi dennis,

My setup is like that my link is connect with cloud then my end we give manual route to reach that destination with particular ISP.

Any suggestion for this.

Regards

Brijendra

Mark Malone · ‎08-15-2017

if you have to use statics use ip sla with tarckinbg setup

follow this easy guide it shows exactly how , you could get a bit more advanced too if the device supports it and use PBR with verify next hop reachability

http://www.firewall.cx/cisco-technical-knowledgebase/cisco-routers/813-cisco-router-ipsla-basic.html

brijendrasaini · ‎08-15-2017

hi mark,

Nice document but i have confusion that my Mpls link is on same device on two different port.Port 22 is for aircel and port 8 is for reliance.

In which router i have to configure IP Sla in both router or single router.

At data centre side or Clinent side.

Both router have static Route.

Regards

Brijendra

Mark Malone · ‎08-15-2017

better off using BGP and tie into your provider for this then you can have proper failover and use the metrics to chose which path it takes ,

if though you use policy based routing with ip sla to ping the far end of one link when that becomes unreachable have the pbr set the next hop as the other router circuit , you could do that on one 1 router once it has reachability to the other local router , that should cause an automatics failover and then repeat the same on the other router with the next-hop pointing back to the other circuit

your trying to achieve automatic failover here under the least favourable conditions by using statics , really should speak to your ISP and get a proper solution like BGP in place if this is critical or some other igp

paul driver · ‎08-14-2017

Hello

Faillover can be implement quite easily but it all depends on your topology setup as to what needs to be done.

1) do these sites connect to the two ISP's via one or two rtrs
2) can you post the configuration from one of you remote sites rtr(s)

res

Paul

Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

brijendrasaini · ‎08-15-2017

hi paual,

M giving a small idea to you about my network.

At data center we using 4507 deveice and in second location we use 3650

Scenrio is that when my ant link down then we have to chnage the route manually from both the end.

Then only we are able to DC other wise not able to connect.

One end Conf my sharing with you:-

Current configuration : 4378 bytes
!
version 12.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname indb
!
boot-start-marker
boot-end-marker
!
enable secret 5 $1$M8hw$MFtHp5V6ORk7UXjyaCjLH1
!
!
!
no aaa new-model
clock timezone UTC 5 30
system mtu routing 1500
ip routing
!
!
!
!
crypto pki trustpoint HTTPS_SS_CERT_KEYPAIR
enrollment selfsigned
serial-number
revocation-check none
rsakeypair HTTPS_SS_CERT_KEYPAIR
!
!
crypto pki certificate chain HTTPS_SS_CERT_KEYPAIR
certificate self-signed 01
30820249 308201B2 A0030201 02020101 300D0609 2A864886 F70D0101 04050030
37310E30 0C060355 04031305 696E6462 2E312530 0F060355 04051308 43464434
30343030 30120609 2A864886 F70D0109 02160569 6E64622E 301E170D 31343038
32363130 32323438 5A170D32 30303130 31303030 3030305A 3037310E 300C0603
55040313 05696E64 622E3125 300F0603 55040513 08434644 34303430 30301206
092A8648 86F70D01 09021605 696E6462 2E30819F 300D0609 2A864886 F70D0101
01050003 818D0030 81890281 8100A860 62B9DAF4 951926FE A57EDDBF D44C3ADA
FE0B4BE3 4B851CC8 F6773E5C A27248EB C4AC4804 577FB7EB 701A334B 65B0529F
B6370960 1B60E9D9 7636F016 1FF9C40B 7F56C60E C18E0587 A8D37E43 0AAF6D82
05B1E3E5 6F8F1CC4 CA5364DD 3D572733 5F5897DD 577368F0 FA04DC4C 80D3BB71
A3EB62F4 AEFE3395 0B299BA5 3FD10203 010001A3 65306330 0F060355 1D130101
FF040530 030101FF 30100603 551D1104 09300782 05696E64 622E301F 0603551D
23041830 16801469 BE77FB63 B43F093A 36155D85 0C3F1750 052F9E30 1D060355
1D0E0416 041469BE 77FB63B4 3F093A36 155D850C 3F175005 2F9E300D 06092A86
4886F70D 01010405 00038181 00A3E55D 8A9AEF50 A831104B C79F5EC1 D9089703
558B04BB AB68F50C A6437596 1BC498F5 68E3BA97 85DA4BE5 9E8DB612 D0DBD7AE
ABE4E62A 68EEE1A1 B72942AA 2BF6D062 61C6C882 4CA71BE2 41F8F951 13B0388C
BB2CBB06 0B5B0526 500492E1 BF2399A2 ACFEC7F7 29B1CD90 E82C8A3F 967A246A
21B5ED97 49D40AFA 3A6662F3 0F
quit
spanning-tree mode pvst
spanning-tree extend system-id
!
!
!
!
vlan internal allocation policy ascending
!
!
!
interface FastEthernet0
no ip address
no ip route-cache cef
no ip route-cache
no ip mroute-cache
!
interface GigabitEthernet0/1
switchport access vlan 148
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet0/2
switchport access vlan 148
switchport mode access
!
interface GigabitEthernet0/3
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet0/4
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet0/5
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet0/6
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet0/7
description ULINK TO 5TH FLOOR EH-INDORE-5THFLOOR-6
switchport trunk encapsulation dot1q
!
interface GigabitEthernet0/8
no switchport
ip address 172.20.148.154 255.255.255.252
!
interface GigabitEthernet0/9
!
interface GigabitEthernet0/10
!
interface GigabitEthernet0/11
!
interface GigabitEthernet0/12
!
interface GigabitEthernet0/13
!
interface GigabitEthernet0/14
!
interface GigabitEthernet0/15
!
interface GigabitEthernet0/16
!
interface GigabitEthernet0/17
!
interface GigabitEthernet0/18
!
interface GigabitEthernet0/19
!
interface GigabitEthernet0/20
!
interface GigabitEthernet0/21
!
interface GigabitEthernet0/22
description ***4Mbps MPLS Reliance****
no switchport
ip address 172.20.148.149 255.255.255.252
!
interface GigabitEthernet0/23
!
interface GigabitEthernet0/24
!
interface GigabitEthernet1/1
!
interface GigabitEthernet1/2
!
interface GigabitEthernet1/3
!
interface GigabitEthernet1/4
!
interface TenGigabitEthernet1/1
!
interface TenGigabitEthernet1/2
!
interface Vlan1
no ip address
!
interface Vlan148
ip address 10.40.148.1 255.255.255.0
!
interface Vlan999
ip address 10.40.151.254 255.255.255.240
!
ip classless
ip route 10.22.0.0 255.255.0.0 172.20.148.150
ip route 10.40.0.0 255.255.0.0 172.20.148.153
ip route 10.40.33.76 255.255.255.255 172.20.148.150
ip route 10.40.33.77 255.255.255.255 172.20.148.153
ip route 10.44.0.0 255.255.0.0 172.20.148.153
ip route 172.18.1.0 255.255.255.0 172.20.148.153
ip route 172.20.40.244 255.255.255.252 172.20.148.15
ip http server
ip http secure-server
!
!

We are using Mpls of elince and aircel.

Regards

Brijendra

FAILOVER CONCEPTS