{"id":343,"date":"2014-03-15T11:49:34","date_gmt":"2014-03-15T11:49:34","guid":{"rendered":"http:\/\/virtualworlduk.co.uk\/?p=343"},"modified":"2014-03-15T11:49:34","modified_gmt":"2014-03-15T11:49:34","slug":"vcenter-support-assistant-installation","status":"publish","type":"post","link":"https:\/\/www.virtualworlduk.co.uk\/wordp\/vcenter-support-assistant-installation\/","title":{"rendered":"vCenter Support Assistant – Installation"},"content":{"rendered":"

Recently VMware released their vCenter Support Assistant that helps to streamline the process of dealing with support by automatically scanning your environment on a schedule and proactively logging tickets with VMware on your behalf if there are any discovered issues.<\/p>\n

This post is designed to give a walkthrough of the installation process for this new virtual appliance and the basic configuration process. \u00a0Please note that this appliance links into the vSphere Web Client.<\/p>\n

Download and Deploy OVF<\/strong><\/p>\n

The first task is to download the vCenter Support Assistant – go to the VMware web site and search for ‘vCenter Support Assistant’, this should provide you with a link to download the appliance as OVF. \u00a0The appliance is approximately 650MB in size – once deployed (using Thick Lazy format), there is a requirement for 254GB of disk space.<\/p>\n

Once the appliance has been downloaded, log into the vSphere Web Client. \u00a0Right mouse click on the host that you wish to deploy the appliance to and then select ‘Deploy OVF Template’
\n\"01\"<\/a><\/p>\n

The wizard to begin deploying the appliance will now start. \u00a0You will be presented with a screen similar to this:<\/p>\n

\"02\"<\/a>Browse to the file that you downloaded earlier, then click ‘Next’. \u00a0You will now be asked to confirm the details of the appliance to make sure that you have selected the correct file, click ‘Next’ to continue:<\/p>\n

\"03\"<\/a>Accept the license agreement and then click ‘Next’. \u00a0You are now asked to supply a name for the appliance and to choose a relevant folder to deploy the appliance to. \u00a0Click ‘Next’ to continue:
\n\"05\"<\/a><\/p>\n

Choose a relevant disk to deploy the appliance to, then click ‘Next’:
\n\"06\"<\/a><\/p>\n

Choose the correct network and then click ‘Next’:
\n\"07\"<\/a><\/p>\n

You should now enter the IP Address, Default Gateway, Subnet Mask and DNS settings for the appliance and then click ‘Next’:
\n\"08\"<\/a><\/p>\n

You are now at the confirmation screen, confirm the settings and tick the box to power up the appliance once deployed. \u00a0The appliance does not take long to deploy and within a couple of minutes you should be able to ping the IP address of the appliance.
\nAt this point I would confirm that the appliance is fully booted by viewing the console screen for the appliance:<\/p>\n

\"10\"<\/a><\/p>\n

 <\/p>\n

Configuration<\/strong><\/p>\n

The appliance is now deployed but is not configured. \u00a0Browse to the web page of the appliance (this is shown on the console screen). \u00a0You should see a web page similar to below:<\/p>\n

\"11\"<\/a>To log into the appliance the default username is: \u00a0root \u00a0 with the default password configured as: \u00a0 vmware<\/p>\n

Once logged in, you should see a screen similar to below:<\/p>\n

\"12\"<\/a>Tick the box to accept the terms and conditions and then click ‘Next’<\/p>\n

\"13\"<\/a>You now need to input the address of the vCenter lookup service, this box is quite intelligent and therefore you can just enter the ip address or FQDN of the server that has the Lookup Service installed and the rest of the box will be completed. \u00a0Click ‘Next’ to continue<\/p>\n

\"14\"<\/a>You will now be required to enter in the SSO username and password for your environment to allow the appliance to be installed and connected to your vCenter environment. \u00a0Please also note that if you have multiple vCenters utilising Linked Mode, then this will link through to all of them and therefore only one appliance is required in your environment.<\/p>\n

Once you click ‘Finish’ the appliance will install and you may be requested to authorise access to your vCenter, enter additional details for Proxy access and also the contact details for when a support request is logged.<\/p>\n

 <\/p>\n

Accessing the Appliance in vSphere Web Client<\/strong><\/p>\n

So you have now deployed the appliance and configured it for your environment… how do you access it? \u00a0 Well, you log into the vSphere Web Client, under ‘Administration’, there is a new section called ‘Support’ and a link to the ‘Support Assistant’:
\n\"15\"<\/a><\/p>\n

Click the ‘Manage’ tab to manage the ‘Proactive Support’ and also your ‘Support Requests’, you should adjust the data collection times as required and make sure that you enable the log collection functionality:
\n\"16\"<\/a><\/p>\n

The Support Requests section is pretty good as this allows you to see the existing Support Requests, plus manually create new ones, manually upload logs and add additional comments as required.\"17\"<\/a><\/p>\n

The final section of the appliance is the ‘Monitor’ tab, this gives you a quick indication of whether the appliance is sending the logs as expected and also allows you to exclude files etc, although keeping this as default is probably recommended.<\/p>\n

\"18\"<\/a>And that is all there is to the vCenter Support Assistant… I’m sure that more functionality will be added to the appliance in later releases but this is certainly a good start.<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Recently VMware released their vCenter Support Assistant that helps to streamline the process of dealing with support by automatically scanning your environment on a schedule and proactively logging tickets with VMware on your behalf if there are any discovered issues. This post is designed to give a walkthrough of the installation process for this new virtual appliance and the basic […]<\/p>\n","protected":false},"author":1,"featured_media":451,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[9],"tags":[],"class_list":["post-343","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/posts\/343","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/comments?post=343"}],"version-history":[{"count":0,"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/posts\/343\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/"}],"wp:attachment":[{"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/media?parent=343"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/categories?post=343"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/tags?post=343"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}