new1234.jpg

Archive

Posts Tagged ‘ESXi 4.1’

VMware: WARNING: VFAT: 155: File_Ioctl

August 24th, 2012 3 comments

Today I was troubleshooting a disconnected vSphere 4.1 u1 host in the vCenter cluster by a customer. After connecting ILO and troubleshooting the vmkernel log I saw some errors flooding:

image

 

WARNING: VFAT: 155: File_Ioctl
Feb 10 21:56:45 vmkernel: 2:03:12:35.935 cpu0:672979)WARNING: VFAT: NotSupported_File_Ioctl:155: File_Ioctl
Aug 15 16:30:59 vmkernel: 122:14:58:30.147 cpu7:45795719)WARNING: VFAT: 155: File_Ioctl

 

Solution:

These messages are generated by the VMware ESXi BusyBox implementation during interactions with the host’s filesystems.

These messages are informational and can be safely ignored.

This issue is resolved in ESXi 4.1 Update 2.

 

Source: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Illegal OpCode after adding HP NC553i 10Gb 2-port FlexFabric adapter (RSOD)

July 20th, 2012 2 comments

Today I was adding some new HP NC553i 10Gb 2-port FlexFabric mezzanine cards in existing BL460 G7’s.. 3 months ago I’ve installed the latest firmware, the hypervisor installation is VMware vSphere ESXi 4.1 Update 2.. I received this warning messages:

image

 

Adapter type: HP NC553i 10Gb 2-oirt FlexFabric Adapter

image

 

Solution:

VMware released a KB article KB1035114:

When installing ESX 4.x on the ProLiant BL460c G7, BL465c G7, BL680c G7 and BL685c G7 server blades you are required to include network drivers for the NC551i and NC553i network adapters. These network cards use a controller from ServerEngines (now owned by Emulex), and the drivers are included in the Driver CD for ServerEngines BladeEngine 10Gb Ethernet Controller package (currently at version 2.102.440.0). 

 

Install latest firmware:

Download and install the latest firmware firmware, I’ve installed HP Smart Update Firmware Pack 10.10 (you can install the single FlexFabric Network adapter firmware here)

Download supported drivers:

I’ve downloaded the HP “VMware ESX 4.0/4.1 Driver CD for Emulex OneConnect OCe10102 10GbE Adapter (Network Function)” pack with the following supported drivers:

 

  • HP NC550SFP Dual Port 10GbE Server Adapter
  • HP NC550m Dual Port Flex-10 10GbE BL-c Adapter
  • HP NC551i FlexFabric 10Gb Adapter
  • HP NC551m FlexFabric 10Gb Adapter
  • HP NC552m 10Gb 2-port FlexFabric Converged Network Adapter
  • HP NC552SFP 10Gb 2-port Ethernet Server Adapter
  • HP NC553i 10Gb 2-port FlexFabric Converged Network Adapter
  • HP NC553m 10Gb 2-port FlexFabric Converged Network Adapter
  • HP Flex-10 10Gb 2-port 552M Adapter
  • HP FlexFabric 10Gb 2-port 554FLB Adapter
  • HP FlexFabric 10Gb 2-port 554FLR-SFP+ Adapter
  • HP FlexFabric 10Gb 2-port 554M Adapter
  • HP CN1000E Dual Port Converged Network Adapter
  • HP CN1100E Dual Port Converged Network Adapter

Download source: HP

 

Install the latest supported driver:

– Start the host and disable the adapter in the BIOS
– Upload driver via SSH/WinSCP/or (if possible) Browse Datastore..
– To install the driver:

esxupdate –bundle=EMU-be2net-4.1.334.0-offline_bundle-654249.zip update

image

 

Installation output:

image

.. reboot the host > enable the adapter in the BIOS, result:

 

image

 

More information: VMware KB

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Citrix Provisioning Target boot can take more than 5 minutes on vSphere 4.1

July 18th, 2012 2 comments

I’m currently working on a project with Citrix Provisioning 6.1 build 1082 / XenApp 6.5 RP1 running on a VMware vSphere 4.1 build 721871 cluster, we discovered some boot “time” problems at the target VM’s, some of our Citrix XenApp 6.5 targets take more then 5 minutes to get past the bootstrap portion of the boot process.


Solution:

