Steps to resolve HA firewall issues in vCenter 2.5

HA

If after enabling HA on a vCenter cluster you get the above configuration error, check in event log. if error is “Could not enable firewall ruleset:vim.fault.NotFound”

a.Disconnect host from vCenter
b. Log into host with PuTTy
c. Run the command esxcfg-firewall -e aam
d. service mgmt-vmware restart
e. Wait about 5 minutes
f. Connect host in vCenter
g. Open the configuration tab for the host in the VIC and go to “Licensed Features”
h. Edit License Source
i. Configure license server on host to Your license server
j. Right click on the host in the VIC and select “Reconfigure for VMware HA”

Advertisements

Changing the MAC Address on a VM to a Non VMware MAC Address

I recently had to P2V a server where the application that was running on it was bound to the MAC address of the physical server NIC. This was not going to work with the VMware assigned MAC address 00:50:56:ae:46:27. I had to set the NIC on the VM to the same as it was on the physical server.   Since I am still in the dark ages and working with VIM 3.5 this was not going to work. After finding a couple of old posts online http://jasonnash.com/2008/08/30/disabling-mac-address-checking-in-vmware/

http://www.networknet.nl/apps/wp/archives/787

 I was able to get the VM to use the MAC address from the physical server and have the VM power up. Without the error

 Mac1

Here is what I did

First I found that changing the MAC in the vSphere Client would not work.  I was working in ESX 3.5 and it does not allow you to change the MAC to anything but VMware generated.  This is not the case in vSphere 5 where you are able to change the MAC within the vSphere Client.

 Mac2

So I opened up the .vmx file and made a couple of changes.

I changed:

ethernet0.addressType = “vmx”

ethernet0.generatedAddress = “xx:xx:xx:xx:xx”

 

To:

ethernet0.addressType = “static”

ethernet0. Address = “xx:xx:xx:xx:xx”

Then I added:

ethernet0.checkMACAddress = “FALSE”

 

After making these changes and saving the .vmx file back to the host, the VM powered on successfully with the correct MAC address.

 

Another thing that I noticed was that after these changes were made I was no longer able to make any edits to the NIC via the client.  It would give the “MAC address is not valid” error.  This was ok with me, I will just make any future changes to the NIC such as port group changes via the .vmx file.

Storage vMotion (SVM) in vCenter 2.5

Storage vMotion in vCenter 2.5

Storage vMotion was introduced in VMware Virtual Infrastructure 3.5
Storage VMotion (SVM) enables live migration of virtual machine disks from one datastore to another with no disruption or downtime. Just as VMware VMotion allows IT administrators to minimize service disruption due to planned server downtime, Storage VMotion allows them to minimize disruption by reducing the planned storage downtime previously required for rebalancing or retiring storage arrays. Storage VMotion simplifies array migration and upgrade tasks, and reduces I/O bottlenecks by moving virtual machines while the VM remains up and running. It provides a hot migration of the storage location on which the vmhome resides.

SVM can only be done via the Remote Command Line Interface (RCLI), vSphere Command-Line Interface (vCLI) or PowerCLI.  For this guide I will only illustrate the PowerCLI method.

The assumption will be that you already have PowerCLI installed.

Start a PowerCLI session.

PowerCLI_1

 

Connect to the vCenter you are going to do the SVM on.

[vSphere PowerCLI] C:\> Connect-VIServer <vCenter_server_name>

When prompted log in to vCenter just as you would if you were using the VIClient.

Run the following command substituting the VM that you want to move and the datastore you want to move it to.

> Get-VM <VM_To_Move> | Move-VM -Datastore <Datastore_to_move_to>

 PowerCLI_3PowerCLI_2

You will see the progress bar in the PowerCLI window as well as the VIClient as noted above. 

If you add the parameter  –RunAsync at the end of the command, it will not wait for the progress to complete and will allow you to move on to another task immediately.

>  Get-VM <VM_To_Move> | Move-VM -Datastore <Datastore_to_move_to> -RunAsync
I am glad that this has been added to the GUI for all later releases of vSphere, but at my day job this is what I have to work with.