NetXMS Support Forum

Hi,

Had a good search on the site and couldn't find the answer. Is there a limited feature set in the Windows clients Dashboard than other systems? For example, there is no Dial Chart or custom widget option. If it is a limitation of Windows, do you need the server to be a different OS or just the client?

Another feature we would like is the ability to add a network map into a Dashboard. We had been using a Network map on our wall PC that shows all 34 of our sites along with their current status. This looks great but is a bit limited. I have now created a Dashboard with the status of each of the sites and an alarm browser. This is much more practical and useful but not as "pretty"! It would be nice to have the network map added in a slideshow of Dashboards but I can't see a way of doing this at present.

We use a distribution list so we email [email protected] to get it to come to all of us

Perfect - many thanks Victor

Hi,

I mentioned this happening in a different thread but it is happening again for a different, simpler DCI so I thought it time for a dedicated topic.

For a couple of our DCIs, I want to set a custom schedule. For the latest one I have tried, it is just to run once a day at 8:00 am as I want to check the modify date of a file to see if a backup has worked.

I add a custom schedule of 0 8 * * * and then apply. However, the DCI will still collect every minute and when I go back to look at the Custom Schedule, it is empty. If I check before the next collection happens, the schedule is still there but a minute or two later, it is gone.

Can you please let me know if there is something I need to change? Attached is a screenshot of how it looks when I add the schedule.

Quote from: Victor Kirhenshtein on January 09, 2013, 05:30:51 PM
Hi!

It's not possible to specify such relation manually. Anyway, it is layer 2 connectivity issue, not layer 3, as both nodes (physical host and VM) are in same subnet, so 192.168.1.10 is not involved in the routing process, but acting as Ethernet bridge. I will add a feature request for including layer 2 topology into event correlation process.

As a workaround, you can check status of the host node in the script in event processing policy, but this may not work as expected if VM polled first (so server don't know that host is already down).

Best regards,
Victor

Thanks - I might give that a go as the event I am using waits for 5 minutes before emailing so the server must be down at the same time as the VM.

Is there a way I can manually specify a link between nodes? It looks like by setting up a VPN connector between, say, 192.168.1.1 and 192.168.5.1, IP Route knows that it gets from 192.168.1.10 to 192.168.5.1 via 192.168.1.1 so hopefully this means that it will only pass a node down for 192.168.1.1 if the line goes down. However, we also have a lot of virtual servers. Is there a way I can setup a link between 192.168.1.12 and 192.168.1.10? If 1.10 (The physical server) is down then it follows that 192.168.1.12 (The virtual server) is down so I want to stop the node down for 1.12

As I added these nodes manually, I need to somehow let NetXMS know there is an extra step in the IP Route. Can I do this without adding a VPN link between the two? (I'm guessing this would work but would be wrong as it is a VM, not a VPN connection

Quote from: Victor Kirhenshtein on January 09, 2013, 02:44:18 PM
Hi!

In 1.2.5 we improve event correlation based on topology, so if NetXMS knows full path between itself and remote node it should correlate events automatically and only pass NODE_DOWN event for router. You can check this by selecting management server node object in object tree, then select "IP Route" from context menu, select remote node, and check that correct IP path is shown.

Sorry, I didn't fully understand web site question. Can you give a simple scenario please?

Best regards,
Victor

Sorry I wasn't clear. The Website check was an idea I had for stopping an email. For example, if a remote node is down, check if the website is down as well. If so, then don't send an email. It did occur to me that I could do this using Google (Which should never go down in theory!) so before emailing, check if Google is down. If so then do not email as it is very likely that the link from Head Office is down.

However, I hadn't seen that 1.2.5 had been released. I will upgrade and try IP routes. Thanks again for your prompt support and for your excellent software!

Sorry, me again! I have got our system set up to monitor our 35 remote sites and send an email if the node is down for more than 5 minutes which works perfectly thanks to your earlier help. However, when the connection to our head office went down the other night, we come in to around 200 emails telling us that every node was down and then back up again.

Can you suggest an easy way of changing the setup so we don't get emails if the main line goes down? Before settling on NetXMS, I tried OpenNMS and they had a critical path feature whereby you specify the Node connections it relies on so you don't get notifications if the critical path is down. I'm sure this can be done using individual rules but with a router and at least one, if not several servers at each site, I don't really want to have to create a separate rule for each node.

I have also set a check for our website which is hosted elsewhere. I am wondering if a check in the rule that if the website is down as well then don't email but that would stop monitoring working properly if the website is down for any length of time.

Any advice would be welcome.

Quote from: Victor Kirhenshtein on January 04, 2013, 04:47:51 PM
Hi!

What you mean by "disappeared"? It stops collecting data, or configured schedule really disappears from DCI configuration?

Best regards,
Victor

It really disappears from DCI configuration. It seems to stay for the first few minutes but then goes completely

That didn't work either - just disappeared after 3 or 4 minutes

Actually I've just tried * 9,10,11,12,13,14,15,16 * * * after reading the Wiki page on cron - hopefully this will work

I have setup an average ping time DCI for one of our sites that has a poor network connection and set it to email if the Average pings for the last 5 collections is over 1 second. This works perfectly but keeps emailing us in the early hours when the backup runs across the network. I tried to set up a custom schedule to just collect data in the day using rows like the following:

*/1 9 * * *
*/1 10 * * *
*/1 11 * * *
..
..
..
*/1 17 * * *

This doesn't work however and the schedule disappears after a few minutes. Is there a way I can just collect every minute between say 9 and 5 or 9 and 6?

Hi,

Apologies for what may be a basic question but we are a small IT department with limited knowledge of NMS systems. We have the basics we wanted working perfectly which is ping servers and emailing if they go down for longer than 5 minutes - our World map showing all of our sites and their status is drawing a lot of attention from other departments!

I am now looking to try and add jam to the cake by adding small things that would help us out which basically means collecting more attributes than we have been doing. I have managed to get Free Disk space working but I am struggling with others. The main one that would be useful is PhysicalDisk.smartstatus so we can get warnings when one of our disks is predicted to fail. We have the NetXMS agent installed on all of our servers and I have added the attribute PhysicalDisk.SmartStatus(0) which as I understand it should work. All that happens when I run a status check is the last value shows error.

Am I missing something obvious? I found the other question about this attribute in the forum which explained how to find the disk number and our server has disk 0 and 1 but neither seem to work. Should this work through the agent or does it need SNMP installed to work?

When I was having a play when I first installed the system, I was getting this error when I tried a few attributes. Any pointers to help me understand would be much appreciated!

Many thanks for the swift response - I will give it a go although the agent did crash when I tried to install it on the server

Hi,

We have an old Windows 2000 Server which hosts a lot of shared files but it is currently slowly dieing. Once a week or so, it stops serving access to these files until we reboot it.

Whilst we try and work out a way of moving all the files elsewhere, is there anything I can do with NetXMS to check whether it can access a file on this server and create an alert if it can't?