NetXMS Support Forum

Hi,

could you please run netxmsd under gdb (with Cisco driver back) and when it crashes show output of bt command. You'll need to install -dbg packages if you installed NetXMS from deb packages.

Best regards,
Victor

In source config on new machine specify address of old server in DBServer. You may need to enable Postgres connections from new machine in pg_hba.conf on old machine.

Best regards,
Victor

Hi,

it is not necessary that both databases are local for nxdbmgr migrate - both just should be accessible from the machine where you running migration tool. Usually it's better to run migration on destination (new machine) - then you can create correct netxmsd.conf for use by new server, copy netxmsd.conf from old server under different name or path, change it so that DBServer points to old database server, and run nxdbmgr migrate.

Best regards,
Victor

Then you need instance discovery DCI that will create separate DCI for each processor instance. You can set DCI parameter name to .1.3.6.1.2.1.25.3.3.1.2.{instance} and in instance discovery method select SNMP Walk - OIDs and use .1.3.6.1.2.1.25.3.3.1.2 as a base.

Best regards,
Victor

Hi,

as you are not interested in each individual CPU usage you don't actually need instance discovery. Instead, you could use script DCI that will walk all CPU load OIDs and calculate average. This script should work:


snmp = CreateSNMPTransport($node);
if (snmp == null)
return null;

varbinds = SNMPWalk(snmp, ".1.3.6.1.2.1.25.3.3.1.2");
if (varbinds == null)
return null;

count = 0;
total = 0;
for(v : varbinds)
{
count++;
total += v->value;
}

return total / count;


It returns null to indicate data collection error if SNMP walk fails.

Best regards,
Victor

Yes, but you have to use node object here, not IP address. You can use FindObject or FindNodeObject functions to get object by name.

Longer commands are not possible without agent and/or server modifications. Currently there is 1024 character limit on parameter length in AgentRead... functions.

I've also created couple of feature requests for SSH improvements:
https://track.radensolutions.com/issue/NX-1649
https://track.radensolutions.com/issue/NX-1650

Best regards,
Victor

Я попробую воспроизвести сегодня у себя - были другие жалобы на такую-же проблему с MS SQL, похоже сломали что-то в коннекторе.

We have a mid-June deadline, so should be soon.

Best regards,
Victor

Hi,

looks like a bug. That could happen if nodes were removed from the map and then added back. Try to run server with debug level 6 for some time, and when you experience that problem again, filter lines with NetworkMap word in it and post here.

Best regards,
Victor

Hi,

you can use NXSL script and function AgentReadList like this:


AgentReadList($node, "SSH.Command(mikrotik_ip,login,password,/system package update install)");


where $node is a node with SSH subagent installed. Of course you can use string concatenation to insert proper credentials and device IP address. For example, if variable $node points to NetXMS server node and variable mt to Mikrotik device, you can do


AgentReadList($node, "SSH.Command(" . mt->ipAddr . ",login,password,/system package update install)");


Best regards,
Victor

Quote from: Egert143 on May 27, 2019, 10:11:15 AM
I would like to ask one additional question, but not sure if i should start new thread for that. Is there possibility to have a "safe / know" list of devices per "site / subnet" for example known good mac + ip combo and when new device appears with network discovery it will get flagged?

Yes, it's possible with some scripting. Rough idea is to create mapping table with good MACs, setup script action to SYS_NODE_ADDED event, and in that script check if one of node's MAC addresses is in that table.

Best regards,
Victor

Hi,

predefined graphs and dashboards configurations are completely independent now. Adding predefined graph to dashboard seems like a good idea, I'll add it as feature request.

Best regards,
Victor

This was the bug in 2.2.14. Actually nxdbmgr check from 2.2.15.2 should have fixed that issue, you hadn't to reinstall everything.

Best regards,
Victor

Update: in release 2.2.15 size limit for instance field increased to 1023 characters.

Best regards,
Victor

Hi all!

NetXMS version 2.2.15 is available. It is mostly hotfix release for issues found in version 2.2.14. Full change log is following:

- Improved driver for Cisco Small Business switches
- Fixed issues:
        NX-1609 (Duplicate server configuration parameters)
        NX-1627 (Proxy node should not ping through itself)
        NX-1637 (Unrecognized Cisco SG Switch)
        NX-1639 (NXSL persistent storage entries not saved in database)
        NX-1644 (DB gets corrupted when adding container/nodes)
        NX-1645 (Broken UI element layout in table DCI "General" property page)

It is highly recommended to run nxdbmgr check after upgrading binaries and before first server start.

Best regards,
Victor