vCloud Director - vShield Manager Registration

[haripadmam]

Dear Friends,

I have installed vCloud Director in our environment. After installation and initial configuration I'm trying attach vCenter and vShield Manager with vCloud Director installation using 'Attache New vCenter' wizard. On the 'Connection to vShield Manager' page, I have filled in my vShield Manager IP, user name and password. But I'm getting error on click next 'vshield manager is not registered with the VC <VCNAME>. Perform VC registration in vShield Manager and retry'.  Please help me resolve this error.

Thanks a lot.

Hari.

[IamTHEvilONE]

Please make sure that you entered the exact same value for the hostname of vCenter into vCloud Director and vShield Manager.  If you put an IP into vShield and a Hostname into vCloud, this will fail to match.

Basically, make sure to copy and paste from one to the other.  I can post a picture when I get into the office.

Aside from this, if you are on vShield 5.1.x generation, please ensure to be on the 5.1.2a maintenance bundle.

[JayhawkEric]

This error message will happen if your vShield Manager is not registered with your vCenter.  You can check to see if it is by looking at the Plug-ins to see if it is listed there.  If not you need to logon to your vShield Manager and register it with your vCenter from its portal first.

[haripadmam]

It worked after I recreated the vShield Instance and reregister it with vCenter. Yesterday vCloud was working well but today after i reboot it vCloud is not not getting started. I'm getting some error in cells.log which i have attached. When i open http connection I'm getting a grey page which is getting reloaded every few second automatically then gives error. I have attached error log. Kindly check the log and help me resolve this. Here is my observation and attempts to resolve this so far.

- I tried deleted the pid of vCloud but then I'm getting some JMX error

- Before I install vCloud on RHEL I remember I installed VMware tools. Yesterday evening in vSphere client vmtool status status for RHEL is showing not installed!!! Then I reinstalled it today morning and from then I'm having this issue. So I suspect this could be causing some issue though I;m not sure. Hope this will help you understand the current issue.

Thanks and Regards,

Hari.

[haripadmam]

vCloud Services started automatically after an hour of errors in the log file. But I have no idea what was the issue and how it got resolved automatically. Anyone has any idea what could be issue? I'm afraid this issue could happen again if I reboot the cell.

[abhilashhb]

haripadmam, the vmtool issue is not related to vCloud. Its something that is usually seen on linux machines. I have faced such errors(after reboot the VMtools status says not running) but don't think that is affecting the vCD instance. After installation it takes a while for the Application initialization to complete. I have installed vCD around 10 times and all the time the initialization time varies. But i don't think it wil take an hour. did you check it after an hour or u were monitoring it constantly? 

[haripadmam]

Hi Abhilash, Thank you for your response. I was continuously monitoring the logs for one hour. During this time cell service is recovered several times as you can see in the log i have attached. I have not rebooted my cell after that I must reboot it sometime though to validate the setup.

btw you have any idea on vCloud task approval process? I'm reading through blocking tasks and AMQP. But if you can give some idea that will be really great.

Thanks and Regards,

Hari

[abhilashhb]

Just follow these steps...Its little tricky with setting up AMQP using RabittMQ server(For which you will need to take a look at other blogs which tell you how to set up AMQP). Other than that, if you have a good knowledge of vCO and vCD you'll be able to pull it off!

https://communities.vmware.com/docs/DOC-20446

[campellos]

That's totally right! Thanks a lot

[FM19999999]

Please make sure that you entered the exact same value for the hostname of vCenter into vCloud Director and vShield Manager.  If you put an IP into vShield and a Hostname into vCloud, this will fail to match.

     This my exact issue. It was the difference between a lower case "C" and a capital one.

Copy and past the vcenter server field under vshield settings and reports. It will save you lots of pain.

I also learned that under the vshield section don't use FQDN, Use IP instead.