NetXMS Forum

Hi,

Sorry for reviving this old post, but I sure would also like to see this feature implemented.
In my situation, we instead have a bunch of Supermicro Twin-servers which are 4x servers in 2U.

One way to maybe solve this issue could be to add an option to create a "Chassi" in the Object tree and then add the option to add Node(s) to a Chassi.
The Chassi should be able to be assigned to a Rack and specified how many rack-units in size it is.
In that way the Rack-picture would know how many Nodes are assigned to the chassi, its unit-size and rack-location and then the picture could be rendered based on that information.

I've attached a illustration of how a 10-node blade (with one faulty node) could be presented to the end user.

Regards,
// Anders

Hi Tatjana,

Thanks but it really doesn't solve my problem. I was looking for a way to override the executing parameters in the init-script without having to modify the actual init-script, simply because the /etc/init.d/nxagentd gets overwritten each time you upgrade the agent software (considering I have about 80 machines, that creates allot of undesirable work each upgrade).

But I think I've found a working solution to my problem. The great people developing NetXMS has used the standard debian/ubuntu init-script which automatically loads and overrides init-script variables from: /etc/default/nxagentd... so basically if anyone else has the same needs as me, they can simply execute the following command to get an parameter override that doesn't get overwritten:

echo "DAEMON_ARGS=\"-d -c /etc/netxms/nxagentd.conf\"" > /etc/default/nxagentd

I suppose this means that my feature request has already been fulfilled

Hi,

I most often monitor Ubuntu Linux installations and tend to keep my: nxagentd.conf configuration file, scripts etc. under the path: /etc/netxms. By default the init-file for the netxms-agent looks for the configuration file under: /etc/nxagentd.conf.

I'd like to have a default property file under: /etc/default/netxms-agent (or /etc/default/nxagentd) where I can override startup options without having to modify the original init-file (/etc/init.d/nxagentd), specially as it gets overwritten every time there is a new release of the agent.

Thanks for a fantastic product!

Anders

This would be a nice feature, most of our machines are IPMI-capable.

@alk said in Mac OS X Management Console Installation Error:

Could you please try this version: https://www.dropbox.com/s/wmwq997zlny55nk/nxmc-1.2.10.dmg?
This build is signed with proper keys from Apple, so it should work properly with Gatekeeper enabled.
Please note: it's built from from latest sources and incompatible with 1.2.9, so don't overwrite your existing app.

I can confirm that this version starts without any issues when the setting for "Allow apps downloaded from" is set to: "Mac App store and identified developers" under Security & Privacy.

If you really need NetXMS Console version 1.2.9 a temporary solution could be to:

1. Download https://www.netxms.org/download/nxmc/nxmc-1.2.9-macosx-cocoa-x64.tar.gz and extract the tar-archive.
2. Open a Terminal and navigate to the extracted folder.
3. Make the "nxmc" program executable. chmod +x nxmc.app/Contents/MacOS/nxmc
4. It should now be possible to start the application.

I have the exact same symptom as saa85 on my Mac.

I have tried it on a 10.8.5 and today with 10.9. Same problem.

Hi,

I'd like to suggest that the nxpush command gets included in the netxms-agent deb-package, or made available in a optional netxms-util deb-package.

Currently the nxpush command doesn't seem to be included in neither netxms-agent, netxms-base or the netxms-server debs.

Regards

Anders

Hi mrugani,

This sounds more of an Qemu related question than NetXMS related, but I'll give it a try.

Are you using some sort of management wrapper such as: libvirt (virsh) or similar to manage your virtual machines? or are you using the native Qemu-monitor to migrate your virtual machines?

Works now, I've also been waiting for this

Thanks, but isn't there a way to prevent NetXMS server to retrieve the interface list for newly added nodes?

My node for example has > 1000 interfaces named eth0, if I try to unmanage all of those, my interfaces freezes and it doesn't really solve my problem. I'd like to reducing the amount of interfaces under the node and if possible, just allow one main interface with the "default" ip-address.

Hi,

I have a Linux machine with *allot* of logical interfaces, it's probably > 1000. As you can imagen it often freezes the NetXMS Console UI and creates scenarios where the NetXMS Console crashes when trying to browse the node.

Is it possible to somehow limit the amount of polled interfaces?

Thanks in advance

Anders

Hi,

Did this fix make it into 1.2.5?

Regards

Anders

Great news, thank you Victor! Does the Process.Count() work in a similar way?

Btw, what is the most up to date source for reference information for all supported attributes for a command such as: Process.Count() or Process.CPUTime() ? I haven't been able to find any related information in the wiki.

I'd guess that the custom scheduler doesn't affect/work on the average PING-agent(?).

An alternative solution could be to write a filter script in the Event Processing Policy that only allows alarms between 9am and 5/6pm. Then you wouldn't lose the statistics.

Hi,

I'm facing a problem where I need to monitor the availability of a number of qemu-kvm processes (virtual machines) in Linux.

Normally you can gather statistics by for example defining: Process.CPUTime(qemu-kvm) but what if I have a number of qemu-kvm processes that I'd like to monitor individually? The only way to tell the processes a part is by --name XXXX attribute, which states the virtual machines name and/or id.

I guess the ideal scenario would be to setup the monitoring and DCI collection on a cluster-object and associate all the qemu-kvm hosts underneath it, then the monitoring and the stats would keep collecting even if a virtual machine is migrate to a different host. But my problem is that I can't filter running processes by attributes, or at least, I haven't found out how...

Hopefully someone can give me a hint in which way to go, thanks!

Anders

Thanks for the hint jdl and sorry for my late reply.

I did actually get a new node down alert and when the node went up again the alert and the red-dot problem disappeared...

Thanks anyway for your quick reply on my problem, I'll try that if the problem ever occurs again.

Aha! Thanks Victor, this should have been obvious, but for some reason I got the impression that time() returned the agents local time and not the netxms servers local time.

Hi,

I seems to have got a "stuck" red-dot on a subnet below the "Entire Network", but when I expand the sub-net, I can't find any DCI-node that "owns" the error. I believe that the red-dot is a remnant from a deleted node.

How would I go about to remove the red-dot?

Thanks,

Anders

Hi,

I have been trying to setup a time-drift template, that monitors my agents local system time and compares it to the time of the monitoring server, basically I'd like to find servers that drifts in time despite of a NTP daemon (all servers are in the same time zone).

But I can't seem to get it to work as I only seem to be able to get the agents local time.

Any suggestions on how this could be solved?

Thanks

Anders