Time to replace my Homelab – Part 1

My current homelab contains 2x HP ML10v2, 1x HP Microserver Gen8 and 2 Switches (1 Mikrotik Cloud Switch 24 Port, Zyxcel 16 Port). This setup was sufficient for a long time. But due to the increased resource requirements of some VMware products and my activities with vROPs, Log Insight and other solutions I require more resources. Furthermore I would like to reduce from 3 to 1 server and run more activities virtually based on the lab scripts from William Lam.

Current Setup:

HostnameCPUMemoryStorageAdd-On
xmesx01eIntel® Pentium® G3240 (3.1GHz/2-core/3MB/54W)32 GB1x 240GB Intel SSD1x HP Quad Gbit NIC
xmesx02eIntel® Pentium® G3240 (3.1GHz/2-core/3MB/54W)20 GB1x 240GB Intel SSD1x HP Quad Gbit NIC
Storage (Freenas on HP Microserver Gen8):Intel® Pentium® G2020T (2.5GHz/2-core/3MB/35W)16 GB4x 2TB WD RED1x HP Smart Array P410 + 512MB Cache Modul + Battery

New Setup:

CategoryDescription
Type:HP Proliant DL380 G7  
ChipsetIntel  ®   5520 Tylersburg + Intel ICH 10
CPU TypIntel ®  Xeon ®  CPU L5630
CPU Speed2.13 GHz
Cores / Threads2 CPU(s), 4 Cores per CPU, 2 Thread(s) per Core, 16 total
L1, L2, L3 Cache32k+32k,   256k,    12288k (12 MB)
Memory32 GB DDR3 ECC 
Installed8 x 4 GB
SAS - Controller:HP Smart Array P410i Controller
Controller PCIe:1x GB LAN Broadcom PCIe Karte
2x Fiber Channel Finsar Singel Port PCIe card
Disks8x 2,5“ SAS HDDs 

The plan is to extend the machine with 8x 146GB SAS disks and additionally upgrade the memory to 144GB at least. The FC card will be removed as it will not be used in my Homelab.

If someone is interested in buying one or two HP ML10v2 please send my a message.

to be continued …

Homelab the current state

It’s time for a new update about my new Homelab. In the past I was running HP Microserver 2x N40L and 1x Gen8. All these machines are still here but no longer in use and will be for sale soon. My new Homelab contains now 2x HP ML10v2, 1x Zyxel 16 Gbit Switch, 1x Lenovo ix4-300d storage.

2x Server HP ML10 v2: HP ProLiant ML10 v2 G3240-Server (nicht Hot-Plug-fähig, 4 GB-U, B120i, 4 LFF, 350-W-Netzteil)
2x SSD adapter per Server: Kingston SNA-DC2/35 SATA DriveCarrier Einbaurahmen für 6,4 cm (2,5 Zoll) bis 8,9 cm (3,5 Zoll) schwarz
Memory: Samsung 8GB (1x 8GB) DDR3 1600MHz (PC3 12800E) 2Rx8 ECC Unbuffered Dimm Server Workstation Arbeitsspeicher RAM Memory
1x Zyxel 16 Port Gbit Switch: Zyxel GS1100-16-EU0101F Gigabit Switch (16-Port, RJ-45)
1x Lenovo ix4-300d Storage: Lenovo Iomega ix4-300d Network Storage (0TB Diskless EMEA, Marvell Armada TM XP, 1,3GHz, 4x HDD, 512MB RAM)
2x HP Quad Network adapter: HP 538696-B21 PCI-e Quad Port Gigabit Server Adapter
2x Intel SSD 240GB: Intel SSDSC2BW240H601 interner Solid State Drive 240GB schwarz
4x WD RED 2TB: WD 2TB Red interne NAS-Festplatte (8,9 cm (3,5 Zoll), 5400rpm, SATA III) WD20EFRX

xmesx01e

xmesx02e

I have installed vSphere 6 on my servers. The Lenovo storage is providing 2 iSCSI targets to fulfil the requirement of 2 shared datastores for HA. Both datastores are part of an SDRS cluster. Besides this I have created a cluster which has HA and DRS enabled. On the network side I have created 3 standard vSwitches each with 2 Gbit network adapters. vSwitch0 is for the virtual machine traffic. vSwitch1 is for iSCSI and vSwitch2 is for VMotion. Yes I know thats a bit the old school way of networking but hey thats only my Homelab so a dvSwitch with Network IO control should not be required. A simple setup is sufficient for Homelab use. Maybe in the future I’m going to change it but that will have to wait until the next vSphere release.

So whats next?

Next will be to setup vRealize Operations Manager 6.3 to improve my troubleshooting knowledge of this product. Additionally I have an idea about how to simplify the troubleshooting and improve the supportability of the product. But this is a different topic. Today I’m going to install the lastest ESXi patches and check for upgrades of my vCenter appliance.

More to come …

Homelab upgrade and Options to install a SSD into the HP Microserver Gen8