BUG0321533: Booting in a VMware environment can take more than 4 minutes to get past the bootstrap portion of the boot process. This has only been reported using ESX 4.1

Download hotfix: here

1. From Provisioning Services server machine, backup the following file: ARDBP32.bin

For Windows 2008 this file is located in (default) "C:\ProgramData\Citrix\Provisioning Services\Tftpboot".

2. Copy the following file included in the hotfix folder to the "Tftpboot" sub-directory indicated above:

ARDBP32.bin

3. Back up the following files from the Provisioning Services-installation-folder\TSBboot folder (Default is C:\Program Files\Citrix\Provisioning Services\TSBboot):

TSBBDM.BIN

4. Copy the following files from the hotfix folder to the Provisioning Services-installation-folder\TSBboot folder (Default is C:\Program Files\Citrix\Provisioning Services\TSBboot):

TSBBDM.BIN

image

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Unable to load module /usr/lib/vmware/vmkmod/vmfs3: failure

March 29th, 2012 5 comments

Today I was installing VMware vSphere ESXi 4.1 at some brand new BL460 G7’s.. after creating a new array I started the installation, after F11 to “Accept and continue” I received this error message:

vmkctl.hostctlexception: unable to load module /usr/lib/vmware/vmkmod/vmfs3: failure

 

image

 

Solution:

To resolve this issue, download the ESXi 4.1 HP build from HP at https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=HPVM06.

  • This issue has been observed on these servers: 
    • HP BL 685c G7
    • HP BL 680c G7
    • HP BL 495c G5
    • HP BL 465c G7
    • HP BL 460c G7
    • HP BL 490c G7
  • After I Installed the HP version (always recommended but this customer installed the other hosts with the original installer) the setup completed!


More information from HP:

The Broadcom bnx2x VMware ESX Driver Version 1.54 does not function with HP Virtual Connect Device Control Channel (DCC) and SmartLink features on ProLiant and Integrity server blades configured with the NC532m or the NC532i adapter running firmware version 2.2.6. After installing or upgrading VMware ESX/ESXi 4.1 the following functionality is either not installed or is lost:

  1. New installation – DCC and SmartLink functionality is unavailable in an HP Virtual Connect environment with the NC532m or NC532i Network Adapters after installing VMware ESX/ESXi 4.1.
  2. Upgrade installation – If the bnx2x Asynchronous Driver Update CD version 1.52 was previously installed on a VMware ESX/ESXi 4.0 host, DCC/SmartLink capabilities will be lost after upgrading to VMware ESX/ESXi 4.1, which will overwrite the bnx2x driver version 1.52 with version 1.54 that is included with the base VMware ESX/ESXi 4.1operating system.
  3. Network failover – ProLiant and Integrity server blades hosting VMware ESX/ESXi 4.1 may lose network failover capabilities that use the VMware ESX NIC teaming failover policy (vSwitch setting) "Link Status only."

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Easy upgrade ESXi 4.1 to ESXi 5.0

July 13th, 2011 35 comments

Last night I did an upgrade from vSphere ESXi 4.1 to ESXi 5.0 using the ESXi 5 installation CD. The upgrade process was very easy.. elapsed time: 10 minutes!

image

^ Current installed OS: VMware ESXi 4.1.0 build 260247

– Mount the vSphere 5.0 cd-rom in the host
– Boot from CD-Rom drive

image.

– Choose: ESX-5.0.0 Installer in the menu

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Configure new vSphere 4 host with PowerCLI

July 5th, 2011 No comments

I’ve created a PowerCLI script that can be used to configure a vSphere 4 host with a custom configuration. And you can select in the menu to configure the host (option 1) + you can select (option 2) to add the host into a cluster on a vCenter Server. I’ll update this post with new configurations/versions, I’m still a PowerCLI beginner so.. please comment if you have any tips or suggestions.

Menu:

1. Configure new vSphere host:

– Connect vSphere host;
– Enter maintenance;
– Set the hostname and domain name;
– Configure DNS settings;
– Configure NTP Server;
– Configure Support User;
– Enable the software iSCSI initiator;
– Delete the default VM Network;
– Configure vSwitch0 – Management / vMotion (incl. failover en load balancing);
– Configure vSwitch1 – Network;
– Configure vSwitch2 – iSCSI (incl.VMkernels + failover en load balancing);
– Configure iSCSI target address;
– Exit Maintenance Mode

