NetXMS Support Forum

On the agent side, you only enable the relevant proxy items in the configuration.
For the port forward, you only forward the NetXMS Agent port, i.e. 4700 TCP.
If you are using zoning, you'd set the default SNMP proxy for the zone to that proxy agent and any SNMP polling for nodes in the zone will automatically happen via the Proxy. Otherwise you probably have to set the SNMP proxy on each node individually.

The issue with the Alarm Browser is most likely due to you not having the "View all alarm categories" permission.
This was added in 2.1 and is not enabled by default on an upgrade. A lot of people ran into this one.

The errors in the screenshot appear unrelated (inability to store Table DCI data? Maybe some issue with the database upgrade or some table locks?).

Install an agent in the other network and configure it as SNMP proxy.
You can either setup Active Agent Tunnels to allow that proxy node to talk back to your server or you can configure a port forward on the router at the other end to the proxy node. Either way will allow NetXMS and the proxy to talk to each other.

Once you have the proxy node going, you can add the other L2 devices and poll them via that proxy node.
I would generally recommend configuring NetXMS for zoning in this scenario and configure the other site as a separate zone. That may or may not be required in your case (it is required if there are overlapping subnets).

Hi,

Just wondering, do/shoulod environment variables work in a Logwatch parser definition?
I tried using %PROGRAMDATA% and the result was that the NetXMS Agent service would not start anymore. The moment I replaced that with C:\ProgramData everything just worked. As different Windows versions use different paths, using an environment variable would be preferable to creating a number of parsers (one for each possible file location)?

Cheers

Yes and no.
The firewalls do allow configuring multiple physical interfaces as a single Bridge or VLAN interface, which in effect turns those physical ports into a switch.
Any traffic that is passed between such physical interfaces is Layer 2 only, and there is no routing involved.
Of course we also have setups where each interface is indeed in another network and then all traffic routed.

Especially smaller sites though will quite often only have one external interface and the remaining ports joined into a single VLAN interface with multiple devices connected to it.

Cheers

I just double-checked and it was part of the release notes of 2.1-M1:
- SSH subagent (for collecting data and executing actions via SSH)

Cheers

Hi,

I know I can use SSH for DCIs. Based on the 2.1 release notes, it should also be possible to use this for Actions, but I can't find documentation on how to make this work.
Are those Actions configured in an Agent configuration file or Actions that can be configured in Object Tools or both?

Reason for asking is that I am thinking of setting up some Object Tools which will run commands on routers/switches to pull some information for troubleshooting on request (without having to SSH into the device).

Cheers

Hi,

I have a few systems which I do want to be part of a zone, but I do not them to be polled via proxy.
The zone itself does have a default proxy set, as that makes sense for 99% of all systems in the zone.

How can I force this node to not use a proxy?
Only thing I can think of right now is to set the NetXMS server itself as "proxy"? Is that the correct way of doing it?

Cheers

Some ExternalParameters we call can run for quite a while (i.e. in those cases lag is expected), so we increased the ExecTimeout on those agents. Otherwise the commands ran into timeouts, the agent terminated them and we never got the results. Not sure if that is what you are experiencing? If you have really long running scripts/commands, you may also want to look at ExternalParametersProvider (we haven't used this ourselves yet, so can't give any advise on actual configuration/usage).

If your proxy is connecting to a lot of other agents/systems and polling a lot of DCIs, you may want to increase the number of MaxSessions on that proxy. I think the default is 32. We have a couple of sites where we had to increase this.

Hi,

We have around 5x the number of DCIs you have and are running on 4000 data collectors (of course this will all depend on how often you actually poll and your poller timeouts). I found that in general when I see the issue you are describing, I simply need to keep upping the number of collectors until things work as expected, and at some point possibly the database writers to ensure they can keep up.

Cheers

We're running on Linux, so no conversion required here. Looks like PEM to me.

ServerCACertificate points at the actual CA root certificate.
ServerCertificate is the intermediate certificate I created from that root. This intermediate certificate consists of the certificate and private key.
The password for that private key is stored in netxmsd.conf under ServerCertificatePassword.

The intermediate/ServerCertificate certificate looks like this:
-----BEGIN CERTIFICATE-----
[..]
-----END CERTIFICATE-----
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
[..]
-----END RSA PRIVATE KEY-----

Cheers

Hi,

1) I don't think you can store preset filters, nor can you select to only show some columns.
2) There is an "Export all to CSV" icon in the top right corner for logs (i.e. not in the Alarm Browser, but the Alarm Log).

The original post is from 2014 and the link Victor posted for the feature request no longer works, as the bugtracker system was switched in between.
However, I believe this is the new link for this request (i.e. it's still open): https://track.radensolutions.com/issue/NX-357
Note that the original request was about the Alarm Dashboard, not the Alarm or Event Logs.
There is another request for those two here: https://track.radensolutions.com/issue/NX-1052

You may want to add a comment to the above with your suggestions and/or requirements.

Cheers

Yes.
I've done that for some DCIs, e.g. created DCIs on a disk enclosures that itself could not be monitored directly, then set the source node to the server the enclosure is connected to. That way I can easily see which disks are in which enclosure (the instance discovery filter script I'm using checks for the enclosure id for this purpose).

Cheers

Hi,

There is a sticky post on the forums where people posted templates they were happy to share:
https://www.netxms.org/forum/general-support/sharing-standard-templates-for-netxms/

I have to admit, we spent a lot of time developing ours from scratch and making them work with our alerting system (unfortunately I am not at liberty to share them).
We learned quite a bit on SNMP/SNMP Traps/Performance Counters, etc. along the way. The fact that we had to build it means we understand what we are monitoring and why a lot better. But as I said, it wasn't a quick process. Mind you, we have a lot of different devices out there.

What kind of systems/devices are you trying to monitor?
If there is nothing in the forum post mentioned above, maybe someone else can help (as I said, I can't share our stuff, though I am able to give pointers)?

Cheers

Hi,

Just like everyone else, we have implemented transformation scripts as workarounds (mostly based on the speed of the interface in our case).
Of course the new counter32/64 types would be a much better solution. I assume they would actually handle resets correctly in that they calculate the traffic that occurred during the reset? As that's something our transformation script doesn't handle at all at present.
With some interfaces resetting every few minutes (yes, lots of traffic), we end up with a lot of dips to "0" at present.

For which release is this planned?

Cheers