I have sysedge running on two hosts for snmp. They have the same SNMP configuration in HKLM\SYSTEM\CurrentControlSet\services\SNMP exactly the same, but one host does not work. If I restart sysedge on the host, an snmpwalk works up to a point (at the HOST-RESOURCES-MIB) but hangs and returns a timeout after some time. After the timeout, the snmpwalk does not work unless I restart the service again (where it fails at the same point).
This is where it fails in the walk:
HOST-RESOURCES-MIB::hrSystemInitialLoadDevice.0 = INTEGER: 0
Also, before I start the walk, sysedge is using 00 CPU and about 5,000 K Memory. After I do the walk that times it out, it climbs to ~20,000 K, then bounces between 23,000 K and 41,000 K Memory usage.
Does anyone know what could be causing this?