NetXMS Support Forum

MIB files only provide a more convenient way to work in MIB explorer.

SNMP driver is selected from a number of drivers present in the system. List of drivers is available in docs: https://www.netxms.org/documentation/adminguide/snmp.html?highlight=snmp%20driver
These drivers provide special handling for some devices that are not handled well by generic driver.

Hi!

1) as discussed in another thread, under linux logger utility could be helpful to generate syslog messages
2) A matched syslog line generates an event, so we have to do the logic in Event Processing Policy (EPP). There you have filtering script - if it's not empty, event will be processed further only if that script returns true. You can just take current time in that script and check it:
now = localtime();
return (now->hour >= 8);

3) I am not exactly sure how to use the repeatCount in syslog processing, but anyway reaction to syslog only happens when a new syslog message is received. Here we need something in another place that would be executed regularly, event if there will be no syslog messages from a given node. A possible approach could be:
- when you receive backup successful message, store current unixtime in custom attribute of the node. You can do this in filter script in EPP:
$node->setCustomAttribute("lastBackupTime", time());
- create a DCI with origin "Internal" and parameter "Dummy".
- in transformation script add the following:
return time() - $node->getCustomAttribute("lastBackupTime");
as the result this DCI will have time in seconds since last backup.
- add threshold so that an event will be generated when time since last backup is too big.

Quote from: NicovdWalt on January 04, 2021, 11:25:23 AM
Good day,
I also did the update to 3.7.95 today and it keeps failing to start.
Centos 7.9

Check /var/log/netxmsd for any errors (or run       netxmsd -D5     in this case it will put log messages right to the console).

For active discovery do you specify particular proxy in "Active Discovery Targets"?

Do you have ping.nsm subagent enabled in proxy's configuration file?

Try abort instead of return null:

if ($1 < -100) {
  abort;
} else {
  return $1;
}

In properties of Infrastructure services -> Access Control you need to enable
- Read
- View alarms
access rights for that group.
And also View in properties of "Maps".

Web console by default tries to connect to server at 127.0.0.1. You need to specify the address of container where netxmsd is running. There are multiple ways how to do this, see here:
https://www.netxms.org/documentation/adminguide/installation.html#installing-web-interface-on-remote-system

What about netxmsd server, is it installed and running?

Try renaming the .war file to nxmc.war and deploying it.

There is no need to install intermediate version - latest version should be able to upgrade all the way through.
However, upgrade process ran into in issue on one of the steps. Can you please open psql, connect to your netxms database and show the output of the following commands:

\d alarms;

select count(*) from alarms;

\d old_alarms;

\d event_log;

\d  event_log_v35_2;

В Object Details в поле Driver что показывает для 1900-16 и 1920-48?

А какой драйвер определился на 1900-16 и 1920-48?

Импорт MIB файлов нужен для того, чтоб более удобно выбирать OID при создании DCI. На то, как отображаются интерфейсы устройста это не влияет, за это отвечает SNMP драйвер.

Для мониторинга состояния RAIDа также нужно найти OID, отдающий эту информацию и настроить DCI.

Оно в таком виде запускается: -d директория с исходными файлами, -o результирующий файл:
nxmibc -d /usr/share/netxms/mibs -o /usr/share/netxms/mibs/netxms.mib

и исходные файлы все должны быть с расширением .txt

I would restart the agent just to make sure, but you probably already did that.

There could be a few ways for the agent to read another config then the default one
- running it with -c <config_file_name>
- running it with -M <server_ip> - it would get config file from server
- configuration policies that add up to the config - they reside in system32/config/systemprofile/appdata/local/nxagentd/config_ap/   (or other user home folder, if agent is started under other user, not system one).

10 lines of log are not enough - they span for less then 0.1 seconds. Let's improve the process:

nxadm -c "debug client.* 6"
nxadm -c "logmark"
<replicate the error>
nxadm -c "debug client.* -1"

This will produce
2020.12.16 18:20:52.119 *D* [                   ] ******* MARK *******
line to server log. We need the log file from that mark to the end of the file.