Community discussions

MikroTik App
 
SmalleR
just joined
Topic Author
Posts: 20
Joined: Fri Feb 24, 2006 2:49 pm

BGP Synchronize

Mon Apr 28, 2008 4:14 pm

Ver.3.x of Mikrotik RouterOS has the checkbox "Synchronize ".

routing bgp network print
 #   NETWORK            SYNCHRONIZE
 0 A 195.66.xxx.0/23    no
I didn't found any information in the Manual. For what it is necessary?
 
hippo
just joined
Posts: 24
Joined: Wed Mar 26, 2008 2:12 pm

Re: BGP Synchronize

Mon Apr 28, 2008 4:58 pm

Short answer, stay away from it. It's evil :)

For a long answer on what syncronization is:
http://www.juniper.net/techpubs/softwar ... fig11.html

(yehe I know it's for juniper, but it applies for anything that talks bgp)
 
User avatar
ptaabodi
Trainer
Trainer
Posts: 10
Joined: Wed Dec 24, 2014 8:48 am
Location: Sharjah - UAE
Contact:

Re: BGP Synchronize

Mon May 08, 2017 2:21 am

HI:
If you Enable Synchronize in Networks BGP, by default network is advertised only if corresponding route is present in routing table else (if it`s Disabled) you can advertised every subnets even if corresponding route is NOT present in your routing table.
 
patrick7
Member
Member
Posts: 352
Joined: Sat Jul 20, 2013 2:40 pm

Re: BGP Synchronize

Mon May 08, 2017 6:37 am

It also "synchronizes" the route attribute.

Example
/ip route add dst-address=1.2.3.0/24 bgp-communities=123:456 type=blackhole
And you enable synchronize, the community 123:456 will be announced, too
 
User avatar
ZeroByte
Forum Guru
Forum Guru
Posts: 4047
Joined: Wed May 11, 2011 6:08 pm

Re: BGP Synchronize

Mon May 08, 2017 6:45 pm

Short answer, stay away from it. It's evil :)
This is completely wrong IMO/

TLDR: Standard BGP behavior is to announce networks based on their reachability in the active routing table. Best practice is to create static null routes to nail up your advertisements if you need to do so.

Network statements are commands that instruct the BGP process to originate prefixes, and synchronize means the router should only originate those prefixes which is has matching IP routes. In other words, don't hoist the flag and announce a prefix unless you actually know how to get there. This is the default behavior in other vendors' implementations. Best practice for a small network where you have only one border router, for instance, would be to create a static null route (type=blackhole in Mikrotik-speak) for your destination. This is a "nail-up" route. This may seem nit-picky in the beginning, but I've had several instances over the course of my career where I didn't think something was important best-practice-wise, and I just did whatever worked, and later had to face challenges based on my non-standard configurations.

Who is online

Users browsing this forum: ardziu, Azazul123, erlinden and 34 guests