3 Replies Latest reply on May 3, 2012 4:20 PM by Rohit Nayyar

    Routing Rules in the new 8.2 Unified Agent Installer

    Joe Piotrowski

      First I want to verify that I have the concept of Remote Host Authentication Routing Rules correct. Then I would like to know if there are any best practices in using these Rules that I am not aware of.


      First, my understanding of Remote Host Authentication Routing Rules is that I can use conditions to determine which:

      - Remote Host Authentican to use (Windows PsExec, Linux SSH, etc)

      - Which Automation Principle to use (username/password)


      This allows me to create a single Agent Installer Job, referencing multiple Agent software installer binaries (Windows, Linux, AIX, etc) and multiple authentications (username/password) to install Agents. The Remote Host Authentication Routing Rules will then determine which binaries and authentications to use to install the Agent. Is that correct?


      If that is the correct process, then I need some assistance on best practices for these Rules. From what I can determine, the only Property I can reference to create a Rule is the server TARGET property. But before the Agent is installed, there are very few unique Property values populated for me to reference. In fact the only two server property values I can think of to leverage are the IP_ADDRESS and NAME properties.


      So, if all of my Linux server names begin with "L" or all my Windows servers are in a certain IP range, I can easily create Rules to match that. But what if there is no common server naming convention? Or if they don't use certain IP ranges for different OSs? Are there any other Rules I can create to facilitate my Agent installs? Or is that basically it?

        • 1. Re: Routing Rules in the new 8.2 Unified Agent Installer

          You can create Custom Properties on the Server class to differentiate the Servers and use  the same property in these rules.

          This is similar to Proxy rules. 


          This being very new, the best practices I think will be based on the The different authentication mechanism you choose as per your environment

          • 2. Routing Rules in the new 8.2 Unified Agent Installer
            Joe Piotrowski

            Thank you Rohit. Just so I understand you I would have to do something like the following:

            - Create a new global Server property (UAI_OS for example)

            - When I import my servers, have that property set (UAI_OS = Linux, Windows, AIX, etc)

            - Change my Rules accordingly (If TARGET.UAI_OS = "Linux" then use this server/credentials)


            Unfortunately, my current mechanism is failing because both of my Rules are;

            if TARGET.NAME != null


            So it works on Linux servers (because it checks and OKs that Rule first) but fails on Windows servers.

            • 3. Routing Rules in the new 8.2 Unified Agent Installer

              Yes, the OS based rules will work

              The rules you have specified are same, the first one will always be evaluated as successful, and hence everytime it will use the Linux Authentication ,the first one

              Base it on the OS Type is a good idea because I believe most of the environments will have different authentication mechanisms allowed on OS basis.

              If you are integrating Provisioning , it will be a better idea to propogate this through the device property and

              make this a mandatory Server Property so that for every server, u have this property set.

              1 of 1 people found this helpful