NetXMS Support Forum

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!

 Thanks very much,  I will try again！

NetXMS Server Remote Console V4.3.1 Ready
Enter "help" for command list

netxmsd: show stat
Objects............: 28053
Monitored nodes....: 557
Collectible DCIs...: 783
Active alarms......: 0
Uptime.............: 0 days,  0:07:58

netxmsd: show q
Data collector                  : 0
DCI cache loader                : 0
Template updater                : 0
Database writer                  : 0
Database writer (IData)          : 0
Database writer (raw DCI values) : 17
Event processor                  : 0
Event log writer                : 0
Poller                          : 0
Node discovery poller            : 0
Syslog processor                : 0
Syslog writer                    : 0
Scheduler                        : 0
Windows event processor          : 0
Windows event writer            : 0

netxmsd: sh thr
MAIN
  Threads.............. 24 (24/768)
  Load average......... 0.00 0.01 0.00
  Current load......... 0%
  Usage................ 3%
  Active requests...... 0
  Scheduled requests... 1
  Total requests....... 27
  Thread starts........ 0
  Thread stops......... 0
  Wait time EMA........ 0 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 0 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

AGENT
  Threads.............. 32 (32/256)
  Load average......... 0.00 0.00 0.00
  Current load......... 0%
  Usage................ 12%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 2475
  Thread starts........ 0
  Thread stops......... 0
  Wait time EMA........ 0 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 0 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

NPE
  Threads.............. 1 (1/1024)
  Load average......... 0.00 0.00 0.00
  Current load......... 0%
  Usage................ 0%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 0
  Thread starts........ 0
  Thread stops......... 0
  Wait time EMA........ 0 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 0 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

DATACOLL
  Threads.............. 30 (30/750)
  Load average......... 0.05 0.10 0.04
  Current load......... 0%
  Usage................ 4%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 6136
  Thread starts........ 0
  Thread stops......... 0
  Wait time EMA........ 0 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 0 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

CLIENT
  Threads.............. 16 (16/2048)
  Load average......... 0.00 0.00 0.00
  Current load......... 0%
  Usage................ 0%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 2213
  Thread starts........ 0
  Thread stops......... 0
  Wait time EMA........ 0 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 1 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

SYNCER
  Threads.............. 11 (10/100)
  Load average......... 0.00 0.00 0.00
  Current load......... 0%
  Usage................ 11%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 2646
  Thread starts........ 1
  Thread stops......... 0
  Wait time EMA........ 83 ms
  Wait time SMA........ 39 ms
  Wait time SD......... 24 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

DISCOVERY
  Threads.............. 192 (24/192)
  Load average......... 415.48 1596.52 946.05
  Current load......... 0%
  Usage................ 100%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 5511
  Thread starts........ 168
  Thread stops......... 0
  Wait time EMA........ 242677 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 0 ms
  Queue size EMA....... 904
  Queue size SMA....... 0
  Queue size SD........ 0

POLLERS
  Threads.............. 63 (30/750)
  Load average......... 2.76 36.67 29.92
  Current load......... 0%
  Usage................ 8%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 10282
  Thread starts........ 33
  Thread stops......... 0
  Wait time EMA........ 104 ms
  Wait time SMA........ 84 ms
  Wait time SD......... 226 ms
  Queue size EMA....... 26
  Queue size SMA....... 0
  Queue size SD........ 0

SCHEDULER
  Threads.............. 3 (3/192)
  Load average......... 0.00 0.00 0.00
  Current load......... 0%
  Usage................ 1%
  Active requests...... 0
  Scheduled requests... 1
  Total requests....... 2
  Thread starts........ 0
  Thread stops......... 0
  Wait time EMA........ 0 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 0 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

MOBILE
  Threads.............. 4 (4/256)
  Load average......... 0.00 0.00 0.00
  Current load......... 0%
  Usage................ 1%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 0
  Thread starts........ 0
  Thread stops......... 0
  Wait time EMA........ 0 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 0 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

netxmsd:  sh watc
Thread                                          Interval Status
----------------------------------------------------------------------------
Item Poller                                      10      Running
Syncer Thread                                    30      Sleeping
Poll Manager                                    5        Sleeping
Ad hoc scheduler                                5        Sleeping
Recurrent scheduler                              5        Sleeping

netxmsd: sh watchdog
Thread                                          Interval Status
----------------------------------------------------------------------------
Item Poller                                      10      Running
Syncer Thread                                    30      Sleeping
Poll Manager                                    5        Sleeping
Ad hoc scheduler                                5        Sleeping
Recurrent scheduler                              5        Sleeping

