Categories
Home Lab PowerCLI Starwind Virtual SAN Virtualization Vmware

Home Lab 2.0 – Starwind VSAN : The Greatest addition to my Home Lab

At the end of my previous post about The Beast I mentioned about lacking shared storage for my Virtual Hosts. My first thought was to go out and purchase a NAS like a Synology or a QNAP NAS. However I am trying to do this on the cheap and an extra $1200 when figuring in the cost of drives is just not in my budget. Now I am not sure about Synology, but I believe that they are comparable to QNAP in the sense that you can present disks as iSCSI LUN. Which I have done several times in the past and works brilliantly.

So here I am sitting in my office looking at the Beast and I was racking my brain trying to figure out what I can do with all this storage in this one box and how I can share it among my Virtual Hosts. I started looking at FreeNAS and running it as a VM in VMware Workstation and that worked! Until I had a power failure and the virtual disks became corrupted and I could not get them to come back online. Very Frustrating, my search continued.

Anyway, after doing some research I discovered Starwind VSAN. It allows you to take storage on a Windows machine and present it as an iSCSI LUN. I thought this is great and I signed up for a trial which gives you the ability to install it on one host but no graphical interface (it uses PowerShell) but unlimited LUNs. After some quick googling about the syntax I was able t piece together the commands with relative ease. Within a few minutes I was up an running with three new iSCSI LUNs and they were mounted in vCenter.

I mentioned earlier about having issues with FreeNAS and power failures, well ironically we had a power failure but Starwind VSAN came back online without a hitch. I was very impressed with how resilient it was. I have not had the chance to really put it through it’s paces, but so far I think I found a winner.

I plan to s follow up post once I really get off and running to the races so stay tuned for updates.

Categories
Home Lab Virtualization Vmware

Home Lab 2.0 – The Beast

Continuing on our series on my Home lab we now move into present day. Well…. a few months ago at least. As I mentioned in my previous post about my Razor Blade 15, I used that as my home lab until I was able to procure parts for my current hyper converged VMware Home Lab.

Below is my part list for The Beast:

Once all the parts came in I managed to get it all hooked up relatively quickly and without issue. I must admit that this is the first time I have ever used a Noctua Cooler, but it is whisper quiet, and nowhere near as expensive as I thought it would be.

So moving away from the hardware I then installed Window 10 and after 4 hours or so of Windows updates I was finally able to install VMware Workstation Pro 15. Well, almost…. it turns out that Virtualization Support was not enabled by default. But I can get into that at a later time. I then built out a Domain Controller (another 4 hours of Windows Updates) and 3 Virtual hosts (no Windows Updates). Once the hosts were built I then deployed a VCSA appliance.

Now I think I have everything I will need to play with VMware Products. That is until I remembered I don’t have Shared Storage for my Virtual hosts. What ever will I do?!

Stay tuned for my next post in this series, especially if you are looking to build a home lab on the cheap.

I hope you found this helpful and if so please share it with your friends, we could really use your support.

Categories
Virtualization Vmware

Home Lab 1.5 – Razor Blade 15

To continue with my Home Lab Journey Series. In my previous post on the subject I covered what I consider my workhorse laptop. Once I realized that my laptop was just not powerful enough to do what I wanted to do I decided that I needed to look into a different solution. After watching some of my favorite YouTubers it came to my attention that there are laptops that could exceed the 16 GB barrier. So after reviewing some of the videos I came to the conclusion that I should look into Razer. Specifically the Razer Blade 15 as it has the gaming power to allow me to play games (like Skyrim) but it is also portable for me to carry around for presentations.

So after weeks of agonizing over it, I pulled the trigger and finally bought it. At first I was gun shy and definitely had buyers remorse. But after a few days I was able to peel myself away from my HP laptop and make the switch over to the Blade, and my first impression was WOW. It was so fast, powerful, and LOUD. This was all before the 32 GB upgrade which I had to wait for Amazon to deliver. I provided the link to the kit above just encase you were wondering as it was a PiTA to find it.

