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. Node with question mark on the icon of object browser

Node with question mark on the icon of object browser

Scheduled Pinned Locked Moved Support
7 Posts 5 Posters 10.4k 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.
  • T
    T
    tivanni
    wrote on last edited by
    #1

    Hi!
    On netxms, i have a node that cannot be monitored throught icmp ping. On that node, i have a dci that store the info about the status of the node and i manage the alarms depending on the value assumed by this dci.
    The only problem is that appear a question mark on the icon of the node in the Object three menu; i think this is caused by the icmp polling disabled .
    Is there a way to eliminate the question mark on the icon?
    Thank you!

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

      Hi!

      The only workaround I've found is to generate alarm for that node with "Normal" state and keep it in outstanding or acknowledged state. I've added a feature request for adding DCI based status calculation (https://www.radensolutions.com/chiliproject/issues/324).

      Best regards,
      Victor

      1 Reply Last reply
      0
      • Z
        Z
        Tatjana Dubrovica
        wrote on last edited by
        #3

        Will be available in next release 1.2.17.

        1 Reply Last reply
        0
        • Dani@M3TU
          Dani@M3TU
          Dani@M3T
          wrote on last edited by
          #4

          I see this feature is in V1.2.17. But how we can use it. I didn't found a documentation.

          1 Reply Last reply
          0
          • T
            T
            tomaskir
            wrote on last edited by
            #5

            @user54119 said in Node with question mark on the icon of object browser:

            I see this feature is in V1.2.17. But how we can use it. I didn't found a documentation.

            DCI > Options > Other Options > Use this DCI for node status calculation

            What exactly does it do, I dont know 🙂

            How does status calculation work if this is checked? Can it be checked for multiple DCIs? Etc...

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

              Hi,

              as previously noted, you can select one or more DCIs with "Use this DCI for node status calculation". Server expects such DCI to return numeric value in range 0 .. 4 which indicates status (0 =  normal, 1 = warning, 2= minor, 3 = major, 4 = critical). Most critical status of all status DCIs and active alarms will be taken as current node status.

              Best regards,
              Victor

              1 Reply Last reply
              0
              • Dani@M3TU
                Dani@M3TU
                Dani@M3T
                wrote on last edited by
                #7

                ok. I made my tests to this new feature:

                • node created with no interfaces (for an unmanagable device)
                • in polling properties of this node I deactivated all except 'Disbale data collection'
                • DCI created on this node which checks the status of the switch port (gives back 4 for down and 0 for up) and 'use this DCI for node status calculation' = ON

                Now when I switch off the device, I get an event 'SYS_NODE_CRITICAL'. When I switch on the device again, I get a 'SYS_NODE_NORMAL' event.
                But for my existing event processing policy I need 'SYS_NODE_DOWN' and 'SYS_NODE_UP' events. So I created a threshold on the DCI (!=0 -> SYS_NODE_DOWN, deactivation event SYS_NODE_UP) and everything works as expected.
                I will first use it for unmanageble provider-modems and switches.
                Maybe this helps someone.

                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