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. Get Status of node but disable alarms

Get Status of node but disable alarms

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 23.6k 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.
  • D
    D
    davidfs
    wrote on last edited by
    #1

    Hi,
    I'm trying to get all devices of my network classfied (switches, servers, but also phones, tablets, laptops, etc..), and I'd like to separate in two main categories, or profiles: The "critical" ones, which I want to be notified for any change, and the only "observed", which I only want to keep track of ip, mac address, dns name, but don't need to be notified at all.

    The "crititcal" ones, have a fixed ip address, and the oberved have a dynamic ip assignment by dhcp. The dhcp is configured to keep dns name consistent.

    I'd like to get advice about how to accomplish this with netxms. What options do I have?

    If I'm not wrong, if I set a node in Unmanaged mode, it does not keep track of the ip changes, isn't it?

    I'll manually classifiy the nodes into containers, and the critical and oberved are the 2 main containers inside "Infrastructure Services".

    Thanks.

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

      Hi,

      if nodes already classified into one of two containers, all you need to do is to change relevant rules in event processing policy to only trigger for nodes in "critical" container (just add that container as source filter in the rule).

      Best regards,
      Victor

      1 Reply Last reply
      0
      • D
        D
        davidfs
        wrote on last edited by
        #3

        Thanks Victor,
        I've seen and applied new policies.
        Netxms can be difficult at first, but i'ts worth to give it a chance.!!

        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