NetXMS Support Forum

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

It makes sense. Theoretically it is possible that main process terminates before watchdog process completely stopped, and so files are still locked when installer start copying new files. I've changed agent so main process waits until watchdog process terminates and only then exits.

Was watchdog enabled in all cases of failed upgrades?

Best regards,
Victor

There are error in configuration, but it should not prevent alarm generation.

Can it be that you define threshold for DCI and only after define rule in event processing policy? In that case threshold violation event might be created before you define handling rule. You can check this by setting repeat interval in threshold - then it will repeat threshold violation event.

As for error I mention - you probably want to resolve existing alarm by "normal" event? If yes, then it will not work that way Problem is with alarm keys - resolve find alarm to resolve by key, but you specify different key in resolve rule than in alarm creation rule. This could be reduced to two rules:

1. Generate alarm from events CPU_LOAD_WARNING or CPU_LOAD_CRITICAL, with severity "from event" and key "CPU_LOAD_%i_%5".

2. Resolve alarm from event CPU_LOAD_NORMAL by key "CPU_LOAD_%i_%3".

Notice difference in key - %5 vs %3 - for historical reasons DCI ID is parameter number 3 for threshold rearm events and number 5 for threshold violation event.

Best regards,
Victor

According to trace, installer was unable to rewrite some files because of sharing violation - system didn't allow rewriting them as they was already open (presumably by some process). Looks like nxagentd.exe didn't exit before upgrade. I'll try to simulate this in my network.

Best regards,
Victor

Hi!

"Command generates output" option is not handler correctly yet for agent actions. Will fix this for next release.

Best regards,
Victor

Hi!

Likely some sobtle error in configuration. By description everything looks correct. Can you share screenshot of exact configuration - maybe I'll spot the problem.

Best regards,
Victor

You have to select .1.3.6.1.4.1.9.9.13.1.3.1.2 (or any other working OID inside .1.3.6.1.4.1.9.9.13.1.3.1) as table's base OID, and use .1.3.6.1.4.1.9.9.13.1.3.1.2, .1.3.6.1.4.1.9.9.13.1.3.1.3, etc. for column OIDs. I've created short document with working SNMP table example: http://wiki.netxms.org/wiki/Creating_SNMP_table_DCI.

Best regards,
Victor