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. Icmp.AvgPingTime

Icmp.AvgPingTime

Scheduled Pinned Locked Moved Support
4 Posts 2 Posters 27.5k 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.
  • N
    N
    netago
    wrote on last edited by
    #1

    I hate to ask this because I am sure it is very simple.

    I have enabled the ping subagent. with target=192.168.254.253:target_1

    If I do a nxget localhost icmp.AvgPingTime(target_1) I get a value.

    However, I am unable to add a DCI to the node. I have tried putting icmp.AvgPingTime(target_1) in the parameter field, as well as the nxget localhost icmp.AvgPingTime(target_1). Either way I cannot get any data, so what the heck am I doing wrong.

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

      Hi!

      Are you trying to configure DCI on node you are pinging? If yes, then you have to set proxy node to your management server node.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • N
        N
        netago
        wrote on last edited by
        #3

        The other thing I have now found, is that the device has to be added to Trusted Nodes, or the server configuration parameter "ChecktrustedNodes" needs to be 0. Otherwise, you get an alarm indicating that the DCI is UNSUPPORTED.

        Is there a limit of targets that can be used? We have about 35 routers that I would like to track Ping Times and Packet Loss for.

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

          There are no hardcoded limit for number targets. The only limit is system and network resources (sockets, memory, etc.) but 35 targets definitely should be no problem.

          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