OpenManage Integration for VMware vCenter Version 4.3

Updating appliance through backup and restore

About this task

To update the OMIVV appliance from an older version to current version, perform the following steps:

Steps

  1. Take a backup of the database for the older release.

  2. Turn off the older OMIVV appliance from vCenter.

    NOTE: Do not unregister the OMIVV plug-in from vCenter. Unregistering the plug-in from vCenter removes all the alarms that are registered on vCenter by the OMIVV plug-in and all the customization that is performed on the alarms, such as actions, and so on.

  3. Deploy the new OpenManage Integration appliance OVF.

  4. Power on the OpenManage Integration new appliance.

  5. Set up the network, time zone, and so on, for the new appliance.

    NOTE: Ensure that the new OpenManage Integration appliance has the same IP address as the old appliance.
    NOTE: The OMIVV plug-in might not work properly if the IP address for the new appliance is different from the IP address of the older appliance. In such a scenario, unregister and re-register all the vCenter instances.

  6. The OMIVV appliance comes with default certificate. If you want to have a custom certificate for your appliance, update the same. See Generating Certificate Signing Request and Uploading HTTPS certificate. Else, skip this step.

  7. Restore the database to the new OMIVV appliance. See Restoring the OMIVV database from a backup .

  8. Verify the appliance. See the Installation verification in OpenManage Integration for VMware vCenter Installation Guide available at Dell.com/support/manuals.

  9. Run the Inventory on all the registered vCenter servers.

    NOTE: Dell EMC recommends that after the upgrade, you run the inventory again on all the hosts that the plug-in manages. To run the inventory on demand, see the Scheduling inventory jobs.
    NOTE: If the IP address of the new OMIVV version y is changed from the OMIVV version x, configure the trap destination for the SNMP traps to hover over the new appliance. For 12th and later Gen servers, the IP change is fixed by running the inventory on these hosts. While running the inventory on 12th Gen hosts, if SNMP traps do not hover over the new IP, those hosts are listed as noncomplaint. For hosts earlier than 12th Gen that were compliant with earlier versions, the IP change is displayed as noncompliant and requires you to configure Dell EMC OpenManage Server Administrator (OMSA). To fix vSphere host compliance issues, see Running the fix noncompliant vSphere hosts wizard.
    NOTE: After backup and restore from an earlier OMIVV version to a later OMIVV version, if you observe 2 Million error or Dell EMC logo is not displayed at vCenter, do the following:
    • Restart vSphere Web Client on the vCenter server.
    • If the issue persists:
      • For VMware vCenter Server Appliance, go to /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity and for Windows vCenter, go to C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity folder in the vCenter appliance and see if the old data exists, such as: com.dell.plugin.OpenManage_Integration_for_VMware_vCenter_WebClient-X.0.0.XXX.
      • Manually delete the folder corresponding to the earlier OMIVV version.