Install Guide

Upgrading registered vCenter
You can upgrade a registered vCenter for non-administrator users or administrator users. Before upgrading a registered
vCenter, see the VMware Documentation if you upgrade to the latest version of the vCenter server, such as vCenter 6.5.
Perform the tasks in either of the following options after upgrading a registered vCenter, as applicable:
● For non-administrator users:
1. Assign extra privileges to non-administrator users, if necessary. See Required privileges for non-administrator users on
page 11.
For example, when you upgrade from vCenter 6.0 to vCenter 6.5, assign the extra privileges.
2. Reboot the registered OMIVV appliance.
● For administrator users:
1. Reboot the registered OMIVV appliance.
Verifying installation
The following steps verify that the OMIVV installation is successful:
1. Close any vSphere client windows, and start a new vSphere web client.
2. Confirm that the OMIVV icon appears inside vSphere web client.
3. Ensure that vCenter can communicate with OMIVV by attempting a PING command from the vCenter server to the virtual
appliance IP address or host name.
4. In vSphere Web Client, click Plug-ins > Managed Plug-ins.
5. In the Plug-in Manager window, verify if OMIVV is installed and enabled.
Migrating from 3.x to 4.0
You can start with a fresh deployment of the v4.0 OVF after uninstalling the old version and then migrate the data from older
version (3.x) to 4.0 version by using backup and restore path.
To migrate from an older version to the OMIVV 4.0 version, perform the following steps:
1. Take a backup of the database for the older (v3.x) release.
For more information, see OpenManage Integration for VMware vCenter User’s Guide available at Dell.com/support/
manuals.
2. Power off the older appliance from vCenter.
NOTE:
Do not unregister the OMIVV plug-in from vCenter. Unregistering the plug-in from vCenter removes all the
alarms registered on vCenter by the OMIVV plug-in and all the customization that is performed on the alarms such as,
actions and so on. For more information, see Recovering OMIVV after unregistering the earlier plug-in version if you
have unregistered the plug-in after the backup.
3. Deploy the new OpenManage Integration version 4.0 OVF.
For more information on deploying the OVF, see Deploying the OMIVV OVF by using the vSphere web client.
4. Power on the OpenManage Integration version 4.0 appliance.
5. Set up the network and time zone on the appliance.
Ensure that the new OpenManage Integration version 4.0 appliance has the same IP address as the old appliance. To set up
the network details, see Registering OMIVV and importing the license file.
NOTE:
The OMIVV plug-in might not work properly if the IP address for the OMIVV 4.0 appliance is different from the
IP address of the older appliance. In such a scenario, unregister and re-register all the vCenter instances.
6. Restore the database to the new OMIVV appliance.
NOTE:
If you have enabled Proactive HA on clusters, OMIVV unregisters the Dell Inc provider for those clusters and
re-registers the Dell Inc provider after restore. Hence, health updates for the Dell hosts are not available until restore is
complete.
For more information, see Restoring the OMIVV database from a backup in the OpenManage Integration for VMware
vCenter User’s Guide available at Dell.com/support/manuals.
16
Introduction