2. Configure new vSphere host to vCenter Server

– Connect vCenter server;
– Add vSphere Host to vCenter server;
– Re-Balance Cluster

0. Quit

The script: [updated: 07/07/2011 – v.1.5]

#====================================================================#
#   SCRIPT:        Configure_new_ESXi_Host_Menu.ps1                  #
#   FUNCTION:      Configure fresh installed host                    #
#   CREATED:       05/07/2011                                        #
#   MODIFIED:      07/07/2011                                        #
#   VERSION:       v.1.5                                             #
#====================================================================#
#   CHANGELOG:                                                       #
#                                                                    #
#    v.1.5                                                           #
#	 - Added answer field to configure host;                         #
#	 - Added start menu: config host and add to vCenter server       #
#	 - Hide config output, show's only when failure;                 #
#                                                                    #
#====================================================================#
# START MENU                                                         #
#====================================================================#
do {

Write-Host "Please make your choise:" -foregroundcolor yellow
Write-Host " 1. Configure new vSphere host"
Write-Host " 2. Configure new vSphere host to vCenter Server"
Write-Host " 0. Quit"
Write-Host " "
$response = Read-Host "Select 0-2"
Write-Host " "

switch ($response)
{
1 {
#====================================================================#
#   HOST = CUSTOM DEFINITIONS                                        #
#====================================================================#
$ESX_host = read-host "Select ESXi host by DNS to connect"
$newhostname = read-host "Select hostname to configure"
$newdomainname = read-host "Select domain name to configure"
$root_user = "root"
$root_password = read-Host "Select root password to connect"
$new_user = read-host "Select extra username to configure"
$new_user_password = read-Host "Select extra password to configure"
$dns01 = read-host "Select Primary DNS to configure"
$dns02 = read-host "Select Secundary DNS to configure"
$VMK01 = read-host "Select iSCSI VMkernel01 to configure"
$VMK02 = read-host "Select iSCSI VMkernel02 to configure"
$iSCSIsub = read-host "Select iSCSI Subnet Mask to configure"
$iSCSItarget = read-host "Select iSCSI target to configure"
$vMotiontcp = read-host "Select vMotion VMkernel to configure"
$vMotionsub = read-host "Select vMotion Subnet Mask to configure"
$NTPServer01 = "0.pool.ntp.org"
$NTPServer02 = "1.pool.ntp.org"
Write-Host "vSphere Host-configuration will begin..." -foregroundcolor Green
#====================================================================#
Write-Host "Connect to the target ESXi Host" -foregroundcolor green
#====================================================================#
Connect-VIServer "$ESX_host" -User "$root_user" -Password "$root_password"
Sleep 10
#--------------------------------------------------------------------#
Write-Host "Enter Maintenance mode" -foregroundcolor green | out-null
#--------------------------------------------------------------------#
Get-VMHost | Set-VMHost -State maintenance | out-null
#--------------------------------------------------------------------#
#
#
#====================================================================#
# ***CONFIGURE HOST SETTINGS***                                      #
#====================================================================#
Write-Host "Set the hostname and domain name" -foregroundcolor green
#--------------------------------------------------------------------#
Get-VMHostNetwork | Set-VMHostNetwork -DomainName $newdomainname -HostName $newhostname | out-null
Sleep 10
#--------------------------------------------------------------------#
Write-Host "Configure DNS settings" -foregroundcolor green
#--------------------------------------------------------------------#
Get-VMHostNetwork | Set-VMHostNetwork -DnsAddress $dns01 | out-null
#--------------------------------------------------------------------#
Write-Host "Configure NTP Server" -foregroundcolor green
#--------------------------------------------------------------------#
Add-VmHostNtpServer -NtpServer "$NTPServer01" , "$NTPServer02" | out-null
#--------------------------------------------------------------------#
Write-Host "Configure Support User" -foregroundcolor green
#--------------------------------------------------------------------#
New-VMHostAccount -Id "$new_user" -password "$new_user_password" -Description "Tech Support" -AssignGroups root -GrantShellAccess | out-null
#--------------------------------------------------------------------#
#
#
#====================================================================#
# ***CONFIGURE NETWORK***                                            #
#====================================================================#
Write-Host "Delete the default VM Network" -foregroundcolor green
#--------------------------------------------------------------------#
Get-VirtualPortGroup -Name "VM Network" | Remove-VirtualPortGroup -Confirm:$false | out-null
#--------------------------------------------------------------------#
Write-Host "Configure vSwitch0 - Management / vMotion" -foregroundcolor green
#--------------------------------------------------------------------#
Get-VirtualSwitch -Name vSwitch0 | Set-VirtualSwitch -Nic vmnic0,vmnic1 -Confirm:$false | out-null
New-VMHostNetworkAdapter -PortGroup vMotion -VirtualSwitch vSwitch0 -IP "$vMotiontcp" -SubnetMask "$vMotionsub" -vMotionEnabled:$true -Confirm:$false | out-null
get-virtualportgroup -name vMotion | Get-NicTeamingPolicy | Set-NicTeamingPolicy -MakeNicActive vmnic1 | out-null
get-virtualportgroup -name vMotion | Get-NicTeamingPolicy | Set-NicTeamingPolicy -MakeNicStandby vmnic0 | out-null
get-virtualportgroup -name "Management Network" | Get-NicTeamingPolicy | Set-NicTeamingPolicy -MakeNicActive vmnic0 | out-null
get-virtualportgroup -name "Management Network" | Get-NicTeamingPolicy | Set-NicTeamingPolicy -MakeNicStandby vmnic1 | out-null
#--------------------------------------------------------------------#
Write-Host "Configure vSwitch1 - Network" -foregroundcolor green
#--------------------------------------------------------------------#
New-VirtualSwitch -Name vSwitch1 -Nic vmnic2,vmnic3 -Confirm:$false | out-null
Get-VirtualSwitch -Name vSwitch1 |Set-VirtualSwitch -NumPorts "256" -Confirm:$false | out-null
Get-VirtualSwitch -Name vSwitch1 | New-VirtualPortGroup -Name "VLAN-100-Production" -VLANID 100 | out-null
Get-VirtualSwitch -Name vSwitch1 | New-VirtualPortGroup -Name "VLAN-200-Management" -VLANID 200 | out-null
Get-VirtualSwitch -Name vSwitch1 | New-VirtualPortGroup -Name "VLAN-300-DMZ" -VLANID 300 | out-null
#--------------------------------------------------------------------#
Write-Host "Configure vSwitch2 - iSCSI" -foregroundcolor green
#--------------------------------------------------------------------#
New-VirtualSwitch -Name vSwitch2 -Nic vmnic4,vmnic5 | out-null
New-VMHostNetworkAdapter -PortGroup "iSCSI01" -VirtualSwitch vSwitch2 -IP "$VMK01" -SubnetMask "$iSCSIsub" | out-null
New-VMHostNetworkAdapter -PortGroup "iSCSI02" -VirtualSwitch vSwitch2 -IP "$VMK02" -SubnetMask "$iSCSIsub" | out-null
get-virtualportgroup -name "iSCSI01" | Get-NicTeamingPolicy | Set-NicTeamingPolicy -MakeNicActive vmnic4 | out-null
get-virtualportgroup -name "iSCSI01" | Get-NicTeamingPolicy | Set-NicTeamingPolicy -MakeNicStandby vmnic5 | out-null
get-virtualportgroup -name "iSCSI02" | Get-NicTeamingPolicy | Set-NicTeamingPolicy -MakeNicActive vmnic5 | out-null
get-virtualportgroup -name "iSCSI02" | Get-NicTeamingPolicy | Set-NicTeamingPolicy -MakeNicStandby vmnic4 | out-null
#--------------------------------------------------------------------#
#
#
#====================================================================#
# ***CONFIGURE STORAGE***                                            #
#====================================================================#
Write-Host "Configure iSCSI target address" -foregroundcolor green
#--------------------------------------------------------------------#
Get-VMHost | Get-VMHostHba -Type iScsi | New-IScsiHbaTarget -Address "$iSCSItarget" | out-null
#--------------------------------------------------------------------#
Write-Host "Configure iSCSI initiator" -foregroundcolor green
#--------------------------------------------------------------------#
Get-VMHostStorage | Set-VMHostStorage -SoftwareIScsiEnabled $True | out-null
#--------------------------------------------------------------------#
#
#
#====================================================================#
# ***FINISHING CONFIGURATION***                                      #
#====================================================================#
Write-Host "Exit Maintenance Mode" -foregroundcolor green
#--------------------------------------------------------------------#
Get-VMHost | Set-VMHost -State connected | out-null
#--------------------------------------------------------------------#
#
#
Write-Host "vSphere Host-configuration has finished.." -foregroundcolor yellow
break;
}
2 {
#====================================================================#
#   vCenter - CUSTOM DEFINITIONS                                     #
#====================================================================#
$vCenterServer = read-host "Select vCenter server to connect"
$vCenterAdministrator = read-host "Select vCenter Administrator"
$vCenterPassword = read-host "Select vCenter Administrator password"
$cluster = read-host "Select Cluster to add host"
Write-Host "vSphere Host will be added in vCenter server..." -foregroundcolor Green
#====================================================================#
Write-Host "Connect to the target vCenter server" -foregroundcolor green
#====================================================================#
Connect-VIServer "$vCenterServer" -User "$vCenterAdministrator" -Password "$vCenterPassword"
#====================================================================#
Add-VMHost $ESX_host -Force -Location (Get-Cluster "$cluster") -User root -Password "$root_password" | out-null
#====================================================================#
#
#
#====================================================================#
# ***FINISHING CONFIGURATION***                                      #
#====================================================================#
Write-Host "Tell DRS to re-balance VMs including the new host" -foregroundcolor green
#====================================================================#
Get-DrsRecommendation -Cluster (Get-Cluster "$cluster") -Refresh | out-null
#====================================================================#
#
#
Write-Host "Host is added to vCenter Server.." -foregroundcolor yellow
break;
}
}

}
while ($response -ne "0")

