NetXMS Support Forum

More question...

Is it possible to tunnel traffic between dashboard and server in HTTP / HTTPS?


Br,
JDamien

Hi,

would you be so kind to give us some information about how the communication is setup between any Web GUI (remote laptop for example) and the NetXMS server?

Which port is effectively used? Wireshark shows only traffic to server port 4701. No traffic seems to be going on 8787.

How secure is the link between the remote laptop running the Web GUI dashboard and the NetXMS server?

We try to understand how likely it is that comm between remote dashboard and server will cross firewalls and how secure this comm can be.

Many thanks in advance.

Best regards,
Jdamien

Will do point 1)
For the moment, in the log, we can see that all nodes not included in a cluster are polled. We get messages "Starting status poll for node <IP@> (ID: <ID>)" and "Finished status poll for node <IP@> (ID: <ID>)"
For those nodes that are in a cluster the messages are different: "Starting discovery poll for node <node_name> (<IP@>) in zone 0", then "Discovery poll for node <node_name> (<IP@>) - reading routing table" and finally "Finished discovery poll for node <node_name> (<IP@>)".

Those cluster nodes only appears under "Infrastructure Services" not in the "Entire Network" section and network sub sections. Our netXMS server appears in both containers and is not a cluster.

Br,

Jdamien

Dear Victor,

did you solve this issue or was there something put in the latest releases to alleviate this issue of disappearing cluster nodes?
I'm currently using your latest release (1.1.10) on CentOS 6.0. I have created two clusters X and Y which have each two nodes. All nodes have an interface on network A. The nodes of cluster X have interface on network B and those of cluster Y have interface on network C.

Auto Discovery is on. Both clusters have been created as described in forum. Nodes where discovered and allocated to Clusters. I left the setup stabilize over the week-end. Today, all nodes have disappeared. Both clusters are correctly populated. Polling of any cluster node is successful. Each node is SNMP and NetXMS agent activated. Some other nodes exist and are correctly discovered in networks A, B and C.

Any advise is welcome.

Best regards,

JDamien

Hi,

Did install NetXMS 1.1.5 on CentOS 6.0. And have experienced some issues with getting nxagentd recognized/detected on server.
In agent log file, following errors were reported:

[27-Oct-2011 14:24:53] Log file opened
[27-Oct-2011 14:24:53] Additional configs was loaded from /etc/nxagentd.conf.d
[27-Oct-2011 14:24:53] Debug level set to 9
[27-Oct-2011 14:24:53] Failed to load agent's registry from file /var/opt/netxms/agent/registry.dat
[27-Oct-2011 14:24:53] Failed to save agent's registry to file /var/opt/netxms/agent/registry.dat: No such file or directory
[27-Oct-2011 14:24:53] Subagent API initialized
[27-Oct-2011 14:24:54] Linux: using /sys/block to distinguish devices from partitions
[27-Oct-2011 14:24:54] Unable to parse /proc/drbd, DRBD data collector will not start
...
...

Though the agent was started it was not recognized.
I did create /var/opt/netxms/agent directory and the first two errors disappeared after having restarted the agent.
The last one - DRBD related - remains.

Anything you can help here?
Performance are not collected in console (performance tab).

Br,

Jdamien

Hi,

when you will find some time for "non critical" items, maybe you want to improve this small one:

When you use the MIB Browser and select a node to get a value, if you want to change node you have to quit MIB Browser and restart it.
Adding some flexibility by allowing to change all involved parameters (a.o. the IP address of the polled node) would be more user-friendly 


Best regards,

JDamien

Hi,

Using the new PostEvent functionality in a NXSL script, I managed to redirect alarms (warning and more severe msg) to appropriated nodes (kind of proxy). These messages are extracted from an application log file on the application server and tell whether a node has an issue or not w.r.t. this application.

Now I was wondering why (and if this is the expected behaviour) all messages appear correctly in the main "event log" opening from the icon tool bar menu and were not displayed in the "Alarms" tab of the specific nodes in the "Object browser"? I would have expected that I can have those messages (or at least the alarms) displayed in this tab.

