VMware vSphere 5.0 « andysworld!

Posts Tagged ‘VMware vSphere 5.0’

HOW TO: Enable SSH Remote Access on a VMware vSphere Hypervisor 5.1 (ESXi 5.1)

Tuesday, May 28th, 2013

In my previous VMware Articles, most featured Intermediate VMware Topics. My next series of articles will concentrate on topics for the VMware Novice; this is the fifth article in this series.

If you would like to read the other articles in this series, they are listed here for your convenience.

HOW TO: Install and Configure VMware vSphere Hypervisor 5.1 (ESXi 5.1)

HOW TO: Connect to the VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client

HOW TO: Create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1)

HOW TO: Upload an ISO CD-ROM/DVD-ROM image to a VMware datastore for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client, and checking its MD5 checksum signature is correct.

In this series of basic VMware articles for the Novice, I’ll be showing you the basic VMware skills required to install, configure and deploy virtual machines using VMware’s FREE VMware vSphere Hypervisor (ESXi).

In this article we will show you HOW TO: Enable SSH Remote Access on a VMware vSphere Hypervisor 5.1 (ESXi 5.1) so you can remotely connect to the VMware vSphere Hypervisor 5.1 (ESXi 5.1) server remotely via SSH (PuTTY).

1: Connect to the VMware vSphere Hypervisor 5.1 (ESXi 5.1) or vSphere vCenter Server using the vSphere Client

Please refer to my Andysworld! article on HOW TO: Connect to the VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client

vSphere-Client-Connected-to-ESXi

Once connected to the “default hypervisor home page”, click the Inventory icon, to see the server’s Inventory.

Click Configuration Tab

Click the Configuration Tab.

Click Security Profile

Click Security Profile, followed by Properties

Service Properties

The Security Service Properties will be displayed.

SSH Options

Click the SSH label followed by Options button, you will notice the daemon service is currently stopped, this is the default.

SSH (TSM-SSH) Options – Click Start

The SSH (TSM-SSH) Options will be displayed. Click Start to start the SSH deamon. You can change the options here if you wish to Start and stop the SSH daemon service with the host, or Start automatically if any ports are open, and stop when all ports are closed. Check with your Security IT Policy which is best for you. Opening SSH ports long term can be considered a security risk.

SSH Daemon Running

You will notice the SSH Daemon Status has changed to Running
. Click OK to continue, and Click OK to return to Inventory.

Confirm using PuTTY, you can connect to the server successfully.

In vSphere 4 1, 5.0 and 5.1, when you have enabled Remote SSH management of hosts from the vSphere Client, you may notice that that a Configuration Issues warning yellow box appears on the Summary page of the host ESXi server.

Configuration Issues, SSH and ESXi shell enabled Configuration Issues, SSH and ESXi shell enabled

This Configuration Issues warning yellow box only appears when Remote SSH and/or ESXi shell has been enabled.

Please refer to my Andysworld! Article on HOW TO: Suppress Configuration Issues and Warnings Alert displayed in Summary status for ESXi 4.1 U2 or ESXi 5.0 after enabling SSH or ESXi Shell

Congratulations, you have successfully Enable SSH Remote Access on a VMware vSphere Hypervisor 5.1 (ESXi 5.1)

Tags: ESXi 5.0, ESXi 5.1, PuTTY, SSH, VMware vSphere 5.0, VMware vSphere 5.1, VMware vSphere Hypervisor
Posted in Virtualisation, Virtualization, VMware | Comments Off on HOW TO: Enable SSH Remote Access on a VMware vSphere Hypervisor 5.1 (ESXi 5.1)

HOW TO: Upload an ISO CD-ROM/DVD-ROM image to a VMware datastore for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client, and checking its MD5 checksum signature is correct.

Tuesday, May 28th, 2013

In my previous VMware Articles, most featured Intermediate VMware Topics. My next series of articles will concentrate on topics for the VMware Novice; this is the fourth article in this series.If you would like to read the other articles in this series, they are listed here for your convenience.

HOW TO: Install and Configure VMware vSphere Hypervisor 5.1 (ESXi 5.1)

HOW TO: Connect to the VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client

HOW TO: Create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1)

In this article we will show you HOW TO: Upload an ISO CD-ROM/DVD-ROM image to a VMware datastore for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client, and checking its MD5 checksum signature is correct. There are other third party tools, that can be used to upload ISO image files, these include:-

WinSCP – http://winscp.net/eng/index.php

