NetXMS Support Forum

There are multiple ways of doing this. Below is auto bind script that illustrates one approach:


if (not ($container->name match "^Site:(.*)"))
   return false;
router = FindObject($1);
if (router == null)
   return false;
for(rp : router->parents)
{
   if (classof(rp) == "Subnet")
   {
for(np : $node->parents)
   if (np->id == rp->id)   // Same object
      return true;
   }
}
return false;


This script assumes that container is called "Site:RouterName", so it extracts name of the router object from own name. You can choose whatever method of router identification that suits you best. Then it checks all subnets this router belongs to, and binds all nodes from those subnets (including itself). For practical use you may have to add additional filters on what subnets to consider.

Best regards,
Victor

You can go to "Entire Network" subtree and under appropriate subnet object you'll find all nodes within that subnet.

Best regards,
Victor

Do you have reporting related logs in C:\NetXMS\log? Also, when exactly you get this error - when trying to start reporting service from Service Manager? Did you choose "hardening file system permissions" during installation?

Best regards,
Victor

Try to login with system user - maybe there is some issue with objects access rights.

Best regards,
Victor

Set debug level on agent to 6 and check agent's log for SSH related messages.

Best regards,
Victor

Hi,

you should enable web service proxy on agent by adding
EnableWebServiceProxy = yes
to config.

Best regards,
Victor

Hi,

you should add to config file of your agent the following line:

EnableWebServiceProxy = yes

This change was done for improving security. Before 3.8 read access to agent allows you to do port scan (by requesting URLs with different service types and port numbers) and even local file access (using file:// URLs).

Best regards,
Victor

Hi,

reporting server is now included as part of Windows server installer, so if you select to install it it should be properly configured as Windows service. We also did lot of internal changes to improve stability. For each report being run server now prepares view for accessing all DCIs on all nodes according to access rights of the user that starts the report - this greatly simplifies creation of DCI based reports (like top nodes with highest CPU usage, etc.). We plan to add some standard reports to the package in one of patch releases.

Best regards,
Victor

Thank you!

We have unexpected issues with deb packages, working on it.

Best regards,
Victor

Hi,

I just tried to download nxmc 3.7.144 and it starts without issues. Try to remove .nxmc from your home folder and start nxmc again. Also, make sure that you have Java 11 or newer.

Best regards,
Victor

Hi all!

NetXMS version 3.8 is released. It is minor release that provides some performance and usability improvements, as well as updated reporting server. Full change log since version 3.7:

- Improved reporting server
- Support for key based SSH authentication
- Web service proxy function in core agent now disabled by default
- Only HTTP and HTTPS are allowed in web service URLs
- Context configuration removed from global log parsers configuration views in UI
- New NXSL functions PollerTrace and SendNotification
- New method setNamedParameter in NXSL class Event
- Fixed bug in subnet mask correction
- Added Topology.RoutingTable internal DCI table
- Fixed bug on node creation
- Fixed issues:
        NX-1437 (Show tunnel connection time in tunnel manager)
        NX-1775 (Add deactivation event to list of thresholds in DCI properties)
        NX-1988 (Show full user name in user selector dialogs)
        NX-1991 (Incorrect handling of HTTP and communication errors when collecting data from web services)
        NX-1992 (Properly parse : in web monitoring parameter name)
        NX-1994 (Handle multiple agents connecting back to same node)
        NX-1999 (Make routing table available as internal table)
        NX-2000 (Snooze timer in EPP to avoid repeating actions)
        NX-2001 (Add ability to put trace messages from hook scripts to text output of status/conf/etc poll)
        NX-2004 (/objects/<container_id> REST API endpoint against container object returning error 46 - multiple JSON fields named flags)

Best regards,
Victor

Quote from: Zebble on February 05, 2021, 11:12:17 PM
Finally, slightly related but is the asterisk.nsm subagent available anymore?  It appears that the libosip2/libXosip2 library dependency is really old and unsupported with newer version of openssl, so is difficult to build on more modern build environments.

Asterisk subagent is supported. We provide binary builds for all supported Debian and Ubuntu versions. Ubuntu 20 does not have libexosip2 package, but when you install Asterisk subagent from our repository it will bring our build of libexosip2. If you build from sources, you can download and build libosip2 and libexosip2 version 5.2.0 - they are fairly new and seems to be building without issues on modern distributions.

Best regards,
Victor

Looks like DB issue. Do you have any DB-related errors in log?

Best regards,
Victor

This is done by alarm keys. When you create "problem" alarm, you create event processing policy rule that do "generate alarm" and here you can set the key. For terminating you create another rule that handles recovery event and do "terminate alarm" with the given key. You can look at rules for SYS_NODE_DOWN and SYS_NODE_UP events.

Best regards,
Victor

P.S. Questions like this have much more chances to be responded quickly if placed into correct section on forum. "Development" section is intended for developing of product itself or using it's APIs, so many users simply never look at posts there.

Это баг в NXSL интерпретаторе, уже починили. В следующем релизе будет работать.