I can establish a BGP Peering Session to one of our ISP’s but as soon as the routes are received it kicks me out of the winbox console and disconnects the BGP Peering Sessions. We have only been able to receive the default route from the ISP and ONLY the default route, if they try to send any more it fails.
I am currently running 2.9.41 but plan to upgrade tonight to 2.9.46, has any body any ideas?
The ISP says it looks like its a memory problem but i have 512MB ram in the box and when looking at the resources it never dips below 460MB free
Any ideas on where to go next would be great cause i am stumped!
do the upgrade to .46 first. if that doesnt fix it, try this … enter a routing filter that marks all routes received as disabled. You can then see them in your routing table and review them to see if there is a route causing things to break.
256MB would be enough. So it is another problem.
the only idea I have is that the routing information you receive or send influences
the routing to your bgp-peer. So getting the bgp-routes kills your routing and your
bgp-session. When session is dead bgp-routed are deleted and everything starts
from the beginning.
So double-check the routing between your/your upstreams Router.
Make a filter to just receive a bunch of routes and see if this works.
right this problem has sorted itself and now another exists (typical!)
anyway i have 2 peers and both are sending the full routing table to me and i receive now ok.
Problem is that only one is receiving my prefix, although both are configured identical.
the other is receiving the entire routing table. even though i have the prefix lists setup!
my other small issue is since the upgrade to .46 i cant find the prefix list with in the telnet or winbox session.
So i cant check that they are ok anymore!
can anybody shed some more light on this for me ..