This host has no isolation addresses defined as required by vSphere HA

This content is 3 years old. Technology changes with time. Keep that in mind as you read this article.

Had some troubles with an ESXi 5.5 host the past week and rebuilt some of the networking which included removing a vmkernel and re-adding to a standard vSwitch and then setting up VMotion and Management tags on it.

Came across the following error on my host in vSphere Client:

2016-05-13_135825

To resolve this issue, I needed to make sure that there is a default gateway on the port group that the VMotion vmkernel is on.

Click on the ESXi Host then navigate to Configuration > Networking and on the VMkernel Port that I’m using for VMotion, click Properties…

2016-05-13_135657

Next, I examine properties of the VMotion VMkernel.

2016-05-13_135706

Looking at the IP Settings tab, I see there is no VMkernel Default Gateway defined, so I clicked Edit…

2016-05-13_135712

I entered in my default gateway and clicked OK and then OK again to exit the switch properties dialog.

2016-05-13_135718

Finally, I right-click on the ESXi host and click Reconfigure for vSphere HA

2016-05-13_135743

At this point, no additional errors are reported for my ESXi host.  =)

Monitor ESXi Free using SNMP

This content is 3 years old. Technology changes with time. Keep that in mind as you read this article.

ESXi 4.1 and 5.0 Enable SNMP

SSH to host and edit the SNMP.XML file:

vi /etc/vmware/snmp.xml

Make the following changes:

<config>
<snmpSettings>
<enable>true</enable>
<communities>public</communities>
<targets>192.168.1.100@public</targets>
</snmpSettings>
</config>

Restart management agents with the following command:

/etc/init.d/hostd restart

On ESXi 5.1 and 5.5 enable SNMP

SSH to host and run the following command:

esxcli system snmp set --communities=public --enable=yes --targets=192.168.1.100/public

Test SNMP trap

vicfg-snmp --server <ESXiServerIP> --username root --password <Password> --test

Reviewing the SNMP configuration

When I look at my SNMP configuration using vCLI (once again, this is a read operation so I can use vCLI), I see the following.

vi-admin@vma:~> vicfg-snmp --server <ESXiServerIP> --username root --password <Password> -s

Current SNMP agent settings:
Enabled : 1
UDP port : 161

Communities :
public

Notification targets :
192.168.1.100@162/public

Options :
EnvEventSource=indications

vCenter Converter unable to see disks on source

This content is 4 years old. Technology changes with time. Keep that in mind as you read this article.

I’m working on converting a physical 2008 R2 server to a virtual machine for ESX 4.1.  I installed vCenter Converter Standalone 4.3 on this machine and ran through the wizard.  When I got to the disk configuration, nothing was listed.

2015-01-27_113507

Some research pointed me to this VMware KB article indicating to check the logs which are located in C:ProgramDataVMwareVMware vCenter Converter Standalonelogs.

2015-01-27_113533

Upon reviewing the logs, I see the following error:

[#1] [2015-01-27 11:31:16.775 04316 warning 'App'] Failed to get info for \.PhysicalDrive0: error Read \.PhysicalDrive0 disk layout: Incorrect function (1)

Researching this error, I arrive at another VMware KB article which indicates GPT partition support was not available in vCenter Converter editions lower than 5.1 (I had installed 4.3).

2015-01-27_113540

 

Proxmox VE 3.2 Installation Screenshots

This content is 5 years old. Technology changes with time. Keep that in mind as you read this article.

Installation of Proxmox VE 3.2 on an ESX 4.1 host. Note that KVM in Proxmox VE is not supported due to VT-x virtualization not being supported in ESX 4.1. ESXi 5.0+ support VT-x virtualization which would allow for Proxmox VE KVM support. OpenVZ containers in Proxmox still work without issue.

Hyper-V: Error applying Virtual Switch Properties changes

This content is 5 years old. Technology changes with time. Keep that in mind as you read this article.

I got the following error when attempting to create a Virtual Switch in Hyper-V on Windows 8.1.

2014-06-02_153048

Error applying Virtual Switch Properties changes

I resolved this by removing Oracle VirtualBox.  Some how this was causing the issue.  I’ll research it at a later date to get a specific reason for the failure.