After the upgrade I then proceeded to install VMware Workstation (I can’t remember the version…. 15 maybe) and then began to deploy vSphere. I was able to deploy VCSA and 3 hosts with 8 GB of RAM each. I was even able to run some (like 2) VMs on those ESXi Hosts. After about 3 months or so I learned that I had more bottle necks that I originally anticipated such as:

  • Memory (32 GB for 3 hosts, vCenter, and Windows 10 was not enough)
  • Network (running off of WiFi, nuff said)
  • Storage (512 GB SSD was not enough)

To combat the network bottleneck I purchased a USB-C dongle with a network connection, and for storage I thought about using a iSCSI NAS but I was not able to convince my Wife to allow me to spend the money at the time. Who am I kidding, I am just cheap and didn’t want to spend the money.

So at this point I am need of additional storage and more memory. That is when I started to think about building my latest creation…. THE BEAST. You can find my parts list here on KIT.CO

I hope you found this post helpful and if so please share with your friends and help us to grow.

Categories
Home Lab Virtualization VMUG VMUG Advantage Vmware

Home Lab Version 1.0 – HP Envy x360

So I mentioned in a previous post about my history with setting up a lab. Now that I was without a place to test things I figured that I really didn’t need one and that I would be totally fine, and I was for a time. But then I joined VMUG and went to a UserCon for the first time. While I was there I got to meet other professionals in the “local” area and we talked about things that we are doing at our respective places of employment and I had the opportunity to see some the the amazing things going on in the industry at the time. I also learned about the VMUG Advantage, but I was not able to drop that kind of money ($200) on something that I was not ready to mess around with it. I did however go back to my work and tell my boss about it. Then I promptly forgot about it.

Fast forward a year later and VMUG USERCon is right around the corner. I am getting ready to ask off of work, and my boss reminded me about the VMUG Advantage and how I has asked to get a subscription. He remembered, he actually remembered!! So I took him up on the offer but I said I wanted to wait until I was there because they offer a discount.

Before going to UserCon my wife got me a New Laptop! It was an HP Envy x360. It came with an Intel i5 Processor, 8 GB of RAM, and a 1 TB HDD. Not only that, she got me the 16 GB upgrade kit! So I thought to myself that I could make this work. Being an engineer I came up with this whole plan to make it work.

So I go to USERCon and I purchase my first VMUG Advantage Subscription. It was amazing, I couldn’t wait to get home to play with it. the first thing that I did was install and configure VMware Workstation (I can’t remember what version it was at the time) and then I started building out a Domain Controller which I also installed VMware vCenter Server 5 on and even deployed 1 ESXi host. Then…. I ran out of RAM…. damn. I tried several times to make it work but I was just too constricted by my lack of memory and it was Maxed out.

I was really bummed out, but I did not allow that to deter me. I continued to use my laptop as my virtual lab, testing various version of Linux and appliances. It was actually the first laptop I used when I started my Blog back on Blogger.com. To this day it is still my workhorse and I consider it a cornerstone of my 3D Printing operation as I use it for 3D Modeling, Slicing, and controlling my printer. I still call it my work horse.

I am going to continue this series about my home lab adventure because there are some really exciting things ahead. I really want you to get the feeling for where I am coming from.

I hope you find this whole thing helpful and enlightening. If you do please thing about sharing this with your friends and Social media.

Categories
Home Lab Virtualization Vmware

My Journey to my own VMWare Home Lab – The Background

So a while ago I mentioned that I was planning on creating a Hyper Converged VMware Home lab. It has been my dream to have rig at my house that I could play with. Having came from a job where I was a consultant I figured out early that you need a lab to test out configurations and updates before it goes live. I first setup a lab at my previous employer using some old server hardware that we had laying around and was just collecting dust. This was before anyone had ever heard of the word Virtualization. That first lab was built on VMware Infrastructure server 3.5 (yeah I am that old) before that I had been mostly working with VMware workstation and VMware GSX ,you know the one you would install on a Windows server and had an MMC console (Yeah I am that old). That lab became the proof of concept for the company which was the first brick in a very long road to 100% Virtualization. I didn’t know it at the time, but that was the beginning of my love affair with everything VMware. From that Lab we started to virtualize non critical servers and then next thing we new we had a SAN and 2 brand new Virtual hosts. My Lab stayed in place but eventually I upgraded it to ESX 4 (yep not ESXi as that was witchcraft). I then went to VMware training and got my first VCP. I came back from that and Immediately started to upgrade my lab to ESXi 5.x. With every upgrade I did my little lab grew larger and better and I took a sense of pride in maintaining it as mine.

