NetXMS Support Forum

Hi,

I have a question about network discovery with NetXMS(version 0.2.15) automatically.
As the result, there is no action after the setting of network discovery.
Here are my steps;

On NetXMS Console, I select the "Network Discovery" menu as the belows.

1. click Control Panel on the View menu
2. click Network Discovery on the Contorl Panenl Menu

Then "Network Discovery Configuration" window is pop-up.
And, I set items as the belows.
1. On General tab
     1) Network discovery mode --> Actvie and Passive
     2) Discovery filter --> no filtering
     3) default SNMP community --> public
2. On Active Discovery Target
     1) add a subnet

And, I check the server configuration as the belows.
1. click Control Panel on the View menu
2. click Server configuration on the Contorl Panenl Menu
And, I check some parameters
1) DefaultCommunityString  --> public
2) DiscoveryFilter --> none
3) DiscoveryFilterFlags --> 7
4) NumberOfDiscoveryPollers --> 1
5) RunNetworkDiscovery --> 1

After the setting, I have no result. So, I restart server serivice and re-login NetXMS console.
But, I have same result.

Please let me know how can I use "network Didcovery" funtion.
I want to discover all nodes of serveral subnets automatically.

Best Regards,
-Terry

Hi,

The auto-Network discovery was done.
But there is a problem.

NetXMS found a subent takes too long.
It takes over 3 hours.
Is it normal?

If anyone have a comment, please let me know.

Best Regards,
- Terry

Hello!

By default, NetXMS server will run active discovery every 2 hours, and passive discovery polls every 15 minutes. You can change this by changing appropriate server parameters: ActiveDiscoveryInterval and DiscoveryPollingInterval (both in seconds). Also, if you have large subnet with a lot of unused addresses, it can take significant amount of time to scan it using active discovery: because for each unused address server will wait for a response until timeout expires, and because timeout is ~6 seconds, if you have /24 subnet with most addresses unused, it will take ~20 minutes to scan them. Firewall between NetXMS server and scanned subnet may also affect discovery time (for example, if firewall blocks TCP connections to port 4700 which NetXMS server will check to determine if agent is running on the host).

Best regards,
Victor

Hi,

Thanks for your help.

I change ActiveDiscoveryInterval and DiscoveryPollingInterval.
And, the speed of auto-discovery is rapidly.

Again, great thanks.

Best Regards,
-Terrry

Hi, terry
when i set the DefaultCommunityString and the DiscoveryFilter=SNMP their "restart" status doesn't turn to "yes" it remains "no"
even if i had restarted the netxms server.
I have the same problem like you, when i add a node i find him but for automatic discover there is no nodes.
So could you help please with your configuration of intervals