v3.7 cannot disable Network Discovery

Started by blazarov, March 02, 2021, 11:47:40 AM

Previous topic - Next topic
Print
Go Down Pages1
User actions

blazarov

March 02, 2021, 11:47:40 AM
Hello,
shortly after upgrade to 3.7 we have decided to give it a try of the network discovery.
Initially it worked seemingly well, but we decided to not use it for multiple reasons.
However it seems to me that it never stops, regardless of disabling it from configuration->network discover-> general settings: Disabled
Even after netxmsd restart devices keep appearing in the Zones' subnets.

Also there is a significant increase in load of netxms server and agent proxies that i believe is caused by the continous network discovery.

is there a way i can actually check if discovery is acutally happening and a way to forcefully disable it?

blazarov

#1
March 02, 2021, 01:04:23 PM
I just increased debuglevel to 6 and i have lots and lots of these:

2021.03.02 13:03:50.815 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.5.43): failed
2021.03.02 13:03:50.930 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.5.93): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:50.930 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.5.90): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:50.941 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.5.86): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:50.999 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.5.95): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.016 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.5.124): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.080 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.5.126): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.106 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.5.137): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.110 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.5.142): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.110 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.5.141): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.142 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.5.148): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.229 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.5.142): trying version 0 community 'public'
2021.03.02 13:03:51.307 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.151.100): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.366 *D* [snmp.discovery     ] SnmpCheckV3CommSettings(10.8.17.113): failed
2021.03.02 13:03:51.366 *D* [snmp.discovery     ] SnmpCheckCommSettings(10.8.17.113): trying version 1 community 'public'
2021.03.02 13:03:51.406 *D* [snmp.discovery     ] SnmpCheckV3CommSettings(10.8.24.102): failed
2021.03.02 13:03:51.406 *D* [snmp.discovery     ] SnmpCheckCommSettings(10.8.24.102): trying version 1 community 'public'
2021.03.02 13:03:51.406 *D* [snmp.discovery     ] SnmpCheckV3CommSettings(10.8.49.107): failed
2021.03.02 13:03:51.406 *D* [snmp.discovery     ] SnmpCheckCommSettings(10.8.49.107): trying version 1 community 'public'
2021.03.02 13:03:51.505 *D* [snmp.discovery     ] SnmpCheckCommSettings(10.43.113.249): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.613 *D* [snmp.discovery     ] SnmpCheckCommSettings(10.42.19.197): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.666 *D* [snmp.discovery     ] SnmpCheckCommSettings(10.40.173.2): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.691 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.14): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.700 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.11): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.702 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.14): trying version 0 community 'public'
2021.03.02 13:03:51.710 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.11): trying version 0 community 'public'
2021.03.02 13:03:51.735 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.10): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.737 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.28): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.763 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.31): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.768 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.51): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.773 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.31): trying version 0 community 'public'
2021.03.02 13:03:51.779 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.27): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.779 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.37): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.803 *D* [snmp.discovery     ] SnmpCheckV3CommSettings(10.8.168.14): failed
2021.03.02 13:03:51.803 *D* [snmp.discovery     ] SnmpCheckCommSettings(10.8.168.14): trying version 1 community 'public'
2021.03.02 13:03:51.815 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.32): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.835 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.40): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.838 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.36): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.844 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.40): trying version 0 community 'public'
2021.03.02 13:03:51.849 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.36): trying version 0 community 'public'
2021.03.02 13:03:51.975 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.88): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.983 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.102): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:51.990 *D* [snmp.discovery     ] SnmpCheckCommSettings(192.168.1.88): trying version 0 community 'public'
2021.03.02 13:03:52.229 *D* [snmp.discovery     ] SnmpCheckCommSettings(78.90.9.1): trying version 1 community 'CyIraBpNx3JjBqUDExzM'
2021.03.02 13:03:52.247 *D* [snmp.discovery     ] SnmpCheckCommSettings(10.43.114.250): trying version 1 community 'CyIraBpNx3

Does this confirm that network discovery is actually runing despite it is disabled in the configuration?
what can i do to stop it?

Victor Kirhenshtein

#2
March 02, 2021, 10:11:01 PM
Most likely server processes already queued discovery tasks. Restart of netxmsd should fix it.

Best regards,
Victor
Print
Go Up Pages1
User actions