[bdNOG] Automatic update of Next Hops in Routing Policies for Internet bound traffic in interior routers.
Palash Kanti Barua
palash at bol-online.com
Thu Nov 21 19:46:05 BDT 2013
Since you are already doing Policy Based Routing (PBR) in your all DRs so
you have to change next hop-IP manually. There is no such device which can
automatically change the next-hop IP for your specific prefix. Better you
put a CORE router in between your DRs and BRs router, and do PBR from only
your CORE router. That would be the ideal solution for your scenario.
Palash Kanti Barua
From: nog-bounces at bdnog.org [mailto:nog-bounces at bdnog.org] On Behalf Of
Sent: Thursday, November 21, 2013 6:48 PM
To: nog at bdnog.org
Subject: [bdNOG] Automatic update of Next Hops in Routing Policies for
Internet bound traffic in interior routers.
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
| ---(BR1)-> <eBGP Adv. 192.168.0.0/24
to upstream A>
192.168.0.64/26-------\ | /
18.104.22.168/26--------(DR2)-----[SW]----(BR2)-> <eBGP Adv. 22.214.171.124/24
to upstream B>
126.96.36.199/26-------/ | \
| ---(BR3)-> <eBGP Adv. 188.8.131.52/24
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
More information about the nog