NetXMS Support Forum

Как-то так:


return $1 / GetDCIValueByName($node, ".1.3.6.1.2.1.43.11.1.1.8.1.1");


Small addition: if you have lot of values to convert or they change frequently you may want to create mapping table on the server (via Configuration -> Mapping Tables) and use NXSL function map (https://www.netxms.org/documentation/nxsl-3.0/#func-map) to map code to text.

Best regards,
Victor

Everything looks good. Please show object overview for few duplicating access points (I'm mostly interested in MAC address) and output of manual configuration poll on node.

Best regards,
Victor

Another option to avoid storing double events is to remove "write to event log" option from original event.

Best regards,
Victor

Hi,

you can switch object display mode to "large labels". In addition to basic object information any DCI marked as "Show last value in object tooltips" will be displayed on the label.

Best regards,
Victor

Hi,

seems like deadlock on server shutdown. Please try to capture netxmsd thread states with attached script (preferably on 3.0).

Best regards,
Victor

Hi,

is it that b.b.b.b/24 is actually 10.b.b.b/24 (i.e. within 10.0.0.0/8)? If not, could it be that those nodes actually have other interface with address in 10.0.0.0/8 subnet?

Best regards,
Victor

Hi,

when XMPP action is triggered but you do not see messages please try to capture state of netxmsd threads using attached script (you will need to install gdb and appropriate -dbg packages if you have installed server from deb repository). Also please try to set debug level to 6 and extract lines with text XMPP from server log when XMPP action is triggered.

Best regards,
Victor

Hi,

please also send walk output for .1.3.6.1.2.1.2.2.1.

Best regards,
Victor

Could you please provide SNMP walk output for OID .1.3.6.1.4.1.14988.1.1.1.3.1 on this Mikrotik device? Also, what NetXMS version you are using?

Best regards,
Victor

Yes, it's possible.

Best regards,
Victor

Update: version updated to 3.0.2357 to include small fix for regexp matching in network service checks.

Best regards,
Victor

Hi,

we just published server version 3.0.2355 - it has additional LDAP related debug output that can help in debugging.

Best regards,
Victor

Hi all!

NetXMS 3.0 patch release 5 (version 3.0.2355) is available. Only server component is affected. Changes since patch release 4:

- Fixed server crash after debug console command "show objects"
- Fixed server memory leak when exporting configuration
- Fixed server memory leak when creating ad-hoc summary tables
- Fixed bug in log writer
- Agent policies correctly uninstalled when node is deleted
- Fixed bugs in zone change operation for node
- Fixed bug in duplicate node detection
- Improved server debug output

Best regards,
Victor

Hi,

source address for connection is determined only by routing. NetXMS server itself does not specifically select source IP address. If routing is correct then it should work. For network service checks to work you should have "portcheck" sub-agent loaded in local agent (the one running on NetXMS server itself). Make sure that it is loaded. Also you may increase debug level for agent and check what is going on when server requests service check.

Best regards,
Victor