ok thank you I missed this post, instead for the problem of the “prefix count” field which always remains zero on BGP sessions, is there a possible resolution of the problem?
Thanks.
Currently there is no mechanism to count exact session prefixes, That is why this parameter is not even set. If you want to know exact prefixes installed in the routing table received from a specific peer, then use /roruting route print command with appropriate filtering options, like “belongs-to” or “bgp.peer-cache-id”
RB5009 still does not show cpu type in /system/resources. Also after every reboot VxLAN Mac address changes.
thanks for the information, in the future it is plausible to restore the “prefix count” value visible on the string of the established session?
How do you think where the fixes for 7.2.1 were tested? 
When containers?
How do you think where the fixes for 7.2.1 were tested?
[/quote]
Did you know that you can send me testing images for testing?
Doesn’t sound the new routing engine was very well thought out before implementing.
How is it possible that basic features were not even considered during the design phase?
BGP Prefix count per session
BGP Advertisements
Routing filters with no clear plan on how to make it GUI friendly and in line with all the rest of ROS/Winbox syntax/UI.
No BFD
It’s sad to have great new hardware for the datacenter being released, and no viable software yet to use them.
Without a fully working BGP (and I mean production, business ready, not beta testing), v7 is useless to me.
+1
Not only that, but it takes ages and many versions to get it fixed.
It would already be nice when the old /routing filter rule add syntax could be accepted and converted on-the-fly to new syntax and stored.
The code for that should be available as it is also done for v6-to-v7 upgrades.
Bonus points for allowing a v6 style “route filter +” operation in the GUI with the same result (a v7 compatible filter rule).
I of course understand that the hard part would be to then “modify” a rule created this way, but that could be done later.
In fact the same thing as above would also be nice for /routing bgp instance and /routing bgp peer commands. Accept v6 form and convert to v7 on the fly.
This would make it easier to write configuration guidelines and automatic configuration generators that work on both versions.
For people wanting to join our HAMNET network I have a config generator that creates appropriate v6 config automatically, ready for cut-and-paste.
Of course I will update that for v7 (once it is viable to use it in the network) but I can guess that others have similar things, HOWTOs etc. which were made useless by the config changes in v7.
But it will have to be written for the prefix limit handling anyway, isn’t it? When that is done, can’t it be shown in the session table as well?
Also, please make that session table auto-refreshing as it was in v6. We cannot be tricked by showing an Uptime counter that is ticking on and on even when the session is actually down (which becomes apparent when pressing F5). In v6 the table shows the actual session status and uptime, as it should be, without pressing F5.
It seems 6to4 interface routes are not installed in vrf with 7.3.
/interface 6to4
add !keepalive mtu=1480 name=HE remote-address=X.X.X.X
/ip vrf
add interfaces=HE name=VRF-HE
/ipv6 address
add address=2001:470:xxxx:cc::2 advertise=no interface=HE no-dad=yes
/routing/route/pr det where immediate-gw=HE
Ac afi=ip6 contribution=active dst-address=2001:470:xxxx:cc::/64 routing-table=main gateway=HE immediate-gw=HE distance=0 scope=10
belongs-to=“Connected route” local-address=2001:470:xxxx:cc::2%HE
debug.fwp-ptr=0x20243720
Ac afi=ip6 contribution=active dst-address=fe80::%HE/64 routing-table=main gateway=HE immediate-gw=HE distance=0 scope=10 belongs-to=“Connected route”
local-address=fe80::3:5797:fc5d%HE
debug.fwp-ptr=0x20243300
+1
this also creates problems for us in correctly monitoring the status of established BGP sessions
I sincerely hope that Mikrotik developers are working on a solution to this.
I am still in awe that critical and basic operational BGP features such as:
**- Set max-prefix-limit and a restart time on a per peer basis
- View advertised-prefixes on a per peer basis
- View received-prefixes on a per peer basis**
Were not considered in the design of the new routing engine.
The ability to view advertised and received prefixes on a per peer basis was raised as a requirement well in advance of V7 routing existing:
http://forum.mikrotik.com/t/decline-of-mikrotik/103106/1
http://forum.mikrotik.com/t/routeros-v7-0-beta1-when/84572/1
And I never thought such a critical feature like max-prefix-limit could be overlooked!
I think they always intended to implement the prefix count for received prefixes, otherwise the field to display the prefix count would not be there, rather than being there but displaying zero instead of the correct value. For the other things, I agree, I’m not sure why they weren’t anticipated as being needed.
Just tested v7.3beta33 to see how VPLS works given that this finally has MPLS fixes. VPLS still hangs the device. One ping goes through the tunnel and gets responded to, followed by one of the four CPU’s on my 4011 going to 100% CPU utilization and the device becoming completely unresponsive, requiring me to pull the power and plug it back in physically to get it working again.
I know VPLS is working for some people but others have the same problems as me, and I can’t risk even deploying this to a remote location as a test device if the only fix is to physically pull the power which may require a trip.
This is the only way I have been able to get received prefix count by peer - it’s a bit buried
Came across it when I was doing testing of full table convergence on the CCR2216s because I needed to evaluate total route count
[zuul@ccr2216-02.test.lab.ipa] > routing/stats/origin/print interval=1 where instance-id=1686070274
Flags: Y - synthetic; Z - terminal; X - stopping; D - owner-dead; H - hold; U - attrs-updated; M - attrs-merge
12 name="BGP IP routes from 198.18.92.254" instance-id=1686070274 publisher-idx=12 route-type="8" owner=28 route-count=0,387726,0,0,0,0,0,0,0,0,0,0,0 total-route-count=387726
13 name="BGP IP routes from 198.18.92.253" instance-id=1686070274 publisher-idx=13 route-type="8" owner=30 route-count=0,329737,0,0,0,0,0,0,0,0,0,0,0 total-route-count=329737
14 name="BGP IP routes from 100.126.100.1" instance-id=1686070274 publisher-idx=14 route-type="8" owner=31 route-count=0,517453,0,0,0,0,0,0,0,0,0,0,0 total-route-count=517453
Please allow us to select Address Lists for the Networks in OSPF interface-templates, we can already do this with BGP.