Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Egert143

#46
General Support / Re: Network Discovery
June 02, 2022, 03:30:43 PM
One example switch that was not auto discovered 192.168.135.93.

i added more precise subnet 192.168.135.0/24 and started manual scan with debug lvl6.

results:2022.06.02 15:18:39.072 *D* [poll.discovery     ] Starting SNMP check on range 192.168.135.1 - 192.168.135.254

2022.06.02 15:18:44.337 *D* [poll.discovery     ] Active discovery - node 192.168.135.93 responded to SNMP probe
2022.06.02 15:18:44.337 *D* [poll.discovery     ] Checking address 192.168.135.93 in zone 0 (source: Active Discovery)
2022.06.02 15:18:44.337 *D* [poll.discovery     ] New node queued: 192.168.135.93/24
2022.06.02 15:18:44.337 *D* [poll.discovery     ] NodePoller: processing address 192.168.135.93/24 in zone 0 (source type Active Discovery, source node [0])
2022.06.02 15:18:44.337 *D* [poll.discovery     ] FindExistingNodeByMAC: IP=192.168.135.93 MAC=

2022.06.02 15:18:49.598 *D* [poll.discovery     ] Active discovery - node 192.168.135.93 responded to SNMP probe
2022.06.02 15:18:49.598 *D* [poll.discovery     ] Checking address 192.168.135.93 in zone 0 (source: Active Discovery)
2022.06.02 15:18:49.598 *D* [poll.discovery     ] New node queued: 192.168.135.93/24
2022.06.02 15:18:49.598 *D* [poll.discovery     ] NodePoller: processing address 192.168.135.93/24 in zone 0 (source type Active Discovery, source node [0])
2022.06.02 15:18:49.598 *D* [poll.discovery     ] FindExistingNodeByMAC: IP=192.168.135.93 MAC=

2022.06.02 15:18:54.849 *D* [poll.discovery     ] Active discovery - node 192.168.135.93 responded to SNMP probe
2022.06.02 15:18:54.849 *D* [poll.discovery     ] Checking address 192.168.135.93 in zone 0 (source: Active Discovery)
2022.06.02 15:18:54.849 *D* [poll.discovery     ] New node queued: 192.168.135.93/24
2022.06.02 15:18:54.849 *D* [poll.discovery     ] NodePoller: processing address 192.168.135.93/24 in zone 0 (source type Active Discovery, source node [0])
2022.06.02 15:18:54.849 *D* [poll.discovery     ] FindExistingNodeByMAC: IP=192.168.135.93 MAC=

2022.06.02 15:19:01.443 *D* [poll.discovery     ] Active discovery - node 192.168.135.93 responded to SNMP probe
2022.06.02 15:19:01.443 *D* [poll.discovery     ] Checking address 192.168.135.93 in zone 0 (source: Active Discovery)
2022.06.02 15:19:01.443 *D* [poll.discovery     ] New node queued: 192.168.135.93/24
2022.06.02 15:19:02.240 *D* [poll.discovery     ] NodePoller: processing address 192.168.135.93/24 in zone 0 (source type Active Discovery, source node [0])

2022.06.02 15:19:03.037 *D* [poll.discovery     ] FindExistingNodeByMAC: IP=192.168.135.93 MAC=

2022.06.02 15:19:55.062 *D* [poll.discovery     ] Finished active discovery check on range 192.168.139.1 - 192.168.135.254


note the end range "192.168.139.1 - 192.168.135.254" should be 135.1-135.254 instead
#47
General Support / Re: Network Discovery
June 02, 2022, 09:50:56 AM
Server.QueueSize.Current(NodeDiscoveryPoller) for the last 24H has stayed constantly 0, is that normal ?

Server.ThreadPool.Load(DISCOVERY):
Usage (%): 100
Normalized load avg (1min): 0.00
Current size: 16
Current load (%): 0
Avg wait time (ms): 475


Seems its quite idle or not polling at all :)
#48
General Support / Re: format dci coordinate
June 02, 2022, 08:36:57 AM
Many thanks :)

Egert
#49
General Support / Re: Network Discovery
June 01, 2022, 11:11:23 AM
Manually adding did not show error that it already exists. Also is it bad idea to have /16 network in active discovery with interval 900? :)

Egert
#50
General Support / Network Discovery
May 31, 2022, 09:16:12 AM
Hello

Today i noticed that Active discovery haven't found few older switches. NetXms server can ping them fine but for some reason active discovery fails. Other nodes in same /24 subnet are found.

Egert
#51
Is the ssh commands universal, i mean are they supposed to work with all ssh capable devices, or does it depend on device.

Any examples on ssh output processing?
#52
Hello

Is it possible to alert on dci values that suddenly are different to what they normaly would be around that time / date? for example network throughput or cpu usage etc ?

Egert
#53
General Support / Re: format dci coordinate
May 27, 2022, 07:55:38 AM
With string formating it shows correctly, but then its not possible to create thresholds with less than or greater than.
#54
General Support / Re: format dci coordinate
May 26, 2022, 04:31:25 PM
When i tested format, under history it shows correctly, no trailing "0". But under Last Values, it still shows extra "0".

Also when i test without format, it still show correctly in history, but with extra 0 in Last Values.
#55
General Support / format dci coordinate
May 26, 2022, 11:45:26 AM
Hello

When i have coordinate dci for example "5837845.0", how can i convert it to "58.37845"?

I tried Transformation with "return $1/100000;" but this results "58.378520", there is extra 0 in the end. How to remove it ?

Egert
#56
Many thanks!

Wish all those litle snipets of info would be published. :)
#57
Hello

Is it possible to make dci that checks Network Discovery status, for example if "Disabled", "Active only" or "Active and Passive". Yesterday i noticed that for some reason it was set to disabled but it should be active.
#58
Thanks for the info. :)

Will there be features with ssh in future, like some automation with ssh commands or similar?

Egert
#59
Is that correct behavior when ssh user and password haven't been inserter then NetXms will still try to connect?
Also is there a way to mass disable ssh polling currently? Later when needed i can manualy activate it again.
#60
Hello

After upgrade from 4.0.2151 to 4.1.333 i have noticed that "Evidence" switches show error message "Failed login: User: SYSTEM, from netxms:57774 (SSH)", but other switches dont show that error. Is it something driver related and how to turn it off?

Egert