Mikrotik BGP Problem

I configured a new hardware with RouterOS 2.9.41 and the same configuration that the other MK that works fine.
With the original router all works great, it have RouterOS 2.9.30.
When connect the new hardware with the same configuration, 4 of 6 bgp peer doesn´t established the connection:

Example:

name="PEER1" instance=default remote-address=200.XX.17.1 remote-as=11XXX tcp-md5-key="" nexthop-choice=default multihop=no route-reflect=no hold-time=3m ttl=1 in-filter="" out-filter=filter-peer1-out remote-id=0.0.0.0 remote-hold-time=0s used-hold-time=0s used-keepalive-time=0s state=active

07:22:57 route,bgp,info Failed to open TCP connection: No route to host
07:22:57 route,bgp,info RemoteAddr=200.xx.17.1
07:22:57 route,bgp,info RemotePort=179
07:23:17 route,bgp,debug,timer ConnectRetryTimer expired
07:23:17 route,bgp,debug,timer RemoteAddr=200.xx.17.1
07:23:17 route,bgp,debug Connecting
07:23:17 route,bgp,debug RemoteAddr=200.xx.17.1
07:23:17 route,bgp,debug RemotePort=179
07:23:17 route,bgp,debug,state Entering Connect state
07:23:17 route,bgp,debug,state RemoteAddr=200.xx.17.1
07:23:17 route,bgp,info Failed to open TCP connection: No route to host
07:23:17 route,bgp,info RemoteAddr=200.xx.17.1
07:23:17 route,bgp,info RemotePort=179
07:23:17 route,bgp,debug,state Entering Active state
07:23:17 route,bgp,debug,state RemoteAddr=200.xx.17.1
07:23:19 route,bgp,debug,timer KeepaliveTimer expired

Thanks .-
IntermediaspAsked:
Who is Participating?
 
gheistCommented:
Yes - that's it. Link down means dropping route to peer, with all consequences.
First check cabling. And ethernet switches.
If you run gigabit, then cat5 cables create quite a mess...
0
 
gheistCommented:
First of all remove all obfuscated addresses from your output.
And post your routing table without BGP started. (netstat -nr or route -n show)
0
 
IntermediaspAuthor Commented:
Gheist, I can´t understand you very well.
Can you explained what you mean with obfuscated addresses ?, remember that I use Mikrotik RouterOS

Thanks
0
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

 
gheistCommented:
You gave syntactically invalid IP adresses. No-one except you or your peers can diagnose problem at your site.

%host 200.xx.17.1
Host 200.xx.17.1 not found: 3(NXDOMAIN)
%traceroute 200.xx.17.1
traceroute: unknown host 200.xx.17.1

First of all - can you ping at least one BGP peer from your new router?
0
 
gheistCommented:
/lib/modules/2.4.31 in initrd.rgz filesystem reminds of Linux kernel v2.4.31
that looks like custom shell running above that. and it asks me for key, so I delete it.
We are solving BGP connectivity problem, not RouterOS config problem.
Quick answer on OS/kay problem is - go install OpenBSD and Zebra, and it will work.
0
 
IntermediaspAuthor Commented:
No gheist, I can´t ping the peer ..., I´m thinking about layer 1/2 problem, can it be ?
0
 
gheistCommented:
Yes - there is lower layer problem.
0
 
IntermediaspAuthor Commented:
Yes, when monitoring link status I saw "link-ok" and them "no-link", I supposed that the problem is the 3COM cards, could it be ??
0
 
IntermediaspAuthor Commented:
This was a problem ...., thanks a lot !
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.