NetXMS Support Forum

Hi all,

NetXMS version 2.0.7 is released. It is another patch release for stable 2.0 branch, and likely last release for this branch. Changes since release 2.0.6 are following:

- Number of polls can be set for "diff" type thresholds
- New method "enableDiscoveryPolling" in NXSL class "Node"
- New NXSL functions: AgentExecuteAction, GetAllNodes
- NXSL functions GetNodeInterfaces, GetNodeTemplates, GetNodeParents, GetObjectChildren returns correct object classes
- Instance discovery scripts can return instances as map instance/instance name
- SMS driver for Nexmo service
- SMS driver for SMSEagle gateway
- SMS driver for MyMobile service
- H3C driver correctly reads IPv6 addresses on interfaces
- Added support for CHAP, MS-CHAPv1, and MS-CHAPv2 in RADIUS authentication
- Fixed FreeBSD 11 compatibility issues
- Fixed excessive memory consumption by web UI in some situations
- Fixed server crash when changing scheduled tasks
- Fixed various minor UI glitches
- Fixed issues: #1090

Best regards,
Victor

Hi,

there was a bug in text2reach driver build, so reference to libcurl was not added to driver's binary. It was fixed in version 2.1-M1 and upcoming 2.0.7. As workaround you can pre-load libcurl before starting netxmsd.

Best regards,
Victor

Hi,

check if libcurl is installed and what version.

Best regards,
Victor

Hi,

there are also driver for text2reach (http://www.text2reach.com/?language=en).

Best regards,
Victor

Hi,

please run nxdbmgr upgrade with -t option and post output.

Best regards,
Victor

Hi,

for menus and buttons & character precedes letter that will be used as keyboard shortcut. So for example text

Show &object details

will be displayed as

Show object details

and letter "o" will be keyboard shortcut (and depending on the system will be underlined).

It is better to use existing shortcuts when possible as they are non-overlapping - but if not possible you can choose different shortcuts - it can be fixed later.

Best regards,
Victor

Hi,

search for MAC address works only using FDB on switches - so if you don't have your switches in the system it won't find anything. If you do have switches managed by NetXMS, than it is probably a bug. In that case, could you please show FDB for the switch where this node actually connected?

Best regards,
Victor

Hi,

1) currently no;

2) it is known issue that should be solved in 2.1 (and possibly in 2.0.7).

Best regards,
Victor

Hi,

in second PostEvent you pass DCI name as tag, not as first event parameter. You have to insert null there (as in first PostEvent call).

Best regards,
Victor

Это баг. Исправили репозиторий.

ubnt можно мониторить через агента (он использует http/https) - https://wiki.netxms.org/wiki/Ubiquiti_and_Ligowave_wireless_monitoring

Уже перенесен в 2.0 ветку, будет в релизе 2.0.7.

Hi,

yes, logwatch is a correct choice. Parser could be following:

<parser>
   <file>/path/to/log/file</file>
   <rules>
      <rule>
         <match>Failed to connect to FX Server</match>
         <event>FX_SERVER_CONNECT_FAILED</event>
      </rule>
   </rules>
</parser>


and add the following to nxagentd.conf:

# this is main section
SubAgent = logwatch.nsm

[LOGWATCH]
Parser = /path/to/parser.xml


you have to create event FX_SERVER_CONNECT_FAILED on server (of course you can name it differently) - it will be generated each time this string will be found in log file.

Best regards,
Victor

Hi,

there is a bug introduced in 2.1-M1 - SMTP sender do not accept loopback addresses. I'll fix that for next release. In the meantime you can use server's external IP as mail server address.

Best regards,
Victor

Hi,

topology poll can be started via nxadm:

nxadm -c "poll topology <node_id>"

Best regards,
Victor