NetXMS Support Forum

Good morning,

update:

Discover found the new devices at about 8 pm.

queues at the moment (still increasing):
netxmsd: sh queue
Condition poller                 : 0
Configuration poller             : 0
Data collector                   : 0
Database writer                  : 0
Event processor                  : 0
Network discovery poller         : 0
Node poller                      : 77701
Routing table poller             : 0
Status poller                    : 0

I created the dump, but I think you can see all the devices and related community strings in it. For security reasons I renamed all community strings in the file, I hope it is still readable for you.

Link to the dump was sent to you per pn.

Thanks for the help,

Greetings
Tom

The node pollers increase rapidly now...

netxmsd: sh que
Condition poller                 : 0
Configuration poller             : 0
Data collector                   : 0
Database writer                  : 0
Event processor                  : 0
Network discovery poller         : 0
Node poller                      : 10422
Routing table poller             : 0
Status poller                    : 0

netxmsd:

hm, ok... it's a pity cause it sounded so good

Just found the parameter "PollCountForStatusChange"  and I think I will test this one.

Hi,

the server runs normal now after activating the dump...

But I think there is a problem now with the pollers or discovering. Discover is activated, but no new devices are found until now.

Here is the output:
netxmsd: sh qu
Condition poller                 : 0
Configuration poller             : 0
Data collector                   : 0
Database writer                  : 0
Event processor                  : 0
Network discovery poller         : 0
Node poller                      : 3469
Routing table poller             : 0
Status poller                    : 0

netxmsd: sh poll
PT  TIME                   STATE
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:41:01   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:41:01   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:41:01   wait
S   29/May/2008 13:41:01   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:41:01   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:41:01   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:41:21   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:41:01   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:41:01   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:41:16   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
S   29/May/2008 13:40:56   wait
C   29/May/2008 13:15:22   wait
C   29/May/2008 13:12:51   wait
C   29/May/2008 13:15:17   wait
C   29/May/2008 13:14:47   wait
R   29/May/2008 13:38:32   wait
R   29/May/2008 13:38:32   wait
R   29/May/2008 13:38:39   wait
R   29/May/2008 13:38:32   wait
R   29/May/2008 13:38:32   wait
D   29/May/2008 13:06:46   wait
N   29/May/2008 11:05:49   wait
N   29/May/2008 11:05:49   wait
N   29/May/2008 11:05:49   wait
N   29/May/2008 11:05:49   wait
N   29/May/2008 11:05:49   wait
N   29/May/2008 11:05:49   wait
N   29/May/2008 11:05:49   wait
N   29/May/2008 11:05:49   wait
N   29/May/2008 11:05:49   wait
N   29/May/2008 11:05:49   wait
A   29/May/2008 12:45:49   wait


Is this a normal behavior?

DiscoverInterval is set to 6000 and active.

Greetings
Tom

yes, windows.

ok, I will try to reproduce the error.

Thanks

it just happened again...

I deleted round about 10 devices and changed the discover parameters. After restarting netxms core the server crashes after about 3 minutes.

Server restart, crash after some minutes.

server restart, disable discover - server restart - crash after a few minutes.

server restart, now it runs for about 10 minutes without problems.

Any idea? I think it happend because I deleted some devices...

Hi,

I increased the value of of "SNMPREQUESTTIMEOUT" to 5000 (ms) and restarted the server.
But this night there are still node down/node up events.

So still another request for the next release

Greetings Tom

Hi,

thank you very much for the statement. It's easier for me now to stand on my decision of netxms as our new network management software.
Nice to hear that development is still ongoing. I cant await some improvements

Greetings
Tom

Hi,

while reading the manual of zabbix I found the names victor and alexander kirhenstein (misspelled?) in the section "contributors".

Are there plans to merge the two projects?
We are really looking for a stable network management solution with ongoing development and now are unsure of the development of netxms. Today I would say "yes, netxms can help us in most cases, even if there are some bugs".

It would be nice to hear what plans you have 

Thanks,

Greetings
Tom

Hi,

I thought about increasing the snmp timeout value, but I think this will not change anything, because the initial request can not be made. But I will test it.

Thanks you for your plans to improve this

Greetings
Tom

Thanks for the help, I will do a test with the script

Hi,

is there a way to exclude some clients in autodiscover process? I scan the networks for snmp devices. unfortunately, some HP Printers react on my snmp community and are added to the devicelist.

Its only one subnet - I have 10 switches there to manage, and 10 printers that I dont want to include in the scan.

Is there a way to exclude the whole subnet from configuration polls? There are nor changes in this network normally.

Thanks,

greetings
Tom

Hi,

we have a problem with busy snmp agents on some switches.

We have some nodes that are changing the status in 1 minute from normal, to down, to normal.
For example:
"20:33:47" "warning" "switch1" "SYS_SNMP_UNREACHABLE" "SNMP agent is not responding"
"20:33:47" "critical" "switch1" "SYS_NODE_DOWN" "Node down"
"20:33:47" "critical" "switch1" "SYS_NODE_CRITICAL" "Node status changed to CRITICAL"
"20:34:50" "normal" "switch1" "SYS_SNMP_OK" "Connectivity with SNMP agent restored"
"20:34:50" "normal" "switch1" "SYS_NODE_UP" "Node up"

I think the reason is that our older switches are sometimes heavy loaded at the management interface because we use Kiwi Cat Tools to get the actual mac table and port infos every 30 minutes.

Is there a way to change the retry intervals for snmp connectivity? It would be no problem to receive a error message after 2 minutes instead of 1 minute. Its better than a system that produces 5 or more false error messages a day...

Greetings
Tom

i enabled the autodiscover after it runs stable a while.

no crash during the last hour now...

strange, but ok