Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - jdl

#1

"In Management Console (not the Web based), the "Cluster" panel in "Object Details", the window showing the schematic of the cluster infrastructure is not properly sized. The bottom info about resources ownership is not displayed entirely and there is no roll bar. If you resize window then things appear."

Note, I experience this issue also in NXMC web-based GUI
#2
Hi,

I've installed NetXMS 2.0-M4 on CentOS 6.6 and have some feedback / issues - hope this helps.

Compared to release 1.2.17 I find it not so user-friendly to have to create nodes in the "Infrastructure Services" tree to force nodes discovered. That's currently the only way I found to force the discovery of some nodes. But then I cannot delete the node from the "Infrastructure Services" otherwise it disappears from the global "Network". Is there a way to proceed? I think there was a way to do it in a user-friendly way in 1.2.X. "Create Node", define IP and something like "Ping" or "Resolve". Why not available anymore?

Second, Many of my nodes have several IP addresses on a single NIC (alias / virtual IP). NetXMS 2.0-M4 does not seems to manage this well. Sometimes, it finds the physical IP, sometimes the virtual and sometimes the node hostname. Whatever it takes, it does not seem to be possible to harmonize the display and get hostname displayed.

Also, in 1.2.x the cluster related features were not optimal but seemed to work. Here as the alias / virtual IP are not well handled, it is not usable.

Also, when defining the "networks" of the cluster, if you enter an ip address that you then change, your network is automatically increased by one!!!

I regularly get put up with "An internal error occurred during "Get DCI values for node <IP Addr>", java.lang.NullPointerException.

In Management Console (not the Web based), the "Cluster" panel in "Object Details", the window showing the schematic of the cluster infrastructure is not properly sized. The bottom info about resources ownership is not displayed entirely and there is no roll bar. If you resize window then things appear.

For some strange reason, I had the "MTU" column filled in in the "Interfaces" panel of "Object details" for some Agent/SNMP enabled nodes but not all. And for those, the aliases where found. But that was under NetXMS 2.0-M2. The other columns seem to be correctly filled up.

Also in "Entire Network" nodes are discovered and labeled with an IP address that is not related to the network under which they are reported. Those nodes have an IP address in this network. But one would expect to get the node name as label or the IP address related to the network under which it is listed.
For example, a node has an IP address 172.10.25.11 and the virtual IP of that interface (cluster resource) is 172.10.25.10. That same node as another interface on 10.10.0.11 and the virtual IP for that side is 10.10.0.10. Well the node is then discovered as 172.10.25.10 under the network 10.10.0.0/24 and the Interfaces under "Object Details" show only the IP 172.10.25.11 and 10.10.0.11 not the virtual ones while they are used somehow for the labeling.

Do you have a clean way to empty the DB so that I can restart discovery from scratch and see if it helps?
That does not seem to be feasible through nxdbmgr tool.

Many thanks
Best regards,

Jdamien





#3
General Support / Re: webui IP address
November 07, 2014, 10:57:14 AM
Could you, please, confirm in the WiKi the file path where to put this nxmc.priorities file?
From my side, I tried as presented in the WiKi and the content was not taken into account / loaded - file ownership given to Tomcat

Br,
jdamien
#4
General Support / Re: Any setDCIValue?
November 06, 2014, 05:56:45 PM
Ok using nxpush as action within an external Perl script for example.
But what if you would need to perform this type of action from within a script?
#5
General Support / Any setDCIValue?
November 06, 2014, 05:54:16 PM
Hi,

Is there any function similar to setDCIValue?

That could be useful while executing a script attached to an event policy to define the next value of a DCI based on event parameters and/or last DCI value (or some other DCI values) for example. Unless this can be done differently.

Br,
Jdamien
#6
Hi,

Is there a way to define a data collection on a node that would collect data from another node?
This can be interesting when willing to poll a node for a data that is already available on another node (maybe becasue there is already a specific monitoring ongoing) which is much simpler / cheaper to poll than this other one (possibly because the link is congested or resources shall be reserved for service and not monitoring)

Many thanks
Jdamien
#7
While using the source, one could still face the issue already reported for release 1.2.3 at: https://www.netxms.org/forum/installation/error-compiling-v1-2-3/[\b]

So as advised by Victor, deleting old NetXMS agent lib files solve the issue - at least in our scope.

Br,

Jdamien
#8
The way I solved this issue for me is as follows:

a. download server sources
b. run ./configure --with-agent
c. then clean up the mess if you had a previous release

Did not manage any NetXMS agent installation for v1.2.7 using provided packages on Linux.

Br,

Jdamien
#9
Do you have Tomcat6, Catalina, Web GUI working on a Windows OS?
Mine are running on CentOS 6.3
I had problems with a management console on a Windows XP

This could be the start of a path to solution...
#10
Maybe check whether you have Tomcat6 cleaned (cache and others) + restart
#11
Confirmation: list of parameters available in Web GUI v1.2.7

So issue seems to be restricted to Management Console v1.2.6 and v1.2.7

Br,
Jdamien
#12
I did parse the nxagentupdate.log and found:

Use internal libtre: YES
There are several messages of Making all in libtre and entering/leaving directory with libtre (gmake) but no error.

That's it
Jdamien
#13
Hi,

NetXMS server runs on Linux CentOS 6.3 kernel 2.6.32-279.14.1.el6.x86_64
We have Web Console 1.2.5 installed and it was clearly working with server 1.2.5. I just tried to log in but got access refused because "server uses incompatible version of communication protocol". We will get Web GUI updated to 1.2.7 and will test this. Results will be posted very soon.

Br,
Jdamien
#14
I got one install running ok.
The only difference I see is that encyption is NOT enabled.

How do I do to disable encryption?
What are the possible arguments to the command line?

Thx
Jdamien
#15
In the present scope, the console is deployed on a Windows XP PC.
Whenever I update the console, I always first remove the previous release.

So, I have just removed management console release 1.2.7.
We kept the server running release 1.2.7.

First feedback: console v1.2.5 does not work with server v1.2.7. we were using console v1.2.5 with server 1.2.5 prior to upgrade.

Installation of console v1.2.6 with all components and same directory structure as for 1.2.7. Console v1.2.6 seems to work with server v1.2.7 BUT same problem is reported: no supported parameter listed in collection parameter with origin set to NetXMS agent.


I guess something has changed from 1.2.5 to 1.2.6. The console v1.2.5 said that it could not connect to server 1.2.7 because communication protocol was different. Could that be the scope where to investigate?

Br,

Jdamien