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. Support
  3. Internal DCI's of NetXMS server changed to UNSUPPORTED

Internal DCI's of NetXMS server changed to UNSUPPORTED

Scheduled Pinned Locked Moved Support
4 Posts 4 Posters 53.8k 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.
  • K
    K
    Marshall Chen
    wrote on last edited by
    #1

    I just upgraded NetXMS server from v2.2.10 to v3.2.400. Everything is fine apart from below DCIs of NetXMS server itself.

    Server.ThreadPool.Load
    Server.ThreadPool.CurrSize
    Server.ThreadPool.LoadAverage
    Server.ThreadPool.Usage
    Server.Heap.Active
    Server.Heap.Allocated
    Server.Heap.Mapped

    it's keeping sending alarm saying the status of DCI changed to UNSUPPORTED. I can't find any post to discuss this case, anyone can give some prompt?


    Image 3.png

    1 Reply Last reply
    0
    • WoodyW
      WoodyW
      Woody
      wrote on last edited by
      #2

      Hello,
      here is the same issue, but on an other server:
      https://www.netxms.org/forum/general-support/snmp-requests-changed-to-unsupported/
      I hope this will be fixed soon.

      1 Reply Last reply
      0
      • T
        T
        tfines
        wrote on last edited by
        #3

        Seeing the same thing on NetXMS server 3.2.380 on Windows.

        1 Reply Last reply
        0
        • F
          F
          Filipp Sudanov
          wrote on last edited by
          #4

          Thank you for reporting.
          The ThreadPool DCIs are failing because you have only one SYNCER process configured (default setting) - in this case thread pool mechanisms are not used.
          Server.Heap ones work only if server was compilled with jemalloc.

          In coming 3.3. version out of the box templates were updated to fix these issues.

          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