Am I right or is there a difference between the "Event Log" window and the node specific "Alarms" tab?

Many thansk in advance
Best regards,

Jdamien

Would this be a bug?

Best regards,

Jdamien

Hi there,

This is a low priority feedback.
When graphing a stat and zooimng in using the mouse to select an area, while x-axis adjusts accordingly, y-axis and related scale stays as it was. Would it be possible to have Y-axis dynamically adapted to the selected area to be zoomed.

If you have values from 1 to 100 and zoom only on an area where only values between 50 and 60 are present, you expect the y-axis to be tuned to 40-50-60-70, for example. Currently it stays to 0 - 100. Which may become very unconvenient when values are high.

Best regards,

Jdamien

Correct - one '0' too much.
Sorry for that.

It works
Br,

Jdamien

This sounds great...

I tried it on Linux (I have compiled server with --with-client option). Here is the error I get:

/usr/local/netxms/bin/nxevent -u <user> -P <passwd> -o 12 <server_ipAddr> 1000009
Unable to send event: Invalid or unknown event code

Could you, please, describe a bit more the differnet parameters required. Only options are describedd in the "help" page.

Best regards,
Jdamien

If I may select one or the other... I would prefer a generic series of built-in fonctions to manage and produce event from within scripts.
A kind of SendEvent enabling triggering events from within NXSL scripts with all possible arguments configurable by user. And especially the source of the event 

BTW: a similar command line would be powerful as well to integrate in external PERL (and Co) scripts.

Best regards,

Jdamien

Hi Victor,

Again, many thanks for your support and the quick answer. I very much appreciate how dynamic this forum is.

I've tried both your suggestions. Setting server's configuration variable CheckTrustedNodes to 0 (+ restarting server) solves my problem. That's a great point.

Now, if one want sto keep these security aspects that you can manage with the notion of "Trusted Node", adding the NODE1 to NODE2 list of trusted nodes does NOT work. Still same issue. You may want to have a look at this. I restarted agent: still NOK. I restarted server: still NOK. There is nothing I can report based on the log files. I also - based on what I experienced early this week- waited a while before dong anything.

In addition to this, I would highly appreciate if you could provide the list of all the functions that exist and are related to DCI, Node and Event objects. The user manual does not list them all (only DCI related). The forum provides some of the node related functions. Maybe there are more implemented but not yet known to us 

BTW: I have not seen any input in the logfile regarding to access right from one node to another - trusted node. Maybe it would be interesting to have some to support our troubleshooting. What do you think?

Best regards,

Jean-Damien

Hi,

I'm getting closer and closer to what I want but still there sth missing  
Would be glad if you help me on this one.

So I come back to my story...
I have one service server which host a logfile and an NXAgentd. There is a LOGWATCH running for this logfile. Parsing each alarm, it is possible to determine which node is impacted by the error - not the server, some other node which is not hosting any NXAgentd.

I want to have a specific DCI defined and updated according to data in the error message for each particular node.
Using NXSL I can determine the node name and use the NXPUSH command. But I'm block at the time I need to identify the DCI and get its latest value (GetDCIValue + FindDCIValue). Why? Because in the NXSL script those two functions require the first argument (node) to be an object! In my context, the $node object refers to the service server and not to the node which name can be extracted from the error message.

Is there no way to get around this problem?

One may want to consult a DCI from a node when handling events related to other nodes.

I understand from other posts that one could use the FindNodeObject function to get the node object" once we know for example its name. But I persistently get error 14, saying that my left side (objDciNode->name) of the following expression is not an object:

objDciNode = FindNodeObject($node, vDciNode);
// Some debugging trace
trace(3, "Node name = " . objDciNode->name);

Is there sth I forgot?

typeof(objDciNode) == NULL but my node exists well!

Many thanks in advance for your help
Best regards,

JDamien

Well I'm lost... it is working now... Nothing really different - just working!!

Could it be that once you change config on server you might have to wait for a while before it becomes active?
JDamien