VMware has released a new White paper about ESXi IP storage troubleshooting.
In this paper, we:
• Describe how you can analyze packet traces to identify functional and performance issues in an
ESX IP storage environment.
• Compare packet capture alternatives, and explain why we recommend an inline optical network
tap connected to a packet capture system.
• Present the challenges of 10G packet capture, and describe key features of commercial 10G
• Describe the design of an inexpensive, self-assembled 10G packet capture solution optimized for
troubleshooting that you can build relatively easily. We also describe our experience with multiple
prototypes of this design, which we have used in our ESX IP storage testbeds for NFS and iSCSI
performance for many years.
• Present examples of analyzing packet traces to solve ESX performance issues for NFSv41, software
iSCSI over IPv6, and hardware iSCSI.
VMware has released a new set of Light Board videos in the vSphere 6.5 playlist, you will find them here.
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.
|xmesx01e||Intel® Pentium® G3240 (3.1GHz/2-core/3MB/54W)||32 GB||1x 240GB Intel SSD||1x HP Quad Gbit NIC|
|xmesx02e||Intel® Pentium® G3240 (3.1GHz/2-core/3MB/54W)||20 GB||1x 240GB Intel SSD||1x HP Quad Gbit NIC|
|Storage (Freenas on HP Microserver Gen8):||Intel® Pentium® G2020T (2.5GHz/2-core/3MB/35W)||16 GB||4x 2TB WD RED||1x HP Smart Array P410 + 512MB Cache Modul + Battery|
|Type:||HP Proliant DL380 G7|
|Chipset||Intel ® 5520 Tylersburg + Intel ICH 10|
|CPU Typ||Intel ® Xeon ® CPU L5630|
|CPU Speed||2.13 GHz|
|Cores / Threads||2 CPU(s), 4 Cores per CPU, 2 Thread(s) per Core, 16 total|
|L1, L2, L3 Cache||32k+32k, 256k, 12288k (12 MB)|
|Memory||32 GB DDR3 ECC|
|Installed||8 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|
|Disks||8x 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 …
VMware has just released a new technical white paper about performance best practices for VMware vSphere 6.5
It covers hardware for use with VMware vSphere, ESXi and Virtual Machines, Guest Operating Systems and Virtual Infrastructure Management.
I would like to receive push messages for triggered alerts from my vCenter. There is the possibility to execute a command when a alert has been triggered so I decided to write a script which will use Prowl to send push notification to my mobile apple device. I used Prowl already for other devices like my Homematic home automation system. It’s easy to use with an simple curl command. You can find a lot of good examples available by using Google.
Sources and Services:
You have to create an account on www.prowlapp.com and generate a new API key. The new API key has to be added to script (replace PLACE_YOUR_API_KEY_HERE with your API key).
This script is really basic and is only a proof of concept. I will extend and improve it over time.
root@vcenter [ ~ ]# mkdir bin root@vcenter [ ~ ]# cd bin root@vcenter [ ~/bin ]# vi alert.sh
#!/bin/bash #set -x value="$VMWARE_ALARM_ALARMVALUE" if [ $$value == "red" ]; then priority=2 else priority=0 fi app="$VMWARE_ALARM_NAME" event="$VMWARE_ALARM_EVENTDESCRIPTION" description="$VMWARE_ALARM_TARGET_NAME" apikey=PLACE_YOUR_API_KEY_HERE curl https://prowl.weks.net/publicapi/add -F apikey=$apikey -F priority=$priority -F application="$app" -F event="$event" -F description="$description"
Edit vCenter alert definition:
To receive the push notification you have to install the prowl app on your iOS device and login from the app to prowl.
Thats basically all what is required for vCenter push notifications on your iPhone.
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
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 …