NetXMS Support Forum

Thank you so much for taking the time to reply to my post and offer your help!

I'm trying to set up reliable alarm and recovery notifications for my monitoring setup, and I was hoping you could advise me on the best way to achieve this using **native EPP rule configurations** in NetXMS 6.1.3, without needing to write custom NXSL scripts.

The core functionality I need is:
1.  **Alarm deduplication**: Only send one notification for the same issue within a 2-hour window, to avoid spamming
2.  **Proper alarm-recovery pairing**: Ensure recovery notifications are only sent for issues that actually triggered an alarm earlier
3.  **Targeted device filtering**: Only send notifications for devices I've marked as "focused" (not all devices in the system)

I did try writing my own NXSL scripts to implement this, but I got stuck on one critical part: I couldn't figure out how to design a **universal key value that works across all types of events and alarms** (similar to what I've seen others refer to as an "alarm key") to properly link alarm events with their corresponding recovery events. Without this, I can't reliably ensure that a recovery notification is only sent if an alarm notification was actually sent for that specific issue first.

I've looked through the EPP rule settings but I'm not sure how to combine these three requirements correctly using the built-in options. Could you walk me through how to configure the EPP rules to achieve this, or point me to the relevant documentation sections?

Thanks again for your time and generosity.

Dear Support Team,
I'm writing to seek technical support for two issues with the network topology functions.
When I right-click a node, select Topology maps, and choose Layer 2 topology or other topology types, the displayed topology coverage is far too large. It appears that the discovery scope is not restricted by the parameter Topology.DefaultDiscoveryRadius, which is currently set to 5.
Regarding the Network Map feature: when using MSTP links with ISP communication devices deployed between two end nodes, the system sometimes fails to recognize the connection relationship between the two terminal nodes. We presume this issue results from improper configuration of the intermediate ISP-side devices.
We sincerely hope you can offer relevant solutions and troubleshooting suggestions. Thank you very much for your help!
Best regards！

Hello NetXMS Development Team,
 
I have a question about the AI tool invocation format of NetXMS.
 
I heard that NetXMS currently only accepts AI tool calls developed based on standard JSON format, and it cannot work properly with models that adopt XML format for tool calling.
 
The Qwen3.6 series large models use XML format to implement tool invocation. I would like to confirm whether NetXMS is indeed incompatible with XML tool calling mode right now.
 
Besides, I sincerely hope that you can add support for XML format AI tool calls in subsequent version updates. This optimization will bring great convenience for users applying Qwen3.6 and other XML-based AI models.
 
Thank you very much for your time and support!

I have two questions to ask:
A previous issue (https://www.netxms.org/forum/general-support/help-h3c-port-security-policy-causes-the-switch-to-fail-to-learn-the-interface/msg32436/#msg32436) seems to have reappeared in the latest version. When a port security policy is configured on a switch interface, the MAC address status on the switch shows as secure instead of learned, and NetXMS appears to ignore MAC addresses in the secure state.
The AI model cannot execute tool calls, as shown in the screenshot. My configuration in netxmsd.conf is as follows:
plaintext
Module=aitools

[AI/Provider/qwen3]
Type = openai
URL = http://IP/v1/chat/completions
Model = qwen3.6-35b-a3b
Token = xxx
ContextSize = 32000
Timeout = 900
Slots = default

[AI]
DefaultProvider = qwen3
Looking forward to your reply. Thank you very much!

netxms client versions 4.0.6 and 4.0.7 do not run under 64 bit window7, no interface appears, the log in the .nxmc4 directory is empty, and versions prior to 4.0.5 work, what could be the reason for this, thank you very much!

netxms peernode shows up on wrong interface

System version: debian 11

netxms version: 4.4.1

Device Model : System Description=H3C Comware Platform Software, Software Version 7.1.070, Release 7557P03 H3C S7506E-V Copyright (c) 2004-2017 New H3C All rights reserved.

Problem:
The interface FortyGigE1/0/0/1 of the device is not in use and the status is down, but the interface shows that the peernode of this interface is juyuwang-10.61.252.221:10GE2/2/0/4, but the interface connected to juyuwang-10.61.252.221:10GE2/2/0/0/4 should be Te1/2/0/47. Try to set the snmp.driver property of the device to H3C or clear it, the problem still remains. Attached is the snmp walk result and debug 7 log, please point me in the right direction, thank you very much!

We need to locate the IP or mac address quickly, but if we configure a port security policy on the switch interface (as shown in the figure), the mac address status on the switch is "secure" instead of "learned". The problem is that netxms only learns the mac address of the "learned" state ( Switch Forwarding Database  ), the mac address of the "security" state seems to be ignored, please ask what is the way to learn all the mac addresses, thank you very much!

Take an aggregation device as an example, it is down-connected to dozens of devices, all of which have LLDP and SNMP working normal and have added nodes in netxms, but regardless of the peer node column in the NIC list or in the network topology, only part of peer nodes can be found, and the debug log shows: ProcessLLDPConnectionEntry( :SNMP get failed for remote ID D494E8582820). Your help is urgently needed, thank you very much!

Why are the epel and fedora sources not updated to the latest 4.3.2 version, thank you very much! Also, there seems to be a peer node recognition problem in 4.3.1, for example, aggregated devices can only recognize individual downlinked devices, while in the previous version 4.3.0 they could be fully recognized.

In centos8.5 system, it is prompted that netxms cannot be installed because of the missing "libjansson.so.4", but the file does exist, please ask the experts to guide, thank you very much!

When I manually disconnect a switch, the system quickly detects SNMP and ICMP errors, but then the node status becomes UNKNOWN, and then the polling of that node seems to stop, and the SYS_NODE_DOWN event cannot be generated,  the node status cannot become CRITICAL, please tell me under what circumstances the node status will become UNKNOWN and how to solve this problem, thanks a lot!

I would like to ask the expert a question: if an aggregation device is disconnected, all the devices under it will be offline, and each device will send an alarm message at this time. How can we make sure that only the top device performs the action of sending alarm message, and the lower part relies on the device not to send alarm message?

A few questions about network map：
1、How to hide the link label in the network map by default, or the default abbreviation, such as gigabitethernetg1/0/1 can be shown as g1/0/1?
2、The default network topology will show subnets, can be canceled?
3、If I want to show only the devices directly connected to the root node in the network topology, how to filter it?
I look forward to your guidance, thank you very much!

How can I filter the auto-discovered devices through snmp community, the current script is
sub main()
{
    transport = $1->createSNMPTransport(161,"stonewell2000");
    if(transport != null)
    {
        sysname = transport->getValue(".1.3.6.1.2.1.1.5.0"); 
        if(sysname != null && sysname !="" && sysname !=" ")
        {
            return true;
        }
    } 
    return false;
}

But the script reports an error, suggesting that if $1 is replaced by $node or $ NewNode , it will also report the same error, please ask the experts for guidance, thank you very much!