NetXMS Support Forum

Set "Repeat event" (in seconds, 86400) in threshold configuration - activation event will be regenerated if threshold is still active.

How many objects do you have in the systems? What are queue sizes?
Show output of:
* nxadm -c 'sh st'
* nxadm -c 'sh q'

We haven't tested anything newer than 12c, but I see no reason why it should not work with newer.

Quote from: Sch.Donat on February 10, 2020, 11:20:21 AM
What Oracle DB versions does NetXMS Support? Is it supports any newer version(s) than 12?

А это ноды вообще отдают список интерфейсов через SNMP?

Проверьте при помощи snmpget/snmpwalk:

# количество интерфейсов
nxsnmpget IP .1.3.6.1.2.1.2.1.0
.1.3.6.1.2.1.2.1.0 [INTEGER]: 33

# список индексов интерфейсов
nxsnmpwalk IP .1.3.6.1.2.1.2.2.1.1   
.1.3.6.1.2.1.2.2.1.1.1 [INTEGER]: 1
.1.3.6.1.2.1.2.2.1.1.2 [INTEGER]: 2
...

# имена
nxsnmpwalk IP .1.3.6.1.2.1.2.2.1.2
.1.3.6.1.2.1.2.2.1.2.1 [STRING]: GigabitEthernet1/0/1
.1.3.6.1.2.1.2.2.1.2.2 [STRING]: GigabitEthernet1/0/2
.1.3.6.1.2.1.2.2.1.2.3 [STRING]: GigabitEthernet1/0/3
...


# имена другим методом
nxsnmpwalk IP .1.3.6.1.2.1.31.1.1.1.1
.1.3.6.1.2.1.31.1.1.1.1.1 [STRING]: GigabitEthernet1/0/1
.1.3.6.1.2.1.31.1.1.1.1.2 [STRING]: GigabitEthernet1/0/2
.1.3.6.1.2.1.31.1.1.1.1.3 [STRING]: GigabitEthernet1/0/3
...

# алиасы
nxsnmpwalk IP .1.3.6.1.2.1.31.1.1.1.18
.1.3.6.1.2.1.31.1.1.1.18.1 [STRING]: ESX1
.1.3.6.1.2.1.31.1.1.1.18.2 [STRING]: ESX2
.1.3.6.1.2.1.31.1.1.1.18.3 [STRING]: ESX1-vMotion
...


nxencpasswd does not support passwords longer than 32 symbols, you have 33:
➜ orig git:(master) ✗ nxencpasswd netxms 'k081vv3C$UKe7z!ysP4Yf408^4m78SGF'
gyuWboDpO52LQYPeHCQ6LlksHezjf3cJmhb5/VpmgJE=
➜ orig git:(master) ✗ nxencpasswd netxms 'k081vv3C$UKe7z!ysP4Yf408^4m78SG'
gyuWboDpO52LQYPeHCQ6LlksHezjf3cJmhb5/VpmgJE=
➜ orig git:(master) ✗ nxencpasswd netxms 'k081vv3C$UKe7z!ysP4Yf408^4m78S'
gyuWboDpO52LQYPeHCQ6LlksHezjf3cJnms/LdPWmmg=

On my system this encoded password is different:
➜ ~ nxencpasswd netx 'k081vv3C$UKe7z!ysP4Yf408^4m78SGF'
STeHwaoRxKBJIy3cwcleEAcdrDERe/54rbusH9c57kA=

Do you use prepackaged binaries or do you compile netxms yourself?

Check netxmsd log for failed sql queries. Also check db writer queue size (there should be automatically created DCIs on the server node).

https://wiki.netxms.org/wiki/How_to_migrate_to_another_database

Yes, it's a bug, looks like automatic cast not working correctly in set custom attribute. Wrap -1 in quite marks and it will work.

// Set initial device attributes
// If an attribute does not exist, will create it with -1 as value
// If attribute already exists, will not change it


sub AirFiber()
{
if (GetCustomAttribute($node,"TestVar1") == null) SetCustomAttribute($node,"TestVar1","-1");
}

sub AirMax()
{
if (GetCustomAttribute($node,"TestVar2") == null) SetCustomAttribute($node,"TestVar2","-1");
}

Add brackets in "if":

if ( ifType->value == 1 && ifType->value == 1 ) return %(true,$1,ifName->value);

А на какой платформе запускаете клиента?

Yes

There was a mistake in the script - there are few more object types which can have idata_* tables.
Please use this script instead:

SELECT s.name FROM (
    SELECT
        substr(t.table_name,7) AS id,
        t.table_name AS name
    FROM information_schema.tables t
    WHERE
        t.table_schema='mtest'
        AND t.table_name LIKE 'idata_%') AS s
WHERE s.id NOT IN (
        SELECT id FROM nodes
        UNION SELECT id FROM clusters
        UNION SELECT id FROM access_points
        UNION SELECT id FROM sensors
        UNION SELECT id FROM mobile_devices
    );

Hello.

Number of idata tables should be roughly the same as number of nodes in the system.

This query should return list of tables without corresponding record in nodes or clusters:
SELECT s.id,s.name FROM (SELECT substr(t.table_name,7) AS id, t.table_name AS name FROM information_schema.tables t WHERE t.table_schema='mtest' AND t.table_name LIKE 'idata_%') AS s WHERE s.id NOT IN (SELECT id FROM nodes UNION SELECT id FROM clusters);

I assume you are talking about SYS_IF_DOWN, because SYS_NODE_DOWN is unrelated to expected interface status.

I see two ways:
1) Create DCIs
2) Change interfaces back to expected UP/DOWN and filter out SYS_IF_DOWN in EPP (with "stop processing" action). Most likely you'll want to change status propagation on interfaces to Normal, this way they will not affect status of the node itself (expect up/downlinks, probably). All these changes can be scripted (in Hook::ConfigurationPoll).