For a customer I’m migrating their legacy vSphere 5.5 environment to vSphere 6.5 U3. The migration is from a windows vCenter to the VCSA. First, we tried to use the GUI and stumbled over an issue.
The GUI, is of course a nice, friendly way to do this process. But when we got at the stage to select the size of the VCSA, we only had the ‘xlarge’ option. And well… that was a bit too much. Because we were aiming at the ‘small’ size.
So we did some searching on the internet and found out that we were not alone. Although it was an encouraging thought, we still didn’t find what we were looking for. Most of the threads and blog posts pointed to database size, log size etc.. And yes, they need to be checked. We had a vcenter database table of 7 million records, the size of the database was 80 GB. After some cleaning up and shrinking the database it was only a few GB. But al this effort, didn’t persuade the GUI to give us the desired ‘small’ size option.
Hoping that the validation in the GUI was different than when using the CLI, we decided to migrate using the vcsa-deploy CLI method.
Yes, it involves creating a json file. But the .iso file for the vcsa contains several template files, for several migration scenarios. We used on of the templates, customized it to our needs (setting the size to ‘small’. And after some trial and error we finally got it working.
If you want to read more about the CLI way of migration, check the vmware docs here.
vcsa-deploy creates for every run a new log folder . When we checked the logs we found out that vcsa-deploy was content with the ‘small’ size option we configured in the json file.
Why not 6.7 U3, well due to dependencies 6.5 U3 is at the moment the most current version we can run. Although this post is about migrating to 6.5 U3, it could also work for 6.7 U3, but no guarantees. The gist of this all is, if the GUI doesn’t work, try doing it the CLI way.
I know, it is not the most interesting subject to blog about. VMware gives you the opportunity for your My VMware account to use MFA. And I would advise to use MFA.
Well, depending on the situation, your my vmworld account can have access to different company accounts. Giving you, depending on roles and permissions, the ability to create support requests, download software, access licenses etc… And that is great. But it is a risk when your account gets hacked. That is where MFA can help. It is an extra line of defense.
MFA stands for, multi factor authentication. And when MFA is enabled,a person needs to present multiple pieces of evidence to authenticate (see https://en.wikipedia.org/wiki/Multi-factor_authentication ) Most of the times these pieces are a password and a token, generated by a authentication app or device. So, when you would know my password, you still can’t use my ‘my vmware’ account because I’ve enabled MFA. And the token is generated on my phone, which I have with me, and is locked.
Use a strong password. Strong doesn’t mean a lot off difficult characters, although there are some rules you have to follow. Study has shown that also the length of your password is a big key in having a strong password.
Enable MFA. Check this VMware KB on how to enable MFA for your My VMware account.
I already blogged about my VCAP deploy experience.( you can find it here ) And as stated…. I passed !!!… Sadly VMware doesn’t let you know the mistakes you made in the exam. But in the end…. this is what counts !!!
Next step ??
Well… to do the VCAP design exam. To be honest, I don’t look forward to it, because theory questions are not my strong suit. My strategy is going to study, visit VMware Empower europe 2019, do the VCAP design exam @ Empower (it is part of the conference) so I get a direction of what the exam looks like…. and maybe pass it on the first try.
Maybe you think, we’ll how hard can it be ?? Yes, that was the same question I had. And to be honest… it is not that hard. But there are some quarks or gotchas. In this post I’ll explain the route I took for patching a vCenter HA setup.
Why don’t you use the VAMI ?
VAMI stands for ‘ Virtual Appliance Management Infrastructure ‘. It can be accessed via port 5480 like https://<FQDN VMware appliance>:5480 . The VAMI of a vCenter Appliance (VCSA) has an update section, which you can use to patch the VCSA. This is a nice and easy way for patching the VCSA, but when you have vCenter configured as vCenter HA then this option won’t work. (I know from experience….) After trying (and failing) I thought, why not read the manual…. VMware has a nice article about patching a vCenter in HA and you can find it here. I still use the VAMI, but not for patching but for making a backup.
Yesterday I did the VMware VCAP-DCV 2018 Deploy experience. I dreaded to do the exam because the VMware DCV landscape is a fast landscape. I do have enough experience and expertise, but to know all the tiny details…. To be honest , there was a little fear for failure…. Especially because I heard that you really need all the time (3,5 hours)…. and that the performance of the virtual environment is bad …. And no access to VMware pubs/Docs/KBs and blog sites…. Do I really have it in me to pass this exam ??
But, eventhough I don’t now the score yet ( that could take up to 6 weeks or so)…. I’m quite confident that I passed it. Why ? Well… the situations you need to solve are for me common troubleshoot scenarios in a vSphere environment. Yes some questions are tricky… but hey… of course they are, you want to prove that you have advanced knowledge in this area.. I even enjoyed taking the exam. It just felt as a normal day at the office…
Yes I do have some critical comments. It is true, the lab enviroment (same experience as a VMware HOL enviroment), performs poorly. Not sure if it is because the internet connection, the hardware, or just the exam enviroment. But…. it was a while back that I used a 17″ monitor…. (i mean years…. prehistoric period)… but yesterday… yes …. really…. my exam enviroment had a 17″monitor…. Which is challenging. As you maybe know… the HOL enviroment has a book area where the questions and explanations are shown (right side on the screen)….. I had to switch often between this area and the console area. With a normal monitor, you can keep them side by side… And the performance…. selecting text with the mouse, click delays up to 10 seconds …. which is really annoying, and not helpful for someone who is nervous.
So I have to wait a few weeks for the result. And even if I failed, I still think that in hindsight I should have taken this exam earlier. If you have day to day hands on experience with a vSphere datacenter virtualization environment for more then a year, then I my advise would be to consider this exam. Your experience should be like, implementations , troubleshooting, and day-2 operations of a vSphere datacenter environment. Get some experience with the VMware HOL environment to get used to the lab environment. It is also a great place to practice with certain functionalities without destroying your own production … euh…. test environment. You can find VMware HOL here.
So fingers crossed (f0r me) and good luck when you want to certify your advance experience with a vSphere environment.
This article is part of a series of articles about issues I encountered during implementation of a vSphere stretched cluster based on vSphere 6.7 U1. You can find the introduction article here
This issue is irritating, to say at least. You configured your first ESXi host in a cluster, polished it etc… and created a host profile from this host. And then it should be easy to configure the other hosts. But, when you apply the host profile…. the host disconnects (because of a reboot….)… but never comes back…. What happened ??
What happened is that in the wisdom of the vSphere environment the vCenter instructed the host to delete vmk0… yes the kernel interface that vCenter uses to connect to ESXi (assuming the vSphere host is clean installed and has just one kernel port). Delete it to create vmk0 again….. But it never gets to that part…. Do you recognize this issue ??
I googled for this issue and found blog posts going back to vSphere 5.1. So it looks like a difference in interpretation of how it should work.