Veeam FastSCP which is now part of Veeam Backup Free Edition for VMware and Hyper-V – http://www.veeam.com/virtual-machine-backup-solution-free.html?ad=vmware-esxi-fastscp-go-to.html

The above applications, require additional installation and configuration, in this article we will use the VMware vSphere Client.

1: Connect to the VMware vSphere Hypervisor 5.1 (ESXi 5.1) or vSphere vCenter Server using the vSphere Client

Please refer to my EE article on HOW TO: Connect to the VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client

vSphere Client Connected to ESXi 5.1 Server

Once connected to the “default hypervisor home page”, click the Inventory icon, to see the server’s Inventory.

Inventory

Right Click on the datastore. In this example the datastore name is datastore1. This is the default name given to the datastore on installation, it can be changed. Please refer to Step 4 Conducting a simple task using the VMware vSphere Client in my Andysworld! article HOW TO: Connect to the VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client

Right Click and select Browse Datastore

Right Click the datastore name ‘datastore1’ and select Browse Datastore.

Datastore Browser window

The Datastore Browser window will be opened, and you can browse the files and folders, that are located on the datastore. If no virtual machines or files are present, this will be empty. To organise your ISO image files, we would recommend you create a folder called isos. Either select the ‘Create A New Folder’ icon, on the ribbon bar, or right-click in the right-hand empty panel, and select New Folder.

Create Folder in datastore

Enter folder name – isos, and Click OK

Enter Foldername – isos

The isos folder will be shown in the datastore

datastore1 with isos folder

Select and Double-Click the isos folder to change folders.

isos folder

2: Uploading the ISO CD-ROM/DVD-ROM image to the datastore ‘datastore1’

Please refer to my Andysworld! Article HOW TO: Create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1)

Upload files to this datastore

Select the ‘Upload files to this datastore’ icon on the ribbon bar.

Select Upload Files

Select Upload File…

Browse to location of the stored iso image file on your computers hard disk

Browse to location of the stored iso image file on your computers hard disk, in my example, we have stored the iso image file, in c:isos, from our previous EE Article, the filename is Ubuntu 12.10 amd.iso. Click OK to continue and upload the file.

Select Yes to the Upload/Downloading Operation Warning

Select Yes to the Upload/Downloading Operation Warning.

Uploading…

The ISO image file, e.g. Ubuntu 12.10 amd.iso will be upload to datastore1 in the folder isos. This can take several minutes depending upon size and speed of connection to the VMware vSphere Hypervisor 5.1 (ESXi 5.1) host server.

datastore1 with iso image

datastore1 with the ISO image uploaded and stored in the folder isos. Click the X in the top right hand corner to Close the Datastore Browser.

3: Confirming the upload of the ISO image file has been transferred successfully using the MD5 checksum signature

To complete the following step SSH must be enabled and running on your VMware vSphere Hypervisor 5.1 (ESXi 5.1) host server, if SSH is not running you will receive a connection refused message.

To Enable SSH on your VMware vSphere Hypervisor 5.1 (ESXi 5.1) host server, please see my Andysworld! article HOW TO: Enable SSH Remote Access to a VMware vSphere Hypervisor 5.1 (ESXi 5.1)

Connect to the VMware Hypervisor ESXi server via SSH. Using PuTTY a free telnet and SSH client or another SSH client Login and Connect to the VMware Hypervisor ESXi server, using IP address or hostname of the VMware Hypervisor ESXi server, using root username and password credentials. This can also be performed if you have access to the console.

PuTTY SSH terminal session

logged in as root to ssh terminal session

You will need to change folder or directories to the location of the iso image file. The VMware VMFS datastores are mapped here /vmfs/volumes. Use the following command to change to the datastore1 datastore and isos folder.
cd /vmfs/volume/<datastore name>/<folder name>

change folders

example :- cd /vmfs/volumes/datastore1/isos
type cd /vmfs/volumes/datastore1/isos in the SSH session window.

md5sum

When you have successfully changed folders to the location of the isos image file which has been uploaded, use the following command to check the MD5 checksum signature.
md5sum <filename>
example md5sum Ubuntu 12.10 amd.iso

MD5 Checksum Signature

type md5sum Ubuntu 12.10 amd.iso in the SSH session window. After several minutes, and the time taken, depends on the size of the ISO image file, and speed of host processor and storage, a MD5 checksum signature will be displayed. The number displayed next to the filename – 7ad57cadae955bd04019389d4b