Unfortunately the Lab that I setup for myself was taken over by another division and then became their DEV environment which meant I didn’t have a place to try out new things. I tried to come up with alternatives which I will cover in a later posts. But you should always try to stay up on the latest and greatest in our industry. If you don’t you will just get left behind.

If you are interested in setting up your own VMware Home lab you should really check out the VMUG Advantage Program here!

For a mere $200 you will get access to THOUSANDS of dollars worth of VMware Software as well as some Cloud Compute and discounts on training and certifications. I have been a member now for 4 years and the resources that I have gained are invaluable. On the subject of VMUG, you should also be sure to check out your local VMUG as that too can be an amazing resource of knowledge.

I am going to end this post here but if you found this post helpful please share with your friends.

Categories
PowerCLI Virtualization Vmware

PowerCLI – Virtual Host Hardware Information

I have recently been working on a asset inventory issue where I was provided a list of serial numbers from our hardware vendor and I was asked to reconcile it with what we had. Well that is easier said than done in most cases.

I know that vCenter collects a bunch of hardware information and I wanted to see if there was a way to pull the Serial number that is on the System board and put that information into a .csv.

In comes the following command:

 Get-VMHost | Get-VMHostHardware -SkipAllSslCertificateChecks | Export-Csv C:tempVMHostHardware.csv

This command will pull all the hardware information that vCenter records and puts it to a .CSV.

I will do my best to update this post with an example of what the results will look like.

I hope you find this post helpful, if so please share with your friends.

Categories
Virtualization Vmware

How to unlock and reset SSO password in vSphere 6.x (2146224)

So I have a bit of a embarrassing confession to make. I forgot to record the Administrator password for my VCSA Appliance. Total disclosure, I was freaking out and I really thought I was going to have to start from scratch. I did some research I was surprised to find out that you can actually reset the Administrator account on a VCSA appliance as long as you have the root password for the appliance and you have access to the VCSA Console. Below are a list of the links to the KB Articles from VMware.

Resetting SSO Administrator Password
https://kb.vmware.com/s/article/2034608
Resetting SSO Administrator – VCSA 6.x

Below is the PUTTY session as an example.

shinnk@Computer:~$ ssh [email protected]
ssh: Could not resolve hostname devvcsa01.xxx.xxxxx: Name or service not known
shinnk@Computer:~$ ssh [email protected]
The authenticity of host ‘172.26.44.18 (172.26.44.18)’ can’t be established.
ECDSA key fingerprint is SHA256:7E4K1HVpg2ExWz+vEkkRdJ0M5jUYftb3HZw6OSDKFEICSOEPWWKYERe4.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘172.26.44.18’ (ECDSA) to the list of known hosts.

VMware vCenter Server Appliance 6.5.0.21000

Type: vCenter Server with an embedded Platform Services Controller

Password:
Connected to service

    * List APIs: “help api list”
    * List Plugins: “help pi list”
    * Launch BASH: “shell”

Command> shell.set –enabled true
Command> shell
Shell access is granted to root
root@devvcsa01 [ ~ ]# /usr/lib/vmware-vmdir/bin/vdcadmintool

==================
Please select:
0. exit
1. Test LDAP connectivity
2. Force start replication cycle
3. Reset account password
4. Set log level and mask
5. Set vmdir state
6. Get vmdir state
7. Get vmdir log level and mask
==================

3
  Please enter account UPN : [email protected]
