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. Interface changed state

Interface changed state

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

    I am monitoring about 10 machines so far.  For the most part I am not having a problem.  I just rebooted each of the 10 machines.  I have a problem with two of them.  80% of the machines have dual nics.  Each nic is on a different subnet.  Let's say 10.1.1.x for one nic and 10.1.2.x for the other nic.  I had just two machines, upon a reboot, not give me a node down status.  Instead, I got a Minor warning and the message was Interface "Local Area Connection 2" changed state to DOWN (IP Addr: 10.1.2.x/255.255.255.0, IfIndex:12)  This nic is not set as the primary (dont know if that makes a difference or not).  I would like a node down instead of this warning.  How do I fix this?

    Thanks.

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

      Hi!

      Server considers node as down if all it's interfaces is not reachable and node cannot be contacted by SNMP or via agent. How long a reboot was taken? If it was relatively fast, then it is possible that moment when node was completely unreachable fall between two status polls (each 60 seconds by default), and server never seen these two nodes as completely down.

      If this is the case, solution depends on your goal - for example, if you wish to detect that node was rebooted, you can add monitoring of system uptime, and if it below some small value, like 100 seconds, that means that node was just rebooted and you can generate appropriate event.

      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