Posts Tagged ‘VMware’

Unable to connect to the MKS – VMware vSphere Console Fix

VMware

Here’s an old favourite of mine.  When trying to open a console session to a virtual machine within the VMware vSphere Client you may receive a black screen and the following error message: “Unable to connect to the MKS: Host address lookup for server”, “failed: No such host is known”.

Although there are a couple of things that can cause this error the most common reason is that the host is unable to resolve the name of the VMware ESX or ESXi host on which this VM is running.  As you’d expect this is often caused by a DNS issue or lack of an entry for the ESX/ESXi  host which is stopping the host’s name from being resolved.

VMware vSphere Host address lookup errorFirst of all you may be wondering what the ‘MKS’ part of the error message stands for, well you’ll be disappointed to know that it isn’t an acronym for something high tech and very complicated but rather is stands for; mouse, keyboard, screen.

When you go to request a console session of a VM by clicking ‘Open Console’, the client machine from which you are running the vSphere Client will receive a response back from the ESX or ESXi host providing it’s (ie: the ESX/ESXi host) name to the client machine.  At this point the client then uses the name of the ESX/ESXi host (as provided by the host) to establish communication through to the ESX/ESXi host for the purposes of viewing the VM’s console.

Of course, as you’d expect, if the client machine running the vSphere Client can’t resolve the ESX/ESXi’s host name then the console session cannot be established, hence the “Unable to connect to the MKS”, “Host address lookup” error message.

Troubleshooting & the Fix (not the drug variety):

So how do you resolve this issue I hear you say?  Well, this part is also quite straight forward as all you have to do is enable the PC/laptop running the vSphere Client to resolve the name of the ESX/ESXi host(s).  As you probably know a Windows based PC or laptop will use a local host file or DNS (also WINS with earlier versions of Windows OS) to resolve host names.

To resolve or not to resolve?  That is the question….

Your first step should be to open a command prompt (CMD) on your client and perform a ping to the name of the ESX/ESXi host.  Don’t forget to use the fully qualified domain name (FQDN) of the ESX/ESXi host if this is how the host is registered in the vSphere client.  To avoid any confusion look at the error message as this will contain the name of the ESX/ESXi host, in my example (see below) the name of my ESXi host is ‘esx5-01.domainname’.

 

Unable to connect to the MKS

The ping should, in theory, successfully resolve the ESX/ESXi’s host name to an IP address, if this doesn’t happen then you should ensure that your client PC or laptop is pointing to the correct, and working, DNS that contains an entry for the ESX/ESXi host. Hint: Your internet service provider (ISP) isn’t going to have the names of your ESX/ESXi hosts in their global DNS Smile so ensure you are running a local DNS service (eg: on a Windows Server OS VM) with the names of your ESX/ESXi host(s) entered into it or ….

… You could do the following, which is much easier for small vSphere lab environments, and will get you around needing to install a DNS service….  Note: Most people know about the local hosts file on a Windows OS, though I have included a little more detail to benefit those who weren’t aware of it.

Every modern Windows OS will have something called a local hosts file, which can be found in the following directory: C:\Windows\System32\drivers\etc

Strangely enough this file is called ‘hosts’ – the clue’s in the name. Winking smile

The contents of this hosts file will by default look like this:

VMware vSphere Unable to connect to the MKS

This local hosts file provides you with the ability to add in your own host names and associated IP addresses to your PC or laptop, which are then used by your Windows OS.  When trying to resolve a host name the Windows OS will by default look at this local hosts file first before using alternative name resolution services such as DNS to resolve a host name.

So, all you need to do is enter, and save, into this local host file the name and IP address of the ESX/ESXi host(s) in your vSphere environment.  Just to be on the safe side ensure you create an entry using the ESX/ESXi host’s FQDN and non-FQDN.  After making these changes make sure you save your changes to the local hosts file.  Here is an example of what the formatting would look like:

