VCSA – Page 20

Hope to see you at VMworld 2015

06.23.2015 by William Lam // 1 Comment

The VMworld 2015 Content Catalog just went live this morning and I am please to announce that I have two sessions that were accepted at both VMworld US and Europe. The first session will be a Technical Deep Dive on our new Content Library feature which was introduced in vSphere 6.0 and I will be co-presenting that with James Chang, one of the Content Library Engineers. The second session will be covering a topic that is near and dear to my heart which is the vCenter Server Appliance (VCSA) and I will be covering some of the best practices along with some of the tips and tricks that you may not know about the VCSA. I hope to see you in one of these sessions and I look forward to meeting and chatting with some of my readers at VMworld!

INF5106 - Content Library Technical Deep Dive

What’s the best place to store and maintain your VM templates, ISOs, and vApps? How do you share them with other administrators and users in your organization or between two sites? The solution is a content library, a content management tool within vCenter that manages and replicates content across data centers. In this talk you will learn how to organize your VM templates for the best VM provisioning speed, pick up best practices for automatically sharing your content between sites, and understand how to migrate content from your existing vCloud Director to vCenter with the least amount of effort. And all this right from the vSphere client that you are already familiar with! Next, we will dive into advanced features like external webserver support (e.g. Amazon S3), HTTP mirroring for scale, and rapid sync using array replication technologies. Lastly, we will conclude the talk with a product demonstration showcasing the advanced content management and consumption use cases within a software defined data center

INF4528 - vCenter Server Appliance (VCSA) Best Practices & Tips/Tricks

In this session, I will go through some of the best practices and considerations when deploying and managing the vCenter Server Appliance (VCSA). I will walk through some of the changes between past releases and the new vSphere 6.0 release. In addition, I will also provide tips and tricks on using the VCSA as well as ways in migrating from a Windows based vCenter Server to the VCSA

vCenter Server 6.0 Tidbits Part 12: New methods of downloading Support Bundles for VCSA / PSC

06.18.2015 by William Lam // Leave a Comment

Many of you are probably pretty familiar with the process of generating a VMware Support bundle for vCenter Server when it comes to troubleshooting or filing an SR with VMware GSS by using either the vSphere Web/C# Client UI. With the released of vSphere 6.0 and specifically with the vCenter Server Appliance (VCSA) there are now some additional methods in generating a VMware Support bundle which can come in handy if the vSphere Web Client is not running or if you wish to perform this simply through the command-line on a remote system.

The first option is simply by pointing your web browser to the following URL of your VCSA:

https://192.168.1.60/appliance/support-bundle

You will be prompted to login with a local account such as the "root" user which ensures that there is no dependency that SSO must be running which is the case when using the vSphere Web Client. Once authenticated, the VMware Support bundle will be generated and you will then be able to download it onto your system. The VMware Support Bundle is in the format of a compressed tar file which you can use gzip or tar to extract.

The second option is simply using cURL or wget from the command-line which you will also need to provide valid credentials to download. Here is an example of using curl and we will be saving the file as "support-bundle.tar.gz":

curl -k -u root -o support-bundle.tar.gz -O https://192.168.1.60/applmgmt/support-bundle

Once we have downloaded the VMware Support bundle to our desktop, we can then extract it using a variety of tools such as tar for example:

tar -zxvf support-bundle.tar.gz

In situations when you need to quickly resolve a problem by providing support logs to VMware, time is of the essence and being able to quickly generate the necessary support files can help lead to a quick resolution. Hopefully these additional methods of generating a VMware Support Bundle can help save you time when you may need to call upon them.

All replicated Platform Services Controller should be joined to Active Directory

06.16.2015 by William Lam // 4 Comments

Last week a colleague of mines was setting up a new vSphere 6.0 environment which contained a vCenter Server with an external Platform Services Controller (PSC) for our Management vSphere Cluster and another vCenter Server also with an external PSC for our Compute vSphere Cluster. The PSC's were configured to replicate with each other which meant they were part of the same SSO Domain providing us with the new Enhanced Linked Mode (ELM) feature that was introduced in vSphere 6.0.

With ELM, you can now easily view all of your vCenter Servers by logging into either of the vSphere Web Client Servers provided by any of the vCenter Servers that are connected to the replicated PSCs. In addition to providing a single view into your vSphere environment, data such as Licensing, Tags, VM Storage Policies, Roles/Permissions & Affinity/Anti-Affinity Rules to name a few are also replicated and made available to all the other vCenter Servers.

As part of the initial setup, my colleague had joined the first PSC (psc-01) to our Active Directory domain after completing the deployment of the VCSA, as the vSphere Web Client was required to make further changes to the PSC. The question that my colleague had was whether or not additional PSC nodes were required to be joined to the same Active Directory domain or would it automatically be handled by the PSC replication?

This was actually a great question and in fact something that could easily be overlooked or at least until you try to login using an Active Directory account and can not. What you will notice when going to the SSO Admin Configuration screen is that the Active Directory Identity Source has been added, so I can see why one would assume this would automatically be handled. If we take a closer look at my home lab environment and the Active Directory configuration within each of the PSC, we will see why this not the case.

If we take a look at the Active Directory configuration for psc-01, we can see that it is part of our AD Domain and the "Join" option is grayed out.

If we now take a look at psc-02, you will see that the Active Directory configuration is empty and the option to "Join" is still available.

To resolve this problem, you just need to add the additional PSC nodes to Active Directory and then reboot for the changes to go into affect. The PSC's also support different Active Directory domains as long as a trust relationship exists between the two, for more details take a look at this VMware KB 2064250. It should also be noted that this should not be an issue for those deploying a Windows based vCenter Server since it is usually a best practice to joined the Windows system to an AD Domain prior to installing additional software on top.