New password is –
/a+p|8M?vRl`%”p4*+oZ

==================
Please select:
0. exit
1. Test LDAP connectivity
2. Force start replication cycle
3. Reset account password
4. Set log level and mask
5. Set vmdir state
6. Get vmdir state
7. Get vmdir log level and mask
==================

Once you go through all these steps you are now able to log into VCSA with that temporary password that you are given and you are also able to reset it as well.

I hope you find this post helpful, and if you do please share it out to your friends.

Categories
PowerCLI Virtualization Vmware

Getting past Certificate issue in Power CLI

So I recently started working more with PowerCLI. After my time at VMWorld 2019 (which I will cover in another post) I realized how powerful that PowerCLI actually is (pun not intended). In starting to work with PowerCLI I came across the following message whil: trying to connect to my vCenter

Connect-vIServer : xx-x-xxxx xx:xx:xx Connect-VIServer Error: Invalid server certificate. Use Set-PowerCLIConfiguration to set the value for the InvalidCertificateAction option to Prompt if you’d like to connect once or to add a permanent exception for this server.

I did some googling and I found this article,so shout out to Ivo Beerens for his article.

https://www.ivobeerens.nl/2018/07/18/quick-tip-powercli-invalid-server-certificate-error/

In his article he goes on to share this command

Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -Confirm:$false

After putting that into PowerShell and pressing enter you will no longer get the Invalid Certificate message.

I hope you found this post helpful, I will be posting about some of the scripts that I have been posting on my Github. Please share with your friends if you found this helpful. 
Categories
PowerCLI Virtualization Vmware

Power off entire Virtual Environment using a PowerShell Script and PowerCLI

So I have a lab that I manage where we have had several scheduled power outages in the last few months. So it is my job to make sure that we power off the lab so none of our equipment have issues when we bring it back up.

I would estimate that our lab is comprised of about 90% VMware ESXi Hosts, and after going through the exercise of powering off the whole lab 1 or 2 times, it became it bit of a pain.

So I created a PowerShell Script using PowerCLI to not only power off all the Virtual Machine, but also the Virtual Hosts, and the VCSA appliance itself.

I have posted the script to my Github which you an check out here:

https://github.com/kenbshinn/Poweroff_VirtualEnvironment

Feel free to check it out and let me know what you think.

I hope you found this post helpful, and if so, please share it with your friends.

Categories
Virtualization Vmware

All vCenters not showing up after adding a new one to an SSO Domain

As I have mentioned before, the company I work for had a disaster event that took place almost a year ago and because of that we have had  some of our infrastructure duct taped together.

Today I am proud to say that I had the opportunity to rip off another piece of that duct tape and actually move our Virtual Infrastructure forward.

You see, Pre-Disaster we had a single vCenter appliance which managed 3 sites. (Yes I know… yuck)

But, because of the disaster we had to move all of our services from the 1 site to the other 2. In the middle of the DR event I had to create 2 VCSA appliances to be able to manage the 2 sites, and due to a lack of sufficient network connectivity at the time, they were just islands. I even set them up a separate SSO Domains.

Fast forward to today, and I have now consolidated these 2 SSO Domains down to 1 and I must say it is pretty slick.

I did however run into a bit of an anomaly, which is the purpose of my post today. You see on the VCSA appliance that was added to the existing SSO domain, I discovered that I could see the first VCSA Appliance in the vSphere Web Client as well as it’s inventory which was awesome!

However on the vSphere Web Client of the Original VCSA Appliance, I can only see the 1 VCSA Appliance.

I consulted Dr. Google but found nothing at first, until I came across this post on the IBM Cloud for VMware Solutions site.

It turns out that you need to restart the vSphere Web Client in order for the new vCenter server to appear.

Just encase the link dies I will post the resolution here:

This is a known VMware 6.5 issue.

To resolve the problem, you must restart the vSphere Web Client:

Using the root account, connect over ssh to the vCenter VM (virtual machine) of the previously ordered instance.
Type shell to enter the bash shell.
Enter service-control –stop vsphere-client to stop the client.
Enter service-control –start vsphere-client to restart the client.
After the vSphere Web Client of the previously ordered instance is restarted, confirm that the vCenter Server system for the newly added secondary instance is visible in the vSphere Web Client.

NOTE: Rebooting the VCSA Appliance will also resolve your issue.

I hope you found this helpful, and if so please let me know and share with your friends.