I upgraded one of my PROD CCR2004's (arm64) last night to RouterOS v7.1.1 and I can't get a simple iBGP peering established with my CCR1036 RouterOS v6 Router. This PROD CCR2004 is along my redundant path so no traffic should be passing through it. It is very possible that it is user error by me, but I can't get it working for some reason. I have played around with the iBGP config as much as I can think of and nothing brought it online. Keep in mind that this iBGP peering was established on RouterOS v6. I am able to ping the loopbacks fine from both of the Routers. I was hoping I could get a sanity check on the below config:
CCR2004 RouterOS v7.1.1 (RTR-02):
Code: Select all
/interface bridge
add name=Lo1
/ip address
add address=172.16.204.2 interface=Lo1 network=172.16.204.2
/routing bgp connection
add address-families=ip as=123412 disabled=no hold-time=30s input.filter=RTR-02-to-RTR-01-in keepalive-time=10s local.role=ibgp name=RTR-01-peer nexthop-choice=force-self output.default-originate=if-installed .filter-chain=\
RTR-02-to-RTR-01-out remote.address=172.16.204.1/32 .as=123412 router-id=172.16.204.2 routing-table=main
/routing filter rule
add chain=RTR-02-to-RTR-01-in disabled=no rule="accept;"
add chain=RTR-02-to-RTR-01-out disabled=no rule="if (dst in 123.123.123.0/23 && dst-len in 23-32) { reject; }"
add chain=RTR-02-to-RTR-01-out disabled=no rule="set bgp-local-pref 400; accept;"
CCR1036 RouterOS v6.47.9 (RTR-01):
Code: Select all
/interface bridge
add name=Lo1
/ip address
add address=172.16.204.1 interface=Lo1 network=172.16.204.1
/routing bgp peer
add hold-time=30s in-filter=RTR-01-to-RTR-02-in instance=bgp1 keepalive-time=10s name=RTR-02-peer nexthop-choice=force-self out-filter=RTR-01-to-RTR-02-out remote-address=172.16.204.2 remote-as=123412 ttl=default update-source=\
Lo1
/routing filter
add action=accept chain=RTR-01-to-RTR-02-in
add action=accept chain=RTR-01-to-RTR-02-out