NetXMS Support Forum

Hi!

Currently there are no way to detect alarm ack/termination by operator and do some actions. It's a good idea to add a hook for that. I'll think how it can be implemented.

Best regards,
Victor

Hi!

Acknowledged alarm will remain in list of active alarms, but in "acknowledged" state. Terminated alarm will be removed from active alarm list. Main idea behind this is to provide mechanism for operators to inform each other that problem do exist, but somebody already aware of it and working on it.

Best regards,
Victor

Filtering script always should have a body. If you don't need filtering, just use


return true;


Best regards,
Victor

It is ok to have comments this way in the script. The problem is probably due to either bug in NXSL interpreter, or some typo (or maybe non-printable character) in filtering script. You can also try to copy script into file and try to execute it with nxscript.

Best regards,
Victor

Hi!

The problem is that your device reports loopback address 127.0.0.1 on physical port. NetXMS ignores loopback interfaces when read interface list. I'll made a fix for that in next release.

Best regards,
Victor

Hi!

It's error in filtering script, not a config itself. How your filtering script for config looks like?

Best regards,
Victor

Hi all!

Attached is a configuration with data collection template and SNMP trap mapping for Nortel (now Avaya) Wireless Security Switches.

Best regards,
Victor

Hi all!

NetXMS version 1.1.6 is out. Changes from previous release:

- Added possibility to run different subagents under different user accounts (currently supported only under Windows)
- Improved work with 802.1x capable switches
- New MIBs added: EF-6000-MIB, ES-1000-MIB, IBM-6611-APPN-MIB, IBM-MIB, IBMCPU-MIB
- Fixed interoperability problems with IBM AS/400 SNMP agent
- AIX support improved
- Fixed serious memory leaks in server
- Many small improvements in management console

Best regards,
Victor

Hi!

Agent is modular, and platform-specific parameters are provided by subagents. When agent starts, it automatically loads so-called "platform subagent", which provides these parameters. For example, on Windows agent will load "winnt.nsm", and on Linux it will load "libnsm_linux.so". After subagent loading, parameters provided it added to m_ParamList in core agent. You may take a look inside subagent.cpp if you are interested how subagents are loaded.

Best regards,
Victor

Spasibo za patch dlja OpenBSD, ja vkljuchu ego v trunk.
Chto kasaetsja 1.1.x, to v celom eta vetka uze dostatochno stabil'na. Ja rasschitivaju k koncu goda sdelat' oficial'nij stable release 1.2.0 i okonchatel'no zakrit' 1.0.x. Chto kasaetsja 1.1.5, to ja rekomenduju podozdat' neskol'ko dnej do vihoda 1.1.6.

Hi!

Can you post at least one example of your DCI configuration? And don't forget that any SNMP OID has "instance" - so, for example, system description OID shown in MIB tree as ".1.3.6.1.2.1.1.1", should be configured in DCI as ".1.3.6.1.2.1.1.1.0". You can check what instances are available by using "walk" option in MIB explorer.

Best regards,
Victor

Hi!

Sorry, I was unable to find the reason immediately, and then I forgot about that. Could you please send me results of the following walk:

nxsnmpwalk -c your_community switch_ip .1.3.6.1.2.1.4.20

Best regards,
Victor

Hi!

Most likely agent returns an error in response for those parameters. You can check it with nxget command line tool. Also, please note that physical disk parameters are working only for some devices.

Best regards,
Victor

By default it will be file name (exactly as written in <file> tag), and you will be able to change it by adding name attribute to <parser> tag. For example,
for parser

<parser>
  <file>*System</file>
  ...
</parser>

instance name will be *System, and for


<parser name="SystemLog">
  <file>*System</file>
  ...
</parser>

instance name will be SystemLog.

Best regards,
Victor

Done it. Next release will have these parameters implemented.

Best regards,
Victor