I was busy upgrading and rebuilding my home lab in the last weeks. Now I want to share with you in detail how it looks like.
This blog post will cover the following topics:
The basic idea behind the lab is to have a separate basic infrastructure on one host that is capable of managing one or more Hyper-V hosts in addition to one or more ESXi Hosts.
The first system in my lab was built with these components:
The monitor is a Samsung S32D850T 31,5 inch LED-Monitor. He is really huge and the best feature is that you can run two pictures side by side on it. It has a resolution of 2560 x 1440 Pixel (WQHD). In my opinion the best monitor I´ve ever had.
The mouse is a Mad Catz R.A.T. 7 Gaming Maus with 6400 dpi. I love it because you can change ergonomic parts an it to fit perfectly in my hand. I wanted a mouse with a cable because batteries are empty in the most stupid moments.
The keyboard is a SteelSeries 6Gv2 keyboard. I love the feedback of the keys because they feel like to old server keyboards 15 years ago.
Some details about the tower
The Tower supports two systems under one cover. I find this pretty cool because it doesn´t look like garbage in the room like if you use different types of housings. You can insert E-ATX, ATX, Micro-ATX Mainbords on one side and Micro-ATX and Mini-ITX on the other side.
Front removed with a view into the HDD racks.
There are 6 system fans included in the tower and I use three with the first system. Each of the HDD racks supports three 3,5″ drives and two 2,5″ drives. Additionally you can put two 2,5″ drives at the floor on each side. This is how it looks like from the back:
At the top is room for another 6 optional 120mm fans and there are four USB 3.0 Ports with HD Audio per system available.
Take a look inside. You can see that I have enough room for further expansion of the system.
The system is connected to the Diskstation via two 1 GB Ports.
The Diskstation is equipped with the following drives:
The two SSDs are used for read and write caching. The HHDs are configured in RAID 6. The left 4 Slots are used with 4 Seagate Barracuda 2 TB HDDs for source files and documents configured in RAID 5.
This is the back of the Diskstation. Two Ports are used for the load balanced iSCSI connections to the Hyper-V host. One is connected to the corporate network to the Cisco Meraki box, the other one is connected to my home network.
All components are also connected to a Cisco Meraki Z1 with a minimum of one Ethernet Port. This way I can access my Lab from the office vice versa through a private VPN connection. If you haven´t heard about Cisco Meraki Cloud Managed network components you can access more information here.
The base installation of the Windows Server 2012 R2 Hyper-V Host is done on the two 120 GB Samsung SSDs in a RAID 1 configuration. I was using VMware Fusion before switching to Hyper-V. The main reason why I switched is the memory handling. In VMware Fusion you assign a certain amount of memory e.g. 2048 MB RAM and this is fixed. In Hyper-V you can start with 512 MB base RAM and tell the machine to not use more than x MB RAM. This ends in much more available RAM in my lab. I have 32 GB RAM on my first machine and I can easily run 20 VMs.
It took me some time to figure out how to configure iSCSI with MPIO and the network card settings to get performance that is acceptable for me.
iSCSI and MPIO
How iSCSI and MPIO should be configured can be found here: https://www.synology.com/de-de/knowledgebase/tutorials/552
The first failure I did was not placing the Synology adapters and the adapters of my Hyper-V hosts in different subnets. This forum post helped me with the solution:https://forum.synology.com/wiki/index.php/How_to_use_the_iSCSI_Target_Service_on_the_Synology_DiskStation
Receive Side Scaling and TCP Offload
Performance was bad after the first tests. After disabling Receive Side Scaling and TCP offload resolved the performance issues. You can find more information on that topic here:https://social.technet.microsoft.com/Forums/en-US/6754b837-f96d-42c4-b22f-292756c83ea4/iscsi-connections-at-startup?forum=winserverfiles.
Issues with XenApp 7.6 and XenDesktop 7.6 VDA installations
Because I was using VMware in my lab before this error message was new to me.
I had created all the VMs as Generation 2 machines. This led to the problem that the installation of a VDA failed because Secure Boot is enabled by default in this configuration (more information about Secure Boot can be found here: https://blogs.technet.com/b/jhoward/archive/2013/11/01/hyper-v-generation-2-virtual-machines-part-6.aspx). After disabling Secure Boot for the VDAs via PowerShell installation worked as expected. You can set the configuration via PowerShell:
Set-VMFirmware -vmname $env:computername -EnableSecureBoot Off
For more information about the problem visit also: https://support.citrix.com/article/CTX137731
I made a Iometer test based on a blog post Jim Moyle wrote on the Atlantis Computing Website. You can easily compare your homelab performance to mine. You can find the blog post here: https://community.atlantiscomputing.com/blog/Atlantis/August-2013/How-to-use-Iometer-to-Simulate-a-Desktop-Workload.aspx
I think the numbers are not that bad.
Jump Desktop is my preferred app to access remote desktops. I created connections to all lab servers. See for yourself:
I will add one Rasperry Pi 2 as admin client with Windows 10 and all administrative tools installed on it.
The second half of the Lian Li housing will be used for the following configuration (or similar):
Synology DiskStation DS2415+
You might ask yourself why didn´t choose a DX1215 es expansion unit for the DS2415? This is because of the missing ports on the expansion unit and I want to connect the Hyper-V host – like the first system – with load balanced 1 GB Ports. Some disks need to be there as well.
I am also thinking about adding three Intel NUCs in a similar case like Ruben did in his home lab. If you haven´t seen Rubens homelab you should take a look look. It really looks awesome.
I hope this was interesting for you and you might get ideas for your own homelab.
Der RISC.Blog beschäftigt sich mit den zahlreichen Facetten moderner IT-Infrastruktur. Angefangen von neuesten Trends und Entwicklungsstufen der Enterprise-IT berichtet das Expertenteam der RISC über technische Problemstellungen verschiedenster Projekte und deren detaillierten Lösungen.
Wir hoffen damit anregende Diskussionen zu schaffen und laden Sie herzlich dazu ein, Ihre Erfahrungen durch Kommentare zu den einzelnen Themen zu teilen.