NetXMS Support Forum

Должно быть %%

Hi,

now you should use state attribute to determine node state. For convenience server version 3.0 defines constants for each state:

NodeState::Unreachable
NodeState::NetworkPathProblem
NodeState::AgentUnreachable
NodeState::SNMPUnreachable
NodeState::CacheModeNotSupported

ClusterState::Unreachable
ClusterState::NetworkPathProblem
ClusterState::Down

SensorState::Unreachable
SensorState::NetworkPathProblem
SensorState::Provisioned
SensorState::Registered
SensorState::Active
SensorState::PendingConfigUpdate

So equivalent of 2.2.x

if ($node->runtimeFlags & 0x0004)


will be


if ($node->state & NodeState::Unreachable)


State bit 4 is not used and it's presence is a bit of a mystery. Probably something goes wrong during DB upgrade. You can left it as is - it will not affect anything, or clean it up in database while server is stopped using the following queries:

UPDATED object_properties SET state=0 WHERE state=4;
UPDATED object_properties SET state=1 WHERE state=5;

This will clean it up for most common flag combinations.

If you are using PostgreSQL you should be able to do this in one query using bitwise AND:

UPDATED object_properties SET state=state & ~4;

Best regards,
Victor

Hi,

there is no built-in function specifically for FDB retrieval but you can do SNMP walk and retrieve FDB that way. I see more problems with calling external REST API. Alternatively you can do everything from nxshell script - get FDB, do REST call, and rename interface.

Best regards,
Victor

Hi,

we don't have other reports for such behavior, even for quite large deployments. Please turn on debug logging on proxy and server to level 6 and send part of the logs for period when one such issue experienced.

Best regards,
Victor

Это проблема старого агента - он возвращал неполные версии пакетов и получались дубликаты. Обновление агентов должно решить проблему.

Please share your config.log. I've installed clean CentOS 7 and mariadb-devel package and build went without errors using --with-mysql. However versions are different:

rpm -qa *aria*
mariadb-devel-5.5.64-1.el7.x86_64
mariadb-libs-5.5.64-1.el7.x86_64

How did you install MariaDB client?

Best regards,
Victor

Hi,

if your devices supports enable/disable port by changing certain SNMP OID you can use script action with SNMPSet function.

Best regards,
Victor

Hi,

try to use --with-mysql instead.

Best regards,
Victor

Hi,

yes, it was broken in 3.0. I've just uploaded web service war version 3.0.2296 where this bug is fixed.

Best regards,
Victor

Yes, it's possible. What is currently missing for that device which should be provided by the driver? Currently driver can be used to get list of VLANs, interfaces, physical port layout, wireless access points and clients.

Best regards,
Victor

Hi all,

we just published patch release 3.0.2292. It fixes issues broken NXSL function SNMPSet, potential heap corruption in GSM notification channel driver, and bug in database migration if target is TimescaleDB.

Best regards,
Victor

Можно например таким NXSL скриптом:


global visited = %();

EnumerateNodes(FindObject(1));

sub EnumerateNodes(rootObject)
{
for(o : GetObjectChildren(rootObject))
{
if (classof(o) == "Node")
{
PrintDCIs(o);
}
else if (classof(o) == "Subnet")
{
EnumerateNodes(o);
}
}
}

sub PrintDCIs(node)
{
if (visited[node->id] != null)
return;

println("***** " . node->name . " *****");
for(dci : FindAllDCIs(node))
{
println("   " . dci->description);
}

visited[node->id] = 1;
}


На какой ОС установлен сервер? Версия сервера 3.0.2287?  Если Windows, пришлите пожалуйста минидамп после падения если он есть.

Это список того, что сервер обнаружил на устройстве. Проблема в том что на SNMP устройства не отвечают - надо смотреть почему. В первую очередь стоит проверить настройки файрвола, какой community string прописан на сервере и соответствует ли он тому, что настроено на устройствах, прописаны ли ограничения по IP адресам на устройствах.

Hi,

it is probably misleading choice of status icons. We have white cross on red circle to indicate port is down and red circle to indicate that it is disabled. Probably we could use something more gray colored to underscore that interface was disabled intentionally rather than has problem.

Best regards,
Victor