NetXMS Forum

That worked great, thanks,

Ok,

Thanks a lot.

Hi Victor,

Did you get my email? I sent you a diagram of how my network is arranged.

Thanks,

Hi,

I upgraded my installation with version 1.2.5 yesterday on my customer site and luckily it's the day that they also schedule some power testing so I was able to check this functionality. However I didn't seem to see any difference with before. I still got all my NODE_DOWN events, and I didn't see any SYS_NODE_UNREACHABLE.

Thought that SYS_NODE_UNREACHABLE is actually in the list of events, so version wise I think I'm good.

Anything I could do to get this to work?

Thanks,

Cool,

I'll try that in a couple of days. That means that node downs won't be reported if the switches that the device connects to is down? What if the switch comes back up

All my routers and switches are Cisco 2960S and 4507, and NetXMS has access to those switches via SNMP, this setup should be fine right?

Hi,

I saw that 1.2.5 has been released earlier this month and that the problem of this thread has been addressed. Is it done automatically or are there any specific things to configure to have this working?

Thanks,

Hi,

I would be interested in exporting the list of nodes of my system along with some of the parameters such as IP configuration (Address, Mask, Gateway) from the database into an excel file for example. It's in order to verify the list of nodes and put all this configuration in a document, is there any functionality to do this?

Thanks,

Hi,

I recently configured situation similar to what is explained in the user manual. But would like a bit more advice on it.

My problem now is that I have network equipment plugged in on a switch. Weekly there is a power shutdown for testing purposes. For NODE_DOWN events I send SMS notification to my team. So in those cases, I receive quite a bit of those notifications for the switch and the equipment connected to it. When reading the manual I thought that the example for the situation is fitting perfectly my case, if the switch goes down, don't send any of the notifications for equipment plugged in to this switch. However in most of the cases, the NODE_DOWN event for the switch arrives after a lot of NODE_DOWN for the equipment. Is there anything that I can try to do to avoid this. Maybe increase the frequency of the checks for the switch?

Thanks,

Ok,

I'll try that. Thanks,

Hi,

I'm running NetXMS (v1.1.10) on a network with roughly 400 hosts, with automatic discovery to add the new nodes. I realized recently that some nodes would be automatically added even if the this node already exists.

It's quite annoying because it happens occasionally on my core switch. As this switch belongs to all the networks and has some ports that are not connected, every once in a while my customer would open the console and see all the network as having an issue. Only because this switch is duplicated, present in all networks and as it's just discovered, I can't manage/unmanage the ports that are in use.

It happens also for other nodes in the network (but the impact is more limited). In one particular case, a UPS, it keeps adding the node, but not in its subnet, it adds it below the "Business Services" in the list. Which is quite strange.

Anyway to prevent this duplication of nodes?

Regards,

Hi,

I recently purchased new USB-3G adapters for testing before deploying the notification to my customer's office. I was quite surprised to see that NetXMS wouldn't send the notifications with the new model of adapter while it had no problems with the old one. I updated the configuration to have the good COM port, when my adapter is plugged in.

I even did tests with putty to send SMS using the AT commands and it looks like both the devices are able to send SMS that way, so I'm a wondering if there are additional configuration that needs to be done with more recent adapters?

Here are the models of adapters I use:

• Working: Huawei E1550
• Not working: D-Link DWM-156

Regards,

All right,

Thanks for the help, let me know when this is done.

Hi,

So basically with this new functionality I would have to do something like this right?

if (isLocalMgt(server1))                           //processing by server1
   return true; //process event
else
   if (!NetXMSServiceRunning(server1))             //processing by server 2
      return true; //process event
   else                                            //server 2 doesn't need to process the event.
      return false; //don't process event

Hi,

Thanks for your input.

Unfortunately the NetXMS servers are running Win7 so I don't think clustering is a possibility. And yes you're right the two servers are monitoring the same network.

Hi,

I'm wondering if there is a functionality to configure a "failover" server in case the main NetXMS server goes down?

To explain a bit more what I want to do here's the setup. I have 2 server rooms with one NetXMS server in each of the rooms for redundancy purposes. They are working fine independantly and I usually copy the DB over when I do a change one of them. I have now to commission a SMS notification for the system. With my setup I get twice the notifications because both my servers are configured the same way.

From what I understand the way to get the notifications from only one server is not to change the configuration of my server 1. Create a situation on my server 2 that changes with the status of NetXMS Core service on server 1. Then I have to add a check on this situation in the filtering rule of all my events processing on server 2. That way I receive notifications from server 2 only when the NetXMS Core service on server 1 is not running. Is that the best way to do or is there a better way? My concern here is that if I do modifications on one server, it's going to be more complex to copy over the db as I'll need to add or remove the filtering rules.

Thanks a lot,