NetXMS Support Forum

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!