9c1dcb – is the MD5 checksum signature. Compare this number with the original number computed before the ISO image file was uploaded, if they match, the transfer was successful. If they do not match, repeat Step 2 above.Congratulations, you have successfully uploaded an ISO CD-ROM/DVD-ROM image to a VMware datastore for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client, and checked its MD5 checksum signature is correct.

Tags: datastore, ESXi 5.0, ESXi 5.1, ISO, VMFS, VMware vSphere 5.0, VMware vSphere 5.1, VMware vSphere Hypervisor
Posted in Virtualisation, Virtualization, VMware | Comments Off on HOW TO: Upload an ISO CD-ROM/DVD-ROM image to a VMware datastore for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client, and checking its MD5 checksum signature is correct.

HOW TO: Create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1)

Wednesday, May 22nd, 2013

In my previous VMware Articles, most featured Intermediate VMware Topics. My next series of articles will concentrate on topics for the VMware Novice; this is the third article in this series.

If you would like to read the other articles in this series, they are listed here for your convenience.

HOW TO: Install and Configure VMware vSphere Hypervisor 5.1 (ESXi 5.1)

HOW TO: Connect to the VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client

This article will show you how to create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1).

What is an ISO? (Andy’s Laymen Definition)
An ISO is an image or bit copy of a CD-ROM/DVD-ROM, the ISO is a file, similar to a compressed archived file, this *.iso file contains the data from a CD-ROM/DVD-ROM. The ISO file is a virtual CD-ROM/DVD-ROM. Using an *.iso file has many advantages, some are listed below:-

The original CDROM/DVD-ROM can be stored securely, and is no longer required, after an ISO image has been created.

Multiple virtual machines can use the same *.iso concurrently.

Computers without a CD-ROM/DVD-ROM reader can use the data stored on the *.iso file.

Installing OS (operating systems) or transferring data is faster.

1: Prerequisites

An original operating system CD-ROM/DVD-ROM

Download ISO Recorder from http://alexfeinman.com/isorecorder.htm

Download MD5 & SHA-1 Checksum Utility from http://raylin.wordpress.com/downloads/md5-sha-1-checksum-utility/

2: Install ISO Recorder

Download ISO Recorder from http://alexfeinman.co/isorecorder.htm We like to use ISO Recorder, because it is a small lightweight application, which integrates into the shell of your OS (operating system). e.g. you right click the CD-ROM/DVD-ROM reader and the option is there to create an ISO.

There are several versions of ISO Recorder to download, ensure you download the correct version for your OS, and the correct version for your processor, as there are 32-bit and 64-bit versions available.

After you have downloaded the correct version, Double-Click the installer program (*.msi) you have download, we will install the Windows 7 64 bit version, which has the filename ISORecorder31x64.msi

Welcome to the ISO Recorder Setup Wizard

At the Welcome to the ISO Recorder Setup Wizard dialogue page, Click Next and continue

Select Installation Folder.jpg

At the Select Installation Folder dialogue page select the defaults, and Click Next to continue.

Confirm Installation

Confirm installation at the Confirm Installation dialogue page, and Click Next to continue.

Installation Complete

The installer will Complete the software installation, it only takes a few seconds to complete. Click Close to complete the installation.

3: Create an ISO image file

My Computer

Select My Computer.

CD-ROM Inserted

Insert an original operating system CD-ROM/DVD-ROM into your optical media device. In this example, we are using an Ubuntu 12.10 DVD-ROM.

Right Click the CD-ROM/DVD-ROM

Right-Click the CD-ROM/DVD-ROM, and select Create image from CD/DVD.

Select Destination for ISO image file

Select a filename and destination folder on your computers hard drive to store the ISO image file and Click Next to continue, this will create an ISO image file.

22 percent complete …

51 percent complete…

83 percent complete…

The data will be copied from the CD-ROM/DVD-ROM, and the ISO image will be created. This can take several minutes to complete.

Completed – Finish

Select Finish to complete the operation. The ISO image file has been created.

4: Creating a MD5 checksum signature of the ISO image file

We will use the MD5 & SHA-1 Checksum Utility to create a MD5 checksum signature for our freshly created ISO image file. This is important, so we can compare these signatures, once we have completed the transfer to our VMware host servers, and confirm the ISO image file has not been corrupted in transfer.

MD5 SHA-1 Checksum Utility

Double-Click and start the MD5 & SHA-1 Checksum Utility application. Click browse and select your freshly created ISO image file.

