NetXMS Support Forum

I believe there is an open feature request to "cache" instance discovery DCIs so they are not deleted right away but only after some time (or a number of polls, but ideally something that is configurable per instance discovery DCI).

Are there plans for an implementation in one of the next 2.1 releases?

Cheers

You need one agent in the network to act as proxy.
Other than that, you can monitor everything else in that network using SNMP only via the above agent/proxy.
Just set that agent as your default proxy for the zone in question and ensure you add the other SNMP devices to that zone.

I'm glad you got this working for your setup.

If you ever want a template for "any IIS" with "any AppPool", which you can automatically apply to all Window Servers running IIS, you will need some kind of instance discovery/list to take care of providing a list of AppPools to NetXMS though (but at least you won't need PowerShell to return the status itself).

I guess this could roughly be achieved by:
- Setting up an ExternalList in the NetXMS agent to return the names of all AppPools
- Writing a PowerShell script to return AppPool status for a given AppPool
- Configuring the NetXMS agent with an ExternalParameter to call that script, accepting the AppPool name as a parameter
- Configuring your DCI in NetXMS to use instance discovery using the ExternalList and ExternalParameter you created.

Under the Entire Network tree, nodes will show in the zone that they belong to.
Assigning a node to a zone will assign the default proxy agent for that zone to it.
On the other hand, manually assigning a proxy agent to a node does not make that node part of the proxy agent's zone.

Are you having any specific issues with your proxy/zone setup which you are trying to resolve?

Hi,

This little line in the Changelog got me all excited: "Experimental agent-to-server connections (agent tunnels)"
But how do I experiment with these experimental connections?

Cheers

Hi Victor,

Just installed 2.1-M3. While the MIB Browser no longer shows Hex-STRING in M3, it now shows INTEGER, COUNTER, etc., i.e. the type, but not but not the actual values.

It looks like there's a column (header) missing. It shows the OID, then the "human readable" version of the OID (which shows under the header "Type") followed by the actual type in the column "Value". The value itself is not in the list at all.

Cheers,
Tursiops

Hi,

I seem to be having an issue where instances just disappear.
The reason appears to be that if more than one polling method is enabled, unless all of them fail, the node is not considered to be down.

If the node isn't down, it'll happily run Instance Discovery.
Of course if the agent or SNMP do not respond (but the other does, or ICMP may be working and part of polling), then instance discovery will fail to discover any instances.
That's when it seems to wipe any existing instances.

Has anyone else encountered this?
If that's not just some oddity at our end, maybe instance discovery should only run for agent related items when the agent is considered to be up, same for SNMP. If the agent or SNMP do not respond when instance discovery starts, the results should probably be discarded, to avoid losing all history on existing instances?

Cheers,
Tursiops

You install a NetXMS agent at the other sites and configure it as a proxy node. If required, setup a port forward for port 4700 to that proxy agent, so the server can communicate with it.
Install additional agents, setup SNMP, etc. as required at each site, ensuring that the proxy agent has access to those additional agents (i.e. the proxy agent is the "master server" for those additional agents).

Your NetXMS server will communicate to all other devices/nodes on those networks via those proxy agents. You configure that part either via zone defaults or directly on the nodes.
There is no need for multiple NetXMS servers.

We are monitoring dozens of different sites like this.

We're using LDAP/AD and it works fine.
What does your NetXMS server configuration look like? Does it have access to your domain controller (firewall or user authentication issues)? Are your search base and filter correct? Does your SyncUser exist?
Can you show us your existing configuration (of course without providing usernames/passwords)?

Hi,

I did not need to use the MIB Browser in a while as most our templates just chugging along nicely.
The other day I had a new device type to add and when I tried to use the MIB Browser the result was that every single OID in a full SNMP walk returned "Hex-STRING".
I then went and tried walking other devices which have working templates and SNMP DCIs applied to them: same result.

From what I read, Hex-STRING is what NetXMS shows when there are non-printable characters in the result.
Considering I used the MIB Browser extensively in the past to create templates and now none of the dozen devices I tested are returning anything but Hex-STRING - in the MIB Browser only. DCIs happily return correct data.

I would have last used the MIB Browser while running M2.1-M1, so I am guessing this to be related to 2.1-M2.
This happens in the console as well as the web interface.
Has anyone else seen the same issue?

Cheers,
Tursiops

I suggest submitting the original issue in the Bug Tracker (https://www.radensolutions.com/chiliproject/projects/netxms).
Not being a developer, I didn't call it a bug as it looks to me like the functionality you are looking for was never implemented (i.e. it's not broken, it's missing).

The "Interfaces" tab exists in the web interface on our installation (see attached screenshot; from a server with a single NIC) and can be reached in the same was as in the console. Not sure why it would not be visible in yours.

Not knowing what kind of notes you are leaving, most objects allow you to set "Comments", e.g. containers, nodes, interfaces.
So it would be possible to leave notes on specific objects that those notes may relate to.

Of course you could create a container called Notes, setup "fake nodes" that don't monitor anything and just enter comments in there.
Not quite the same as a "Notes Library" and may be completely unsuitable to your needs.

Hi,

I was wondering if it would be possible to add a feature where one can select as which user to call an ExternalParameter.

To give an example, I use a PowerShell script to monitor DFS Replication Backlog on Windows. The script works fine, but it cannot run as "SYSTEM". It requires a user with administrative privileges to run it.
Obviously I would not want to run the NetXMS service as such a user.
Storing credentials on the system being queries does not seem like a good idea.
Setting up specific user and reconfiguring DCOM and other parts of the system to use a locked down account makes setting up monitoring a very manual process.
Same with setting up a scheduled task on the system (which is what I'm doing right now) to collect the data, dump it into a file and then use NetXMS to read the result.

Being able to call the ExternalParameter with an additional username/password which could be configured inside the DCI would allow this to "just work" straight from a template (except for then manually configuring the credentials per system as required - not sure if that would break the Template/DCI relationship).

Cheers,
Tursiops

A tool that lets you enter the table's index OID, will fetch all OIDs underneath, link it up to your MIB table and present it with a tickbox style interface "Which of these items would you like to query?" and some drop downs/checkboxes reflecting the current Columns configuration options.

Maybe that could be a feature request?