NetXMS Support Forum

Hi,

It's quite easy, just add the devices as source objects to the built-in Event Processing Policy named "Show alarm when node is down".  Also, you will probably want to add them to the related policy named "Acknowledge node down alarm when node is up".


-Kevin C.

Hi,

No, that is not my intention for the final configuration.  I just want 5 minutes.

But I had changed it to 5 at first, and that made no difference - it went to "node down" status in ~60 seconds.  So I decided to put in 300 (just a random big number) to see if that would make any difference, and it did not.


-Kevin C.

Hi Victor,

I have testing by setting the node interface "required poll count" parameter to 300.  There is now a question mark on the node interface icon on the NetXMS console. Then, I disable the switch port that node is plugged into.  But no change, I still get a node down alert in approximately 60 seconds.

Is there anything else I need to check?


-Kevin C.

Greetings,

We are getting many of these alerts with version 1.2.17:

Invalid network mask 255.255.255.192 on interface "vlan1", should be 255.255.255.0

The /26 (255.255.255.192) is in fact the correct mask for this device; this particular node is a firewall that has VLAN's configured on a trusted port.


-Kevin C.

Greetings,

NetXMS 1.2.17 is not discovering all nodes, in 3 or 4 of our remote networks.  It discovered some nodes in those networks, but not all.  Is there a way to force a "re-discovery" of just a certain network?


-Kevin C.

Greetings,

What is the best way to change the threshold on how long it takes NetXMS to determine that a node is down?  Right now, it seems to be about 60 seconds system wide, which is perfect for most nodes.  But I have 50+ nodes that I would like to set the threshold to 5 minutes, before an alert is sent.

Currently running version 1.2.17.  Any info is appreciated!


-Kevin C.

Got this working; as it turns out, the Java update uninstalled all of the "old" versions on my laptop, including the 64-bit version I was using for the NetXMS console.  I downloaded the 32-bit version of the console, and it launches fine, no error.


-Kevin C.

Greetings all,

We are running NetXMS 1.2.14, and have had no major issues... until I did a java update on my laptop.  Now, I can't launch the NetXMS console, it comes up with "Java was started but returned exit code=13".

When I go to the java site to verify my java version, it says I'm running the latest version, and also I have no outdated versions installed.

Any help is appreciated!


-Kevin C.

Greetings,

I am way behind on versions, now running v1.2.6.

Is it possible to upgrade directly to this latest v1.2.14 from v1.2.6 ?


-Kevin C.

Greetings,

Can someone explain how I can accomplish two things:

1) I am currently sending node down/up email notifications, which works great.  How can I add the number of hours/minutes/seconds that the node was actually down?  Of course, this would be based on when NetXMS saw the node go down and then come back up.

2) How can I trigger an email notification when a circuit is experiencing higher than normal latency - say over 75ms, for longer than 1 minute?

Any help is appreciated!


-Kevin C.

Greetings Victor,

We are still running v1.2.6 - is it OK to upgrade directly to 1.2.11 from this older version?

Please let me know, thanks!


-Kevin C.

Greetings,

Is it OK to upgrade directly from 1.2.6 to 1.2.8 ?


-Kevin C.

I have not yet upgraded to 1.2.7, still on 1.2.6, but here is information on one of the many devices that are showing up in the root of the tree. This device happens to be a Zebra printer, we have about 50 of them, and as you can see, there is a subnet mask present:

  System Name:             ZBR4473616
  Web Address:             http://192.168.12.29
  IP Address:              192.168.12.29
  Subnet Mask:             255.255.255.0
  Default Gateway:         192.168.12.1
  Timeout Checking:        Enabled
  Trap Destination(s):     255.255.255.255


-Kevin C.

Greetings,

I am seeing this behavior again on newly discovered devices, running NetXMS 1.2.6.  We are adding 50 new Zebra printers to our network, and all of them are being discovered, but they show up in the root of the tree, not in the proper subnet.  These devices have multiple interfaces showing (including loopback), as well as the active interface with an IP address.  I have attached a screenshot of the console tree root.


-Kevin C.

Hi Victor,

Is there any update on when 1.2.7 might be released?  Possibly before tax day (US)?


-Kevin C.