Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Announcements
  3. NetXMS 3.4 patch release 2 (version 3.4.284)

NetXMS 3.4 patch release 2 (version 3.4.284)

Scheduled Pinned Locked Moved Announcements
3 Posts 2 Posters 4.1k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • V
    V
    Victor Kirhenshtein
    wrote on last edited by
    #1

    Hi all!

    NetXMS 3.4 patch release 2 is published. Changes since previous release:

    • PostgreSQL monitoring subagent
    • Improved driver for Cisco Nexus
    • Improved LLDP based network topology discovery
    • Correctly detect LLDP capability on Mikrotik devices
    • New NXSL functions GetServerNode and GetServerNodeId
    • New NXSL function SendMail
    • Fixed UI bug with accessing collected performance data from data collection editor
    • Configurable size of SNMP proxy thread pool on agent
    • Housekeeper optimization
    • Added drivers for Cambium Networks devices (ePMP and cnPilot)
    • Fixed issues:
              NX-1863 (Logwatch fails on parsing large Windows Event Log events)
              NX-1880 (Duplicate links on automatic maps with multiple seed nodes)
              NX-1895 (After server restart GUI is not showing from where a custom attribute is inherited)
              NX-1897 (ReadPersistentStorage returns incorrect value for non-existing key)
              NX-1901 (Get node of active NetXMS server in NXSL)
              NX-1910 (Spelling mistakes in Java API)

    There were no changes in agents besides WIndows, so agent packages were not updated and 3.4.232 still good to use.

    Best regards,
    Victor

    1 Reply Last reply
    0
    • B
      B
      blingblouw
      wrote on last edited by
      #2
      • Correctly detect LLDP capability on Mikrotik devices

      Very curious about this one. I see devices are still not showing as isLLDP on capabilities also don't get anything on the layer2 topology map

      EDIT: sorry, upgrade went bad. it is showing now. great!

      1 Reply Last reply
      0
      • V
        V
        Victor Kirhenshtein
        wrote on last edited by
        #3

        For reference, for LLDP based topology working correctly with Mikrotik router software should be at least 6.46 (so current LTS version will not work).

        Best regards,
        Victor

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        Powered by NodeBB Contributors
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups