NetXMS Support Forum

Greetings,

Are there any methods within nxsl to filter nodes that are set to unmanaged ? I looked all through the docs and the closest I came was isInMaintenanceMode.I have a several  wireless devices that are being decommissioned and I do not want any type of polling to be done  but I do want to be able to filter them out to keep track of the progress and add them to the decommissioned container.

Not really a support question but just thought what a small world that I just saw the nxagent embedded in the StarWinds CVM which is basically a VM that runs the StarWinds storage software that I am doing a trial on.

I have noticed more latency in the newer versions of  the netxms client where just even switching between different views in the UI will cause a progress bar on the bottom to pop up while loading the view. Is this due to the server or the client ?   

When uploading a file to an agent all files uploaded are owned by root is this the correct behavior ?  the following blog post shows the files being owned by the same user that owns the directory. If so is there a way to change this without having to log into the remote machine and change the file owner.
  https://netxms.com/blog/file-management-and-remote-actions-through-an-agent-how-it-s-done-in-netxms


Thanks

We have a new temperature/humidity sensor  from WebRelay (X-410) which has been added to netxms to monitor temps. The weird thing is for each config poll a different address is seen and interface eth0 is changed to this external address which is not the address we assigned to the device and is external. The device has a single ethernet port and  still responds to the internal address we originally assigned. I have checked with another MIB browser with the IP and IF oids and I don't  see where this address is coming from. Is it possible netxms is generating these addresses ?  I am curious as to what the PING3 driver is and how it determined this device needed that driver.


Thanks

I am using the following script to rename the node to the discovered snmp name 

9  if (($node.snmpSysName != "") and ($node.snmpSysName !=null))
10 {
11 return $object.rename($node->snmpSysName);
12 }

I always get this error and Im not sure why as it compiles and runs without issue
Script (Hook::ConfigurationPoll) execution error: Error 14 in line 9: Function or operation argument is not an object

Are there any default data retention policies setup for TS  ?   I have been trying to figure out why my DB is so bloated at 92GB I only have about 1K devices with only about 200 having about 10-20 DCI's the rest is icmp checks is this normal ?  I have NetXMS setup to only keep 30days of everthing being collected so Im wondering if the data is remaining for some reason.  


Using version 5.22 Debian 12


Thanks

Are these possibly still on the horizon ?  I really think this would be a good addition.  I know other NMS's have implemented it but not sure how difficult this is. 


Thanks,

Just curious as to what people are doing when it comes to topology for these devices ?  I know NetXMS has a driver and shows a few metrics but topology has never been able to be discovered as far as detecting stations connected to AP's  I have tried to manually set the peer's between AP -> Station  but this does not seem to make a connection on the map. I am trying to avoid trying to do this manually because of the number of devices we have and Ubiquiti no longer has a management tool for these devices because it seems they are trying to push everyone to Unifi

Thanks   

Are there any examples of link style scripts ?   Im not sure  If this would be the right place to do this but I would like to highlight/color  a interface/ link based on if the STP status is in a blocking state.  I would like to highlight the interface and change the color of the link to signify that a layer2 loop is broken here in the Ring



Thanks  

Is there any chance there will be a pan/zoomable map (not the global map) that allows you to drag and drop objects and make connections and maybe even possibly and layers that can be turned on and off ?  Are there any fixes with existing maps planned ? I always have issues with maps doing weird things on their own after spending a lot of time getting the layout how I want it even after disabling automatic layout and Lock the map things still manages to change on their own.  I also have issues when moving objects what to snap even though i do not have snap/align to grid enabled.  I am currently using 5.1.2

What features are included with the builds from the repository ?  are most features such as MQTT default now  and are there any features that would require building from source to be enabled. 



Thanks

I noticed a check box []Detect anomalies   I was just curious if this is currently supported or just a future feature and how are the outliers actually being detected. 



Thanks

Previously I was using the following script in the configpoll to use the SNMP sysname

/* Available global variables:
 *  $object - current object, one of 'NetObj' subclasses
 *  $node - current object if it is 'Node' class
 *
 * Expected return value:
 *  none - returned value is ignored
 */
 
if (($node->snmpSysName != "") and ($node->snmpSysName !=null))
{
 RenameObject($node->snmpSysName);
}

I know that RenameObject is deprecated but the new rename() does not seem to work either here is what I tried rename( $node->snmpSysName) is there a better way to do this or can this possibly be implemented in the core functionality or as a server config variable 

After upgrading to 5.0 I have been getting alarms with the Ubiquiti AirMAX templates see below. Not sure if this was fixed with 5.0.1 but wanted to post just incase

I known I am odd and should probably be installing from package but out of habit I have always generally built from source.  Anyway in 5.0 is i am getting the following when running make install. Seem like there a issues with some of the mibs. I also noticed the mibs are no longer .txt and now .mib


