Skip to content
  • NetXMS 6.04: Perfomance View drawing error

    Support
    7
    1
    0 Votes
    7 Posts
    59k Views
    S
    Just upgraded to 6.0.5 (server and webui), now it works as expected! Thanks Victor!
  • NetXMS 6.0 patch release 5

    Announcements
    1
    0 Votes
    1 Posts
    33k Views
    V
    We just published NetXMS version 6.0.5 - hopefully last patch release before 6.1. Changes since previous patch release: Fixed error in log view after console reconnect Fixed incorrect gap detection on line charts Fixed bug in handling permanent authentication token expiration time Fixed server crash during dashboard template processing Added -Z/-L mappings for AI, deployment, downtime, and incident log tables in nxdbmgr Fixed issues:   - #1052 / NX-842 (Ability to switch bar chart from lef-to-right rendering to right-to-left)   - #2561 / NX-2355 (An IP address from a Cluster object does not appear on a map in the address map)   - #3033 / NX-2831 (Custom attribute value lost on child object)   - #3050 / NX-2848 (Issues pinning views on WEB UI)   - #3135 (nxdbmgr migrate: "-Z" should skip related tables)   - #3139 (serial\_number field on nodes table too small)
  • Wireless controller

    Support (Russian)
    4
    0 Votes
    4 Posts
    29k Views
    A
    Не прошло. В теории я бы мог дома развернуть контроллер с одной из точек, проблема в наличии - не поручусь когда будет свободная точка, чтобы я мог ее занять для работ вне конторы
  • 0 Votes
    6 Posts
    29k Views
    E
    6.0.4 - решено, работает, спасибо
  • 0 Votes
    4 Posts
    33k Views
    F
    You can add this to agent config for additional debug: EnableSSLTrace = yes DebugTags = ssl:8 DebugTags = tunnel:8 Does roll-back to 5.2.8 help (agent protocol is backward and forward compatible, so you can use older agent with newer server).
  • NetXMS 6.0 patch release 4

    Announcements
    1
    0 Votes
    1 Posts
    46k Views
    V
    We somehow quietly published patch release 4 for version 6.0. Due to our participation in MWC 2026 last week packaging and publishing of 6.0.4 was very discreet. Changes since previous patch release: File delivery policy deployment uses separate agent connection to avoid interference with data collection NXSL removes trailing zeroes from floating point value representation (unless explicitly set as string) Database manager supports parallel table migration Internal node name resolver cache in syslog processor Fixed issues:   - #2378 / NX-2171 (In Configuration-\>Object Tools-\>General-\>Icon, give more info about image size accepted)   - #2920 / NX-2717 (Custom attribute conflict is not resolved back to normal)   - #3128 / NX-2928 (Add --resolve parameter option to NetworkService.Status)   - #3129 / NX-2929 (Left column of elements not displayed in interface Overview tab)   - NX-2932 (File deployment from multiple policies should be serialized)   - NX-2933 (External metric provider may leave orphaned processes on Windows)
  • NetXMS 6.0 released

    Announcements
    14
    0 Votes
    14 Posts
    719k Views
    V
    @johnnyva said in NetXMS 6.0 released: @victor Also, the timestamp conversion will be a background task after netxms server/db upgrade?  If so, how will nxsl/rest api present the timestamps when not all timestamps have been converted?  Will we have a mix of seconds and millisecond timestamps or will netxms server convert seconds to milliseconds even if the db entry has not been updated by the background task yet? Yes, conversion is a background task (but you should upgrade straight to 6.0.4), server will do conversion in background. Internally server renames idata tables, create new empty tables, and gradually moves data from old to new with conversion. So API will not see incorrect timestamps, but for some time after server start you will not see older data.
  • ICMP.PacketLoss Not Working on Public IP CPE

    Support
    2
    0 Votes
    2 Posts
    11k Views
    N
    I think I’ve figured it out.  Disregard this
  • Tool OID Filter

    Support
    4
    0 Votes
    4 Posts
    14k Views
    G
    After deleting and re-creating the tool and filtering on OID it works as expected
  • help -network discovery

    Support
    3
    0 Votes
    3 Posts
    14k Views
    N
    Victor - this has been resolved.
  • 0 Votes
    1 Posts
    197k Views
    E
    Сабж. Вводят в заблуждение - предлагаю убрать, оставив только квадратики пустые. Либо, что лучше, если возможно и позволит ширина квадратиков - заполнять автоматически giXX / %interface name%, как в всплывающем меню собственно. [image: state-status.png]
  • Upgrade to 6.0.2 - Database upgrade fails

    Support
    7
    0 Votes
    7 Posts
    21k Views
    V
    Just published 6.0.3 - it should have the fix.
  • NetXMS 6.0 patch release 3

    Announcements
    1
    0 Votes
    1 Posts
    46k Views
    V
    Today we have published patch release 3 for version 6.0. Changes since previous release: Added wireless controller bridge for Aruba Instant controllers (PR #257) Improved interactive SSH mode support Improved web API Windows agent renames in-use files during upload if they cannot be replaced Fixed incorrect handling of empty tool call list in LLM response Fixed bug in database schema upgrade on Microsoft SQL Server Fixed issues:   - NX-2369 (Option to add number of items in a container)   - NX-2867 (Disable "Create database and database user before initialization" if SQLite selected in Windows installer)   - NX-2922 (New agent actions: enable / disable ExternalMetricProvider)
  • Can't see AI Assistant view in 6.0.1

    Support
    12
    0 Votes
    12 Posts
    31k Views
    J
    Wow, that's awesome, thank you so much!
  • AI Skills not loading.

    Support
    4
    0 Votes
    4 Posts
    13k Views
    D
    Thanks for the quick response. I've got the files downloaded and the skills have loaded OK now.
  • Syslog retention when deleting a node

    Support
    2
    0 Votes
    2 Posts
    13k Views
    F
    Audit log is retained after node deletion, same for syslog. For event log there's Events.DeleteEventsOfDeletedObject setting in Configuration->Server Configuration, if set to true (default), they are deleted. And there's similar setting for alarms - Alarms.DeleteAlarmsOfDeletedObject. DCI data is deleted. If database is Postgres Timescale, then event log and DCI history is not deleted. In all above situations when data is not deleted, it would be problematic to view it since you need to know node's ID. New decommissioning functionality is basically node unmanage with addition of automatic deletion at later time. So for now you can just unmanage your nodes.
  • 0 Votes
    1 Posts
    42k Views
    E
    Собственно предложение в топике. Сейчас если сетевой интерфейс в операционном статусе DOWN, то есть нет физического линка - система отображает в строке Speed видимо последнее значение. Это путает и не логично. Лучше если бы отображало в этом случае  0 принудительно, независимо от прочитанного по SNMP значения. В данном случае на приложенной картинке специфичный коммутатор фирмы Planet, он видимо некорректно сам возвращает значение скорости, когда link down. Возможно такое поведение есть еще у каких либо промышленных коммутаторов. Версия 5.2.8 [image: Безымянный2.png]
  • Oracle 26ai monitoring CDB and PDB´s with common user

    Support
    3
    0 Votes
    3 Posts
    16k Views
    E
    @filipp-sudanov said in Oracle 26ai monitoring CDB and PDB´s with common user: You can enquote the whole value: Database = "id=CDB0;driver=oracle.ddr;server=//hostABC:1521/CDB0;login=c##netxms_agent;Password=mypassword" Thank you Filipp. This was the missing hint. I tried to enqoute only username. Now it works like a charme. Thank you verry much!
  • Upgrade to 6.0.0 - Database upgrade fails

    Support
    30
    0 Votes
    30 Posts
    73k Views
    A
    In general I always recommend to start with https://pgtune.leopard.in.ua, when using Postgres
  • Mac version 6.0.0 not downloading

    Support
    5
    0 Votes
    5 Posts
    17k Views
    A
    https://netxms.com/download/releases/6.0/nxmc-6.0.2.dmg just published