Community discussions

MikroTik App
 
believewireless
Member Candidate
Member Candidate
Topic Author
Posts: 231
Joined: Wed Jul 06, 2005 6:30 pm

Routing Test BGP - How do you push full routes?

Sun Sep 17, 2006 7:54 am

I have four routers running BGP:

1. Cisco -> 2. MT 2.9.30 -> 3. MT 2.9.30 -> 4. MT 2.9.29

Router 2 gets full routes from router 1. Router 3 gets full routes from router 4. However, router 2 and router 3 do not get full routes from each other.

How can I force the sending of full routes to these peers?
 
Beccara
Long time Member
Long time Member
Posts: 606
Joined: Fri Apr 08, 2005 3:13 am

Sun Sep 17, 2006 7:57 am

Need more details?

Can you print bgp instance and peer config for all routers. Are you using iBgp or eBgp?
 
believewireless
Member Candidate
Member Candidate
Topic Author
Posts: 231
Joined: Wed Jul 06, 2005 6:30 pm

Mon Sep 18, 2006 9:21 pm

Here is the config for router #3. I'm not able to get 66.XX.XX.0/24 to be advertised either.

/ routing bgp instance
set default name="default" as=22361 router-id=63.XX.XX.1 \
redistribute-static=yes redistribute-connected=yes redistribute-rip=no \
redistribute-ospf=no redistribute-other-bgp=yes out-filter="" \
client-to-client-reflection=yes comment="" disabled=no


/ routing bgp peer
add name="Cisco" instance=default remote-address=65.XX.XX.1 remote-as=22361 \
nexthop-choice=default multihop=yes route-reflect=no \
hold-time=3m ttl=60 in-filter=mci_out out-filter=bgp_advertise comment="" \
disabled=no
add name="Router #4" instance=default remote-address=63.XX.XX.221 \
remote-as=22361 nexthop-choice=default multihop=no \
route-reflect=no hold-time=3m ttl=60 in-filter=level3_out out-filter="" \
comment="" disabled=no
add name="Router #2" instance=default remote-address=65.XX.89 \
remote-as=22361 nexthop-choice=default multihop=no \
route-reflect=no hold-time=3m ttl=60 in-filter=mci_out out-filter="" \
comment="" disabled=no


/ routing filter

add chain=bgp_advertise prefix=63.XX.XX.0/24 prefix-length=24 invert-match=no \
action=accept comment="" disabled=no
add chain=bgp_advertise invert-match=no action=discard comment="" disabled=no
add chain=level3_out prefix=65.XX.XX.0/23 prefix-length=23 invert-match=no \
action=reject comment="" disabled=no
add chain=level3_out protocol=bgp invert-match=no action=accept \
set-nexthop=63.XX.XX.221 set-bgp-local-pref=50 comment="" disabled=no
add chain=mci_out prefix=65.XX.XX.0/23 prefix-length=23 invert-match=no \
action=reject comment="" disabled=no
add chain=mci_out protocol=bgp invert-match=no action=accept \
set-nexthop=65.XX.XX.89 comment="" disabled=no
add chain=level3_advertise prefix=65.XX.XX.0/24 prefix-length=24 protocol=bgp \
invert-match=no action=accept comment="" disabled=no
add chain=level3_advertise prefix=63.XX.XX.0/24 prefix-length=24 protocol=bgp \
invert-match=no action=accept comment="" disabled=no
add chain=level3_advertise invert-match=no action=discard comment="" \
disabled=no

/ routing bgp network
add network=63.88.42.0/24 disabled=no
 
karyal
Member Candidate
Member Candidate
Posts: 168
Joined: Sat Nov 12, 2005 12:09 pm

Re: Routing Test BGP - How do you push full routes?

Fri Sep 22, 2006 10:14 pm

I have four routers running BGP:

1. Cisco -> 2. MT 2.9.30 -> 3. MT 2.9.30 -> 4. MT 2.9.29

Router 2 gets full routes from router 1. Router 3 gets full routes from router 4. However, router 2 and router 3 do not get full routes from each other.

How can I force the sending of full routes to these peers?
Did you check why the routes are not propagated (probably discarded?)
Enable bgp logging.
Did you set "force self" option on "neighbour" under peers config?
Bye,
Ricky
 
believewireless
Member Candidate
Member Candidate
Topic Author
Posts: 231
Joined: Wed Jul 06, 2005 6:30 pm

Sat Sep 23, 2006 1:29 am

What does the "force self" option do?
 
karyal
Member Candidate
Member Candidate
Posts: 168
Joined: Sat Nov 12, 2005 12:09 pm

Sat Sep 23, 2006 10:41 am

What does the "force self" option do?
Forces ip address of the announcing router as nexthop for the announced routes to the corresponding peer.
The peer will discard the received routes if routes nexthop is thought as unreacheable.
forcing nexthop to the point to point ip of the peer makes the nexthop reacheable and the routes are not discarded anymore.
the option is available from 2.9.28 only though (and don't use 2.9.28 as it has memory leak on the routing test packages).
Also, you should use routing-test package instead of routing package.
Bye,
Ricky

Who is online

Users browsing this forum: HakanE, Jotne, kevigizmo, monikabpaso, shahjaufar and 103 guests