NetXMS Support Forum

I hacked together something like this: 

transport = CreateSNMPTransport($node);
if (transport == null) { return null; }

diskSize = SNMPGetValue(transport,".1.3.6.1.2.1.25.2.3.1.5.131072");
diskUsed = SNMPGetValue(transport,".1.3.6.1.2.1.25.2.3.1.6.131072");

if(diskSize == null || diskUsed == null) { return null; }

free = diskSize - diskUsed;
free = free * 1024;


return free;
" free = free * 1024; " is because otherwise unit b(IEC) was showing incorrectly.

is there anything that could be improved on this script?

Hello

What is the best approach to make dci that queries 2 separate snmp oids, does some math with them and then returns the output. is it possible to do in one dci, or is multiple required?

Example:
.1.3.6.1.2.1.25.2.3.1.6.131072 - returns 11320 (/1024 = 11mb)
.1.3.6.1.2.1.25.2.3.1.5.131072 - returns 16384 (/1024 = 16mb)
Output = 16-11 = 4mb

Its Mikrotik disk usage.

Hello

i Did exactly as in picture, but for me i dont see any dci discoveries for some reason.

Edit:
When i move the dci directly to node then it works, but under template it doesn't. Maybe it needs longer time?

Edit:
After waitng for hour and no dci-s from template appeared. i deleted template and made it again, this time dci-s started apearing and it seems to work.

Second question. I have script to filter what nodes get applied to template. How can i improve on it to match different oid endings and not manualy add them?

if( $node->isSNMP ) {

    if( $node->sysDescription like "*RouterOS *" && ($node->name like "*[Ap] *") ) {
   
        transport = CreateSNMPTransport($node);
        if ( transport == null ) return NULL;

        ssid = SNMPGetValue(transport,".1.3.6.1.4.1.14988.1.1.1.3.1.4.1");
        freq = SNMPGetValue(transport,".1.3.6.1.4.1.14988.1.1.1.3.1.7.1");
       
        ssidB = SNMPGetValue(transport,".1.3.6.1.4.1.14988.1.1.1.3.1.4.2");
        freqB = SNMPGetValue(transport,".1.3.6.1.4.1.14988.1.1.1.3.1.7.2");
       
        if(ssid != null && freq != null) {
            return true;
        }else if(ssidB != null && freqB != null) {
            return true;
        }
    }
}


return false;


Hello

Could use help with dci instance discovery.

I have 2 Mikrotik wifi devices where i would like to poll ssid name. On one device it reports with .1.3.6.1.4.1.14988.1.1.1.3.1.4.1 on another one with .1.3.6.1.4.1.14988.1.1.1.3.1.4.2. The end number is changing. How can i discover that dynamicaly?

Egert

Hello

I am looking for Juniper Srx router snmp oids to monitor. Perhaps someone has working template that they feel like sharing ?

Egert

Will do.

Hello

Today i tested mass file upload with NetXms and encountered some problems. I have folder with many servers bound under it. All server have Agent installed and have agent policy via template: SubAgent = filemgr.nsm

[filemgr]
RootFolder = C:/

When selecting folder and right click -> Upload file, i selected one file and gave it remote file name "C:\Failid\test2154.exe". Then i monitored the upload progess via View - Server jobs. Upload started on about 50 servers. I see alot of messages "File upload failed. Waiting 10 minutes to restart job", "File upload failed. Waiting 20 minutes to restart job". After about 30 minutes or so those messages begin to dissapear. But even with first round the file is actualy already uploded fine.

Edit: Those messages that dissapeared are now returning with Waiting 40 minutes to restart job" Files are uploaded fine, seems like server doesent get the notice to stop uploading.

Currently running 4.1.333

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

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

Many thanks

Egert

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

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

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?

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