What is a UIM robot Cloud install and how does it work?

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

• Many clients use, a master image to roll out new systems.
• One way to deal with making sure the robot is installed and working properly when these images are deployed is to use the robot cloud install to deploy a partial robot setup to master image that will complete one the final image is deployed.
• This will allow for proper configuration of the robot with the new hostname, IP address and will prevent the problem of duplicate device id's being generated from an improperly set up cloned machine.

Environment

• UIM 8.X 9.X or higher
• Robot 7.X, 9.X or higher

Cause

• Cloning server images

Resolution

The full robot installer will provide two options, Normal install and Cloud install.

You will need to choose the Cloud install.

You will then come to the Cloud install screen below:

Base on how many times it will take for the image to be packaged and the final deployment to happen, you will need to change the number of times to restart.

After the robot installation, ONE of the restarts has been used.

example

1) set the value to 2 if on the third startup the final image will be live. This assumes 1 startup during the robot install 1 restart for packaging/staging on the third startup the robot will be live

2) you will need to set the DNS name for the hub that the robot will contact and get setup information for.

3) Many times these systems come and go and you do not want them left in UIM after they are turned off.

If this is the case make sure to check the Automatic unregister option so that when the robot is shut down it removes itself from the hub.

This install will leave your robot.cfg looking like the following:

<controller>

   domain = <UIM_domain>

   first_probe_port = 48000

   hub_dns_name = <FQDN>

   autoremove = yes

</controller>

 

A normal robot.cfg looks like the following:

<controller>

   domain = <UIM_domain>

   first_probe_port = 48000

   hub_dns_name = <FQDN>

   autoremove = yes

   reuse_async_session = 1

   hub = Primary_hub

   hubrobotname = Primaryhub

   hubip = <IP>

   hubport = 48002

   access_0 = 0

   access_1 = 1

   access_2 = 2

   access_3 = 3

   access_4 = 4

</controller>

 

The installation adds an additional file into the <nimsoft>\robots directory called cloud.cfg which has the contents of:

<setup>

   iterations_left = 1

   hub_is_local = yes

</setup>

 

The cloud.cfg file will be removed after the third startup.

There is a cloud.cfx that can be copied or renamed if it is needed with the original setting from the install.

 

NOTE: A request.cfg can be used with a cloud install to deploy packages for monitoring the robot automatically.