I started to plan the upgrade my current homelab from 1x HP Microserver Gen8, 2x HP Microserver N40L and a Netgear 24 port switch. The only part which I will keep is the HP Microserver Gen8 it has already 16GB of memory and a HP SmartArray P410 with 512MB Cache module incl. battery. This machine will run my infrastructure machines like a tiny vCenter. As work horses I plan to use HP ML10v2 due to the fact that they are cost efficient and they support up to 32GB of memory.

Parts list which I will use in my future homelab:

1x Server HP Microserver Gen8: HP ProLiant MicroServer (Gen8, G1610T, 1P, 4 GB-U, B120i, SATA-Server)
2x Server HP ML10 v2: HP ProLiant ML10 v2 G3240-Server (nicht Hot-Plug-fähig, 4 GB-U, B120i, 4 LFF, 350-W-Netzteil)
2x SSDs per Server: Mushkin MKNSSDRE1TB Reactor 7mm SSD, 1TB
2x SSD adapter per Server: Kingston SNA-DC2/35 SATA DriveCarrier Einbaurahmen für 6,4 cm (2,5 Zoll) bis 8,9 cm (3,5 Zoll) schwarz
2x Disks per Server: HGST Deskstar NAS 3TB 6Gb/s SATA 7200rpm 24×7 RV S
Switch: TP-Link TL-SG3424 Pure-Gigabit L2 Managed Switch (24x 10/100/1000Mbps RJ45-Ports inkl. 4 kombinierter SFP-Anschlüsse, lüfterloses Passivkühlkonzept)
Memory: Samsung 8GB (1x 8GB) DDR3 1600MHz (PC3 12800E) 2Rx8 ECC Unbuffered Dimm Server Workstation Arbeitsspeicher RAM Memory

There are at least 2 options to install SSDs into the HP Microserver Gen8.

Option 1 is to connect a single SSD to the SATA port on the mainboard an place it where normally the DVD drive should be installed. That’s the cheapest method and might be not the best one.

Option 2 will use a adapter to map the 2.5″ SSD into a 3.5″ tray. I personally would use the Kingston SNA-DC2/35 adapter.

2nd Microserver just arrived

I got my 2nd HP Microserver today including the Remote Access Card. In the next days the memory upgrade of both boxes to 8GB each will arrive too. So that means my private Lab is nearly ready. I just miss the external iSCSI storage but this is currently no issue as I use a freenas on my ML115 G5 as shared storage.

Let the tests and trainings begin … :-)

Homelab extension

Yesterday I have ordered the new HP Microserver N40L. This will extend my existing Homelab as second ESXi server.

Hardware specs HP Microserver N40L:

* AMD Turion II Neo N40L (1.5GHz)
* 2GB Memory installed (up to 8GB possible)
* 1x 250GB SATA HDD installed (up to 4 SATA HDD possible)
* Embedded NC107i PCI Express Gigabit Ethernet Server Adapter

Planned upgrades:

* Memory upgrade to 8GB
* replacement/upgrade of Harddisk to 4x 2TB
* HP Microserver Remote Adapter Kit
* SATA/SAS Raid Controller

My existing Homelab:

* 1x HP ML115 G5 AMD Quad Core Opteron
* 8GB Memory
* multiple different Harddisks (2x 3,5″ 160GB; 2x 2,5″ 120GB … )

Currently missing but planned to be ordered:

* Shared Storage based on an Hardware appliance (Qnap, Iomega or equal)
* 2nd HP Microserver

VMware ESXi HA agent failed

If you force problems with reconfigure HA on a ESXi server in a HA Cluster. A possible solution to resolve this is to uninstall the vpxa and the ha-agent. This can be done using the unsupported mode.

Steps:

* set ESXi in Maintenance Mode
* disconnnect ESXi from Virtual Center
* remove ESXi from Virtual Center
* connect with SSH to ESXi or direct using something like HP iLo
* execute the following commands

cd /opt/vmware/uninstallers/
./VMware-aam-ha-uninstall.sh
./VMware-vpxa-uninstall.sh

* add ESXi to Virtual Center
* exit ESXi from Maintenance Mode

* repeat this with all Nodes in the cluster

Proxmox VE 1.6 released

A new version of the open source virtualization software Proxmox VE was released!

Change log:

* New 2.6.32 kernel including OpenVZ support, based on latest Debian Squeeze Kernel
* Removed KSM (OpenVZ does not support KSM)
* DRBD tools: update to drbd 8.3.7
* New KVM user-space tools (0.12.5)
* New OpenVZ user-space tools (vzctl 3.0.24)
* vzdump: use ionice to set io priority. By default, we now set “ionice -c2 -n7” to limit io (instead of using a default bwlimit)
* vzrestore: new –force option to overwrite existing data
* dab bug fix: only print a warning for packages installed directly with ‘dpkg’ (when there is no information in ‘available’ list)
* dab: only mount /proc/ if not already mounted (avoid problems with vzctl 3.0.24)
* Bug fixes

Download