192.168.1.10    esxhost1
192.168.1.10    esxhost1.yourdomain

Now from a command prompt (CMD) perform a ping to the ESX/ESXi host making sure you use the same name (ie: FQDN or non-FQDN) as seen in the original error message.  Everything going well your client PC/laptop should now be able to successfully resolve the name of the ESX/ESXi host.  If not, take a closer look at your local hosts file again.  Hint:  without the correct read/write permissions set on the hosts file you can’t always save it as it is located in a Windows OS systems directory.

Some people have reported that if the line below has been un-commented (ie: there is no # in front of that line) in the local hosts file then this also causes an issue when trying to establish a console session to a VM:

“# ::1        localhost.localdomain localhost”

At this point you should now be able to open a successful console session via the vSphere Client to your VM.

Other things…

The resolution to the “Unable to connect to the MKS: Host address lookup for server”, “failed: No such host is known” as outlined above is one of the most common fixes though as with anything in IT there are other things that can cause the same or similar issue.

At this point I should also point out that having a firewall block the TCP/UDP port 902 used by the ‘console’ will also provide you with connectivity issues so double check to see if the firewall on your local PC/Laptop or any other firewall in between your client and the ESX/ESXi are blocking this port.  Check out this useful KB article from VMware for a list of all used ports

 

I hope this post has helped resolve your console connectivity issue, though if you have any alternative hints, tips or fixes for the “Unable to connect to the MKS: Host address lookup for server”, “failed: No such host is known” error then please share with others by leaving a comment below. Thanks.

 

The VMware VMTN Movement…

VMware

VMware VMTNThere is a movement in the air…  No, not that sort of air movement, but rather the variety where the hearts and minds of an increasing number of people move towards a common goal or objective.  “What is this movement about?” I hear you ask.

Well, it’s all about re-instating the VMware Technology Network (VMTN) subscription, which was cancelled by VMware back in February 2007.  Although a few people have been vocal about VMware bringing back the VMTN subscription in the past, this latest campaign kicked off by well known VMware SRM author, blogger and trainer, Mike Laverick has certainly gained momentum.  Since Mike’s original post back on the 4th November and the associated VMware Community forum thread there has been an overwhelming response from the ever faithful VMware community indicating that they would appreciate the VMTN programme being reinstated again.   

VMware VMTN[7]

So what was the VMTN subscription?  The VMTN was a paid for subscription which allowed you to install and use copies of VMware products for a 1 year period.  If you are familiar with Microsoft’s TechNet or MSDN subscription think of this as the VMware equivalent.

So what are the benefits of using VMTN? Any of you who have subscribed to Microsoft’s TechNet or MSDN programme before will no doubt agree on how useful it is to have full access to Microsoft’s range of OS, application and back office software to run in your work or home lab environment when needed. At present if you want to evaluate one of VMware’s products in your lab environment for an extended period of time you will find yourself, in most instances, having to find a way to generate a new trial key, and also having to reinstall the product itself.  This can be a real hassle!  Though the good news is that …

VMware is listening…

VMware is listeningAs indicated by Duncan Epping’s post here there are signs that VMware are “investigating the option to reinstate the VMTN Subscription program” which, at this early stage, sounds positive.  This VMTN re-instatement movement is certainly building momentum so let’s hope we see a formal announcement from VMware sometime soon.  Although, as Duncan mentions “… starting a program like this does take time and the program will need a serious overhaul”.

I am feeling quietly optimistic that VMware will come through and start offering the VMTN subscription again, which I will definitely sign up for if offered, though I suspect we may have to wait a little while yet.  If/when it does happen this will be great news for all of you running your own home or work vSphere lab and/or studying for a VMware accreditation over a period of a month or two. 

I’d be interested to know your thoughts on this and whether you’d find having a VMTN subscription useful.  Why not leave me a comment below?  Smile

 

 

Running VMware vSphere ESXi 5.0 on the HP Proliant Microserver

VMware

HP Proliant Microserver & VMware vSphere 5Those of you that have bought an HP Proliant Microserver for your work or home VMware vSphere lab are probably wondering whether it will work with VMware vSphere 5.0?  Well, the good news is that it does and that even the installation  process goes through without a hitch both to local internal USB pen drive or local disk.  I have tested this with the final RTM version of vSphere ESXi 5.0, not just the beta builds, and can confirm that the CPU, storage controller, memory and network card are detected without a problem meaning that you’re all set to go for when VMware make available the VMware vSphere ESXi 5.0 download available sometime soon. 

With the free downloadable version of ESXi 5.0 the amount of physical memory accessible in the host has been reduced to 8GB so this combined with the fact that the HP Microserver can only take 8GB anyway won’t leave you feeling like you’ve wasted your money on adding extra memory.  Those of you, like myself, that also have an HP Proliant ML110 G6 with 16GB will either have to look at only using 8GB of it’s memory, keep installing the eval license on a regular basis (too much hassle) or purchasing an entry level vSphere license to allow me to access the full 16GB of memory in the server.  Either way, the new exciting features (see my post here for more details) found in VMware vSphere 5.0 is too much of a temptation to leave my vSphere lab servers at vSphere 4.1.

 

HP Proliant Microserver & VMware vSphere 5 - Summary

VMware vSphere and HP Proliant - CPU

HP Proliant and VMware vSphere 5 - Memory

HP Proliant Microserver & VMware vSphere 5 - Storage Adapters

HP Prolian Microserver & VMware vSphere 5 - Network Adapters

Iomega PX4 NAS Device – Hands on Review

VMware

With Iomega’s recent release of their exciting new PX series of NAS devices I have been fortunate enough to get my hands on one of these funky new units. I have been a happy Iomega IX4 owner for the past two years and run two of them 24×7 in my home VMware vSphere lab.  In this time the only issue I’ve had is a single disk failure in one of the units which in my view isn’t bad going since they’re permanently left on and have live VMs running on them.

Iomega PX Review

There are three models in the Iomega PX series the most notable differences between them being the number of maximum drives, the form factor (ie: free standing versus rack mount) and some minor differences in CPU speed and memory in the device.

The Iomega PX series of NAS devices offer a number of improvements and enhancements over the IX series which makes a compelling reason to take a serious look at the PX if you’re in the market for a NAS for either home, a remote office or a SMB.  One of the most notable improvements for me is the increase in CPU and memory along with the inclusion of removable disk caddies which allows for 2.5” form factor SSD disks – great for adding that extra IOPS horsepower, and yes you can have a mix of conventional 3.5” SATA disks and 2.5” SSDs – cool !

You can’t beat hands on time with a product so here is a quick sub-6 minute overview of the actual physical PX4 product itself including comparisons with the older IX4 model.  Hope you find it of use.  Smile

 

 

 

** Update: 28/06/2011 – Thanks to Mike Foley for pointing out that the USB on the front of the PX is in fact USB 3.0 and not just a USB 2.0 as I mention in the video.  Smile

The following is a high level summary of some of these features and the specification of the Iomega PX devices:

  • High performance through optional solid state drives, dual Core Intel processor, 2GB memory and dual GbE NICs.
  • Multiple RAID levels – 0, 1, 10, 5, 5+1 (hot spare) and 6, all with automatic RAID rebuild and hot swap functionality.
  • Scalable configurations include fully populated, partially populated and diskless options. 7200 rpm SATA HDDs and SSD Drives are available from Iomega or may be purchased from the approved vendor list.
  • Active Directory Support and remote access for anytime, anywhere data availability.
  • Certified for VMware® vSphere 4.0, Citrix® XenServer™, and Windows Server 2003/2008/2008 R2.
  • Cross-platform file sharing with Windows®, Mac® and Linux computers, and simultaneous iSCSI block access for the most efficient storage utilization.
  • All major network file protocols supported.
  • Iomega Personal Cloud technology, a revolutionary web-based computing architecture that connects your Iomega network storage device to other individuals and/or devices via the Internet.
  • Windows Active Directory Trusted Domains, MSCS and Hyper-V Live Migration Support.
  • Data replication and device-to-device copy jobs keeps your data backed up and secure.

I will be putting the Iomega PX4 through its paces in the coming weeks so expect a couple of blog posts here on the performance and usability of the PX NAS device.

 

Technorati Tags: ,,,,,

Dell EqualLogic PS4000: Hands-on Review Part 4

VMware
About the Author

Author: James PearceJames is regular guest contributor to TechHead and is a Kent based qualified accountant, currently working in information security and technical architecture with  most of his  time “being spent on virtualisation and business continuity at the moment”. Check out his new virtualisation and storage blog here for more interesting and informative posts.

_________________________________________________

 Dell EquallogicThe Dell EqualLogic PS4000 series of iSCSI storage arrays are positioned above the MD3000i series and targeted at the SME sector, especially for vmware virtualisation, as well as “branch office” use for larger companies.  The model reviewed here is the XV model, with sixteen 300GB 15k SAS drives, and dual controllers and dual power supplies.

This is quite a complicated product, so I’ve split this into four sections:

Part 1 – The PS4000

Part 2 – EqualLogic Networking with Force10

Part 3 – System Management and Monitoring

Part 4 – Performance

 

Part 4 – Performance

Performance

OK the important bit – the numbers that EqualLogic don’t seem to want to print.  I’ve tested this array in Raid-50, 5 and 6 using a Windows Server 2003 VM running IOMeter on a Dell R610 (with 1 vCPU and 4GB RAM allocated) using the methods described on my blog, here.  For comparison, I’ve also run the tests on a few different storage systems, including a single SATA drive and a few local RAID arrays (note that the IOPS graphs have a logarithmic scale).

Sequential Read

iSCSI with Gigabit Ethernet (GbE) just doesn’t provide great sequential throughput as GbE is good ‘only’ for about 110MB/s.  With some command-line configuration, as described in part 2, a pair of GbE’s can be used load balanced, providing total bandwidth between ESX and the EqualLogic of about 220MB/s.

Running in Raid-50, the PS4000 gets very close to saturating this network connectivity, providing 210MB/s with 64 outstanding IOs.  Raid-5 and 6 fair slightly less well, at about 170MB/s.  Still, compare this to the old Dell Clarion based AX150i iSCSI chassis, providing only 40MB/s:

Of course the throughput is dwarfed by the local Perc-6i with 5 SAS drives, which puts in an impressive 330MB/s.

Sequential Write

The first configuration tested was Raid-6, which provides about 120MB/s on writes.  Given the dual-parity nature of Raid-6, this seems like reasonable performance.

But then there is a surprise – Raid-50 and Raid-5 provide similar performance at 130 and 140MB/s respectively.  Again for comparison, the local Perc-6i sustains over 330MB/s in the same test using Raid-5.

Still, sequential throughput isn’t a deal breaker and is relatively unimportant for virtualised workloads expect perhaps for volume based backups, and even then these figures are likely to be easily sufficient for perhaps 90% of real-life workloads.

Random Throughput

Random IO is what this array is all about – serving multiple contending workloads without allowing latency to rise enough to impact application response times.  This is where the PS4000 really scores over local storage, primarily due to its 16 drive bays.  With 3.4ms average seek and 2ms latency, each 15k6 should give at least 185 IOPS.  In practice,  command queuing and the fact the test file is very much smaller than the overall capacity, in an effort to simulate real life workloads, mean numbers considerably higher than this can be expected in these tests.  EqualLogic pre-sales presentations claim around 270 IOPS per drive in RAID-5 – but does it deliver?

The random workload used is 8K blocks, 100% random IO, 70% read, against a 30GB test volume.  The Raid-6 performance seems amazingly strong, just 10% down on Raid-5 although this is essentially due to the 70:30 weighting of the testing.

Achieving these IOPS rates needs a good queue depth – performance levelling out at about 64 outstanding IOs.  At this level, and even up to 192 outstanding IOs, latency remains comfortably within vmware’s recommended 50ms.

Recovery Mode

After a disk failure, the array immediately starts a rebuild using the spare drive.  As a result of this, performance is impacted – the IOMeter results roughly halved whilst this was ongoing.  Sequential write was hit hard, being reduced to around 30MB/s.

 

In Summary

The EqualLogic PS4000 is an accessible storage system for the SME market built to the usual Dell standards which performs well, scales now up to fourteen units, and should prove reliable thanks to top-quality components throughout.

Failure of disks, power supplies, interconnecting switches and controllers seems to work well and is gladly demonstrated by the commissioning engineer.  Dual-controllers also enable firmware updates to be made without downtime (although a maintenance window should still be used).

Limitations

The system isn’t however without it’s limitations.

In testing, an old Oracle 8i import job proved a corner-case where the array performed badly.  It should be noted that this is a pretty ancient piece of software that works with a low queue depth and is unlikely to see much use today – the problem essentially being the underlying command latency, which will always be higher for iSCSI compared to local storage.

Another limitation is present in preparing for a remote replication deployment.  The system works with block change tracking utilising (internally) 64MB blocks – hence a database changing a single sector will trigger a 64MB transfer to the remote site.  It would be helpful if the system could be used with the block change tracking enabled without a replication partner, in order to collect the statistics needed to assess the viability of SAN layer replication prior to committing a good wedge of cash to it.

Another issue is with the thin provisioning, however this is another iSCSI limitation.  Industry seems to be demanding iSCSI over NFS despite the protocols being very similar in terms of efficiency.  The issue with iSCSI though is that there is no delete command, so a run-away log file in a VM running on a thin-provisioned volume, or a carelessly thick-provisioned VM, will wipe out those gigabytes on the EqualLogic pretty much forever.  The only way to retrieve the space from the LUN is to move the VMs to a new LUN and delete the old.  In contrast, NFS storage simply doesn’t suffer part of this issue since ESX is communicating with it at the file system level (zeroing free space and a storage vMotion would still be needed to shrink thin-provisioned VMDKs).

Finally the sequential write performance seems disappointing, but it should be noted that the interoperable PS6000 series have higher speed processors and 10-GbE in some models, and would probably be better suited to such workloads.  In random performance – much more of interest in virtualisation projects and in particular database workloads – the EqualLogic is of course way ahead of a typical 6-drive server, running as it does at over 4,000 8K IOPS in Raid-50 with latency of under 16ms with 64 outstanding IOs.

Tuning

Getting the network layer configuration right is the key to getting the best from these arrays.  The mostly browser or Java based management interfaces offer excellent performance monitoring capabilities, but there is almost nothing by way of tuning.  This is really a good thing though since the system is self managing and will automatically move data between arrays based on their performance profiles in use.  And less settings to adjust really means less to get wrong.

vStorage

As the long awaited vStorage API seems finally due to make an appearance, the EqualLogic product will get even better since it will be one of the first able to provide hardware off-load capabilities to ESX, such as snapshots.

And Finally

After the release of the first part of this series several months ago, Dell were quick to get in touch to offer any assistance needed including direct access to a high-level engineer and access to an invitation-only user group.  The testing methodology has been reviewed by them and the performance metrics provided here were confirmed to be in the range expected.

The few niggles aside, the EqualLogic PS4000 is an excellent product with excellent management tools, and its support backing and simple configuration (networking aside) are real strengths in this product.

TrainSignal - vSphere Pro
VMware vSphere Recommended Reads
StarWind Software
TechHead Needs You - Top 25 Blog Sites
Veeam #1
Trilead
AppAssure