Move the vmware probe to a new robot or hub

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We would like to migrate our current vmware probe monitoring to a new a new robot under a new hub. How can we do this migration keeping the consistency of the Inventory and the QOS Data? 

Environment

Release : UIM 20.4, vmware probe 4.18

Cause

Guidance

Resolution

The first consideration to take into account is that, if you deploy a VMware probe into a different system that has a different origin, to keep consistency of the inventory and the QOS data the new server must have the same Origin. 

If you simply install the VMware probe on a new system with a new origin,  the VMs, and the Vcenter discovered will be registered as different new duplicated systems:

 

In the below example, it is shown how by only copying VMware settings into a new hub called "remotehub" with its default origin, different from the one we had in the first vmware "marco_origin". As soon as devices are discovered, as the origin is a strong decorrelator, a new instance of the same machine is created under that different Origin, with a new cs_id and consequently the QOS will be registered under that new source:  

 

To keep the consistency of the servers at a discovery level (avoid duplication - cs_id's will be kept) and  at QOS Data level (the same QOS Definition and targets will be kept) follow the instructions below: 

The process for migrating VMware to a different hub would be the following. This process supposes that you are using VMware with Admin Console, using bulk configuration and VMware Templates: 

 

1. Deploy the VMware probe to the new hub or if needed to a robot under the new hub and deactivate the probe. 

2. If the Vmwae probe runs on the hub itself, update the origin of the hub in the hub GUI > Settings> General

3. if you do the above, all the robots under this hub will inherit the modified origin

4. If you deploy VMware on a single robot under a new hub, you can modify the origin on the robot itself only, just from the controller > Advanced Tab (Data Origin (override origin set by the hub) 

5. Copy the VMware probe folder from the original VMware robot (C:\Program Files (x86)\Nimsoft\probes\application\vmware) and paste it by replacing all files in the new VMware probe robot. This will keep the same configuration and templates. 

    (Alternatively, you can activate the probe and configure the new VMware probe in the new system mirroring the configuration and the templates applied from the original VMware but do not activate the profile yet.)

 

6. Once the folder has been replaced with the one from the old installation, stop the original VMware probe. 

7. Now activate the new VMWARE probe

 

After the first polling cycles the VMware probe will start collecting the data and will not create new cs_ids as the newly discovered systems will be merged with the old ones and the same S_QOS_DATA rows will be used as the met_ids will remain intact. 

The same S_QOS_DATA rows will be used for the same discovered targets. The same rows will have a new "host" IP which will correspond to the new VMware robot IP address.