NetXMS Support Forum

Just reduced limit to two bytes, will be included into next patch release.

Best regards,
Victor

Hi,

do you have coredump from the crash? If not, could you try to run netxmsd under gdb? For running onder debugger follow this instruction:

1. Stop netxmsd service
2. Install package netxms-server-dbg
3. Run

gdb netxmsd

4. In (gdb) prompt, enter

run -D2

5. When server stops, you'll get (gdb) prompt again. Enter command

bt

and provide the output.

Best regards,
Victor

Hi,

it requires at least 3 bytes of MAC address. Idea was to limit potentially very broad search. But I think we can change it if there is a use case for such wide searches.

Best regards,
Victor

So, we decided to add a little bit more planning into product development and start publishing development roadmaps. First one is for next minor release of NetXMS - 4.2. Major focus will be on improving network monitoring functionality and finalizing transition to new UI. Currently first release in 4.2 branch is planned for late June.
Below is a list of planned improvements and issues to be addressed:
    - More OSPF information and better visualization
    - Support for binary multipliers in DCIs
    - Measurement units for DCIs
    - Improved Mikrotik device support (VLAN information, maybe easy access to configuration, command execution)
    - Finalize functionality transition to new UI
    - Add 'conflict' marker to inherited custom attributes (issue NX-2251)
    - When creating a node, add the ability to immediately create interfaces with IP and CIDR (issue NX-2238)
    - Add the ability to change the height for passive elements in rack as well as to use custom images (issue NX-2237)
    - Periodically apply changes in templates and data collection configuration if editing tab is not closed (issue NX-2232)
    - Add portcheck functionality into netsvc and deprecate portcheck subagent (issue NX-2192)
    - Configurable server's SNMPv3 engine ID (issue NX-2259)

Best regards,
Victor

С этим буде сложнее - функции фильтра для показа у этого элемента нет. Единственный вариант, который приходит в голову - сделать еще один табличный DCI, и в нем transformation script, который будет удалять ненужные строки. И уже этот DCI выводить на дашборд.

Hi,

it doesn't look like debug level is set correctly. You can open server debug console (either from desktop client via Tools -> Server Console, or from command line on server machine by running nxadm -i) and enter command debug to get current debug levels. Then you can set debug level for required tag with command debug ncd.telegram 7.

Best regards,
Victor

Hi all!

NetXMS 4.1 is released. This is minor release mostly aimed at fixing issues found in 4.0 and minor improvements. Full change log is following:

- Maintenance journals for objects
- SSH connecivity checked as part of status and configuration polls
- Runtime errors in filtering scripts interpreted as "ignore" if applicable and otherwise as "block"
- Authentication option (on by default) for local server console (accessible via nxadm)
- Added driver for Ubiquiti EdgeSwitch switches
- Octal numeric constants removed from NXSL
- New string method "equals" in NXSL
- Jira connector supports Jira Cloud
- Internal metrics for monitoring notification channels
- Improved titles in dashboard elements
- Ignore IP addresses found during network discovery on interfaces marked as excluded from topology
- Added AgentTunnels.Certificates.ReissueInterval and AgentTunnels.Certificates.ValidityPeriod server configuration variables
- Fixed DCI creation from NXSL
- Added $dci variable to DCI script
- Added option to configure column data type for external table
- Fixed issues:
        NX-1183 (Add option to choose automatic colors for instances in performance tabs)
        NX-1734 (Add column "Peer Interface" to interface list view)
        NX-1785 (Automatic color assignment for items on performance tab graph)
        NX-1802 (Binary data support in NXSL SNMP functions)
        NX-2021 (Title is not displayed for some Dashboard elements)
        NX-2154 (Node search by partial MAC address)
        NX-2163 (Show user name on process tab)
        NX-2165 ("Show file" in file manager displays incorrect progress bar message)
        NX-2196 (Keep SNMP alias separately in interface object)
        NX-2215 (Remake XMPP into a notification channel)
        NX-2216 (Telegram notification channel should throttle message sending and retry sending after timeout)
        NX-2220 (Add timer key column to Scheduled Tasks)
        NX-2223 (Notification log view should have multi-line preview panel)
        NX-2225 (Maintenance journal)
        NX-2226 (Agent policy move to TemplateGroup)
        NX-2229 (Add scrollbar and ability to resize to script editor in Object Query)
        NX-2230 (Business service enhancements)
        NX-2231 (Use TCP/UDP for active network discovery)
        NX-2233 (Add new agent metric similar to Service.Check() that would follow redirects)
        NX-2239 (Node SSH polling)
        NX-2240 (Changes to DCI comments in template are not synchronized with DCIs created from that template)
        NX-2242 (On Windows, if agent action calls .cmd file and that file produces output, execution fails)
        NX-2252 (TLS.Certificate.* 500 internal error to some domains when nginx enabled ssl_reject_handshake on)
        NX-2254 (LDAP synchronization error events generated for any LDAP user login error)
        NX-2255 (SQL issues with server_action_execution_log)
        NX-2256 (Have two separate certificates on server - for TLS connection and to issue agent certificates)
        NX-2257 (PostgreSQL.Version returns 0.0 if database is not connected)

Best regards,
Victor

Hi,

you should be able to do that using nxshell script as it provides access to full Java API.

This is sample script that should change SNMP settings to V3, SHA1/AES for all nodes:

for node in [o for o in session.getAllObjects() if isinstance(o, objects.Node)]:
   print 'Node: ', node.getObjectName()
   try:
      md = NXCObjectModificationData(node.getObjectId())
      md.setSnmpVersion(SnmpVersion.V3)
      # Auth/priv set to SHA1/AES, change first number to:
      # 0 for none
      # 1 for MD5
      # 3 for SHA224
      # 4 for SHA256
      # 5 for SHA384
      # 6 for SHA512
      # Change second number to:
      # 0 for none
      # 1 for DES
      md.setSnmpAuthentication("login", 2, "authPassword", 2, "privPassword")
      session.modifyObject(md)
   except:
      print "Cannot change node configuration"


Best regards,
Victor

Hi,

please set debug level to 6 for tag ncd.telegram, try to send notification again, and check server log.

Best regards,
Victor

Возможно используете не тот элемент на дашборде (DCI summary table судя по описанию) - надо использовать "table value" - он показывает значение конкретной таблицы.

Quote from: semi-liquid on April 25, 2022, 09:11:58 AM
мне бы понять таки как в письмо воткнуть имя пользователя)

Там выше предлагался вариант со скриптом. Его можно даже еще упростить и просто вставлять результат в сообщение, без дополнительных атрибутов:


list = $node->readAgentList("System.ActiveUserSessions");
return SplitString(list[0], "\"")[1];


и в сообщении использовать макрос %{script}, где script - это имя скрипта в библиотеке.

Это баг, его уже починили в development ветке. В следующем релизе будет работать.

Да, войдет в 4.1. Мы планируем релиз в течении нескольких дней (скорее всего понедельник).

Ну и сейчас можно сделать любую картинку как фон, и по ней расставить объекты и линки тянуть как угодно (используя тип роутинга bendpoints на линках).

Добавили методы readMaintenanceJournal и writeMaintenanceJournal.

Пример добавления записи:

$object->writeMaintenanceJournal("Maintenance operation description");


Пример чтения:

for(r : $object->readMaintenanceJournal())
println(r);


В readMaintenanceJournal можно передавать два дополнительных параметра - начало периода и конец периода, оба как UNIX timestamp.