Ad Widget

Collapse

Network discovery - multiple different actions

Collapse
This topic has been answered.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Sub
    Junior Member
    • Feb 2019
    • 12

    #1

    Network discovery - multiple different actions

    Hello team,

    I'm looking for help. I'm trying to figure out how to have multiple executed actions for a discovered host.

    To illustrate:
    • 1st action, add host (uk-switch-access-1) and link the "switch" template (criteria: hostname contains "switch")
    • 2nd action, add into the uk group (criteria: hostname contains "uk")
    • 3rd action, add into the "access" group too (criteria: hostname contains "access")
    For sure, I can do all these actions through only one "Discovery Action" but this is not my need because I would like to reuse the 2nd action, for all hosts in UK and the 3rd action for all my access switches over the world.

    Currently, only one action is executed but not the next. Can you help me ? Thanks !
    Last edited by Sub; 17-05-2023, 20:21.
  • Answer selected by LenR at 23-05-2023, 22:03.
    Sub
    Junior Member
    • Feb 2019
    • 12

    Thank you LenR for your answer. Perhaps, the action ID (in database) defines the order, anyway, this is not a big deal for my use case.
    The main issue was about which action is executed or not but indeed, it was just a filter issue.

    To summarize, multiple separated actions work but the order seems to not be predictable.

    The post can be closed.

    Comment

    • LenR
      Senior Member
      • Sep 2009
      • 1005

      #2
      I don't think there is any guarantee that they run in any specific order. If 2 or 3 run before 1, they will fail, no host exists yet. But after the first happens, I would expect the others to follow on the next cycle. (I used that to may advantage on auto registration actions, but never discovery).

      Comment

      • Sub
        Junior Member
        • Feb 2019
        • 12

        #3
        Thank you LenR for your answer. Perhaps, the action ID (in database) defines the order, anyway, this is not a big deal for my use case.
        The main issue was about which action is executed or not but indeed, it was just a filter issue.

        To summarize, multiple separated actions work but the order seems to not be predictable.

        The post can be closed.

        Comment

        Working...