NetXMS Support Forum

Hi!

you mean that you've found some specific place in added code which caused this crash?

Best regards,
Victor

Hi,

I've found a problem, although I cannot understand what caused it yet. From the log it looks like there are some alarm(s) with invalid severity code (255), and some UI parts cannot handle it correctly. Could you please post results of the following SQL queries:

SELECT alarm_id,original_severity,current_severity FROM alarms WHERE alarm_state<>3;

SELECT rule_id,alarm_severity FROM event_policy;

Best regards,
Victor

Hi,

can you please run netxmsd under gdb and post backtrace after crash? Here is the instruction: http://wiki.netxms.org/wiki/Running_NetXMS_under_debugger

Best regards,
Victor

Hi,

I cannot reproduce this. Can you please send me console log (usually %HOME%\.nxmc\data\.metadata\.log)? Do you have this problem on all consoles or only on one?

Best regards,
Victor

Currently you cannot change node status directly - if it is down, it will be critical. You can increase value of "poll count for status change" to 10 - then system will consider node as down only after 10 unsuccessful polls. Then you can setup ping to the node and trigger alarm of lesser severity after first ping loss.

Best regards,
Victor

Пока единственный вариант наверное - это делать новый объект (узел) на каждое такое устройство. Кстати в следующем реолизе появится возможность менять статус таких устройств - например выставлять статус неуправляемого коммутатора на основе статуса порта управляемого коммутатора.

Hi,

probably using proxy agents is best solution for you. All you need is to open port 4700 for connection from NetXMS server to just one server with agent. You can turn on encryption and authentication for security. All devices and servers could then be monitored via this single proxy. You may also need to enable zoning and setup separate zone for each remote site - it may simplify proxy configuration (as you can define default proxy settings on zone level) and is required if remote networks have overlapped IP addresses.

Best regards,
Victor

Yes, seems that it was forgotten. I've created issue in bug tracker (https://www.radensolutions.com/chiliproject/issues/641). As for #4, it will be in 2.0 branch, probably close to year end.

Best regards,
Victor

Seems that it was forgotten. I've scheduled it for 1.2.17 release.

Best regards,
Victor

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