NetXMS Forum

Hi, you can run agent and server as any user. If you start them as a service, you can use configuration file parameters UserId and GroupId or command line options -u and -g to change effective uid/gid after startup. For server it is recommended to enable raw socket access (required for ICMP ping) as described here: https://wiki.netxms.org/wiki/How_to_enable_ICMP_ping_for_NetXMS_server_running_under_non-root_account Yes, rpm packaged are planned. Best regards, Victor

Try to run both agents with debug 6 and check what is logged when connection attempt is made. Best regards, Victor

Hi, in 2.2.3 we have added fix for incorrect value type in transformation script. If you are running older version, try to change transformation script to return uint64($1) * 8; Best regards, Victor

Hello Victor , Never registered a ticket, where i can do this ?

Hello Victor , Thanks. Upgrade is planed for the near future. Anyway i changed the sync interval to 500 and now i get 1 alarm every hour. Still i am not sure how important is this and could i totally ignore the alarm in the event policy, so we don't receive the spam.

Hi! Yes, there is! You can find it in the management console under View --> Alarm log, there you can set custom filters to show the alarm history of specific devices. The size of the alarm history can by configured using this server configuration parameter "AlarmHistoryRetentionTime" which will set the number of days to keep the alarm history. Regards, Eriks

Hi, If you have the email address as one of the attributes of the users in LDAP, simple change the "LdapMappingName" parameter value in NetXMS server configuration to the name of that attribute. When users are synced from LDAP into NetXMS, the attribute configured in "LdapMappingName" is used as the login name.

Maybe related to this one? https://www.netxms.org/forum/general-support/problems-with-ping-subagent-after-update-to-v2-2-1/

Hi, it seems like a bug to me. Could you provide more detailed information about one such device (how it looks like in the system, log file parts and events related to that device)? Best regards, Victor

Hello Tatjana, team, I can confirm that "Remove this template automatically when node no longer passes through filer" option is selected. Thanks for pointing my mistake out. I will check if this is the issue here and will update. Best regards, Adrian

Hi, are you using cache mode for agent? It seems like corrupted data collection configuration on agent side, when agent sends both correct data and data for some other DCI. If yes, please check what is configured in table dc_config in agent local database. You may also try to delete agent local database (while agent is stopped) - it should reconfigure on first configuration poll. Best regards, Victor

Hello Victor, team, I am using SNMP to collect this. The server version is 2.0.7 and the agents are NetXMS Core Agent Version 2.1-RC1 Build 9010 (UNKNOWN) (UNICODE). Best regards, Adrian

Hello , I have a script which returns custom attribute to my devices. Now i made a script as external parameter which i am using as DCI. I set up everything and it seems to be working. I am passing two parameters to the DCI first one is from the custom attribute script and the second one is the node_primary_ip. I am applying this in a template, as follows: RStatus(%{script:CustomAttributeSetScript}, %{node_primary_ip}) This is returning the correct parameters in the DCI, but the DCI is not polling at all. If i want to get status for the DCI i must force poll it. If i give the Custom Attribute parameter value manually it is working with no issue and polling on the interval I set up. Best Regards, Adrian

Hey Tursiops, As expected putting "return" statement in the script solved my issue. It is working like a charm now. Again, thanks for the help! Wish you all the best.

Hello Team , Issue is solved. The problem was with the time for the SQLlite select query (it was taking too long 40-50 seconds). It was solved by backing up the local database. separating it in small pieces and import the pieces one by one.

Hi! Server can read ARP cache and routing table from agent and use it for passive network discovery. Active network discovery through agent is not supported. Discovery itself (and filtering) occurs on server, agents just provide ARP and routing information. No, discovery polls only run on schedule. Depends on where you have information about those nodes and in what format. It could be easier to write simple nxshell script that will read information from external source and create nodes in the system. Best regards, Victor

Thanks for the help ! Best Regards, Adrian

Hi, seems to be a bug. We will investigate it further. I've created issue in our tracker (https://track.radensolutions.com/issue/NX-1148). Best regards, Victor

Hi, this is correct behavior - instance here is OID instance, which is determined by OID suffix (part after walk base). If you want to give other name to the instance, you can use instance filter to change it (and in DCI description you can use {instance-name} then). For example: return %(true, $1, "New name for " . $1); Best regards, Victor

Hello team , Turned out that the files were corrupted, downloaded them again and repeated the procedure, everything is working fine now. Best regards, Adrian