Here is Ping from router 1100ahx2 to airfiber24
why is it doing so, fiber has lots resources and routeros cpu is not full too, they pass <170mb traffic

Here is Ping from router 1100ahx2 to airfiber24
why is it doing so, fiber has lots resources and routeros cpu is not full too, they pass <170mb traffic

There was a problem in earlier version of RouterOS - make sure you are running v6.15.
The link to your airfiber was probably not working for the first several pings. I’ve seen the no buffer space error when the physical link is up, but the device on the other end was not actually doing anything with the packets yet. I think it was while I was trying to ping the remote end of an AirFIber link, actually. I knew what was going on and it made sense so I promptly forgot about it.
Is 172.22.100.2 the near end of the AirFiber link, or the remote end?
Are there any ethernet link status change messages in the log of the interface to which the AirFiber is connected?
Is flow control enabled on the AirFiber? Is it enabled on the RB1100AHx2?
Flow control is disabled, it’s local segment not remote end, link status was up all the time( R mark) it was passing traffic,
I upgraded to 6.15 let’s see what happens, till now on the same hardware 6.2 worked fine for months
the same with 6.15
Write description of problem to support@mikrotik.com
I wrote about another problem and where is answer?
The best way to not get an answer is to not ask the question.
When you send a message to support@mikrotik.com is sends back an automated reply which lists the information they want for every support request. Did you supply all of that information?
If you can afford the downtime for testing, it might be good to install (15-2 = 13, 13%2 = 7, 2+7 = 9) RouterOS 6.9 and see if the problem is there. If not install (15 - 9 = 6, 6%2 = 3, 9+3 = 12) RouterOS 6.12 and test that. Then keep bisecting the versions until you get to version 6.x works and version 6.x+1 does not. That information would probably help MikroTik figure out which code change introduced the issue.
I sent support files, had latest ros, config worked well on previous versions, what else is needed