NetXMS Support Forum

Hi,

NetXMS should fall back to ifTable automatically if ifXTable is not supported. You can forcibly disable by setting "Use ifXTable for interface polling" to "Disable" on "Polling" page in node properties.

Best regards,
Victor

Comma separated.

Best regards,
Victor

It is now possible to set display name for instance which is different from name (it is useful if for example you have to pass actual OID as parameter but want meaningful name in description). Instance name can be inserted into DCI description via {instance-name} macro. To set instance name you should return array of three elements from instance discovery filter: first element must be TRUE, second new instance, and third new instance name. For example, the following script can be used to name interfaces for collecting data from standard interface MIB:


// Get interface name from .1.3.6.1.2.1.2.2.1.2.{instance}
snmp = CreateSNMPTransport($node);
ifName = SNMPGetValue(snmp, ".1.3.6.1.2.1.2.2.1.2." . $1);
return %(true, $1, ifName);


Attached are screenshots with full DCI configuration.

Second is actually very easy - if you attach one instance discovery DCI to another instance discovery DCI, DCIs with actual data created from those will be attached to each other on performance tab as well, using instance as a key to find peers.

Best regards,
Victor

You can use Ctrl+Insert / Shift+Insert in any text field. Problem is that RAP platform tries to handle Ctrl+C / Ctrl+V and so it is not working in text fields. I currently do not have a solution for making Ctrl+C / Ctrl+V work.

Best regards,
Victor

For user_groups table just modify schema manually:


alter table user_groups modify description null


it will not affect upgrade to next version.

Fix for "access denied" error requires server recompilation. On what platform you have NetXMS server installed?

Best regards,
Victor

Hi,

actually, debug is enabled but debug output is not sent to remote console (but it's a bug, not a feature). You still got debug messages in the log.

Best regards,
Victor

Currently we plan to release 1.2.17 early in September.

Best regards,
Victor

Hi,

yes, this is a bug. It is already fixed in development trunk. Can you wait for 1.2.17 release?

Best regards,
Victor

This is because if there are no interfaces to poll NetXMS server uses only alarms to determine node status. You can get "normal" status if you will generate "normal" severity alarm from SYS_NODE_UP event. This is not elegant solution, I think I will move forward with implementing second option in near future - it should not take much effort to implement.

Best regards,
Victor

Hi,

grey background suggests that there was some error in GUI. Can you please post console log - usually %HOME%\.nxmc\data\.metadata\.log?

Best regards,
Victor

Without changes in NetXMS itself the only way to generate node down/up events for node without IP address is to use script in event processing policy which will use PostEvent to send SYS_NODE_DOWN or SYS_NODE_UP event when threshold is violated on interface status DCI.

I'm now thinking that it could be worth to add special functionality for such devices - probably by adding option to manually specify peer interface on managed node. Then status poll will check interface status and if it is down mark unmanageable node as down.

Best regards,
Victor

Я не совсем понял. Запрос по идее возвращает список узлов, у которых primary IP пустой. Но такого по идее не должно быть. Действительно есть ноды у которых primary_ip null?

Очень странно. Могли бы прислать скриншот настройки DCI?

Hi!

I see lot of errors like "Access denied for user 'netxms'@'netxms01' (using password: YES)" in your log. Are you sure everything is correct with password and access control for this user?

Best regards,
Victor

Some additional clarifications:

All configs delivered by policies are merged on agent startup. That means that each policy can bring it's own piece of total configuration, and those can be from same sections. For example, you have PING subagent loaded, and if two policies will have Target parameter in *PING section, agent will have two ping targets.
It is not mandatory to use XML format for configs delivered via policies, key=value format can be used as well.
It is possible to use comments in XML (with standard XML syntax <-- comment here -->).
"Description" tab is a left-over from old versions where there was no common comment field for objects. It should be removed.

Best regards,
Victor