vCenter Infrastructure Navigator Removal How to.

Summary:
A very cool little appliance that looks @ your VM's and everything they interact with.  Unfortunately, the installation can be fraught w/ issues.  I for one found a bug w/ vCenter 5.0 and VIN 1.1.1 (where VIN 2.0 might have been introduced before).  Specifically, I was unable to apply a VIN 1.0 license to my VIN 1.1.1 installation because I tried to introduce VIN 2.0 first.  Interestingly, my 2.0 key worked fine w/ the 1.1.1 version.

Long story short and to make it simple don't introduce VIN 2.0 unless you are on vCenter 5.1.

PreReqs for 5.0 users:
  1. vCenter 5.0
  2. VIN 1.1.1
  3. vCenter Web Client 5.0
Details:
If you have not deployed VIN ever to your 5.0 environment, then I recommend you deploy VIN 1.1.1 and save yourself some headaches.  Otherwise, here are some remediation steps you can take to deploy VIN if you did what I did or set it to auto-upgrade w/o knowing better.
Steps to Remove VIN extensions from vCenter
  1. Remove VIN appliance from vCenter
  2. Go to your vCenter's Managed Object Browser via your web browser
    • https://YourvCenterServerName/mob/?moid=ExtensionManager
  3. Your looking for this in your list:
    • extensionList["com.vmware.vadm"]
  4. To remove select UnregisterExtension and paste com.vmware.vadm into the box and select "Invoke Method.
    • You'll get a null return, this is fine.
  5. Now if you refresh your MOB page, you should no longer see com.vmware.vadm in the extension list.
    • https://YourvCenterServerName/mob/?moid=ExtensionManager
  6. Finally, you'll need to delete the related extension folder from your vCenter's file system.
    • I'm assuming Windows here, not sure where these would be on the vCenter appliance.
    • Delete the "com.vmware.vadm" folder
      • Normally located here: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\Extensions
  7. Now you should be able to re-import the VIN vApp and it'll re-register all its components.

Comments

Anonymous said…
thanks, it worked for vin 5.8.3
November 4, 2014 at 8:14 PM
Post a Comment

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

Image
Summary: Basically had an expiring certificate registered in NSX-T that was associated to a node_id that is no longer valid.  Long story short, there wasn't anything obvious in API to delete or disassociate a certificate from a node_id for 3.2.2.  Not sure how things got in this state, but annotating for future reference.  This may change in future revisions, so always check API for latest. Details: Effectively had a stale node associated w/ a certificate that was expiring.  Could not delete certificate until that node was disassociated from the certificate. To get certificate details and associated node_id's, you can use the following curl call (UI works too): curl -k -X GET -H "Content-Type: application/json" -u admin https://<manager ip>/api/v1/trust-management/certificates/<cert UUID> Above will return something like this: Below must be run from one of the manager nodes via elevation to root: ONLY RUN THIS IF YOU ARE ABSOLUTELY SURE OF WHAT YOU ARE DO...
Read more

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face ...
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnec...
Read more