My RB1100AHx4 Dude Edition is very happy… 
Mine is all upgraded OK, but is not so happy.
On the remote devices I can see in the logs that it has logged into them, but it does not seem to be registering properly.
aoakeley, did you upgrade your agent (server) to 7.2 as well?
Yes.
The remote devices are all 7.2?
No. But surely that is not a requirement?
You must read the changelog,
old RouterOS access are replaced on 6.4??? (do not remember) with another type of strong access, also API are changed
The minimum version of remote devices is 6.48.3
Most are on 6.49.5
Some are on 7.1.3
Some are on 7.2
NONE of them register properly in DUDE since the upgrade.
Are you saying that they ALL need to be on 7.2 before ANY of them will work? I don't believe that/
No, that no,
but you do not have specified the other version, and can be one old version on remote devices the problem.
It’s all…
What is the RouterOS status of the agent device (server)?
RB1100AHx4 Dude Edition RouterOS 7.2
I will do some more investigation tomorrow.
Apparently agent “server” is the default.. so I have no clue, sorry.
Thanks for trying. It prompted me to have another closer look at what was going on.
I found the solution… There were some NAT and Mangle rules I had created years ago to enable The Dude to talk to some remote mikrotik devices on ports other than 8291. These had malfunctioned/broken in the upgrade to 7.2. I’ll have to go back and figure out why, but once I disabled these everything started working.
Also despite @rextended stating otherwise, and as I expected, Dude 7.2 is quite happy talking to older ROS versions. Just in case anyone else was wondering.
Good to see you got sorted. Just a couple of quick questions if you are about - get a chance to answer.
- How Many ROS devices are you monitoring the the RouterOS service.
- Do they all Stay “up/connected”
- What Hardware/License Level - if you don’t mind answering
Asking as we have stuck with an older version of dude and just reduced the connections of RouterOS as it was failing at the time with more than 50 connections (“RouterOS” runs on winbox port - 8291 - so suspect it’s using a login/connection to do so). We run a P1 CHR which should have no such limits - but it certainly does on 6.46.6 (the version we are on, as we had things as old as 5.21 out there last time we assessed - not any more though)
any infor you can give would be great - cheers
Hi..
About 100 devices being monitored
They all stay connected.
License Level 6
Hardware 1100AHx4DE
CPU sits at about 5%
ROS 6.48.6, near 1000 devices, same hardware, CPU fluctuating 4~7%
So I’m bit confused.
I’m currently on 6.48.4 on most of devices. Many of them are used as agents.
If upgrade The Dude Server to 7.2.x will it be able to use agent devices running on 6.48.4 ?
Will be fine
This night, after many issues, I’ve managed to upgrade my Dude Server to 7.3.1, and now all agent connections are broken with good old error: agent NameOfRemoteDevice routerOS version not same as dude servers (6.48.4 (stable)), next attempt at 20:57:24
Same on 6.49.6 devices
Any suggestions how to proceed without upgrading all agents to 7.3.1 at once and still not loosing sight on monitored services behind that agents ?
Not sure… all I can say is that my Dude Server running 7.2.3 is still able to communicate with older ROS devices without any problem. I will try and upgrade it to 7.3.1 one evening this week and see if anything breaks.