Hi Victor, Can you give me an example? Thanks

  @victor said in Primary hostname will not resolved to Primary IP Address: I've register a change request to use agent for DNS resolution for remote zones: https://dev.raden.solutions/issues/778. Should not be hard to implement. Best regards, Victor   Thanks

A few updates today to make the module compatible with 2.0-M releases and forwards. Changelog: apt::netxms_repo - allow specifying which NetXMS apt repo to use Documentation - fixed a few minor errors - updated 'apt::netxms_repo' class documentation

Yes, that could happen if there was incorrect data in event processing policy. You have to manually fix or delete those rules. Best regards, Victor

Yes, nodes will be rediscovered - the only problem if you have configured some data collection on them - all collected data will be lost. If this is not the case then you can just delete them with subnets. Best regards, Victor

Thanks info victor! This would be added to our wish list

Looks like result of database corruption. If I remember correctly lost_interface_#### objects was created in some older versions after errors. Current version should not create them. As they likely had unreachable IP addresses, status poll just take longer due to timeouts. Best regards, Victor

Hello Alex, thanks a lot for your help! Is it possible to use this script to modify the interface Fixed Propagated Status? Thank.

Hi, O_RDONLY means that agent wants read only access to the file. Sharing mode is controlled by third argument, which is set to _SH_DENYNO, meaning that agent allows both read and write shared access to the file. However, the problem may be with the application writing to the file - if application requests exclusive access (i.e. not permitting read access by others), it will not be able to open file for writing. We cannot do anything about it. If you can control the application in question you can change it or request application developers to allow shared read access to the log. Best regards, Victor

That worked but seems like some earlier version pushed install with -D 0 on the service though so the debuglevel config did not work at first but uninstalled and installed new and now it works. Now to the main problem it seems like it ignores the database setting no entry in debug log about this, all i get is: [INFO ] Subagent "dbquery.nsm" loaded successfully Then nothing until it tries query and get: [DEBUG] [session:0] Requesting table "DB.Query(db1,"select Count(*) from ***")" [DEBUG] DBQUERY: H_DirectQueryTable: no connection handle for database db1 EDIT: Problem solved i have missed "*DBQUERY" in the config above Database

The nodes responded to pings from the server.  So I took another look at my discovery settings, and then recalled I had filtered out the upper end of the IP address ranges of those networks when I initially installed NetXMS ! I modified those filters, saved it, and within 5 minutes, NetXMS discovered the missing nodes... chalk this up to pilot error -Kevin C.

Hi, It's quite easy, just add the devices as source objects to the built-in Event Processing Policy named "Show alarm when node is down".  Also, you will probably want to add them to the related policy named "Acknowledge node down alarm when node is up". -Kevin C.

hi, i have installed the 64 bit version and i seems that the console is not included in the installer. the setup says it could not find the file. i think you forgot to include the console installation since the download file size is too small compering to previous versions. Regards, Lindeamon

thanks for that!

Hi, Victor How to solve this problem? Thanks for your help！ Best regards, jovi.

I am having an issue with NetXMS not being able to read Inbound/Outbound traffic on any interface. I am able to connect to the router with SNMP and get status of the interfaces and ARP caches and such. However when I try and create a DCI for bandwidth it does not show up. When I go to Last Values, it displays nothing but the timestamp is "31.12.1969 16:00:01" (PST local). I have tried both Sophos and NetXMS suggested Data Parameters (.1.3.6.1.2.1.31.1.1.1.6.{iface number}). I am unsure where to go from here. Anyone have any ideas or suggestions? Note: I can get bandwidth to register with Intermapper just fine.

Hi, yes, it's a bug. I just fixed it - fix will be included in 2.0-M3 release. Best regards, Victor

Gads.. I forgot to run ldconfig.  Thanks.  I'm so used to packages these days I forget how to do this old-school.

Hello, I try to access a Node from Condition's Status calculation script using FindNodeObject() method. The function still returns null, probably because the Condition isn't in the Node's "Trusted Nodes" list. But I can't add the condition there, because conditions are hidden in the tree when I click Add in "Trusted Nodes". FindNodeObject() works correctly if CheckTrustedNodes is set to 0 in Server Configuration, but it's only a workaround. Version of NetXMS used: 2.0-M1.

OK, this looks like a very powerful tool. Unfortunately I'd want to create a SNMP Table tool which (according to the admin-guide) doesn't support neither macro substitution nor setting a target IP. And without the target IP setting I can't predefine a SNMP Table tool which is independent on IP of the selected node.