vSphere

Some cool new features in vSphere Command Line Interface CLI 4.1

Posted by Brian on Jul 29, 2010 in CLI, VMware, vCenter Server, vSphere | View Comments

Now that vSphere 4.1 has been out for a couple of weeks you’ve probably had some time to play with it in a lab. I’m sure you have also spent some time reading the release notes getting up to speed on the large list of new features that were released. After spending time myself getting familiar with many of the new options I wanted to dig in and see what was new with the Command Line Interface in 4.1. Since this is going to play a big part in how you will be managing ESXi hosts once you move your environment over to the platform of the future.

I have grabbed a list of the new commands added to vCLI 4.1, these command will help narrow the gap that had existed between what you could run on the ESX console (COS) and what you could do via the vCLI with an ESXi host. Notice the part at the end where it lists some of the commands that cannot be executed against a vCenter server for a host in lock down mode.

• vicfg-hostops – Allows you to examine, stop, and reboot hosts and to instruct hosts to enter and exit maintenance mode.
• vicfg-authconfig – Allows you to add an ESX/ESXi host to an Active Directory domain, remove the host, and list Active Directory domain information.
• vicfg-ipsec – Supports IPsec setup.

vSphere CLI 4.1 also includes the following new functionality:

• The following options have been added to esxcli:
  • esxcli swiscsi session – Manage iSCSI sessions.
  • esxcli swiscsi nic – Manage iSCSI network interfaces.
  • esxcli swiscsi vmknic – List VMkernel network interfaces available for binding to particular iSCSI adapter.
  • esxcli swiscsi vmnic – List available uplink adapters for use with a specified iSCSI adapter.
  • esxcli vaai device – Display information about devices claimed by the VMware VAAI (vStorage APIs for Array Integration) Filter Plugin.
  • esxcli corestorage – List devices or plugins. Used in conjunction with hardware acceleration.
  • esxcli network – List active connections or list active ARP table entries.
  • esxcli vms – List and forcibly stop virtual machines that do not respond to normal stop operations.
• Some of the parity issues between vSphere CLI and the ESX service console have been resolved.
• You can now run vCLI commands using SSPI (--passthroughauth) against both vCenter Server and ESX/ESXi systems.
• Lockdown mode allows vSphere administrators to block direct access to ESXi systems. With lockdown mode enabled, all operations must go through a vCenter Server system. The following commands cannot run against vCenter Server systems and can therefore not be used in lockdown mode:
  • vicfg-snmp
  • vifs
  • vicfg-user
  • vicfg-cfgbackup
  • vihostupdate
  • vmkfstools
  • esxcli
  • vicfg-ipsec

If you want to run these commands against an ESXi system, turn off lockdown mode using the vSphere Client.

Use web browser to view vSphere Configuration and Log files

Posted by Brian on Jul 29, 2010 in VMware, vSphere | View Comments

Sure this nothing earth shattering but it’s just something simple that can make your life easier. With a web browser and some links that I will provide below you can view some of the vSphere configuration files and messages from logs. This is probably the fastest way to get a view into your host with out having to SSH into the server or use another method. This method works for both vSphere 4.0 and 4.1 hosts and it works on both ESX and ESXi hosts.

You can view the VMware vSphere Configuration files from a browser using a link formatted like the following. https://hostname/host From that link you will need to authenticate to your host and then will be able to view a list of files from the host. In the list of files presented with be configuration files and some logs.

There is another page viewable with a web browser that will show you log messages from your ESX or ESXi host. Use the following syntax for the link.  https://hostname/host/messages

VKernel accounces Chargeback 2.0 for vSphere and Hyper-V shops

Posted by Brian on Jul 27, 2010 in Hyper-V, Tools, vCenter Server, vSphere | View Comments

The release also adds support for mixed chargeback models. VKernel Chargeback 2.0 now supports both allocated and actual resource consumption models. By reporting on both measures, infrastructure teams can chargeback for actual resource consumption, allocated resources, or simply show application teams the difference in real dollars between their allocated capacity and actual usage. This cost visibility is critical to capacity management, reducing VM spral and supporting private cloud initiatives.

Configure VMware ESXi 4.1 for Active Directory Integration

Posted by Brian on Jul 24, 2010 in VMware, vSphere | View Comments

By now you’re sure to have heard that vSphere 4.1 offers the ability to use Active Directory for authentication. This is something that has been on peoples wish lists for sometime now. There was some hacks to make this work on the previous versions, but they were a use at your own risk option. With AD integration you can use your normal domain user accounts that poses admin rights already to authenticate with your ESX servers. This will help keep things in sync and keep you from having to manually create local accounts on your ESX hosts. If you were just using Virtual Center or vCenter server the new name it has always been able to use Active Directory for authentication.

There are a couple of different ways that you can enable AD integration ( vSphere client, vCLI, scripting or Host Profiles). In this post I will cover the method through vSphere client.

There is a password authentication bug in VMware vSphere ESXi 4.1

Posted by Brian on Jul 15, 2010 in VMware, vSphere | View Comments

While doing my usual surfing in the VMware forums I came across a thread about a password issue with ESXi 4.1. The issue seems to be that the latest version of ESXi only looks at the first 8 digits of your password. So as long as you type in the first 8 digits of your password correct the rest does not matter. I was able to recreate this in my home lab using a 10 digit password.

So to make it crystal clear when I installed ESXi 4.1 with Build # 260247 I entered a 10 digit password for “root”. After the install and a reboot I was able to login using my password as expected. I then enabled TSM mode for local and SSH access. I was then able to log on using local or SSH as the method using my exact password, just the first 8 digits or the 8digits plus anything else after. I even tried entering the first 8 digits and several digits of random characters afterward and it still accepts the password.

I will post a follow up to this post once something is released from VMware regarding this password issue. Until then you can follow along with the thread over on the VMware forums if you wish.

Update July 19th, 2010

VMware released a KB article today that basically explains the issue but does not really offer a fix. It really looks like there will not be a fix and we will just be limited to 8 character passwords. VMware KB Article.

Pre-install requirements for upgrade to VMware vCenter 4.1 server

Posted by Brian on Jul 15, 2010 in VMware, vCenter Server, vSphere | View Comments

With this weeks release of vSphere 4.1 from VMware the operating system requirements have been raised to 64 bit. What this means is that all management consoles and related tools have moved or will be moving soon to 64 bit only systems. Most importantly is that vCenter server 4.1 is now dependent on a 64 bit OS to run. This means that before you rush to upgrade you will need to make sure if your running on a physical server that it is 64 bit capable. If not then you will require a new server or you could elect to move it to a 64 bit virtual machine.

Currently only the operating systems listed below are the only 64 bit options support by the new vCenter 4.1 server.

Something new with this release is the vCenter Server Data Migration Tool. This new tool will help to migrate some of your data and settings over to a new server depending on what your configuration was. There are some very rigid rules on what it will and wont move across. The list below is the only options that it will migrate. Judging from that list every production setup I’ve ever seen is going to require the usual manual steps to be done. Since I don’t think anyone out there is using SQL express as their DB in anything other than maybe a small lab environment. Your gonna need to configure 64 bit DSN’s for your vCenter and Update Manger Databases on the new server yourself.

You can use the vCenter Data Migration Tool to automatically migrate the following to a new server:

• vCenter Server Software and its configuration
• vCenter Update Manager Software and its configuration
• VMware Orchestrator Software and its configuration
• The default SQL Express 2005 database that comes installed with vCenter Server.

To see the full details from VMware on this process refer to this article.