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. NetXMS 'status' parameter

NetXMS 'status' parameter

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

    I see the below 2 logs happening.  Just wondering what the differences are.  Assuming 'Agent not responding' could be a connection problem and 'Device is down' could be a server crash?  Is it possible to have an 'Agent not responding' message even though the server has crashed and that one would never get the server is down message under this condition?  If that is the case would one receive the message 'Node is up' before 'Connectivity with native agent restored' message would appear.  If you did not get the message reply in this order then chances are the server not crashed.  Both responses get the same integer level of 4.

    20-Aug-2012 10:41:11 Warning device 07 (56) Native agent is not responding

    19-Aug-2012 12:11:35 Critical device 02 (51) Node down 

    Hope this makes sense.  Thanks.

    Tony M.

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

      Hi!

      "agent not responding" means that NetXMS server cannot communicate with agent (but node may still be alive and reachable), and "node down" means that node cannot be reached by NetXMS server with any allowed protocol - agent, SNMP, and ICMP. Usually you get "agent not responding" event before "node down", but it will be correlated to "node down" and will not be passed to event processing policy.

      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