[bdNOG] Automatic update of Next Hops in Routing Policies for Internet bound traffic in interior routers.

Aniruddha Barua aniruddha.barua at colbd.com
Tue Dec 3 15:01:37 BDT 2013


I solved it using a little trick which is a combination of PBR/Static Routing and Dynamic Routing
(OSPF). To make redundancy work directly from DRs, I'll have to try VRF-Lite.

Regards,

ANIRUDDHA BARUA 
 Email: aniruddha.barua at colbd.com, cto at colbd.com

---------- Original Message ----------- 
 From: Fakrul Alam <fakrul at dhakacom.com> 
 To: "Mir Amin Uddiin @Yahoo" <nibir78 at yahoo.com> 
 Cc: Aniruddha Barua <aniruddha.barua at colbd.com>, "nog at bdnog.org" <nog at bdnog.org> 
 Sent: Fri, 22 Nov 2013 00:41:41 +0600 
 Subject: Re: [bdNOG] Automatic update of Next Hops in Routing Policies for      Internet bound
traffic in interior routers.

> Dear Nibir Bhai 
> 
> The issue is choosing upstream based on source address/prefix. Changing localpref will not help
caz you can only use one upstream at a time; you can utilize all.  
> 
> For source based TE, PBR is the only choice.  
> 
> Thanks 
> Fakrul 
> 
> Sent from my iPhone 
> 
> On Nov 21, 2013, at 11:06 PM, "Mir Amin Uddiin @Yahoo" <nibir78 at yahoo.com> wrote: 
> 
>  
> 
> Dear Aniruddha Da, 
> 
> Is it possible to do iBGP full mesh? If so, PBR can be avoided and changing local-preference of
default-routes (received from BRs) at DRs, upload can be manged without impacting CPU. 
> 
> Please correct me if I missed to understand the problem statement correctly. 
> 
> ~ nibir 
> 
>  
>  
> 
>  On Thursday, November 21, 2013 6:48 PM, Aniruddha Barua <aniruddha.barua at colbd.com> wrote: 
>  
> Hello everyone, 
> 
> Please view this email in plain text with mono-spaced fonts because it has a text based diagram. 
> Please take a look at it. Generally, Policy Routing is done in Distribution Routers (DR) to send 
> Internet bound traffic from a specific prefix to appropriate Border Router (BR) so that upward and 
> downward traffic uses the same upstream SP. When prefixes are moved from one BR to another BR due to 
> business requirements, Network Admin needs to manually update Next Hop information in Policy Routing 
> configurations in all DRs. If the number of prefixes and/or the number of DRs increases, this 
> becomes cumbersome. Is there any way (vendor specific and/or vendor independent) to automate these 
> updates? 
> 
> 192.168.0.0/26--------\      <OSPF> 
> 192.198.1.64/26-------(DR1)------| 
> 192.200.2.128/25------/          | 
>                                   |  ---(BR1)->  <eBGP Adv. 192.168.0.0/24 to upstream A> 
> 192.168.0.64/26-------\          |  / 
> 192.198.1.0/26--------(DR2)-----[SW]----(BR2)->  <eBGP Adv. 192.200.2.0/24 to upstream B> 
> 192.200.2.64/26-------/          |  \ 
>                                   |  ---(BR3)->  <eBGP Adv. 192.198.1.0/24 to upstream C> 
> 192.168.0.128/25------\          | 
> 192.198.1.128/25------(DR3)------| 
> 192.200.2.0/26--------/ 
> 
> (DR)=Distribution Router, (BR)=Border Router, [SW]=Switch. 
> 
> With thanks and best regards, 
> 
> ANIRUDDHA BARUA 
> Email: aniruddha.barua at colbd.com, cto at colbd.com 
> 
> _______________________________________________ 
> nog mailing list 
> nog at bdnog.org 
> http://mailman.bdnog.org/mailman/listinfo/nog 
> 
>  
> _______________________________________________ 
> nog mailing list 
> nog at bdnog.org 
> http://mailman.bdnog.org/mailman/listinfo/nog 
>  
------- End of Original Message -------



More information about the nog mailing list