NetXMS Support Forum

Here's an example of map filter script to start with.
if ($node->name == "sw-shelf") return true;

for (i:$node->interfaces) {
  p = i->peerInterface;
  n = i->peerNode;
  if (n != null and p != null and n->name == "sw-shelf" and p->name->contains("gi1/0")) return true;
}
return false;
It shows sw-shelf node and nodes connected to ports of the switch that have names beginning with "gi1/0".

But this script only shows directly connected devices. Do I understand correctly, that you actually want all the hierarchy that is connected to a specific port of your core switch?

There is Object Filter in map properties. That's script that is executed for each node to decide if it should be added to the map.
So in that script you can loop through interfaces of the node, interfaces have peerInterface attribute. This attribute, if not null, will have interface object of the switch.

Pls send a note if you need an example of the script.

It looks that there's a space in nodetimer_ %i after _ sign when setting the timer.

In overall - do I understand correctly, that you want do delay node down notification and send node up notification only if node down notification was sent? If so, currently this can be achieved without scripting, by filling in "Snooze/Blocking timer key" field in recovery notification properties.

Yes, if interface is down, it goes to critical (and there's currently no way to configure that severity). But we can affect the way how this status goes up to parent object (switch).

In properties of the switch node you can select Multiple thresholds status calculation. Put 100% to critical and 0 to Warning, Minor, Major. This means that only if 100% of child objects will go to critical, the node will become critical. So it should do the job.

You can also use smaller number there, e.g. if 50% of interfaces...

At some point external parameters started to capture STDERR in addition to STDOUT. Most probably your script produces some sort of textual error that is being captured. Then NetXMS tries to interpret it as integer and this way it becomes 0.

You can check with nxget
nxget IP_ADDRESS_OF_AGENT name_of_the_parameter

I've tried to run
powershell -Command "& {Get-MpComputerStatus | Select -ExpandProperty AntivirusSignatureLastUpdated}"
and the output starts from empty line:


Thursday, July 28, 2022 1:01:30 PM




Not sure if in previous versions agent was skipping empty lines, but currently it just takes the contents of the first line, which is emtpy.
Please try it e.g. this way:
ExternalParameter = DefenderEngineLastUpdate:powershell -Command "& Get-MpComputerStatus | Select -ExpandProperty AntivirusSignatureLastUpdated | Write-Host"

I will check with developers, but most probably reading of this property is not yet implemented in the new UI, as it's still under development.

Asterisk subagent is being built in .deb packages, but in generic Linux build it's not included. So it your platform is not .deb compatible, the only option is to build from sources.

Currently these things are not settable from script. We will discuss this internally, but in the end of July.

Your writing is precise.

For agent to server tunnel industry-standard TLS connection is established.
Also you can install netxms proxy in a remote office. That proxy will be the only node that communicates to the server directly. Proxy would communicate to all other machines at that location.

The only software needed to prepare certificates is openssl, it is included with NetXMS and should be in C:\NetXMS\bin

Try following the manual https://www.netxms.org/documentation/adminguide/server-management.html#initial-configuration
Pls send a message if something is not clear

Upgrade to the latest version - discovery debugging has been a bit improved recently.
Set debug level 6 for tag poll.discovery
Try running discovery - you can create a small range that covers just that IP address and manually force discovery for that range.

It's failing on this part:

wlanOpMode OBJECT-TYPE
SYNTAX INTEGER
{
ap(1),
--sta(2),
apwds(3),
brwds(4),
--stawds(5),
-- cr(6),
-- apr(7),
--rp(8)
--mesh-ap(9),
--mesh-only(10)
}

everyting after brwds(4), is commented out, so brwds(4), is the last item in list and it should not have , after it.

Скоро должны починить, будет релиз только nxmc.

A fixed management client has just been released.