Shortly after selecting the ISO file, the application will start calculating the MD5 and SHA-1 checksums for the file, this can take a few minutes depending upon the size of the ISO image file, which needs to be read.

The MD5 checksum for my Ubuntu 12.10 amd.iso is:-

MD5 Checksum: 7AD57CADAE955BD04019389D4B9C1DCB
SHA-1 Checksum: 8618058554FFD11E317356EC25885BCB8C1D0B36

Generated by MD5 & SHA-1 Checksum Utility @ http://raylin.wordpress.com/downloads/md5-sha-1-checksum-utility

Please note the MD5 checksum value for use with the VMware vSphere Hypervisor 5.1 (ESXi 5.1)

Congratulations you have successfully created your first ISO (*.iso), and created a MD5 checksum signature for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1).

In my next Article in this series, we will show you HOW TO: Upload and Check the MD5 signature of an ISO CD/DVD image to a VMware datastore using the vSphere Client, for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1)

Tags: datastore, ESXi 5.0, ESXi 5.1, ISO, VMFS, VMware vSphere 5.0, VMware vSphere 5.1, VMware vSphere Hypervisor
Posted in Virtualisation, Virtualization, VMware | Comments Off on HOW TO: Create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1)

HOW TO: Tag and Configure a storage device as a Solid State Disk (SSD) in VMware vSphere 5.0 or 5.1 (ESXi 5.0 or ESXi 5.1)

Thursday, November 29th, 2012

In VMware vSphere 5.x (ESXi 5.x) there is a new feature called Host Cache Configuration. This new feature allows the VMware vSphere Administrator to configure the VMware vSphere 5.x (ESXi 5.x) host server to use a cache on a Solid State Disks (SSD) for the virtual machine’s swapfile for better performance, because the SSD has much faster latency than a traditional mechanical disk. This is also known in VMware Administrator circles as Swap to Host Cache or Swap to SSD. Once Host Cache Configuration has been enabled, the virtual machines will be swapping to SSD, but this swapfile is not a true swap file, and the entire virtual machine swap file (.vswp) is not stored on the SSD.However, not all SSD devices are correctly tagged as SSD. This tutorial shows how to tag a Non-SSD storage device as SSD, if you want to experiment with Host Cache Configuration but do not have a SSD to hand. This is not supported by VMware, tagging a non-SSD as a SSD.

The same procedure can be followed to tag a SSD, correctly, if it’s not recognized by the VMware ESXi server.

With the current fall in prices for consumer SSDs, it can give a real performance boost to a VMware ESXi 5.x server which is short on memory. Consumer SSDs e.g. Kingston SSDNow V+200 Drive Model SVP200S37A/60G are generally cheaper than server memory. We recently purchased this model for £29.99 GBP.

The commands we will be using in this Tutorial, are the esxcli commands, these commands can be executed on the ESXi shell, through the vMA or PowerCLI esxcli remote version. In this tutorial I’ll be logging into the ESXi server, and executing the commands on the ESXi shell.

1. Connect to the VMware vSphere Hypervisor (ESXi) or VMware vSphere vCenter Server

Using the VMware vSphere Client, Login and Connect to the ESXi server, using IP address or hostname of the ESXi server, using root username and password credentials. If you have a VMware vSphere vCenter server, you could also specify IP address or hostname of the vCenter server.

Using the VMware vSphere Client, Login and Connect to the ESXi server

2. Check and record the storage device name to be tagged as a SSD

Check there is a VMFS volume already formatted on the storage device, you want to present to the Host ESXi server, as a SSD and record the device name for later in Step 4.

Select Host > Configuration > Storage

storage device to configure as SSD

In the example above, the local storage device mpx.vmhba1:C0:T0:L0 is a local disk, formatted with the datastore name datastore1 as VMFS5. Record the storage device name mpx.vmhba1:C0:T0:L0.

3. Logon to ESXi console (shell) via PuTTY

Using PuTTY a free telnet and SSH client or another SSH client Login and Connect to the VMware Hypervisor ESXi server, using IP address or hostname of the VMware Hypervisor ESXi server, using root username and password credentials.

putty SSH terminal session

logged in as root to ssh terminal session

4. Create a new SATP rule

At the console or SSH session type the following commands to create a new SATP rule.

esxcli storage nmp satp rule add --satp VMW_SATP_LOCAL --device mpx.vmhba1:C0:T0:L0 --option=enable_ssd

using the device name recorded in Step 2 above. The console will return a new line. To check the rule has been created correctly type the following commands

