Hey @SChalakov ,
Thanks for getting back to me on this. I couldn't answer your post because of the 1000 character restriction.
- First, filter the Event Logs on my two Gateways (RP) and look for any related warnings or errors.
I did. There were a couple of errors, which I dismissed at first, thinking they were belonging to a previous problem. However, once I restarted the health services on the GWs they came back:
Type mismatch for RunAs profile in workflow "System.NetworkManagement.Cisco.Memory.InsufficientFreeMemory", running for instance "MEM-20" with id:"{some-id}". Workflow will not be loaded. Management group "MGname"
There were a lot of those. Probably one for every workflow used to monitor each network device. Seems like that's the problem. I suppose my Run As profiles are still configured wrongly. Additionally, I checked the distribution of the SNMP account again. It is distributed to every Mgmt and Gw Server as well as to every RP any network devices are in.
The run as profiles are configured thus:
https://ibb.co/k3341D1 (picture insertion seems to be buggy)
(SNMP Monitoring Account profile)
and
https://ibb.co/CtyTvY9
(SNMPv3 Monitoring Account profile)
- Second, empty the Health Service cache on those two servers.
That I did but seeing as the error persisted, I suppose the above-mentioned configuration is the source.
- Open the Health Explorer of a managed network device and check in the monitor hierarchy if there are monitors, which are initialized.
Every monitor is shown as "Not monitored" (green circle) and there are no events nor any statuses.
Additionally, I deleted some ~110 devices, to get under the 500 devices mark. Made no difference, which makes perfect sense after your answer.
Something I did notice, however; the SNMP v2 devices are monitored correctly.
Another piece of information I might mention is: the devices are already monitored by a different (older MG). They allow my new SCOM env to connect to it but aren't using the new SCOM Servers as a trap receiver. For all I know, that shouldn't be a problem. In any case, the Errors are certainly not issued because of that.
Regards
Simon