vCenter notification send push message using Prowl to iOS devices

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:

VMware Documentation

Push notification service

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).

Script:

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.

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 …

Alternative Setup of a VMware Homelab

My planed new Homelab requires a lot of space due to the fact of the size of the components. But what if someone would like to have a Homelab but does not have the space in the office. One option would be to run a fully virtualized Homelab but this is limited to the resources of the computer/laptop. A more costly option would be to use multiple INTEL NUC and a storage system.

Shopping list:

2x Intel NUC i5: Intel NUC6i5SYH
2x Samsung 32GB Memory: SAMSUNG 32GB Dual Channel Kit 2 x 16 GB 260 pin DDR4 2133 SO-DIMM (2133Mhz, PC4-17000, CL15) passend für alle Intel “Skylake” Notebooks mit DDR4 Standard
2x Samsung M2 SSD 250GB: Samsung MZ-N5E250BW 850 EVO interne SSD 250GB (SATA) grün
1x QNAP NAS 4 Bay: QNAP TS-453A-8G-NAS 4-Bay Intel Celeron Braswell N
4x WD Red 3TB: WD 3TB Red interne NAS-Festplatte (8,9 cm (3,5 Zoll) SATA) WD30EFRX
1x Netgear Managed Switch 8 port: Netgear ProSafe GS108T (8-Port Gigabit Smart Managed Switch 8 x 10/100/1000 – desktop)

You can use the standard ESXi (5.5 or 6) images provided from the VMware web site and install it using a USB stick.

As soon as I have all hardware available I’m going to document the complete setup on my web site.

How to configure VMware monitoring in Check_MK

Check_MK is able to monitor ESXi or vCenter out of the box. The configuration requires 2 steps and preferred a read only user.

1. Login to Check_MK

check_mk_login

2. Create new Host

create_new_host

Hostname: ESXi/vCenter Name or fqdn
IP Address: ESXi/vCenter Management IP

create_new_host_esxi

Save & Go to Services

The error message is normal and we can ignore it.

create_host_error

3. Go to Host & Service Parameters

host_service_parameters

4. Click on Datasource Programs

datasource_programs

5. Click Check state of VMWare ESX via vSphere

Bildschirmfoto 2016-03-03 um 14.53.28

6. Create rule in folder Main directory

Explicit hosts: ESXi-Name
vSphere User name: ReadOnlyUser-Name
vSphere secret: Password of the ReadOnlyUser
Select  
 Host Systems
 Virtual Machines
 Datastores
 Performance Counters
 License Usage
Select
 Display ESX Host power state on 
 Display VM power state on
 Placeholder VMs 

Bildschirmfoto 2016-03-03 um 14.57.08

8. Click on Save

Bildschirmfoto 2016-03-03 um 15.01.20

9. Activate your changes

Bildschirmfoto 2016-03-03 um 15.02.46

Bildschirmfoto 2016-03-03 um 15.04.36

10. Click on Hosts

Bildschirmfoto 2016-03-03 um 15.05.46

11. Click on Hosts

3rd icon – Edit services of host

Bildschirmfoto 2016-03-03 um 15.07.44

12. Activate missing

Bildschirmfoto 2016-03-03 um 15.08.40

13. Activate your changes –> see step 9

14. Check your discovered services.

Go to Views –> All Services

Bildschirmfoto 2016-03-03 um 15.11.56

15. Click on the refresh icon next to Check_MK and Check_MK Discovery

Bildschirmfoto 2016-03-03 um 15.13.38

That’s all. If you have question just leave a comment.

VMware vSphere 6 available

Today VMware released the new VMware vSphere 6. I was running the Beta for a long time and I must say it was working very good.

VMware vSphere 6
VMware vSphere 6 Whats New

The release of vSphere 6 is already exciting but there is one additional extrem cool new product from VMware called VIO (VMware Integrated OpenStack). It is an fully automated setup of an complete OpenStack environment based on VMware. I will try it asap because I’m playing around with OpenStack since a long time and it is definitely not an easy setup. Additionally as stated on the VMware page “Available for free for all customers with vSphere Enterprise Plus, vSphere with Operations Management Enterprise Plus or vCloud Suite.” it’s included in some of the licenses.

VMware Integrated OpenStack

As soon as I could play around with I will write an article about the complete setup process.

vSphere WebClient next to the vCenter

Normally VMware offers only the WebClient as standalone on Windows but there is a nice way to run the Webclient on linux and save the license costs for the Windows machine.

Install your Windows vCenter including SSO. As next step you import the vCenter Appliance and configure the SSO to use the existing SSO of your vCenter. Afterwards you only start the Webclient in the vCenter Appliance and keep the vCenter stopped. Now you have a full supported Webclient running on Linux.