Writeitfor.us – Unique IT writing services

Writing IT for the IT Generation

Troubleshooting VCAC Endpoints

without comments

A core component of VCAC is the endpoints. Endpoints as the name implies, gives the VCAC system access to compute and management resources to be consumed. Without it, VCAC won’t work. This is a note for myself as well as my readers, when I have a senior moment :)

Applying the KISS principle:

1) Have you licenced both the VCAC Appliance and the IAAS server. Without a fully licensed server  setup you will not be able to add any endpoints.

2) Are you using the correct account to add the endpoints, i.e. the Infrastructure Admin that you assigned when you set it up?

2) Moving on through the system, check the account you wish to use is active and the username and password combo is correct. Check this by logging into the vSphere web client with the credentials.  This is a quick and simple test.

3) When setting up your Endpoint, be sure to use the correct endpoint name as setup when you ran the installer (Each endpoint has a different name depending on its type. With vCenter endpoints, this will be vCenter, unless you changed it during the install. You can check what yours  is by looking by checking the services

vcagent

4) On your VCAC Endpoint URL have you both used https and finished the url with /sdk. Without this it wont work!

 

ep

 

Once you have setup the Endpoint,  it will take several minutes to gather the data from the vCenter server. You can monitor the progress, and check for errors.

If everything looks ok, you should be able to see the resources when you create a reservation group.

 

 

Written by admin

April 29th, 2014 at 10:46 pm

Posted in Uncategorized

Install VCAC 6 using SQL Express

without comments

This blog has been a little neglected of late. This bit of information will hopefully help those people who spent some time trying to get VCAC 6  to work with MS SQL Express 2008
It goes without saying that SQL Express should only be used in a test lab and should not be used in a production VCAC environment. This  setup is for the IAAS infrastructure and is designed to sit on the same server as the IAAS (As done in the VCAC ICM  courses)
The steps are quite easy, just they needed to be documented!

Install SQL Express as normal. This should be easy enough!
2) Enable TCP/IP under protocols. As is shown below, select the TCP/IP protocol, right click and select Enabled.

Turning on IP protocol for SQL Express

Turning on IP protocol for SQL Express

3) Remove all dynamic ports (use blank rather than 0)
By default, SQL Express uses Dynamic ports. We don’t want them in VCAC. We want predictability and an easy life.  On the TCP/IP protocol we just enabled, double click to open the protocol settings.  Remove all dynamic port numbers (O’s and everything. This field should be blank. Change TCP port to 1344 (Standard SQL port). Do this for all the IP addresses listed. Then apply the change and exit the screen.
Configure the ports to be used by SQL

Setting the correct port numbers.

4)  Click ok and save the changes.
5) Save and restart SQL server (or reboot the server, whichever is easier.)
6) If you get an installation error when installing VCAC that complains about SQL ports not available, just click the bypass button and continue.

Written by admin

April 21st, 2014 at 8:26 pm

Posted in VCAC