NetXMS Support Forum

You should have AP name as an instance. You can create some attribute, like isDown, and set it to true on down trap and to false on up trap. Then in filtering script for down trap you can check if this attribute already set to true, and then ignore the event. And yes, you can use %2 and other macros as instance and/or attribute value.

Best regards,
Victor

Hi all!

NetXMS version 1.2.2 is out! Changes since previous version:

- New alarm state - "Resolved"
- Added drivers for Cisco ESW and Dell PowerConnect switches
- Added MIBs for Dell PowerConnect switches
- New event processing macros: %g and %I
- Management console:
   - In port view ports are colored according to physical port state
   - Interface IP shown in connection point search results
   - Interface IP and MAC shown in "Interfaces" tab
   - Added "Status Map" view
   - Added option to hide unsupported DCIs from "Last Values" view
   - Added option to indicate data collection errors in "Last Values" view
   - Added "copy to clipboard" function in log viewers and monitors
- Android client:
   - Dashboards implemented
   - Node status/configuration/topology poll implemented
- NXSL:
   - Global variables can be declared in script code
   - New functions: GetConfigurationVariable, GetObjectParents, GetObjectChildren, sleep
   - New attribute "guid" in classes Interface, NetObj, and Node
- AIX Subagent:
   - New parameters available: System.CPU.PhysicalAverage.*
- Fixed bugs:
   - Config file with CRLF loaded incorrectly on UNIX
   - Unable to bind object in WebUI
   - Graph colors can be ignored in dashboards
   - Object deletion may not be immediately reflected in console
   - Unable to upload file into image library from Web UI

Best regards,
Victor

That's strange. Can you show me SNMP trap mapping and part of trap log?

Best regards,
Victor

Hi!

Currently there are no way to find how particular IP address was discovered, except for looking at debug log, level 6 at least. I agree that discovery source information should be available. Added to my todo list.

Best regards,
Victor

Hi!

Quote from: lindeamon on July 23, 2012, 11:12:44 PM
snmp enabled devices like ibm ip kvm and ibm tape library which are connected to switches with drivers are not found,why is that ?

Sorry, I'm not clearly understand the question - drivers not found for tape library, etc. or for switches?

Best regards,
Victor

Every event has source object ID. For events created from SNMP traps, source object determined by SNMP trap packet's source IP address. If node with that IP address cannot be found, event will not be created. Can you check that for both down and up traps events are generated?

Macro for IP address exists - %a. Full list of possible macros available here: http://wiki.netxms.org/wiki/UM:Event_Processing#Macros_for_Event_Processing.

I have added "Key" column to alarm log in 1.2.2.

Best regards,
Victor

I can add this as configurable option. I don't have time to add this in 1.2.2, so I schedule this for 1.2.3 release.

Best regards,
Victor

Hi!

I start building it already Should be available this evening or tomorrow. It was planned to be released much earlier, but I'm overloaded with other tasks...

Best regards,
Victor

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