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. About Subnet Object's Status

About Subnet Object's Status

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

    Hi, Victor!

        A question confused me a lot for long time, according to my understanding, the status of Subnet Object can only be changed by the related 2 interfaces status of network nodes belong to the subnet object, as the graph shows:

    A(X) --- B --- (Y)C

    A is a router, C is also a router,  B is the subnet through which the A & C are connected. X is the interface belongs to subnet B, Y is the interface belongs to subnet B, and by ordinary understanding, only X's and(or) Y's status change to down, B's status will be changed to down.

    But i find as long as A or C's status changes to error(including errors related or not related to the subnet), the B's status will changed to Error and an emergent alarm will arise. This characteristic makes me very confused, because i cannot locate the real problem in the network through monitoring the topology map'icon status changes.

    Please follow with interest, thank you!

    Best Regards!

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

      Status of subnet object will change if any of the node in this subnet will change it's status. It is not important if node status changes because of any one interface is down, or alarm was created for that node. You can slightly change the behaviour of subnet status calculation by changing status calculation rule for subnet object. For example, you can make subnet changing it's stats to critical only if 80% of nodes within this subnet is in critical state.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • B
        B
        Billy
        wrote on last edited by
        #3

        Thank you! i'll try to change the percent.

        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