NetXMS Support Forum

Hi,

yes, will do it before 2.0 release. I've added an issue to track: https://dev.raden.solutions/issues/842.

Best regards,
Victor

MAC address will be all 0s if node do not have SNMP nor NetXMS agent. If node will be added to NetXMS MAC address will be replaced with correct one read from ARP cache later on. Do you have sny discovery filters that may prevent nodes from being added?

Best regards,
Victor

Hi,

currently there is no way to get FDB information into DCIs. I can add a function to read FDB entries for node in next release, then you'll be able to create scripting DCI or poller hook to control it.

Best regards,
Victor

Hi,

currently NetXMS only probes standard SNMP port during discovery. You can fill feature request in our bug tracker to add list of possible SNMP ports to probe (in a same way we do for SNMP communities).

Best regards,
Victor

Hi!

I suppose this is configuration to allow Brekere SIP server to expose internal metrics via snmpd. So you still have to do it on your server, and then setup NetXMS to access SNMP on that server and read SNMP parameters as usual. Do they provide MIB file as well?

Best regards,
Victor

Hi,

I've just uploaded Windows agent installer with a fix.

Best regards,
Victor

Hi all!

NetXMS version 2.0-M5 is out. Changes since previous release:

- Agent-side caching of collected data
- Fixed bug in handling floating point Windows performance counters
- Added "comments" attribute to NXSL "DCI" class
- New NXSL function sha256
- Fixed broken nxagent.sms SMS driver
- Added support for SNMP traps over IPv6
- Switched to SHA-256 for password hashing
- Timestamp can be provided in nxpush and nxapush
- New methods in NXSL class "Event": setMessage, setSeverity, setUserTag
- Command line options for nxagentd to change effective user and group after start
- Fixed occasional NXSL compiler crash on scripts with syntax errors
- Errors in auto bind/apply scripts interpreted as "ignore" instead of "false" result
- New core agent parameter File.FolderCount
- Fixed broken active discovery
- Improved system behaviour on large installations
- Management console:
   - Fixed broken VPN connectors configuration
   - "Inverted values" option on line charts
   - Filter in predefined graphs tree
   - Values of selected DCIs can be shown on object overview page
   - "Stacked" option added to line charts on dashboards
   - In-place file rename in file manager
   - Option to export data from line charts on dashboard to CSV file
   - "Select all objects" option in network maps
   - "Proxy node" option in DCI properties renamed to "Source node" to avoid confusion
- Android Console:
   - Added "capabilities" in node overview (changed to expandable list view)
- Fixed issues: #50, #630, #780, #781, #791, #794, #797, #798, #806, #815, #816, #817, #824, #832, #833, #837

Best regards,
Victor

Hi!

No, there are no such standard functionality. However, if you are familiar with Python programming language, you can create simple tool using nxshell that will export node configuration from container into file and then import it into another server. More information about nxshell can be found here: https://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations.

Best regards,
Victor

Hi,

in DB.Query you specify actual SQL query to be executed, like this:

DB.Query(dbid,"SELECT col FROM my_table")

If you specify query in agent's config then it is executed in background and DB.QueryResult returns cached result from last run. Pre-configured queries are good when you have long-running query - if you use it directly server request may fail on timeout. If you have simple query that executes in less than a second you can use DB.Query.

Best regards,
Victor

Hi,

the problem is that in transformation script you got table as it received from agent. If you want to fill additional column in transformation script you should add it in script like this:

$1->addColumn("Col6");

Best regards,
Victor

Параметр ConfigurableQuery создает запрос который выполняется только по запросу с сервера. Обычно он используется для создания новых метрик с параметрами. Если вам нужен запрос, который выполняется агентом в фоне, то надо использовать Query.

Hi,

there is a bug in active discovery code (it was brojken when we add IPv6 support in 2.0-M3). I fix it in 2.0-M5.

Best regards,
Victor

Мы сейчас собираем и выкладываем 2.0-M5, в этой версии было исправлены несколько утечек. Если обновление не поможет, то будем разбираться.

Только если использовать какую-то внешнюю утилиту для отсылки писем вместо встроенного SMTP клиента.

Hi,

the you have to set search base to the top of the tree, and filter out non-IT users in LDAP search filter. Filter to include only users from IT OUs could look like following (not tested):


(ou:dn:=Information Technology)


I took the OU name from log posted earlier: "CN=a1,OU=Information Technology,OU=Staff,OU=xxx1,DC=mycompany".

Here is more information on such filtering: http://help.globalscape.com/help/eft6/Advanced_LDAP_Filtering.htm.

Best regards,
Victor