vCenter 5.5 Upgrade with Windows Server 2012 R2 – Part 7 – Integrating vIN

This is part 7 of the vCenter 5.1 to 5.5 Update 1c upgrade, detailing the reintegration of vCenter Infrastructure Navigator with vCenter 5.5.

This is an eleven part series, describing how to upgrade from vCenter 5.1 to vCenter 5.5:

Prerequisites

  • You have completed steps 1 to 6.
  • You have administrator access to vCenter.
  • You have downloaded the vIN ova for vCenter 5.5 Update 1c.

Unregister the vCenter 5.1 vIN extension

I tried to reregister the original vIN instance with no success, I am sure there is some procedure for this, but I could not find it.  So redeploy was the only option left.

  1. Open a Web browser and connect to the vCenter extension manager: https://<vCenter IP Address>/mob”
  2. Login as an administrator and select “UnregisterExtension”.
  3. Enter “com.vmware.vadm.ngc51” and press “Unregister”.
  4. Then enter “com.vmware.vadm” and press “Unregister”.
  5. Refresh the “ExtensionManager” screen and verify the “vadm” entries are gone.
  6. Within vCenter, power off and delete the vCenter 5.1 Virtual Appliance.
  7. This process is also describe in VMware KB 1025360.

vcenter_extension_mgr_1 vcenter_extension_mgr_2.

Redeploy the vIN Virtual Appliance for vCenter 5.5

  1.  Connect to the Web Client and select the vCenter 5.5 instance that requires vIN.
  2. Select “Related Objects”, “Virtual Machines” and then select the “Add OVA icon”.
  3. Browse to the file “VMware_vCenter_Infrastructure_Navigator-xxxx.ova” and press “Next”.
  4. Press “Next”.
  5. Accept the EULA and press “Next”.
  6. Enter the “Name”, select the “Datacenter” object and press “Next”.
  7. Select the Cluster and then press “Next”.
  8. Select the “virtual disk format”, “VM storage policy”, “Storage DRS cluster” and then press “Next”.
  9. Select the “Portgroup” network and press “Next”.
  10. Enter the “root” password, “Default Gateway”, “DNS” entries, “IP Address” and “Netmask”.  Then press “Next”.
  11. Press “Next”.  Note if the vCenter extension service is not running, then access the Windows Server “Services” window and make sure the “vCenter Web Service” is running.
  12. Select “Power on after deployement” and then press “Finish”.
  13. After the vIN deployment has completed and powered on, browse to the Licence Management screen by selecting “Home”, “Administration”, “Licenses” and then the “Solutions” object.
  14. Ensure that “vCenter Infrastructure Navigator” has a valid licence key assigned.  If not, assign one using the “Assign License Key” button.
  15. Press “Home” and then “Infrastructure Navigator”.
  16. Press the “Turn on access to VMs” button and enter the administrator service account credentials and then press “OK”.
  17. After some time (depending upon the size of your environment), select any VM and press “Manage” and then “Application Dependencies”.  Verify that an “Application Dependencies” map is present.

vin_1 vin_2 vin_3 vin_4 vin_5 vin_6 vin_7 vin_8 vin_9 vin_10 vin_11vin_vcops_4 vin_12 vin_13 vin_14 vin_15

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s