esxcli storage nmp satp rule list | grep enable_ssd

the following screenshot should be displayed

Confirmation of rule creation

confirming the creation of the rule.

5. Claim storage device

At the console or SSH session type the following commands

esxcli storage core claiming reclaim -d mpx.vmhba1:C0:T0:L0

using the device name recorded in Step 2 above.

I have seen the following error messages when trying to claim devices, either restart the server or use the “unclaim” device command.

Unable to unclaim path vmhba1:C0:T0:L0 on device mpx.vmhba1:C0:T0:L0. Some paths may be left in an unclaimed state. You will need to claim them manually using the appropriate commands or wait for peri

you can unclaim the device by specifying the device name.

esxcli storage core claiming unclaim --type device --device device_name

6. Reload the claim rules

I usually reload the claim rules and run the rules using the following commands:

esxcli storage core claimrule load
esxcli storage core claimrule run

7. Confirm device is Tagged as SSD

Use the following command at the console, to check if the device has successfully been tagged as a SSD

esxcli storage core device list --device=mpx.vmhba1:C0:T0:L0

The following output will be displayed for the device.

local device tagged as SSD

Check the output states “Is SSD: true”

You have successfully configured and tagged a local device as a SSD. If you now repeat Step 2 above, you will see the device now states SSD.

storage device to configure or tagged as SSD

In my next Article, I show you how to configure Host Cache Configuration.

Further reading can be found here in the VMware
vSphere 5 Documentation Center :- Tag Devices as SSD

Tags: ESXi 5.0, ESXi 5.1, Solid State Disk, SSD, VMware vSphere 5.0, VMware vSphere 5.1
Posted in All, Virtualisation, Virtualization, VMware | Comments Off on HOW TO: Tag and Configure a storage device as a Solid State Disk (SSD) in VMware vSphere 5.0 or 5.1 (ESXi 5.0 or ESXi 5.1)

Tweaking ESXi 5.0 – Adding un-supported hardware to VMware vSphere ESXi 5.0 – Adding a QLE-220 to ESXi 5.0

Tuesday, September 20th, 2011

A continuation of this article – Tweaking ESXi 4.1U1 – Adding un-supported hardware to VMware vSphere ESXi 4.1 U1 – Adding a QLE-220 to ESXi 4.1 U1.

No official support for the Qlogic QLE-220 in ESXi 5.0, vSphere GUI client before tweak

Because I’m also now testing Production VMware vSphere 5.0 (ESXi 5.0), and also need to connect the ESXi 5.0 servers to the fibre channel SAN using the same Qlogic QLE-220 4GB fibre channel cards. These are the PCI-E cards that fit in the HP ProLiant MicroServer quite nicely. As these Qlogic cards were NOT supported in ESXi 4.1, it’s unlikely they are supported in ESXi 5.0, and they are NOT, and not included on the HCL (Hardware Compatibility List).

Again, trying to get ahead of the curve, it will not be long, before I’m asked the same question as before with ESXi 4.x.

“ESXi 5.0 does not “see my network interface card, or storage controller.”

“How do I add this mass storage controller, network interface card, fibre channel HBA to ESXi?”

A.Andy’s Thoughts

It is my understanding, that rather than a single oem.tgz, which contains the simple.map Vendor and Device IDs of ESXi 4.x, the simple.map file has been broken down into likewise individual mapping files, /etc/vmware/driver.map.d reveals 60 individual map files which contain the Vendor Id and Device Ids similar to the original simple.map of ESXi 4.x.

ESXi 5.0 contents of /etc/vmware/driver.map.d

The file I need to modify is the qla2xxx.map file, to add the Vendor ID and Device ID. I may also have to alter the pci.ids files as well, but it’s unlikely!

the console command lspci -v reveals the same vendor ID and device ID

console output of lspci -v on ESXi 5.0

When ESXi 5.0 boots up you can see the individual driver modules files being extracted from their tarbal archives and loaded into ramdrive memory. These tarballs contain the mapping PCI ID mapping file and also the drivers for the device. All that is required is to add your new qla2xxx.map file (modified mapping file) into the scsi-qla.v00 tarballed file.

B. Adding the device to the mapping file

I’ve completed this by, extracting the original contents, including sub directories, copying my new mapping file, and creating a new archive.

