[bdNOG] Redistributed static routes of different ADs through EIGRP

Mon Dec 23 17:26:55 BDT 2013

Dear Ronjue Vai,

WAN A is runing EIGRP AS 100 and WAN B is running EIGRP AS 200. WAN A and
WAN B has a common intersection with exchange static route.

Existing:
WAN Cloud A--EIGRP AS 100---Router 1A<-----------Static
Route-------------->Router1B----EIGRP AS 200----WAN Cloud B

New addition:
WAN Cloud A--EIGRP AS 100---Router 2A<-----------Static
Route-------------->Router2B----EIGRP AS 200----WAN Cloud B

I will go for metric based solution which will be applied at Router2A and
Router2B. So that Router2A and Router2B will be secondary path.

Regards,
Mirza Rakib

On Mon, Dec 23, 2013 at 3:57 PM, Ronjue Ahmed <ronjue_kuet at yahoo.com> wrote:

> Dear Mr. Rakib,
> So far, from my understanding, you have one router connected to two
> different Service provider and you are using static route to the service
> provider. and EIGRP is your own IGP. you want advertise the static route
> into eigrp so that the other routers of your domain can get this route as
> Active/Standby concept.
>
> If the situation is like this, then you please use a route map to
> redistribute your static route. And inside route map, mention the metric
> value lower for the active route and use large metric value for standby
> route.
>
> for more discussion, you can call me.
>
> Thanks.
> F.M. Ronjue Ahmed
> 01712558377
>
>
>   On Monday, December 23, 2013 3:32 PM, Mirza Rakib <mmrakib at gmail.com>
> wrote:
>  Hi Ronjue Vai,
>
> Actually i want to make a redundancy(active/standby) between to WAN. Say
> WAN A is running EIGRP AS 100 and WAN B is running AS 200. We do not want
> to integrate the WAN A and WAN B using any dynamic protocol. Right now, we
> have one interface between two WAN with static route. We want to implement
> another interface also with static route. Note that we do not want
> active/active. We need active/standby solution without any dynamic routing.
>
>
> Regards,
> Mirza Rakib
>
>
> On Mon, Dec 23, 2013 at 3:02 PM, Ronjue Ahmed <ronjue_kuet at yahoo.com>wrote:
>
> Hello dear concern
> Please be informed that, EIGRP has the ability to differentiate routes
> coming from different sources (other routing protocol like ospf, rip, bgp
> and even static).
> EIGRP has two type of routes,
>  1. internal route (AD value 90),
>  2. External route (AD value 170).
> So, when ever we try to redistribute any route into eigrp, eigrp consider
> it as external route and assign AD vale 170 and advertise it to other eigrp
> neighbors. As long as you will try to redistribute static route through
> EIGRP, you will find the AD value 170 for those routes.
>
> Advertise routes through same protocol having different AD values does not
> make any sense. Basically one routing protocol one AD value.
> For choosing best route that comes from same protocol, the key parameter
> is metric.
>
> Thanks.
> F.M. Ronjue Ahmed
>
>
>
>    On Monday, December 23, 2013 2:24 PM, Mirza Rakib <mmrakib at gmail.com>
> wrote:
>   Hi Fellow,
> I am trying to redistribute static route with different administrative
> distance(AD). For example at Route1 I have configure a static route with
> default  AD and in another Router2 configured a static route with AD 20.
> We want to redistribute the static routes through EIGRP, so that a remote
> router learn the two routes with different Ads. However, we found the
> default EIGRP static redistributed AD 170.
>
> *Router1:*
>
> ip route static 10.0.0.0 255.0.0.0 172.16.250.254
>
> *Router2:*
>
> ip route static 10.0.0.0 255.0.0.0 172.16.250.250 20
>
> *At access router I found: *
>
> D EX 10.0.0.0/8 [170/3072] via 172.31.2.2, 00:59:48, GigabitEthernet2/0
>                           [170/3072] via 172.31.1.2, 00:59:48,
> GigabitEthernet1/0
>
>
> Please suggest, how can we obtained the redistributed static routes with
> different ADs.
>
>
> Mirza Rakib
>
>
> _______________________________________________
> nog mailing list
> nog at bdnog.org
> http://mailman.bdnog.org/mailman/listinfo/nog
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bdnog.org/pipermail/nog/attachments/20131223/2790bf09/attachment-0001.html>