Parsing source files
[warning] /usr/local/share/netxms/mibs/LSI-AdapterSASIR.mib : Object identifier started with uppercase letter in line 2732
[warning] /usr/local/share/netxms/mibs/LSI-AdapterSASIR.mib : Object identifier started with uppercase letter in line 2740
[warning] /usr/local/share/netxms/mibs/LSI-AdapterSASIR.mib : Object identifier started with uppercase letter in line 2747
[warning] /usr/local/share/netxms/mibs/LSI-AdapterSASIR.mib : Object identifier started with uppercase letter in line 2755
[warning] /usr/local/share/netxms/mibs/LSI-AdapterSASIR.mib : Object identifier started with uppercase letter in line 2763
[warning] /usr/local/share/netxms/mibs/LSI-AdapterSASIR.mib : Object identifier started with uppercase letter in line 2771
[warning] /usr/local/share/netxms/mibs/LSI-AdapterSASIR.mib : Object identifier started with uppercase letter in line 2779
[warning] /usr/local/share/netxms/mibs/CYBEROAM-MIB.mib : Object identifier started with uppercase letter in line 392
[warning] /usr/local/share/netxms/mibs/CDX-6500-COMMON-MIB.mib : Object identifier started with uppercase letter in line 3930
[warning] /usr/local/share/netxms/mibs/CDX-6500-COMMON-MIB.mib : Object identifier started with uppercase letter in line 3937
[warning] /usr/local/share/netxms/mibs/CDX-6500-COMMON-MIB.mib : Object identifier started with uppercase letter in line 3944
[warning] /usr/local/share/netxms/mibs/CDX-6500-COMMON-MIB.mib : Object identifier started with uppercase letter in line 3951
[warning] /usr/local/share/netxms/mibs/CDX-6500-COMMON-MIB.mib : Object identifier started with uppercase letter in line 3958
[warning] /usr/local/share/netxms/mibs/CDX-6500-COMMON-MIB.mib : Object identifier started with uppercase letter in line 3965
[warning] /usr/local/share/netxms/mibs/CDX-6500-COMMON-MIB.mib : Object identifier started with uppercase letter in line 3973
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 39
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 47
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 56
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 63
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 70
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 77
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 85
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 92
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 99
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 109
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 117
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 124
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 131
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 138
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 145
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 152
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 161
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 168
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 175
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 182
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 189
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 196
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 203
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 213
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 220
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 227
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 234
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 241
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 248
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 257
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 264
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 271
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 278
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 285
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 292
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 301
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 308
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 315
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 322
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 329
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 336
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 345
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 352
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 359
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 366
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 373
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 380
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 389
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 396
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 403
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 410
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 417
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 424
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 434
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 441
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 448
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 455
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 463
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 470
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 477
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 486
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 494
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 501
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 508
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 515
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 522
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 529
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 538
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 545
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 552
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 559
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 566
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 573
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 580
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 590
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 597
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 604
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 611
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 618
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 625
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 634
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 641
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 648
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 655
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 662
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 669
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 678
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 685
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 692
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 699
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 706
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 713
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 722
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 729
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 736
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 743
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 750
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 757
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 766
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 773
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 780
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 787
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 794
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 801
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 810
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 817
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 824
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 833
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 840
[warning] /usr/local/share/netxms/mibs/MOSTCOM-MIB.mib : Object identifier started with uppercase letter in line 847
[error  ] /usr/local/share/netxms/mibs/netxms.mib : Parser error - syntax error in line 1
make[4]: *** [Makefile:1437: install-data-hook] Error 1
make[4]: Leaving directory '/home/nmsadmin/netxms-5.0.0/contrib/mibs'
make[3]: *** [Makefile:1373: install-data-am] Error 2
make[3]: Leaving directory '/home/nmsadmin/netxms-5.0.0/contrib/mibs'
make[2]: *** [Makefile:1327: install-am] Error 2
make[2]: Leaving directory '/home/nmsadmin/netxms-5.0.0/contrib/mibs'
make[1]: *** [Makefile:474: install-recursive] Error 1
make[1]: Leaving directory '/home/nmsadmin/netxms-5.0.0/contrib'
make: *** [Makefile:526: install-recursive] Error 1

It would be nice to be able to have checks that would show or alert on duplex mismatches on links between devices. Like wise it would also be beneficial to have indicators on the map the shows differences between interfaces that are 10-100M or 1-10GB etc  or a difference in line width if the links are 100m vs 10GB 

Why does netxms continually try snmp communities when the community is already known ?  I have a few different community strings and netxms will still try all others even though the correct string is already configured  in the node settings. This causes issues with switches that have security measures to block snmp if failed snmp attemps are reached. As well as causing bloated logs with auth failed attempts.

I usually build from source and have no problems but for some reason my server is now dead after installing 4.5.4 from source

Details
Debian 11
Postgres 13 with timescale db extension 2.10

database was upgraded via nxdbmgr successfully

running with -D 9  gives nothing of value last lines are 

Network device driver JUNIPER loaded successfully 
Network device driver NETSCREEN loaded successfully 
Segmentation fault

What are the limits for PS ?  are there in guidelines of how many entries you can store and is this stored in a flat file on the local file system or do these also get put into the same database.