NetXMS Support Forum

Hi!

Yes, you should use situations for preventing duplicate emails. Depending on if you have paired event for access point coming up, you can either set situation's attribute to true when you process first down trap, ignore all other down traps if it's set, and clear it on access port up trap, or you can store current time in situation's attribute, and ignore all next events withing some short time interval.

Best regards,
Victor

No, there are no default rules for handling SNMP ifdown/ifup traps. You should create them by yourself.

Quote from: lweidig on July 20, 2012, 05:50:21 AM
I recently decided to start moving our trap notifications over to NetXMS from what I hope will soon be our old NMS.  We have a number of various model Procurve switches which the system seem to try and detect.  It shows the driver on the general tab as PROCURVE.  However, when we get a trap for link down and then a trap for link up it is NOT clearing the Link down event and it stays up on the device until we manually terminate.  It is detecting the ports correctly from the varbinds, just not clearing.

First traps .1.3.6.1.6.3.1.1.5.3 (link down) followed by .1.3.6.1.6.3.1.1.5.4 (link up).  These appear to be the "standard" down / up noticed and are listed in the SNMP Trap Configuration section.

How do you define rules in event processing policy for create and terminate alarm?

Quote from: lweidig on July 20, 2012, 05:50:21 AM
Not sure how it comes up with the port drawings either, but it is wrong.  For example our 4000M switch shows an odd layout of ports 1-22 in slot 1, 0 - 23 in slot 2, 0 in slot 3 and 1 in slot 4.  In actuality there are 6 8 port cards, 1 1 port card.  It also pops up a components tab with nothing filled in.

Can you please send me output of nxsnmpwalk for the following OIDs on this 4000m:
.1.3.6.1.2.1.1
.1.3.6.1.2.1.2
.1.3.6.1.2.1.47.1.1.1.1

Components tab may be empty because switch may not support appropriate MIB.

Quote from: lweidig on July 20, 2012, 05:50:21 AM
Also, would like to make a suggestions that you allow clipboard copy from the SNMP Trap Monitor display so it is easier to grab OID's or messages. 

It's already done in upcoming 1.2.2.

Best regards,
Victor

Hi!

Do you have libnxcore.so.1 in /usr/local/lib? If yes, try to run ldconfig and then start netxmsd again.

Best regards,
Victor

How did you compile agent for Pi? Can you send me config.h from your build? I suspect wrong byte order detection.

Best regards,
Victor

Hi!

Looks like encryption is now working for some reason, because server drops connection immediately after key exchange. Can you check server logs as well? Also, try to disable encryption in agent to ensure that it's encryption problem.

Best regards,
Victor

Currently server generates SYS_SCRIPT_ERROR events for script compilation and execution errors. You can handle this event and generate alarms or send notifications. But I agree that script editor should do at least syntax checking before saving the script on server. Added this as to-do.

Best regards,
Victor

Hi!

You should see also something like

[session:0] Requesting parameter "Oracle.DBInfo.IsReachable(DB1)"

is it there? If yes, what is after that line?

Best regards,
Victor

Quote from: lweidig on July 17, 2012, 01:56:58 AM
I see that within the client I can add my own Server Configuration variable / value pairs.  How can I retrieve these values within a script and or how would I use my own additions.

"Add" option in server configuration view is intended for adding parameters that are not listed by default for some reason (or was accidentally deleted). But I can add NXSL function to read configuration parameters of course, it's very simple.

Best regards,
Victor

Hi!

It's not working yet. Sorry for misleading configuration

Best regards,
Victor

Some time passed already since July 1st, but just in case - could it be this problem: https://www.netxms.org/forum/announcements/high-cpu-usage-after-172012/?

Could you also please attach debugger to netxmsd process and dump stack trace for all threads:


# gdb /usr/bin/netxmsd
(gdb) attach <netxmsd_pid>
(gdb) thread apply all bt
(gdb) detach


Best regards,
Victor

It is available from NetXMS download page for all major OS. For example, 32 bit Windows version is: https://www.netxms.org/download/nxmc/nxmc-1.2.1-win32-x86.zip.

Best regards,
Victor

Turn off routing and discovery polls on those BGP routers (you did that already if I understand correctly). Restart netxmsd after that if possible.

Routing table polls used for discovery and also can be used for routing change monitoring via Net.IP.NextHop internal parameter.

Best regards,
Victor

Could it be that you have router(s) with very large routing tables, like full BGP table?

Best regards,
Victor

Situation is definitely not normal. Can you please open server debug console (from management console or with nxadm -i), and send me output of the following commands:

show sessions
show pollers
show queue
show stats
show flags
show watchdog


You are correct, containers in infrastructure tree are for logical grouping. Polling is not related to node location in container, and node is polled only once no matter how many times it appears in the tree.

Best regards,
Victor