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

Mir Amin Uddiin @Yahoo nibir78 at yahoo.com
Thu Nov 21 23:06:41 BDT 2013

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?\       <OSPF>|          |
                                  |   ---(BR1)->  <eBGP Adv. to upstream A>\          |  /[SW]----(BR2)->  <eBGP Adv. to upstream B>          |  \
                                  |   ---(BR3)->  <eBGP Adv. to upstream C>\          ||

(DR)=Distribution Router, (BR)=Border Router, [SW]=Switch.

With thanks and best regards,

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

nog mailing list
nog at bdnog.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bdnog.org/pipermail/nog/attachments/20131121/8685d05a/attachment.html>

More information about the nog mailing list