
9. Run the Inventory on all the registered vCenters.
NOTE:
It is recommended that you run the inventory on all the hosts managed by the plug-in again after the upgrade.
For more information, see the section Running Inventory Jobs for steps to run the inventory on demand.
If the IP address of the new OpenManage Integration version 2.1 appliance has changed from that of the old
appliance, the trap destination for the SNMP traps must be configured to point to the new appliance. For 12G
servers, this will be fixed by running the Inventory on these hosts. For all 11G or lower generation hosts that
were earlier complaint, this IP change will show up as non-complaint and will require configuring OMSA. For
more information, see the section, Running the Fix Non-Compliant VSphere hosts Wizard to fix the host
compliance in the OpenManage Integration for VMWare vCenter Version 2.1 User Guide.
How to recover if I have unregistered the older plugin after the backup
If you have unregistered the plug-ins after taking backup of the database of the older version, perform the following
steps before proceeding with the migration.
NOTE: Unregistering the plug-in has removed all the customizing that was done on the registered alarms by the
plug-in. The following steps will not be able to restore the customizing, however, it will re-register the alarms in
the default state.
1. Perform the steps 3-5 in the section Migration Path to migrate from 1.6/1.7 to 2.1.
2. Register the plug-in to the same vCenters that you had registered earlier in the older plug-in.
3. Proceed with step 6 through step 9 in the section Migration Path to migrate from 1.6/1.7 to 2.1 to complete the
migration.
13
Commentaires sur ces manuels