NetXMS Support Forum

Sorry, I miss it. Will take a look.

Best regards,
Victor

Hi all!

NetXMS version 1.2.14 is released. Changes since previous release:

- STP (Spanning Tree Protocol) information used for topology discovery
- Information source for interface peers (CDP, STP, etc.) shown in console
- New NXSL function inList
- New NXSL operator abort
- New methods in NXSL class Node: enableAgent, enableConfigurationPoll, enableIcmp, enableSnmp, enableStatusPoll, enableTopologyPoll
- Fixed server crash if SNMP proxy unavailable
- New MIBs: AIRESPACE-REF-MIB, AIRESPACE-SWITCHING-MIB, AIRESPACE-WIRELESS-MIB, FROGFOOT-RESOURCES-MIB, MIKROTIK-MIB
- SMS driver for websms.ru service
- Macro expansion supported in pattern in agent parameters File.Size and File.Count
- Attribute "instance" added to NXSL class "DCI"
- Added "L" extension to DCI custom schedules
- Traps from unmanaged nodes ignored
- Fixed repeated threshold violation events after server restart
- Added driver for Mikrotik routers
- Added driver for Ubiquity Networks wireless access points
- Added driver for Cisco Wireless Controller 4400 (former Airespace)
- Wireless controller and access point support improved
- Log monitoring subagent sends Windows event source, severity, and code to the server as part of NetXMS event
- DB/2 driver and monitoring subagent included into Windows installation package
- Management console:
   - DCI values can be shown on network map links
   - DCI value can be shown on map as immage, that checnges depending on DCI value
   - DCI value can be shown on map as a text
   - Colored background for DCIs with active thresholds in DCI summary tables
   - IP route visualisation improved
   - On table DCI threshold property page columns can be chosen from dropdown
- Reporting server rewritten from scratch
- Fixed issues: #71, #417, #528, #535, #536, #552, #558, #559, #560, #570, #572

Best regards,
Victor

I just realize that SNMP table was not working because you have to provide one of table OIDs to collect instances. If you change table OID to .1.3.6.1.4.1.14988.1.1.1.2.1 it should work. It is not very convenient nor straight forward, I know SNMP tables definitely need improvement.

Best regards,
Victor

Ограничение по длинне есть, но 256 символов. А можно привести SQL запрос? И с какого символа он был обрезан?

It looks like NetXMS server cannot correctly identify port for B8AC.6FA2.39FA on Switch 4 for some reason, and so shows Switch0 as best match (it is actually previous hop). Can you please send me full MAC address table for both Switch0 (can only for Po4) and Switch4?

Best regards,
Victor

Hi,

to determine peer MAC address server can use information obtained from CDP, NDP, LLDP, EDP, or switch MAC address table (FDB). Also, peer interface will be set only if server knows that there only one remote MAC address on interface - so for example links to unmanaged switches with multiple hosts behind will not have peer information set.

Best regards,
Victor

Hi,

you right, seems that I forgot to fix it. Fixed now (will be in 1.2.14).

Best regards,
Victor

Hi!

I won't be able to help you much. #1, #2, and #4 need changes in agent (#4 also in server). #1 is implemented in 1.2.14 (event source, id, and severity passed as three additional parameters for event generated). #2 should be relatively easy to implement, I'll add this as feature request for 1.2.15. For #4 we plan to introduce new policy type to distribute parser configurations across nodes in a same way as you can distribute configuration files, but I cannot promise exact release when it will be implemented.

Best regards,
Victor

You can query FileSystem.Total(E:) using nxget to check it.

Best regards,
Victor

First problem is that message is empty - this is because of wrong parameter count in event tag - it should be <event params="1">100049</event>. But spam problem most likely caused by this:

[14-May-2014 10:15:41.670] [DEBUG] LogParser: file size differs for stat(4) and fstat(C:\NetXMS\var\log), assume file rename
[14-May-2014 10:15:41.670] [DEBUG] LogParser: file "C:\NetXMS\var\log" (pattern "C:\NetXMS\var\log") successfully opened
[14-May-2014 10:15:41.670] [DEBUG] LogParser: parsing existing records in file "C:\NetXMS\var\log"

we recently encounter this bug on another installation - agent erroneously assume that file was renamed, and start reading file from the beginning. It is already fixed in current development version.

Best regards,
Victor

Hi!

No, tables from scripts are not supported. However, you can use dbquery subagent to read tables from database (it could be sqlite database for example if you need something local).

Best regards,
Victor

Hi!

Condition (value != null || value != 0) is always true - if value is null then it will not be 0, and vise versa. Correct condition will be (value != null && value != 0), so full script could look like this:


snmp = CreateSNMPTransport($node);
value = SNMPGetValue(snmp, ".1.3.6.1.2.1.16.1.1.1.3." . $1);
return (value != null) && (value != 0);


@sperlm:

you are right, returning 0 is the same as returning false.

Best regards,
Victor

I'm a bit lost - are you sure this is log for parser mentioned in the beginning? From this log file I see that parser correctly found matching line (using StatusPoll.* pattern) and generate event. Parser in the first post had different matching pattern. Let's try to combine everything related in one post - server log and agent log for same time period plus actual parser definition.

Best regards,
Victor

Script looks correct. Could it be that disk E: has non-zero total space (could be the case if this is CD drive with disk inserted or any other read-only device)?

Best regards,
Victor

Судя по сообщениям об ошибке (ПРЕДУПРЕЖДЕНИЕ:  нехватка разделяемой памяти), проблема в настройках PostgreSQL сервера. Увеличте размер shared memory, должно помочь.