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. Status of DCI 44 (SNMP: .1.3.6.1.4.1.3224.16.1.2.0) changed to UNSUPPORTED

Status of DCI 44 (SNMP: .1.3.6.1.4.1.3224.16.1.2.0) changed to UNSUPPORTED

Scheduled Pinned Locked Moved Support
6 Posts 2 Posters 29.7k 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.
  • Y
    Y
    yogita
    wrote on last edited by
    #1

    Hi All,

    Need help in setting up NetXMS. I have justed installed the server and added few nodes through autodiscovery. Now I am getting error messages like

    Status of DCI 44 (SNMP: .1.3.6.1.4.1.3224.16.1.2.0) changed to UNSUPPORTED

    Can some body help me on this !!! What this error message mean and how can that be rectified.

    Thanks in Advance,

    Yogita

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

      Hi!

      You can safely ignore them. It's a side effect of applying system templates. I'll fix it in next release.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • Y
        Y
        yogita
        wrote on last edited by
        #3

        Hi Victor,

        I have installed netxms and added few nodes > recently I have applied templates for memory and cpu. But still I am not getting the alarms.

        Its collecting data from node as it shows in DCI database but it shows  nothing in graph or on alarm browser.

        Kindly help to resolve the issue.

        Regards,

        Yogita

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

          Hi!

          Please post screenshots of your configuration (DCI configuration, thresholds, event processing policy) - it's hard to identify problem based on information you have provided.

          Best regards,
          Victor

          1 Reply Last reply
          0
          • Y
            Y
            yogita
            wrote on last edited by
            #5

            Hi Victor,

            Kindly find the screenshots attached.

            Regards,

            Yogita


            netxm.doc

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

              Hi!

              The problem is following: you generate event SYS_THRESHOLD_REACHED when you cross threshold. This event has sverity WARNING. Then, you have the rule in event processing policy, which has two filtering conditions: if event is either SYS_THRESHOLD_REACHED or DC_HIGH_CPU_UTIL AND event's severity is CRITICAL, then generate alarm. Your event will never pass through this filter, because it has severity WARNING. Also, your custom event - CPU_USAGE - is not used at all.

              You should do consistent config, for example as following:

              1. In threshold, set event to DC_HIGH_CPU_UTIL
              2. In event processing policy, leave "severity" column as "any", and leave only DC_HIGH_CPU_UTIL in "event" column
              3. Optionally, change alarm text to %m, if you wish to have alarm text to be the same as event's message

              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