NetXMS Support Forum

I found something in NetXMS source, nxclapi.h


/**
* Node flags
*/
#define NF_SYSTEM_FLAGS           0x003FFF7F
#define NF_USER_FLAGS             0xFFC00080

#define NF_IS_SNMP                0x00000001
#define NF_IS_NATIVE_AGENT        0x00000002
#define NF_IS_BRIDGE              0x00000004
#define NF_IS_ROUTER              0x00000008
#define NF_IS_LOCAL_MGMT          0x00000010
#define NF_IS_PRINTER             0x00000020
#define NF_IS_OSPF                0x00000040
#define NF_REMOTE_AGENT           0x00000080
#define NF_IS_CPSNMP              0x00000100  /* CheckPoint SNMP agent on port 260 */
#define NF_IS_CDP                 0x00000200
#define NF_IS_NDP                 0x00000400  /* Supports Nortel (Synoptics/Bay Networks) topology discovery */
#define NF_IS_SONMP               0x00000400  /* SONMP is an old name for NDP */
#define NF_IS_LLDP                0x00000800 /* Supports Link Layer Discovery Protocol */
#define NF_IS_VRRP                0x00001000  /* VRRP support */
#define NF_HAS_VLANS              0x00002000  /* VLAN information available */
#define NF_IS_8021X               0x00004000  /* 802.1x support enabled on node */
#define NF_IS_STP                 0x00008000  /* Spanning Tree (IEEE 802.1d) enabled on node */
#define NF_HAS_ENTITY_MIB         0x00010000  /* Supports ENTITY-MIB */
#define NF_HAS_IFXTABLE           0x00020000  /* Supports ifXTable */
#define NF_HAS_AGENT_IFXCOUNTERS  0x00040000  /* Agent supports 64-bit interface counters */
#define NF_HAS_WINPDH             0x00080000  /* Node supports Windows PDH parameters */
#define NF_IS_WIFI_CONTROLLER     0x00100000  /* Node is wireless network controller */
#define NF_IS_SMCLP               0x00200000  /* Node supports SMCLP protocol */
#define NF_DISABLE_DISCOVERY_POLL 0x00400000
#define NF_DISABLE_TOPOLOGY_POLL  0x00800000
#define NF_DISABLE_SNMP           0x01000000
#define NF_DISABLE_NXCP           0x02000000
#define NF_DISABLE_ICMP           0x04000000
#define NF_FORCE_ENCRYPTION       0x08000000
#define NF_DISABLE_STATUS_POLL    0x10000000
#define NF_DISABLE_CONF_POLL      0x20000000
#define NF_DISABLE_ROUTE_POLL     0x40000000
#define NF_DISABLE_DATA_COLLECT   0x80000000


and it seems in my case, that regular Pool configuration sometimes pick-ups that ICMP should not be monitored for this Windows Server node.

Can somebody confirm me that I am on correct track to solve the issue ?

Thank you

I also agree it is a small bug, and I hope that NetXMS team will add id to Issues list: https://www.radensolutions.com/chiliproject/projects/netxms/issues

NetXMS team , anyone ?
I still not understand how to enable DNS resolution every time on pooling ...

Hi,
I use great NetXMS to monitor lot of Windows Server nodes, but only on one I have constantly a new alert generated (few times a day) :

Node capabilities changed (Old: 0x090C0002; New: 0x09040002)

Can somebody explain in more detail what were old and what are new capabilities, so I will try to figure out what is causing it, and stop necessary alerting.
(I do not want to turn of this alerting, just to solve problem causing it)

Thank you

Hi,
thank you, currently I am interested more in NetXMS database - https://www.netxms.org/documentation/NetXMS_data_dictionary.pdf
I am interested in table node, description, for example NODE_FLAGS.
Some info is here, but not quiet clear: http://wiki.netxms.org/wiki/NXSL:Node

Addionaly, NetXMS administrator guide, has unfinished chapters (only header/heading name).
https://www.netxms.org/documentation/netxms-admin.pdf

Thank you

Quote from: Victor Kirhenshtein on April 29, 2014, 07:21:35 PM
Hi!

Agent cannot use UDP for communications. It's just standard practice to assign both tcp and udp port numbers - I didn't even request udp ports.

Best regards,
Victor

Documentation says that it needs tcp and udp. Sometimes it is hard to port forward both (some ISPs charge by port etc.)
Also, for example Windows Agent adds two firewall rules, seperate tcp and udp.

So to resime, UDP is not needed at all.

