BGP peering not working with routeros 7.6

mktwifi · Fri Mar 03, 2023 12:58 pm

Hi guys
I hope somebody can help me.
Yesterday I upgraded a CCR204 with RouterOS version 7.6. and, after that, one of the BGP peering went DOWN.
I checked configuration and is exactly the same as versione 6.48.6, then I try to contact our carrier and they told me that they didn't see any BGP connection requests. The other end router is a JUNIPER.
What could be the issue? Can someone help me urgently please?

Thanks in advance

Best regards

mktwifi · Fri Mar 03, 2023 1:09 pm

I've just tried to upgrade RouterOS with version 7.8 but problem is the same: peering BGP with a juniper router does not go up

connectlife · Fri Mar 03, 2023 7:47 pm

Post the configuration otherwise we can't help you..

We have several Juniper/Mikrotik BGP sessions on ROS 7.7 and 7.8 and they work fine

HI

mktwifi · Wed Mar 08, 2023 4:30 pm

Post the configuration otherwise we can't help you..

We have several Juniper/Mikrotik BGP sessions on ROS 7.7 and 7.8 and they work fine

HI

Here it is:

# mar/08/2023 15:16:55 by RouterOS 7.8
#
# model = CCR2004-1G-12S+2XS
#
/routing bgp template
set default as=11111 disabled=no hold-time=3m multihop=yes output.network=\
    bgp-networks .no-client-to-client-reflection=yes router-id=4.4.4.4 \
    routing-table=main
/routing bgp connection
add as=11111 cisco-vpls-nlri-len-fmt=auto-bits connect=yes disabled=no \
    hold-time=3m input.filter=AAAAAAA-IN-LOCALPREF listen=yes local.address=\
    5.5.5.5 .role=ebgp .ttl=10 multihop=yes name=AAAAAAA \
    output.filter-chain=AAAAAAA-OUT-PREP .network=bgp-networks \
    .no-client-to-client-reflection=yes remote.address=6.6.6.6/32 .as=\
    2222 .ttl=10 router-id=4.4.4.4 routing-table=main templates=default
add as=11111 cisco-vpls-nlri-len-fmt=auto-bits connect=yes disabled=no \
    hold-time=3m input.filter=BBBBBBBBBBBB-IN-LOCPREF listen=yes local.role=\
    ebgp multihop=yes name=BBBBBBBBBBBB output.filter-chain=\
    BBBBBBBBBBBB-FIBER-BAS-OUT .network=bgp-networks \
    .no-client-to-client-reflection=yes remote.address=7.7.7.7/32 .as=\
    33333 router-id=4.4.4.4 routing-table=main templates=default
add as=11111 cisco-vpls-nlri-len-fmt=auto-bits connect=yes disabled=yes \
    hold-time=3m input.filter=AAAAAAA-IN-LOCALPREF listen=yes local.role=\
    ebgp-peer .ttl=10 multihop=yes name=TestAAAAAAA output.filter-chain=\
    AAAAAAA-OUT .network=bgp-networks .no-client-to-client-reflection=yes \
    remote.address=6.6.6.6/32 .as=2222 router-id=4.4.4.4 \
    routing-table=main
add as=11111 cisco-vpls-nlri-len-fmt=auto-bits connect=yes disabled=yes \
    hold-time=3m input.filter=BBBBBBBBBBBB-IN-LOCPREF listen=yes local.role=\
    ebgp .ttl=255 multihop=yes name=TestBBBBBBBBBBBB output.filter-chain=\
    BBBBBBBBBBBB-FIBER-BAS-OUT .network=bgp-networks \
    .no-client-to-client-reflection=yes remote.address=7.7.7.7/32 .as=\
    33333 router-id=4.4.4.4 routing-table=main

/routing filter rule
add chain=AAAAAAA-OUT disabled=no rule=\
    "if (bgp-as-path-slow-legacy \"^\$\") { accept; }"
add chain=AAAAAAA-OUT disabled=no rule="reject;"
add chain=AAAAAAA-OUT-PREP disabled=no rule="if (bgp-as-path-slow-legacy \"^\$\
    \") { set bgp-path-prepend 2; accept; }"
add chain=AAAAAAA-OUT-PREP disabled=no rule="reject;"
add chain=AAAAAAA-IN disabled=no rule=\
    "if (bgp-as-path-slow-legacy \"^2222\$\") { accept; }"
add chain=AAAAAAA-IN-NEW disabled=no rule=\
    "if (bgp-as-path-slow-legacy \"^2222_\") { accept; }"
add chain=AAAAAAA-IN-LOCALPREF disabled=no rule="if (bgp-as-path-slow-legacy \
    \"^2222\$\") { set bgp-local-pref 500; accept; }"
add chain=AAAAAAA-IN-LOCALPREF-NEW disabled=no rule="if (bgp-as-path-slow-lega\
    cy \"^2222_\") { set bgp-local-pref 500; accept; }"
add chain=BBBBBBBBBBBB-IN disabled=no rule=\
    "if (bgp-as-path-slow-legacy \"^33333_\") { accept; }"
add chain=BBBBBBBBBBBB-IN-LOCALPREF disabled=no rule="if (bgp-as-path-slow-lega\
    cy \"^33333_\") { set bgp-local-pref 500; accept; }"
add chain=BBBBBBBBBBBB-FIBER-BAS-OUT disabled=no rule=\
    "if (bgp-as-path-slow-legacy \"^\$\") { accept; }"
add chain=BBBBBBBBBBBB-FIBER-BAS-OUT disabled=no rule="reject;"
add chain=BBBBBBBBBBBB-FIBER-BAS-OUT-PREP disabled=no rule="if (bgp-as-path-slo\
    w-legacy \"^\$\") { set bgp-path-prepend 1; accept; }"
add chain=BBBBBBBBBBBB-FIBER-BAS-OUT-PREP disabled=no rule="reject;"
add chain=ospf-out disabled=no rule="if (dst == 8.8.8.8) { reject; }"
add chain=ospf-out disabled=no rule=\
    "if (dst == 94.90.216.240/30) { reject; }"
add chain=ospf-out disabled=no rule="if (dst == 9.9.9.9/29) { reject; }"

Thanks

MichaelHallager · Tue Apr 04, 2023 2:36 pm

Two possibilities to check:

1. ROS7 requires syncronise unlike ROS6 where it was an option. So therefore you will need to pop a static route entry to blackhole and a high distance (250 will do - as long as its higher then anything else) which equals your route announcements.
2. Some config can get lost in ROS6 to ROS7 updates. Go through with a fine tooth comb.

BGP peering not working with routeros 7.6

BGP peering not working with routeros 7.6

Re: BGP peering not working with routeros 7.6

Re: BGP peering not working with routeros 7.6

Re: BGP peering not working with routeros 7.6

Re: BGP peering not working with routeros 7.6

Who is online