There are a lots of tools in the shed when it comes to overseeing the health of your VMware software-defined datacenter. One of those tools, Skyline, is a free SaaS offering on console.cloud.com when you have an active ELA or a Success 360 customer (Premier Support).
From VMware http://www.customerconnect.vmware.com you can go out to Downloads and obtain the VMware Skyline Collector 3.4. This will download an OVA file to deploy in your virtual environment.
I will be fast-forwarding through most assuming the audience is familiar with deploying Virtual Machines.
Some recommendations I would give is prior to deploying in any environment, come up with is reserve an IP, hostname before deploying the appliance. Skyline Collector 3.4 User Guide (PDF)
Choose to leave default name or create a custom vSphere object name (prefer making the name the same as your reserved hostname), everyone’s standard will be different. Click Next.
The next step, select cluster/compute resource the virtual machine will be deployed on.
Review the details of the appliance, the next screen will be EULA (End User License Agreement). Click Next
Select the storage for the appliance, click Next.
Select the desired network, click Next.
For the next step, create a custom ‘root’ account password, assign the networking, domain and DNS related entries to complete customizing the template. Once that is completed, click Finish
In the event you lose or forget the root password for the appliance or the ‘admin’ account, visit the following KB: https://kb.vmware.com/s/article/52652
Initially I got thrown the following error, all i did was refresh my session and run through the installation setup a little quicker, there were some delays while creating the post.
Once the VM is created, you will need to power it on. Once it’s full booted up and network services are on. You should be able to reach the appliance by its hostname.
The default password for the ‘admin’ account is ‘default‘. Once you log in, you will be prompted to change the password immediately and then to log back in.
Once you log in with the newly changed password a setup wizard will begin the registration of the collector to Skyline Advisor and option to configure endpoints. There are some additional prerequisites that are recommended to perform prior to complete next steps, such as creating the suggested Read-Only accounts to be used for configuring the endpoints.
From the beginning 1. Test & Save the hostname configuration and configuring a proxy (optional), click ‘Continue’.
Next is the CEIP, click ‘Continue’,
As we are going through the wizard, step 3. Collector Registration, will require signing onto the console.cloud.vmware.com and from the Cloud Console home select ‘Skyline Advisor’
In our example, there is an existing Skyline under a cloud org and we will be adding an additional collector. Click ‘Add Collector’
You will now be presented with an option to Copy/Paste a generated token
Go back to the Collector configuration wizard, paste the token and click ‘Register Collector’
Create a ‘Friendly Name’ the collector will be identified as in Skyline Advisor, it’s recommended if you are deploying collectors are several sites to create names easily identified.
Enable Auto-Upgrade is off by default, I’m turning it on, this is a service that will not disrupt anything in the environment.
Starting with adding credentials, the following example is an Active Directory account that is configured with a Read Only role set in Global Permissions on the vCenter.
You may proceed with configuring additional products into Skyline. Fast forward through all the solutions, once completed, the Endpoints may come up red for a moment or show green immediatly.
If you go back to the VMware Cloud Console, the final step would be to click ‘Complete Setup’ This should then take you back to the Skyline Advisor and the number of collectors should increase by one.
I hope this document was helpful and there is plenty more of information and details pertaining to Skyline.