netxmsd:  sh poller
Type | Object ID | Object name                    | Status
-----+-----------+--------------------------------+--------------------------
STAT |      7292 | guangyuwang                    | child poll
ICMP |      7292 | guangyuwang                    | awaiting execution
STAT |    24835 | 5HaoXianCT                    | check SNMP
....

...
netxmsd:  show dbcp
0 database connections in use

netxmsd: show dbst
SQL query counters:
  Total .......... 571758
  SELECT ......... 309204
  Non-SELECT ..... 262554
  Long running ... 0
  Failed ......... 0
Background writer requests:
  DCI data ....... 6842
  DCI raw data ... 6842
  Others ......... 2031
netxmsd: show flags
Flags: 0x200425A001385CF1
  AF_DAEMON                              = 1
  AF_USE_SYSLOG                          = 0
  AF_PASSIVE_NETWORK_DISCOVERY          = 0
  AF_ACTIVE_NETWORK_DISCOVERY            = 0
  AF_ENABLE_8021X_STATUS_POLL            = 1
  AF_DELETE_EMPTY_SUBNETS                = 1
  AF_ENABLE_SNMP_TRAPD                  = 1
  AF_ENABLE_ZONING                      = 1
  AF_SYNC_NODE_NAMES_WITH_DNS            = 0
  AF_CHECK_TRUSTED_OBJECTS              = 0
  AF_ENABLE_NXSL_CONTAINER_FUNCTIONS    = 1
  AF_USE_FQDN_FOR_NODE_NAMES            = 1
  AF_APPLY_TO_DISABLED_DCI_FROM_TEMPLATE = 1
  AF_DEBUG_CONSOLE_DISABLED              = 0
  AF_AUTOBIND_ON_CONF_POLL              = 1
  AF_WRITE_FULL_DUMP                    = 1
  AF_RESOLVE_NODE_NAMES                  = 1
  AF_CATCH_EXCEPTIONS                    = 1
  AF_HELPDESK_LINK_ACTIVE                = 0
  AF_DB_LOCKED                          = 1
  AF_DB_CONNECTION_LOST                  = 0
  AF_NO_NETWORK_CONNECTIVITY            = 0
  AF_EVENT_STORM_DETECTED                = 0
  AF_SNMP_TRAP_DISCOVERY                = 0
  AF_TRAPS_FROM_UNMANAGED_NODES          = 0
  AF_PERFDATA_STORAGE_DRIVER_LOADED      = 0
  AF_BACKGROUND_LOG_WRITER              = 0
  AF_CASE_INSENSITIVE_LOGINS            = 0
  AF_TRAP_SOURCES_IN_ALL_ZONES          = 0
  AF_SYSLOG_DISCOVERY                    = 0
  AF_CACHE_DB_ON_STARTUP                = 1
  AF_ENABLE_NXSL_FILE_IO_FUNCTIONS      = 0
  AF_DB_SUPPORTS_MERGE                  = 1
  AF_PARALLEL_NETWORK_DISCOVERY          = 1
  AF_SINGLE_TABLE_PERF_DATA              = 0
  AF_MERGE_DUPLICATE_NODES              = 1
  AF_SYSTEMD_DAEMON                      = 0
  AF_USE_SYSTEMD_JOURNAL                = 0
  AF_COLLECT_ICMP_STATISTICS            = 1
  AF_LOG_IN_JSON_FORMAT                  = 0
  AF_LOG_TO_STDOUT                      = 0
  AF_DBWRITER_HK_INTERLOCK              = 0
  AF_LOG_ALL_SNMP_TRAPS                  = 0
  AF_ALLOW_TRAP_VARBIND_CONVERSION      = 1
  AF_TSDB_DROP_CHUNKS_V2                = 0
  AF_DISABLE_AGENT_PROBE                = 0
  AF_DISABLE_ETHERNETIP_PROBE            = 0
  AF_DISABLE_SNMP_V1_PROBE              = 0
  AF_DISABLE_SNMP_V2_PROBE              = 0
  AF_DISABLE_SNMP_V3_PROBE              = 0
  AF_DISABLE_SSH_PROBE                  = 0
  AF_SERVER_INITIALIZED                  = 1
  AF_SHUTDOWN                            = 0

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!

Thank you very much for the pointers!

Thank you very much, but  if  manually exclude the child nodes, it is too much trouble,  can there be any rule than can  automatically adapte  to it?

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?

Thank you very much for your advice! This is really the most powerful network manager I have ever tried!

I found that only the physical interface can get the peernode, but seems the value fetched by the vlan interface or bridge-aggregation interface is null, how can I get all the directly connected devices?

Okay，thank you very much！！

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!

ok,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!