Thank you for info.

Quote from: Victor Kirhenshtein on March 31, 2014, 11:48:42 AM
Hi!

Currently it's useless (I should hide this menu item). It's incomplete functionality which will allow you to create rack objects and put nodes inside to indicate how physical equipment located in racks.

Best regards,
Victor

OK, thank you, but the plan for implementing this feature exists and future will function properly in some of future versions ? I do not see this in roadmap...

Thank you

NetXMS Agent service, which is configured as a Proxy, should be able to receive SNMP traps, and Syslog messages from local network and relay them / proxy them to the NetXMS server.

I hope this will be implemented.

Hi,
as I saw documentation, it always says that NetXMS Agent uses by default port 4700, TCP and UDP.
As I see on my linux and windows servers, running NetXMS agent daemon only TCP is used.

For which purpose / when Agent uses/listens on incoming UDP 4700?

Thank you

Just linking newer thread / similar problem - https://www.netxms.org/forum/general-support/monitor-nodes-with-dynamic-ip-(dyndns)/

Hi,
I have few cases, where I do not have public static IP, only dynamic IP and I use dyndns.org to resolve to current correct IP address.
I use latest (1.2.13) server and console version.

I have added my node by using hostname, and my agent works, however after 24 hours / change of IP, it seems that netxms wrote previous IP to DB and now it uses only this / old IP. (Even on General communication, primary hostname is displayed correctly). Of course I do have low DNS A record TTL and other services works fine, so it's only netxms server problem. On node - object details , primary host name is fine, but primary IP address is an old one.

I found it in Unsorted Features List - http://wiki.netxms.org/wiki/Unsorted_Features_List

QuoteNetXMS can use DNS name as primary communication address. In that case, change in IP address will be reported via special event. Useful for monitoring machines with dynamic IP.

But I am not sure, how to achieve that netxms server does DNS resolution of node each time when pooling ?

edit:
when I manually Pull Configuration from node, it gets rediscovered and primary ip address changes, and then it works (although expected interface status are reset since they changed from unknown ethehrnet to correct list, is this expected behavior ? :/)

Quote from: Dani@M3T on April 09, 2014, 01:36:53 PM
no one with Windows EventLog parsing experience?

Hi, I am interested in answers also

Quote from: Marco Incalcaterra on April 20, 2014, 05:59:29 PM

Quote from: hkusulja on April 20, 2014, 12:16:12 PM
Hi,
as I understand, netxms server, connects to the netxms agent on both TCP and UDP 4700 (default.)

However, is there a way, that agent connects to the server (instead oposite) and delivers the desired data?

I have few situations, where my monitored nodes are behind NAT and I can not do port forwarding. Only option is that agent delivers periodicaly (pools) data to the server, and if for some times agent does not report data to the server, we can mark node as down.

Is this feature supported and if so, how to configure it ?

As far as I know the only option to send data to the server is using the command line tools "nxpush" and "nxapush". The problem is that they works only with the "Push" origin, this means that you cannot use the agent collected parameters directly.
If you have the possibility to NAT just one of the nodes you can then use it as proxy to allow the server to connect to the agents installed on the other nodes.

Best regards,
Marco

Hi,
Thank you for reply, I am aware of Agent proxy feature which is nice, however in some particular cases I do not have any option to forward / open any of ports, so this is reason why I am using this.
Is there a way to automate push that you mentioned ?

Or I should write this as new feature request ?

Thank you once more

Hi,
as I understand, netxms server, connects to the netxms agent on both TCP and UDP 4700 (default.)

However, is there a way, that agent connects to the server (instead oposite) and delivers the desired data?

I have few situations, where my monitored nodes are behind NAT and I can not do port forwarding. Only option is that agent delivers periodicaly (pools) data to the server, and if for some times agent does not report data to the server, we can mark node as down.

Is this feature supported and if so, how to configure it ?

When will documentation be updated (mainly admin and database, but also a user one) ?
Lots of things are missing there, and its clearly unfinished and out-dated.

https://www.netxms.org/documentation/

Any plans to continue working on docs ?

Hi,
since nobody answers me, i found another solution. Install IIS and configure reverse proxy (using ARR 3.0).
Please keep in mind that "Default Web Site" should liste ONLY on 443, and use SSL certificate.
netxms WebUI can be on default 8080 port.

I can confirm that this method works for my scenario.

Reference:
http://weblogs.asp.net/owscott/archive/2013/10/24/creating-a-reverse-proxy-with-url-rewrite-for-iis.aspx