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. Status propagation for interface up/down

Status propagation for interface up/down

Scheduled Pinned Locked Moved Support
5 Posts 2 Posters 32.9k 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.
  • WatchmanC
    WatchmanC
    Watchman
    wrote on last edited by
    #1

    Hello.
    While DCI-status is propagated to parent objects with the original status (warning, minor, major, critical),
    the status for 'unexpected interface up' (major) or 'interface down' (minor) is always propagated with severity critical.

    As the the interface in object tree shows the status critical, it may be intentionally.
    But I would like to have the original interface severity propagated.

    Status calculation is set to default.
    Is there a setting to change this behavior?

    Thanks in advance.

    1 Reply Last reply
    0
    • F
      F
      Filipp Sudanov
      wrote on last edited by
      #2

      Which version are you using?

      Just tried recent one, unexpected interface up is critical on an interface and changes node to critical. Same for interface down.

      What about status calculation settings on the interfaces, not on the node, are they set to default?

      1 Reply Last reply
      0
      • WatchmanC
        WatchmanC
        Watchman
        wrote on last edited by
        #3

        >>> Which version are you using?
        Version 3.8.266, but I think the behavior has always been like that.

        >>> Just tried recent one, unexpected interface up is critical on an interface and changes node to critical. Same for interface down.
        .. and I think it's not correct.
        Why are events with the status minor or major processed as critical?

        • Event 'Interface down' with severity 'minor'
        • > Alarm 'Interface down' with severity 'minor'
        • > Status 'Interface' gets 'critical'?  ???

        >>> What about status calculation settings on the interfaces, not on the node, are they set to default?
        All status calculation settings are default (server-configuration, interfaces, nodes, container).

        Greetings

        1 Reply Last reply
        0
        • F
          F
          Filipp Sudanov
          wrote on last edited by
          #4

          If this is still an issue - what are values of StatusPropagationAlgorithm and StatusCalculationAlgorithm in Configuration->Server Configuration?

          1 Reply Last reply
          0
          • WatchmanC
            WatchmanC
            Watchman
            wrote on last edited by
            #5

            Values in Server Configuration are
              StatusPropagationAlgorithm: Unchanged
              StatusCalculationAlgorithm: Most critical

            I'll try to describe the 'issue' in other words:

            The 'port down' event (minor) leads into 'port status' critical > minor ≠ critical
            The 'port unexpected up' event (major) leads into 'port status' critical > major ≠ critical

            A change within StatusPropagationAlgorithm and StatusCalculationAlgorithm won't fix it.
            It's a decision of development or a bug.

            Greetings

            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