Queries on moving UIM robots to Secondary hub

Products

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

Issue/Introduction

We have multiple remote hubs and each hub has multiple robots reporting to them. We have a OS patching activity being planned during which the remote hub servers would be rebooted. 

For every remote hub, we have a failover hub for it and robots are configured with the Secondary hub. So when primary remote hub is rebooted, it would failover to HA remote hub and all robots reporting to primary remote hub would report to HA failover hub during the reboot. There are some robots that are not configured with secondary hub and it is difficult to identify which robot does not have secondary hub configuration.

Below are my questions:

1. When the Primary remote hub is rebooted, does it generate robot inactive alerts for the robots under it?

2. Will there be any loss of qos or alarms data from the robots when the primary remote hub is rebooted?

3. Is there way to configure the secondary remote hub in all the robots in bulk?

Environment

Release: 20.4 CU5

Resolution

1. When the Primary remote hub is rebooted, does it generate robot inactive alerts for the robots under it?

>>> Normally no, not within the given time for a reboot of the Primary hub.

2. Will there be any loss of qos or alarms data from the robots when the primary remote hub is rebooted?

>>>No, the local ATTACH queues will queue the data.

3. Is there a way to configure the secondary remote hub in all the robots in bulk?

>>> Yes, create a custom robot_update package.

Here are the basic steps:

In IM, drag and drop the controller probe to the local archive to create a ‘Configuration-Only’ package

1. Carefully edit the controller.cfx so it only contains the necessary data.
2. Then deploy it via drag and drop that to the other robots.

If you select the robot controller probe and drag it to your local archive, you will see this window.

 

You could then rename the package if desired, e.g., robot_update_secondary_hubX_cfg.

 Rt-click to edit the robot.cfx in the cfg package and replace the hub info with just the appropriate secondary hub data.

   secondary_domain =

   secondary_hub =

   secondary_hubrobotname =

   secondary_hubip =

   secondary_hubport =

Empty the OStype and OS values if this needs to be platform agnostic, otherwise leave it as is.

Then Click Ok, then Click Ok again to Save it.

Then distribute it to the target robots.