Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Onboarding existing VMs (checklist)

You onboard existing virtual machines (VMs) by using the ServiceOfferingInstance onboard request. Before you onboard an existing VM, you must ensure that the VM is enrolled in BMC Server Automation and complies with the constraints of the onboard request. The following checklist can help you ensure that the VM is set up correctly in BMC Server Automation and that the input parameters for the API request are correct.

VM onboarding checklist

✅️

Item to check

 

Does the service offering that you want to use for the onboard operation exist?

Ensure that the associated service blueprint meets the following criteria:

  • The blueprint must specify only one resource set.
  • The number of networks specified in the resource set must be equal to the number of NICs available on the VM.

 

Does the network container that you want to use for the onboard operation exist?

Ensure that the network (port group) that the VM is on is part of this network container.

 

For a management network of the VM, is the port group created on the correct switch (as defined in the pod)?

 

Is the RSCD agent installed on the VM?

Ensure that the same version of the RSCD agent is installed on the VM and the  application server.

 

Is the VM enrolled in BMC Server Automation? For information about enrolling VMs in BMC Server Automation, see Knowledge Base article KA383365 (Support login required).

Ensure that you can perform a live browse the VM in the BMC Server Automation console.

Ensure that you complete the following steps as part of the VM enrollment process:

  • Add the server in BMC Server Automation.
  • Create a property state instance (PSI) object that refers to the correct vCenter.
  • Set the server VIRTUALIZATION property to the PSI object.
  • Set the server IS_VIRTUAL property to TRUE.
  • Run an Update Server Properties job against the server.

 

Does the VM have the same name in BMC Server Automation and vCenter?

 

Do you have all the required input parameters for the ServiceOfferingInstance onboard API request?

Ensure that the input parameters are correct:

  • The input owner must be the user from the input tenant company in AR.
  • The input tenant must be mapped to the input network container in BMC Cloud Lifecycle Management.
  • The request definitions of the input service offering and the input tenant must be mapped to the same entitlement package in BMC Cloud Lifecycle Management.
  • If you include the decommissionDate input parameter, ensure that the time stamp is in milliseconds.
  • If the VM does not have the same name in BMC Server Automation and vCenter, ensure that you include the actualVMName input parameter.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*