cd tmp
mkdir tweak
cd tweak
cp /bootbank/scsi-qla.v00 scsi-qla.tgz
tar -xvf scsi-qla.tgz
rm scsi-qla.tgz
Update and tweak the qla2xxx.map file.
Modifying the qla2xxx.map file to add additional Vendor and Device ID
tar -cvzf scsi-qla.tgz etc usr
mv scsi-qla.tgz scsi-qla.v00
cp scsi-qla.v00 /bootbank/scsi-qla.v00
restart server.

Qlogic QLE-220 in ESXi 5.0, vSphere GUI client after tweak

Viola! An un-supported Qlogic QLE-220 added and working in ESXi 5.0.

Tags: ESXi 5.0, Fibre Channel, HP ProLiant, HP ProLiant Microserver, oem.tgz, pci.id, QLE-220, Qlogic, simple.map, VMware, VMware vSphere 5.0, vSphere 5
Posted in All, computing, Virtualisation, Virtualization, VMware | Comments Off on Tweaking ESXi 5.0 – Adding un-supported hardware to VMware vSphere ESXi 5.0 – Adding a QLE-220 to ESXi 5.0

VMware vSphere 5.0 (ESXi 5.0) Officially released and available for Download

Thursday, August 25th, 2011

ESXi 5 installer ISO

VMware-VMvisor-Installer-5.0.0-469512.x86_64.iso

vSphere Client

VMware-viclient-all-5.0.0-455964.exe

Linux Tools ISO

VMware-tools-linux-8.6.0-425873.iso

Tags: ESXi 5.0, VMware vSphere 5.0
Posted in All, computing, Virtualisation, Virtualization, VMware | Comments Off on VMware vSphere 5.0 (ESXi 5.0) Officially released and available for Download

VMware ESXi 5.0 tested on HP ProLiant MicroServer N36L

Saturday, August 13th, 2011

Just confirming that VMware ESXi 5.0 tests out okay on the HP ProLiant MicroServer N36L, ideal for labs or testing, I don’t expect to see this HP ProLiant MicroServer N36L on the Hardware Compatibility List, when VMware ESXi 5.0 is finally launched Q3 2011, but ideal for labs or testing, on this small low powered server.

VMware ESXi 5.0 tested on HP ProLiant MicroServer N36L

As with ESXi 4.1, no support for the “fake RAID controller”, so ESXi 5.o detects both SATA disks, and does not detect as a RAID 1 set. But the Broadcom NetXrtreme BCM5723 Gigabit Etherner network interface is supported.

Tags: HP ProLiant Microserver N36L, VMware ESXi 5.0, VMware vSphere 5.0
Posted in All, Virtualisation, Virtualization, VMware | Comments Off on VMware ESXi 5.0 tested on HP ProLiant MicroServer N36L

andysworld!

Posts Tagged ‘VMware vSphere 5.0’

HOW TO: Enable SSH Remote Access on a VMware vSphere Hypervisor 5.1 (ESXi 5.1)

Connect to the VMware vSphere Hypervisor 5.1 (ESXi 5.1) or vSphere vCenter Server using the vSphere Client

HOW TO: Upload an ISO CD-ROM/DVD-ROM image to a VMware datastore for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client, and checking its MD5 checksum signature is correct.

Connect to the VMware vSphere Hypervisor 5.1 (ESXi 5.1) or vSphere vCenter Server using the vSphere Client

Uploading the ISO CD-ROM/DVD-ROM image to the datastore ‘datastore1’

Confirming the upload of the ISO image file has been transferred successfully using the MD5 checksum signature

HOW TO: Create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 5.1 (ESXi 5.1)

Prerequisites

Install ISO Recorder

Create an ISO image file

Creating a MD5 checksum signature of the ISO image file

HOW TO: Tag and Configure a storage device as a Solid State Disk (SSD) in VMware vSphere 5.0 or 5.1 (ESXi 5.0 or ESXi 5.1)

1. Connect to the VMware vSphere Hypervisor (ESXi) or VMware vSphere vCenter Server

2. Check and record the storage device name to be tagged as a SSD

3. Logon to ESXi console (shell) via PuTTY

4. Create a new SATP rule

5. Claim storage device

6. Reload the claim rules

7. Confirm device is Tagged as SSD

Tweaking ESXi 5.0 – Adding un-supported hardware to VMware vSphere ESXi 5.0 – Adding a QLE-220 to ESXi 5.0

VMware vSphere 5.0 (ESXi 5.0) Officially released and available for Download

VMware ESXi 5.0 tested on HP ProLiant MicroServer N36L

andysworld!

Andy on twitter

Categories

Recently

Archives

Links

Pages

Validate my RSS feed