Client Integration Plugin

[sidymani]

Hi Everyone,

I am trying to deploy NSX but the OVF Template can't be deployed. I have installed Plugin but still getting message - Client Plugin needs to be installed.

I have successfully installed vCenter though and it uses the same Plugin. I am using vCenter Version 6. I have tried it with Safari, Win10 32-bit(Edge, Firefox, Chrome), Win7 64-bit(IE 11, Chrome, Firefox).

With Firefox and Chrome, irrelevant of OS, I am getting the message - SSL certificate has been changed, please restart your browser. Even after restarting or not restarting Plugin is not getting detected.

I tried few ideas from vCenter Community but nothing seems to be working. How are you guys doing it? Anything specific, that I am missing?

Client integration plugin issue with Chrome 57

Regards.

Manish

[Sreec]

If the aim to deploy NSX manager,you can take a direct VI client to host and deploy the ovf if it doesn't take network details ,you can run set-up command and configure it. CIP is always tricky - Better try 6.5 U1 .

[sidymani]

Hi Sree,

Thanks for the reply.

If I understood it correctly, take a direct VI client to host and deploy the ovf, that means I should install NSX directly on ESXi Host.

Which setup commands should I run?

With vCenter 6.5 there shouldn't be any such error?

Can you please elaborate?

[Sreec · Accepted solution]

Yes,take a VI client to one of the host and deploy nsx manager.While deploying update all configuration details.If VM is not taking the details once after it is powered on booted ,you can login to vm console and issue setup command update the details once more.

CIP is no more in 6.5 ,however while uploading ovf you need to select all the files and upload it .Please do refer for vSphere Client (HTML5) and vSphere Web Client 6.5 FAQ (2147929) | VMware KB

[sidymani]

Sreec​ I tried installing vCenter 6.5, but after 80% it is not moving forward. I came to know from various websites that might be because of free version of ESXi or because of DNS. I have provided my DSL Modem/Router(192.168.1.1) as DNS for vCenter(10.10.50.150). There is reachability between both of them. Do you have some suggestions?

P.S. - ESXi is Version 6.5 and it's free trial version.

[Sreec]

Deployment should work irrespective you are running trial or licensed version . Can you post a screenshot of installation ?  For VCSA most important points that you should check before installation is

1. Forward and Reverse lookup entries for VCSA should be configured prior to installation

2. Ensure that you are deploying VCSA on the correct ESXI portgroup -

[sidymani]

I will post Screenshot later when I am home. It shows "Installing RPM" and gets stuck at 80%. Check comments of this blog.

https://www.vladan.fr/how-to-deploy-vmware-vcsa-6-5/

What if I don't want to use any FQDN? Installation showed that FQDN is not mandatory, but if FQDN is there then Forward and Reverse Lookup should be working. 6.0 was working fine without FQDN.

ESXi Port Group? How can I find that?

I tried deploying OVF and also trough Windows UI, and got same result.

[Sreec]

FQDN entry during installation is not mandatory(Its a different discussion- IP vs FQDN) . What i'm saying is ,you should ensure there is a forward and reverse entry for that VC -IP . When you deploy OVF -it gets deployed on one of the esxi host port-group- This port group Uplink should have connectivity with DNS/GW etc . 

[sidymani]

Hi Sree,

I was not able to test it earlier. But these screenshots are from Win2016 Server. I tried with Win 2008r2 and Win10 also. Same issue.

[Sreec]

Okay. Installation logs would be worth looking. vCenter.vsphere.local is this the FQDN of VC ?  The SSO domain name should not be the same as your Active Directory Domain

[sidymani]

At this stage logs are not getting generated or at least I don't see any pop-up/notification regarding logs even after I leave it for hours. Just after many hours I get message - operation time out.

In the mean time I have installed vCenter 6 and deployed NSX directly on ESXi. It seems to be working fine till now.

I will change SSO domain name and test it further, but I will take some time. I want to focus on exam for now.

[sidymani]

The Screenshot of the Error is from the first part of installation. At that point I don't even reach SSO.

SSO comes in the second part.

[Sreec]

If there is a failure,logs will be there. You should go through Triaging a vCenter Server Appliance 6.0 installation, upgrade, or migration (6.0 U2m) failure (21067... . Well my point on SSO was ,it is not a recommended practice use the SSO default domain name as your actual DC . When you say,directly deploying on ESXI worked ,what method you were following earlier ?