Community discussions

MikroTik App
 
tronity2k
just joined
Topic Author
Posts: 17
Joined: Thu Jul 12, 2007 8:22 pm

BGP problem capabilities negotation

Wed Feb 10, 2010 12:33 pm

Hi,

I have a problem with bgp peering negociation, some mikrotik anunced bgp capabilities, produces in cisco router that reiniciate session.

Can I moddify Capability Negotiation of mikrotik peer?
Anyone can help me?
This is a great disadvantage when peering with mikrotik to a IXP (Internet Exchange Point).

routeros 4.3 peer configuration:
name="peer-xxxxx-looking-glass" instance=default
remote-address=xx.cisco.ip.xx remote-as=xxciscoasxx
tcp-md5-key="" nexthop-choice=force-self multihop=no
route-reflect=no hold-time=45s
keepalive-time=15s ttl=255 in-filter=xxxx-in out-filter=xxx-out
address-families=ip default-originate=never remove-private-as=no as-override=no passive=no

Mk log:
04:13:34 route,bgp,info Connection opened by remote host
04:13:34 route,bgp,info RemoteAddress=xx.cisco.ip.xx
04:13:34 route,bgp,error Received notification
04:13:34 route,bgp,error OPEN error: unsupported capability
04:13:45 route,bgp,info TCP connection established
04:13:45 route,bgp,info RemoteAddress=xx.cisco.ip.xx
04:13:45 route,bgp,error Received notification
04:13:45 route,bgp,error OPEN error: unsupported capability
04:14:27 route,bgp,info Connection opened by remote host
04:14:27 route,bgp,info RemoteAddress=xx.cisco.ip.xx
04:14:27 route,bgp,error Received notification
04:14:27 route,bgp,error OPEN error: unsupported capability

Cisco log:
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX open active, local address XX.CISCO.IP.XX
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX went from Active to OpenSent
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX sending OPEN, version 4, my as: CISCOAS
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX rcv message type 1, length (excl. header) 26
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX rcv OPEN, version 4
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX rcv OPEN w/ OPTION parameter len: 16
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX rcvd OPEN w/ optional parameter type 2 (Capability) len 14
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX OPEN has CAPABILITY code: 2, length 0
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX OPEN has ROUTE-REFRESH capability(new) for all address-families
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX OPEN has CAPABILITY code: 65, length 4
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX unrecognized capability code: 65 - ingored
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX OPEN has CAPABILITY code: 0, length 0
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX unrecognized capability code: 0 - ingored
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX OPEN has CAPABILITY code: 194, length 171
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX unrecognized capability code: 194 - ingored
*Feb 10 06:50:57.053: BGP: XX.MK.IP.XX went from OpenSent to Closing
 
tronity2k
just joined
Topic Author
Posts: 17
Joined: Thu Jul 12, 2007 8:22 pm

Re: BGP problem capabilities negotation

Fri Feb 12, 2010 1:28 pm

Anybody know answer on my question?
Maybe support help?
 
User avatar
DeVerm
just joined
Posts: 24
Joined: Thu Feb 11, 2010 2:49 am
Location: Panama
Contact:

Re: BGP problem capabilities negotation

Fri Feb 12, 2010 8:26 pm

What happens if you leave out: tcp-md5-key=""
Also, see if you can set the BGP version to 4.

the rest looks good. But I must say that on an IX you should normally come with a Cisco or Juniper. Your peers are not going to like you much for this trouble and they might stop the peering agreements. At least test it to a Cisco on your bench, use the smalles cheapest 2nd hand Cisco with an image that supports BGP (36xx series from eBay?)

cheers,
Nick.
 
tronity2k
just joined
Topic Author
Posts: 17
Joined: Thu Jul 12, 2007 8:22 pm

Re: BGP problem capabilities negotation

Mon Feb 15, 2010 1:48 pm

I not think that best response is: Get a cisco (if not used juniper or green boxes are why their government forces them to be subject to interception of communications).

It would be great if Mikrotik people decide is useful implement some things you already do Quagga:
- Capability Negotation
- Route Flap Dampening

http://www.quagga.net/docs/docs-multi/C ... ation.html
 
User avatar
DeVerm
just joined
Posts: 24
Joined: Thu Feb 11, 2010 2:49 am
Location: Panama
Contact:

Re: BGP problem capabilities negotation

Mon Feb 15, 2010 5:50 pm

Hmmm... all the Internet exchanges that I know prohibit using routers that can't do flap dampening. All the big ones require it.

You can use something else than Cisco or Juniper but what you use must be able to works flawlessly with those two systems and you must know how to configure that before setting up with your peers at the exchange. What you use must be compatible with the rules also so that means route aggregation, flap dampening and filtering.

cheers,
Nick.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 6047
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: BGP problem capabilities negotation

Wed Feb 17, 2010 11:03 am

It would be great if Mikrotik people decide is useful implement some things you already do Quagga:
- Capability Negotation
RouterOS already supports capability negotiation according to RFC5492
 
dnyl
Frequent Visitor
Frequent Visitor
Posts: 57
Joined: Thu Jan 07, 2010 2:57 am
Location: Budapest, Hungary
Contact:

Re: BGP problem capabilities negotation

Sat May 01, 2010 6:51 pm

When 4 byte AS capability fixed in ROS 4.x?
In 3.30 ROS works fine.

When we upgrade from 3.30 to 4.6 than our bgp peers goes down, and get this problem.
 
dnyl
Frequent Visitor
Frequent Visitor
Posts: 57
Joined: Thu Jan 07, 2010 2:57 am
Location: Budapest, Hungary
Contact:

Re: BGP problem capabilities negotation

Thu May 06, 2010 2:22 am

Any idea for my problem?
I think we need to use again freebsd with openbgpd, because mikrotik don't want to solve this problem.
Or in ROS 4.22 on the next week is it fixed? :)
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8395
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: BGP problem capabilities negotation

Mon May 10, 2010 5:19 am

if you think it's a bug - please write to support@mikrotik.com. it's Community forum...
Russian-speaking forum: https://forum.mikrotik.by/. Welcome!

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.

Who is online

Users browsing this forum: stefki and 13 guests