image

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Compliance Checker for vSphere (freeware)

May 30th, 2011 No comments

Compliance Checker for vSphere downloads to a Windows desktop and the intuitive web-based interface requires little or no learning curve. Administrators simply point the product to the ESX and ESXi hosts they want to test compliance against to perform the test immediately. The resultant compliance report provides a detailed rule by rule indication of pass or failure. Where compliance problems are found, users are directed to a detailed knowledge base for an explanation of the rule violated and advice on remediation. Compliance Checker for vSphere should be downloaded by all VMware customers to assess and report on the security and compliance of deployed VMware servers against the VMware vSphere Hardening Guidelines.

Download free VMware Compliance Checker for vSphere.

image

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: vStorage API – VAAI check status

January 21st, 2011 4 comments

To determine if VAAI is enabled service console in ESX or the RCLI in ESXi, run the commands and ensure that the value is 1:

# esxcfg-advcfg -g /DataMover/HardwareAcceleratedMove
# esxcfg-advcfg -g /DataMover/HardwareAcceleratedInit
# esxcfg-advcfg -g /VMFS3/HardwareAcceleratedLocking

image

Can I check the VAAI status from the command line?

esxcfg-scsidevs -l | egrep "Display Name:|VAAI Status:"

image

More interesting information: yellow-bricks.com

Source: VMware KB

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

Categories: VMware Tags: , , , ,

VMware: My favorite Windows 2008R2 template configuration

January 17th, 2011 26 comments

image

Virtual Hardware (VMX) template configuration:

Hardware: Value:
Memory 2 GB
CPU’s 1
Video card Auto-detect video settings
VMCI device None
SCSI Controller 0 LSI Logic SAS, bus sharing: none
Hard disk 1 40 GB, Thin (after deploy always Thick)
CD/DVD Drive 1 Client Device
Floppy Drive 1 Removed
Network Adapter 1 VMXNET3, network: VM Network with DHCP (for joining domain)
General Options OS: Microsoft Windows Server 2008 R2 (64-bit)
VMware Tools Advanced: Check and upgrade Tools during power cycling
Virtual Machine Version 7

 

Microsoft Windows Server 2008 R2 template configuration:

– Install always the latest VMware Tools (in my case: ESXi 4.1 build 260247)

image

 

– Change the CD/DVD Drive 1 from drive letter D:\ to X:\

image

– Install VMware display driver: VMware SVGA 3D (Microsoft Corporation – WDDM)

image

Driver located: C:\Program Files\Common Files\VMware\Drivers\wddm_video\

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn