NetXMS Support Forum

Hi,

Do you mean you deployed sql server 2014 for your NetXMS database?

What version of the agent are you deploying?

How are you deploying it?

Please post the nxagentd.conf from a machine with the error.

Please post a screenshot from the event log.

Ted

Hi,

Server is NetXMS 3.2.380/Windows, Agent is NetXMS 3.3.314/WIndows.

I work for an MSP (Managed Services Provider), and I'd like to setup NetXMS to monitor all of our clients, and be able to do so through on a single NetXMS server at our site.  We, and all of our clients, have a single external (static) IP address, and internally have private IPs (192.168.x.y) and use NAT.

Zones seem to be the way to do this (section 36.1)

I'm trying to get it working on one client, but am having trouble. Here is what I have done (we have a good, working NetXMS installation at our site already).

1. I created a new Zone (right-click Entire Network -> Create zone).  I noted that zoneUIN=3.
2. I created a new proxy node (right-click Infrastructure Services -> Create -> Node).  Checked "Create as zone proxy" box and selected the appropriate Zone from the drop-down menu.  The agent system is Windows, so I did not config SSH login/password.  Left all else as defaults.
3. I added Port Forwarding rules for port 4700 on our firewall and the client firewall.
4. I installed the NetXMS agent to serve as the proxy agent on one system there, with this nxagentd.conf:

MasterServers = (external ip address of our NetXMS server)
ConfigIncludeDir = C:\NetXMS\Agent\etc\nxagentd.conf.d
LogFile = {syslog}
FileStore = C:\NetXMS\Agent\var
SubAgent = filemgr.nsm
SubAgent = ping.nsm
SubAgent = logwatch.nsm
SubAgent = netsvc.nsm
SubAgent = portcheck.nsm
SubAgent = ssh.nsm
SubAgent = winperf.nsm
SubAgent = wmi.nsm

EnableProxy = yes
ZoneUIN = 3


5. From the NetXMS Console, I right-clicked the Proxy object I created under Infrastructure services, Poll -> Configuration (full).

What was working
The server connected to the agent, and read the default DCI set, and the "Object Details" of the Proxy Node are populated.  Server-Agent communication was happening.  "Software Inventory" and "Hardware Inventory" never worked, as they do for nodes on the local LAN.  (But communication stopped, see next section.)

What isn't working
0. Under the zone, it shows two networks.  One is "113.11.246.0/24" which is a subnet NetXMS made up, based on the single external IP address.  I can just ignore that.
1. The second network is the internal client private network (192.168.x.y/24) which is correct.  However it only has "found" one address (the Proxy Node), but it hasn't found it correctly.  It has "192.168.14.254" as the address of the Proxy Node, but that is actually the address of the firewall (or default gateway).  So now the Proxy Node is marked as Unreachable even though it is reachable.
2. Discovery doesn't seem to be happening, probably because of #1.  I started a manual network scan (Configuration -> Network Discovery -> network address=192.168.14.0, mask=24, Zone=client zone, Proxy=client proxy, Click 'save' icon -> Scan.  Waited an hour but no new nodes are listed under the network.

How do I configure NetXMS so that it knows the correct, internal address of the agent?  I've read section 39.3 of the manual but there isn't a setting to tell the agent what its IP address is?
How do I get scans working?
On other client systems at the remote site? What do I use for the NetXMS server ip address value?  The proxy node IP address?  Do I have to config the zoneUIN on all the agents? I couldn't find anything about this.  Here is an nxagentd.conf file from the client site.
MasterServers = 192.168.14.23
ConfigIncludeDir = C:\NetXMS\Agent\etc\nxagentd.conf.d
LogFile = {syslog}
FileStore = C:\NetXMS\Agent\var
SubAgent = filemgr.nsm
SubAgent = ping.nsm
SubAgent = logwatch.nsm
SubAgent = netsvc.nsm
SubAgent = portcheck.nsm
SubAgent = winperf.nsm
SubAgent = wmi.nsm

ZoneUIN = 3

I feel I'm mostly there, but missing a setting or two.  What have I done wrong?

Thank you in advance,
Ted

Thank you, that was it.

The client and server were working correctly. I *thought* I'd configured an Event Configuration item, but I hadn't.  Thank you.

Seeing the same thing on NetXMS server 3.2.380 on Windows.

Windows Event Log config on client seems OK, but how to configure it on the server?

On a NetXMS Agent I have:
In nxagentd.conf:
SubAgent = logwatch.nsm

In nxagentd.conf.d\custom.conf I have:
[LOGWATCH]
Parser = C:\NetXMS\etc\parser1.xml

In c:\netxms\etc\parser1.xml I have:
<parser>
   <name>parser1</name>
   <!-- *SYSTEM means Windows System Event Log -->
   <file>*SYSTEM</file>
   <!-- more <file> tags can follow -->
   <rules>
      <rule>
         <match>(.*)</match>
         <id>7</id>
         <level>3</level>
         <!-- use this for testing, then comment out and uncomment 'disk' below for production -->
         <source>blueberries</source>
         <!--
         <source>disk</source>
         -->
         <event>SYS_NODE_CRITICAL</event>
      </rule>
   <!-- more <rule> tags can follow -->
   </rules>
</parser>

Then I generate an event from the command prompt with:
eventcreate /t error /id 7 /l System /d "Test-Ignore" /SO "blueberries"

When I do this, in the nxagentd log I get:
2020.04.16 11:03:13.673 *D* [                   ] PostEvent(): event_code=0, event_name=SYS_NODE_CRITICAL, timestamp=1586995393, num_args=7, arg[0]="Test-Ignore", arg[1]="blueberries", arg[2]="7", arg[3]="1", arg[4]="266817", arg[5]="1", arg[6]="Test-Ignore"


And on the NetXMS server, I get no indication in the GUI that anything happened.  In the server log, I do see:
2020.04.17 15:29:47.966 *D* [agent.conn.4       ] Received message CMD_TRAP (0) from agent at 192.168.16.111
2020.04.17 15:29:47.966 *D* [agent.conn.4       ] AgentConnectionEx::onTrap(): Received trap message from agent at 192.168.16.111, node ID 187
2020.04.17 15:29:47.966 *D* [agent.conn.4       ] AgentConnectionEx::onTrap(): trapID is valid
2020.04.17 15:29:47.966 *D* [agent.conn.4       ] Event from trap: 10
2020.04.17 15:29:47.966 *D* [event.corr         ] CorrelateEvent: event SYS_NODE_CRITICAL id 56588 source gordon.odcvu.local [187]
2020.04.17 15:29:47.966 *D* [event.corr         ] CorrelateEvent: finished, rootId=0
2020.04.17 15:29:47.966 *D* [event.proc         ] EVENT SYS_NODE_CRITICAL [10] (ID:56588 F:0x0001 S:4 TAGS:"NodeStatus") FROM gordon.odcvu.local: Node status changed to CRITICAL


I think I have the client configured correctly.  And the server is receiving the CMD_TRAP.  What do I need to do on the server to have it register these and show alarms, and have the node actually get changed to 'CRITICAL'?

Thanks in advance!

Thank you.  I would suggest this information is added to the dialog box when you setup new Tools.  Thanks again for your help.  It does work as expected when I run nxmc!

System: NetXMS 3.2 on Windows Server

Problem: Can create a new Object Tool (Configuration -> Object Tools -> (new), for RDP but new ones never appear in the context menu of objects (right-click an object, Tools).

Another user posted this same problem in 2018 (https://www.netxms.org/forum/general-support/object-tools-rdp/) but received no replies this issue.

Video screenshot showing what I am doing and how the new Tools do not appear:
https://drive.google.com/file/d/1bPntSCtsTi4CTlbK75b2DPtyoy8YgN5a/view?usp=sharing

Has this been fixed?  What am I doing wrong?

Thanks,
Ted

Here's how I SSL-enabled by NetXMS WebUI, the fast and easy way.  I come from a Linux background so I used stunnel, which is a utility that can SSL-enable any connection quickly and easily.  It is so reliable you forget it is there.  I'm new to the other utility listed here, nssm, but it made creating a new service a piece of cake (yes, I know about sc).

System: NetXMS 3.2 listening on the default port of 8080 on Windows Server 2019

Download two files:
stunnel from https://www.stunnel.org/downloads.html
nssm from http://nssm.cc/download

Install stunnel using the installer.  It will have you create a new self-signed certificate.  If you want to use a signed one, there is plenty of info out there on how to do that.  If stunnel starts, stop it using the tray icon or kill it.

Edit the stunnel config file (C:\Program Files (x86)\stunnel\config\stunnel.conf) and find the "TLS front-end to a web server" and make it look like this:

; TLS front-end to a web server
[https]
accept  = 443
connect = 8080
cert = stunnel.pem


Download and unzip nssm to c:\software\ or another non-user-specific location (e.g. c:\program files\ ).
Open an Administrative command prompt and run nssm like:

"C:\software\nssm-2.24\win64\nssm.exe" install stunnel


Browse to and select the stunnel executable ("c:\Program Files (x86)\stunnel\bin\stunnel.exe"), enter a description of "SSL for NetXMS" and click "Install Service"
Go to Services and start the service.

Browse to your NetXMS server using https://netxms.my.org/nxmc  (don't forget the nxmc).

Yes, you have to add the /nxmc at the end.

Worked great for me, hope it helps someone else who doesn't want to setup an IIS reverse proxy, etc.  YMMV.

Ah that does it.  Thank you!

I've seen a few (old) posts of people saying they created a slideshow, but I can't see where to do this?

Do I need to create and script a scheduled task?  Or is there something built in to define a series of dashboards to cycle through, and how long to stay on each?

Thanks!