Hi Tom!
There are 2 different flavors x86 intended for physical hardware and CHR intended for cloud / virtual deployments as you may see in: MikroTik Routers and Wireless - Software
With the latest plugin is not enough to disable the board info because it always uses it to switch between ROS6 and ROS7 options
The following example with ipsec section also fails:
OMD[networking]:~/local/share/check_mk/agents/special$ ./agent_mikrotik -n -c8728 --debug -u api_user_ro -p xxxxxxxxxxx -i ipsec 10.138.xx.xxx
<<<check_mk>>>
Version: 2.4.x-mikrotik_agent
Traceback (most recent call last):
File "./agent_mikrotik", line 359, in <module>
version=myapi(["/system/routerboard/print"])[0]['current-firmware'].split('.')[0]
KeyError: 'current-firmware'
OMD[networking]:~/local/share/check_mk/agents/special$
Here’s a sample output for system resource print:
[admin@FW-01] > system resource print
uptime: 9h15m53s
version: 6.49.7 (stable)
build-time: Oct/11/2022 14:37:24
free-memory: 942.4MiB
total-memory: 992.0MiB
cpu: Intel(R)
cpu-count: 1
cpu-frequency: 2394MHz
cpu-load: 1%
free-hdd-space: 988.2MiB
total-hdd-space: 1020.1MiB
write-sect-since-reboot: 24520
write-sect-total: 24521
architecture-name: x86_64
board-name: CHR
platform: MikroTik
[admin@FW-01] >
Alejandro.-