@fossie @Widmo
Let’s try to debug where things go wrong.
What does cmk -D <hostname> output as “Type of agent”?
Example output from one of my working hosts:
Type of agent:
SNMPv2c (Community: ‘public’, Bulkwalk: yes, Port: 161, Backend: Inline)
Program: /omd/sites/cmk/local/lib/python3/cmk_addons/plugins/mikrotik/libexec/agent_mikrotik --user admin --pass passw0rd --no-ssl --rest --connect 80 --modules bgp,ospf,vrrp,health,board,ipsec,firewall,license 10.11.12.79
Process piggyback data from /omd/sites/cmk/tmp/check_mk/piggyback/myhost
The relevant line would be the “Program:” line, I assume it’s missing in your cases?
Let’s check what (if anything) WATO (“Config”) wrote into the Checkmk config files, again here’s how it should look:
special_agents.setdefault('mikrotik', [])
special_agents['mikrotik'] = [
{'id': '9855ac9a-c594-4251-a506-c51b140690a6', 'value': {'user': 'admin', 'password': 'passw0rd', 'rest': True, 'no-ssl': True, 'connect': 80, 'infos': ['bgp', 'ospf', 'vrrp', 'health', 'board', 'ipsec', 'firewall', 'license']}, 'condition': {'host_name': ['myhost']}, 'options': {'disabled': False}},
] + special_agents['mikrotik']
The relevant path and file would be ~/etc/check_mk/conf.d/wato/rules.mk if you added the Other Integrations rule in the “Main” folder (root of the tree), or in a subdirectory if you added the Mikrotik agent rule within a folder (filename would remain rules.mk).
What does it look like for you? Do you even have a “special_agents[‘mikrotik’]“ line anywhere below ~/etc/check_mk/conf.d/wato/, and what’s the content?
.
. Many thanks for your fast answers!