Apr 16

How to expand a VMDK and extend a partition in Windows for VMware ESX

http://kb.vmware.com/kb/1007266 This video steps you through expanding a VMDK and extending a partition using DiskPart. Essentially, this allows for expanding the virtual disk for virtual machines in VMware ESX.
Check out Amazon’s selection of books on VMware: http://amzn.to/2pZInmt

Rating: 5/5


Oct 22

How to recreate a missing virtual machine disk descriptor file

http://kb.vmware.com/kb/1002511

This video demonstrates how to recreate a missing virtual machine disk descriptor .vmdk file.

Note: VMware recommends to attempt to restore the missing descriptor file from backups if possible. If this is not possible, proceed with recreating the virtual machine disk descriptor file.

To create a virtual machine disk descriptor file:

– Identify the size of the flat file in bytes.

– Create a new blank virtual disk that is the same size as the original. This serves as a baseline example that is modified in later steps.

– Rename the descriptor file (also referred to as a header file) of the newly-created disk to match the name of the original virtual disk.

– Modify the contents of the renamed descriptor file to reference the flat file.

– Remove the leftover temporary flat file of the newly-created disk, as it is not required.

This procedure will not work on virtual disks configured with a Para-virtualized SCSI controller in the virtual machine

For additional information, see VMware Knowledge Base article 1002511 at the following URL https://kb.vmware.com/kb/1002511

Rating: 5/5


Oct 14

Troubleshooting Virtual SAN on-disk format upgrade to 3.0 failures

Posted on October 13, 2016 by Ramesh B S

This video demonstrates how to troubleshoot Virtual SAN on-disk format upgrade to 3.0, which may fail in small Virtual SAN clusters or ROBO/stretched clusters.

Attempting an on-disk upgrade in certain VSAN configurations may result in failure. Configurations that can cause these errors include:

  • The stretched VSAN Cluster consists of two ESXi Hosts and the Witness Node (ROBO configuration)
  • Each Host in the Stretched Cluster contains a single VSAN Disk Group
  • A Virtual SAN cluster consists of three normal nodes, with one disk group per node
  • A Virtual SAN cluster is very full, preventing the “full data migration” disk-group decommission mode

To allow an upgrade to proceed in these configurations, a compromise as to availability must be made. Data accessibility will be maintained, but the redundant copy of the data will be lost and rebuilt during the upgrade process. As a result, data will be exposed to faults and failures such as the loss of a disk on another node may result in data loss. This exposure to additional failure risk is referred to as “reduced redundancy,” and must be manually specified in the Ruby vSphere Console (RVC) to allow the upgrade to proceed. It is not possible to specify reduced redundancy when using the vSphere Web Client to start the upgrade.

Caution: During upgrade, a single point of failure is exposed. Follow all VMware best practices, and your business practices, regarding the backup of important data and virtual machines.

https://kb.vmware.com/kb/2144944

This video demonstrates how to troubleshoot Virtual SAN on-disk format upgrade to 3.0, which may fail in small Virtual SAN clusters or ROBO/stretched clusters.

Attempting an on-disk upgrade in certain VSAN configurations may result in failure. Configurations that can cause these errors are:
– The stretched VSAN Cluster consists of two ESXi Hosts and the Witness Node also called ROBO configuration
– Each Host in the Stretched Cluster contains a single VSAN Disk Group
– A Virtual SAN cluster consists of three normal nodes, with one disk group per node
– A Virtual SAN cluster is very full, preventing the full data migration disk-group decommission mode

During this upgrade, a single point of failure is exposed. Follow all VMware best practices, and your business practices, regarding the backup of important data and virtual machines.

This exposure to additional failure risk is referred to as “reduced redundancy,” and must be manually specified in the Ruby vSphere Console or RVC to allow the upgrade to proceed.

Rating: 5/5


Jun 02

RUSH POST: Microsoft Convenience Update and VMware VMXNet3 Incompatibilities

Introduction

Posted on June 1, 2016 by Deji

Microsoft recently released a “Convenience Update” patch for Windows 7 and Windows Server 2008 R2 SP1. This update has incompatibility issues with virtual machines running on the VMware vSphere virtualization platform. This incompatibility is confined to one specific configuration scenario – It impacts VMs that use the VMware VMXNet3 virtual network adapter type.

Here is the incompatibility issue as described in Microsoft’s announcement of the Update:

Known issue 1 in this convenience rollup

Symptoms

A new Ethernet vNIC may be created with default settings in place of the previously existing vNIC, causing network issues. Any custom settings on the previous vNIC are still persisted in the registry but unused.

Resolution

To resolve this issue, uninstall the convenience rollup.

Status

Microsoft is investigating this issue to determine proper course of action with VMWare. To resolve this issue uninstall the convenience rollup. Further information will be posted here as the investigation continues.

Known issue 2

Symptoms

After you install this rollup, virtualized applications in Microsoft Application Virtualization (App-V) versions 4.5, 4.6, and 5.0 may have problems loading. When these problems occur, you may receive an error message that resembles the following:
Launching MyApp 100%

Note In this error message, MyApp represents the name of the App-V application.

Depending on the scenario, the virtualized app may freeze after it starts, or the app may not start at all.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows.

Resolution

To fix this known issue, configure the TermSrvReadyEvent registry entry on the computer on which the Microsoft Application Virtualization Client is installed.

For Microsoft Application Virtualization 5.0

Registry Key: HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Subsystem\ObjExclusions
Value name: 93 (or any unique value)
Type: REG_SZ
Data: TermSrvReadyEvent

Example
For example, type the following command at an elevated command prompt to add the entry to a system that is running Application Virtualization 5.0:
reg add HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Subsystem\ObjExclusions /v 93 /t REG_SZ /d TermSrvReadyEvent

For Microsoft Application Virtualization 4.6

For all supported x86-based systems

Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions
Value name: 95 (or any unique value)
Type: REG_SZ
Data: TermSrvReadyEvent

Example
For example, type the following command at an elevated command prompt to add the entry to an x86-based system that is running Application Virtualization 4.6:
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions /v 95 /t REG_SZ /d TermSrvReadyEvent
For all supported x64-based systems

Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions
Value name: 95 (or any unique value)
Type: REG_SZ
Data: TermSrvReadyEvent

Example
For example, type the following command at an elevated command prompt to add the entry to an x64-based system that is running Application Virtualization 4.6:
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions /v 95 /t REG_SZ /d TermSrvReadyEvent

Rating: 5/5


Mar 17

RVTools 3.7 is here!

RVTools 3.7 is here!

It has been a year since the last version. This weekend Rob de Vey finally released RVTools 3.7.
With over 400.000 downloads so far, this is for sure the most used free health check tool that exists. And there is a good reason for it, it is most definitely also one of the bests tools that can provide valuable insights.
RVTools is a windows .NET 2.0 application which uses the VI SDK to display information about your virtual machines and ESX hosts. RVTools is able to list information about VMs, CPU, Memory, Disks, Partitions, Network, Floppy drives, CD drives, Snapshots, VMware tools, Resource pools, Clusters, ESX hosts, HBAs, Nics, Switches, Ports, Distributed Switches, Distributed Ports, Service consoles, VM Kernels, Datastores, Multipath info and health checks. With RVTools you can disconnect the cd-rom or floppy drives from the virtual machines and RVTools is able to update the VMware Tools installed inside each virtual machine to the latest version.
Make sure to follow RVTools on twitter for any updates.
RVTools 3.7

This application interacting with VirtualCenter 2.5, ESX Server 3.5, ESX Server 3i, VirtualCenter 4.x, ESX Server 4.x, VirtualCenter 5.0, VirtualCenter Appliance, ESX Server 5.0, VirtualCenter 5.1, ESX Server 5.1, VirtualCenter 5.5, ESX Server 5.5.

Latest Version: 3.7 | March, 2015

Download:

Download | Documentation

• VI SDK reference changed from 5.0 to 5.5
• Extended the timeout value from 10 to 20 minutes for really big environments
• New field VM Folder on vCPU, vMemory, vDisk, vPartition, vNetwork, vFloppy, vCD, vSnapshot and vTools tabpages
• On vDisk tabpage new Storage IO Allocation Information
• On vHost tabpage new fields: service tag (serial #) and OEM specific string
• On vNic tabpage new field: Name of (distributed) virtual switch
• On vMultipath tabpage added multipath info for path 5, 6, 7 and 8
• On vHealth tabpage new health check: Multipath operational state
• On vHealth tabpage new health check: Virtual machine consolidation needed check
• On vInfo tabpage new fields: boot options, firmware and Scheduled Hardware Upgrade Info
• On statusbar last refresh date time stamp
• On vHealth tabpage: Search datastore errors are now visible as health messages
• You can now export the csv files separately from the command line interface (just like the xls export)
• You can now set a auto refresh data interval in the preferences dialog box
• All datetime columns are now formatted as yyyy/mm/dd hh:mm:ss
• The export dir / filenames now have a formated datetime stamp yyyy-mm-dd_hh:mm:ss
• Bug fix: on dvPort tabpage not all networks are displayed
• Overall improved debug information

Rating: 4/5


Mar 17

RVTools 3.6 works with VMware vSphere 6.0

RVTools 3.6 works with VMware vSphere 6.0

This little gem of a piece of freeware is very useful for the home virtualization lab enthusiast. Should you decide to use it, don’t forget to consider donating to Robware’s Rob Deveij.

The VMware API 6 hasn’t changed in a way that’d affect tools like the extremely handy and free RVTools. So it’s highly likely you’ll still be able to make good use of this tool as you prepare your home lab for vSphere 6:

• looking for orphaned VMDK files you no longer use
• cleaning up datastores
• saving off ALL your configuration details, such as networking

Especially helpful if you are considering doing a completely fresh vSphere 6.0 install, with the new vCSA appliance. You can very quickly see everything you have, sort the various views, and export it all to Excel or CSV.

Even after you’ve made the move to vSphere 6.0, there seems to be no issue with continuing to use the tool. This is good! Using the tool is pretty self evident, and I wouldn’t want to take away any of your fun in exploring the various tabs.

As was the case before, you can log in to either the:

• ESXi host
• vCenter server

In my case, I logged RVTools into the vCSA 6.0 appliance, in the very short install/configure video seen below.

Enjoy!

Rating: 4/5


May 26

Installing and configuring the NVIDIA VIB on ESXi (KB: 2033434)

Details

Before you can use the hardware-based (GPU) virtual Shared Graphics Acceleration (vSGA) feature in vSphere, you must install and configure the NVIDIA GPU VIB (vSphere Installation Bundle) on ESXi.

This feature is supported in Horizon View 5.2 and later releases.

Note: This vSphere 5.1 feature is not supported in Horizon View 5.1 or earlier.

Solution

Installing the NVIDIA GPU VIB

To install the NVIDIA GPU VIB:

  1. Download the VIB from the NVIDIA web site: 

    Note: The preceding link was correct as of December 30, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.

  2. Open a command prompt on the ESXi host and run the command:

    esxcli software vib install -v /path_to_vib/nvidia_vib

Alternatively, you can use ESXi Image Builder to create a bootable image that contains the NVIDIA VIB. For more information, see the vSphere Installation and Setup Guide in the VMware vSphere 5.1 Documentation Center.

Starting the xorg Service

Before you start any virtual machines, make sure that the xorg service is running.

To verify that the xorg service is running using the vSphere Client:

  1. Connect to the ESXi host.
  2. On the Configuration tab under Software, click Security Profile.
  3. Click the Properties link for Services.
  4. Ensure that xorg is Running and has the startup policy you prefer. If xorg is Stopped:
    1. Select xorg and click Options.
    2. Click Start.
    3. Select the Startup Policy and click OK.

Note: To verify that the xorg service is running using the vSphere Web Client:

  1. Connect to vCenter Server.
  2. From the inventory, select the ESXi host.
  3. On the Manage tab under System, click Security Profile.
  4. Click the Edit button for Services.
  5. Ensure that xorg is Running and has your desired startup policy. If xorg is Stopped:
    1. Select xorg and click Start.
    2. Select the Startup Policy and click OK.

To verify that the xorg service is running using the command line:

  • From a command prompt on the ESXi host, run the command:

    /etc/init.d/xorg start

Configuring virtual machine video card 3D capabilities

To configure virtual machine video card 3D capabilities using the vSphere Client:

  1. Connect to the ESXi host.
  2. Select the virtual machine.
  3. On the Summary tab under Commands, click Edit Settings.
  4. Under Hardware, click Video card.
  5. Under Displays and video memory, set the video card 3D capabilities:
    1. Set the Total video memory to a value from 64 MB to 512 MB.

      Most applications should work with 128 MB. Video memory values larger than 128 MB are available only with virtual machines with hardware version 9.

    2. Under 3D graphics, select Enable 3D Support.
    3. Click OK.

Note: You cannot set the 3D renderer from the vSphere Client. Enabling 3D support is sufficient to use the hardware-based (GPU) virtual Shared Graphics Acceleration (vSGA) feature in vSphere. To set the 3D renderer, use the vSphere Web Client to configure video card 3D capabilities.

To set the 3D renderer from the vSphere Web Client:

  1. Connect to vCenter Server.
  2. Select the virtual machine:
    1. Click a data center, folder, cluster, resource pool, or host.
    2. Click the Related Objects tab, then click Virtual Machines.

  3. On the Manage tab, click Settings.
  4. Click VM Hardware.
  5. Click Edit.
  6. Expand the Video card setting.
  7. Set the Total video memory to a value from 64 MB to 512 MB.

    Most applications should work with 128 MB. Video memory values larger than 128 MB are available only with virtual machines with hardware version 9.

  8. For 3D Graphics, select Enable 3D Support.
  9. For 3D Renderer, select Hardware or Automatic.
  10. Click OK.

To configure virtual machine video card 3D capabilities from View Administrator:

Note: Hardware-based 3D rendering can be configured from View Administrator in Horizon View 5.2 and later releases.

  1. Connect to VMware View Administrator.
  2. Add or edit a desktop pool. For more information, see the VMware Horizon View Administration guide.
  3. On the Pool Settings page (or tab), set the 3D Renderer to Automatic or Hardware.
  4. Complete the Add Pool wizard or click OK in the Edit Pool dialog.

Note: If you use the Manage using vSphere Client option in View Administrator, you can configure 3D rendering from the vSphere Web Client on a per-virtual machine basis. If Manage using vSphere Client is not selected in View Administrator, the 3D rendering settings you make in View Administrator apply to the entire pool and overwrite any 3D rendering settings you make in the vSphere Web Client.

Uninstalling and updating the NVIDIA GPU VIB

To update the NVIDIA GPU VIB, you must uninstall the currently installed VIB and install the new VIB.

To uninstall the currently installed VIB:

  1. Stop all virtual machines using 3D acceleration.
  2. Place the ESXi host into Maintenance mode.
  3. Open a command prompt on the ESXi host.
  4. Stop the xorg service by running the command:

    /etc/init.d/xorg stop

  5. Remove the NVIDIA VMkernel driver by running the command:

    vmkload_mod -u nvidia

  6. Remove the VIB by running the command:

    esxcli software vib remove -n NVIDIA-VMware

    You can now install a newer NVIDIA GPU VIB by following the steps provided earlier in this article.


May 25

Uploading diagnostic information for VMware through the Secure FTP portal (KB: 2069559)

Purpose

To address a Support Request, VMware technical support requests diagnostic information from the VMware products.
 
This article provides procedures to upload diagnostic information to VMware using the Secure FTP (sftpsite.vmware.com) portal.
 
Note: To upload diagnostic information using FTP, see Uploading diagnostic information for VMware using FTP (2070100).

Resolution

Rating: 5/5

Uploading diagnostic information to VMware using the Secure FTP portal includes these methods:
Notes:
  • Internet Explorer 9 and above is supported.
  • Other supported browsers include Firefox, Chrome, and Safari.
  • When uploading with Internet Explorer 10/11, you may have to switch to compatibility mode.

  • Do not use the HTML interface to upload files larger than 2 GB.

  • Directory listing of file uploaded is disabled due to security reasons.
  • Files are not visible after the upload completes.

Uploading files to the Secure FTP portal using HTML Interface

To upload files via the sftpsite.vmware.com portal using your web browser:
  1. Go to https://sftpsite.vmware.com/.
  2. Enter this information:

    Username: inbound
    Password: inbound

    Note: Use AD account username and password to log in within the VMware network. inbound only works externally and not on VMware network.

  3. Select the HTML option.
  4. Click Login.

    Note: You can see that the directory listing is disabled for security purposes.

  5. Click New Directory.
  6. Enter your Support Request number in the field and click OK. If you receive an error that the file already exists, proceed to the next step.

    Note: The directory name must be the 11-digit SR number. If you enter an incorrect SR number, you see the error:

    Invalid Directory Name.Directory must be 11 Digit SR Number

  7. Click Change Directory.
  8. Click Add.
  9. Select the files you want to upload to VMware Support.
  10. Click Open.

    Note: The files that are uploaded must be less than2 GB.

  11. Click Upload.

    You are notified when the upload completes.

  12. Notify the Technical Support Engineer that the logs have been uploaded:

    1. Send an email to webform@vmware.com.
    2. Ensure that the subject line contains:

      VMware Support Request SR# YOUR_SUPPORT_REQUEST_NUMBER

Click here to open an email with the necessary fields populated. Replace YOUR_SUPPORT_REQUEST_NUMBERin the subject line with your Support Request number. Alternatively, you can update the support request through My VMware with a note indicating you have uploaded files via sftpsite.vmware.com.  

Uploading files to the Secure FTP portal using Java Applet Interface

You can use the Secure FTP portal Java Applet to upload files using your web browser. The Java Applet allows you to transfer files greater than 2 GB.
 
Note: To be able to access the Java Applet interface, you must use Java 1.7 or later.

To upload files using the Java Applet:

  1. Browse to the http://sftpsite.vmware.com/ or https://sftpsite.vmware.com/ URL.
  2. In the Login page, select the Java Applet user interface option.
  3. Enter this information:

    Username: inbound
    Password: inbound

  4. Right-click the Remote System pane and click mkdir. Skip this step if the SR directory already exists.
  5. Enter your SR number as the directory name.

    Notes:

    • Ensure to enter a valid 11 digit SR number as the directory name.
    • Ensure that the directory name does not contain any special characters, such as space, “, “ , # , or $.

  6. In the Remote pane, enter the SR directory name you created.
  7. In the Local System pane, browse to the location of files that are to be uploaded.
  8. Select the file(s) to be uploaded.
  9. Right-click the files to be uploaded and click Upload.

    You are notified when the upload completes.

Uploading files to the Secure FTP portal from a Linux operating system

You can upload files directly to the sftpsite.vmware.com site from a Linux operating system, provided you have the firewall rules open to allow access directly from virtual machines to the Secure FTP site.

Notes:

  • You can use this method to upload files greater than 2 GB.
  • Ensure that you have your Support Request number. This number is provided to you when a Support Request is created.
  • After uploading the diagnostic data, you cannot see the file listing on the server because the directory listing is disabled for security reasons.

To upload files to the sftpsite.vmware.com portal from the command line:

  1. Launch the terminal session from the virtual machine.
  2. Change directory to the location where you have the files to be uploaded.
  3. Enter this command:

    sftp inbound@sftpsite.vmware.com

    After you are connected to sftpsite.vmware.com, you see the message:

    VMware Secure FTP Server :- Directory Name must be 11 Digit SR Number

  4. Enter the password ( inbound) to log in.
  5. To upload files for a new SR, create the SR directory using the mkdir command (if the SR directory does not exist already):

    mkdir SR#

    For example:

    mkdir 12345678901

  6. Change to the SR directory using this command:

    cd SR#

    For example:

    cd 12345678901

  7. Enter this command to upload the file:

    put file_name

    Note: To upload multiple files, you can use the mput command.

Uploading files to the Secure FTP portal using third-party clients

You can use third-party clients, such as FileZila, to upload files to the SFTP clients.

To upload files to the sftpsite.vmware.com portal using FileZilla:

  1. Open the FileZilla client.
  2. Click Transfer > Transfer type > Binary to set the transfer mode to binary.
  3. Click File > Site Manager.
  4. Add the VMware FTP site to My Sites using the Site Manager. The credentials are:

    Address – sftpsite.vmware.com
    Port – 22
    Protocol – SFTP – SSH File Transfer Protocol
    Logon Type – normal
    User – inbound
    Password – inbound

  5. Click Connect.
  6. Right-click the Remote Site pane and click Create Directory. Skip this step if the SR directory already exists.
  7. Change directory to newly created SR directory.
  8. After connecting to the correct destination directory, browse to the location of the log files on your local system using the file browser in the left pane or enter the full path in the Local site field.
  9. Right-click the file and click Upload.
  10. Monitor the transfer progress in the Queued files pane.

See Also


May 25

Uploading diagnostic information for VMware using FTP (KB: 2070100)

Purpose

To address a Support Request, VMware technical support requests diagnostic information from the VMware products. This article provides procedures to upload diagnostic information to VMware using FTP.
 
Note: To upload diagnostic information using the Secure FTP portal, see Uploading diagnostic information for VMware through the Secure FTP portal (2069559)

Resolution

Rating: 5/5

Uploading diagnostic information to VMware using FTP includes these methods:

Notes:

  • If there are several log files, VMware recommends that you create a single ZIP, TAR or TGZ file and upload that. The single file makes the process more efficient.
  • If your files are larger than 2 GB, you must upload using the command line.

Uploading via the FTP portal using your web browser

  1. Go to https://ftpsite.vmware.com/.
  2. Enter this information:

    Username: inbound
    Password: inbound

  3. Ensure that HTML is selected.
  4. Click Login.
  5. Click New Directory.
  6. Enter your Support Request number in the field and click OK. If you receive an error that the file already exists, proceed to the next step.

    Notes:

    • Ensure to enter a valid 11 digit SR number as the directory name.
    • Ensure that the directory name does not contain any special characters, such as space, “, “ , # , or $.

  7. Click Change Directory, enter your Support Request number in the field, then click OK.
  8. Click Add, select the files you would like to upload to VMware Support, then click Open.

    Repeat this step for any additional files.

    Note: Files must be smaller than 2 GB.

  9. Click Upload.

    You are notified when the upload completes.

  10. Notify the Technical Support Engineer that the logs have been uploaded:

    1. Send an email to webform@vmware.com
    2. Ensure that the subject line contains:

      VMware Support Request SR# YOUR_SUPPORT_REQUEST_NUMBER

    Click here to open an email with the necessary fields populated. Replace YOUR_SUPPORT_REQUEST_NUMBER in the subject line with your Support Request number.

    Or you can update the support request through My VMware with a note indicating you have uploaded files via FTP.

Note: When uploading with Internet Explorer 10/11, you may have to switch to compatibility mode.


Uploading via the FTP portal using the command line

Notes:

  • Ensure that you have your Support Request number. This number is provided to you when a Support Request is created.
  • After uploading the diagnostic data, you cannot see the file listing on the server because directory listing is disabled for security reasons.
  1. Open a terminal window to a command line shell:

    • For Windows, click Start > Run, type cmd and press Enter.
    • For Mac OS, click Applications > Utilities > Terminal.
    • For Linux, from your X session run the /usr/bin/xterm command, or open your preferred terminal emulation application.

  2. From the command line shell, run the command:

    ftp ftpsite.vmware.com

  3. Enter this username and password when prompted:

    Username: inbound
    Password: inbound

    Note: The password is not echoed on the screen. Authenticating using this username and password allows you to put files on the site. You cannot delete, move, rename, or modify any files, including the files you upload.

  4. Enable the correct mode for the transfers:

    • If you are using Mac OS, type epsv to disable extended passive mode.
    • If you are using Windows, type quote pasv to toggle between active and passive mode. In Windows, passive mode is required.
    • If your FTP client defaults to ASCII transfer mode, type bin to enable binary transfers to preserve the integrity of the files.

      Note: If you want to monitor the progress of the transfer, type hash at the command prompt prior to initiating the transfer. In Windows, the output looks similar to:

      ftp> hash
      Hash mark printing On ftp: (2048 bytes/hash mark).

  5. Create a remote directory on the FTP site for uploading your diagnostic information files. Run the command:

    mkdir YOUR_SUPPORT_REQUEST_NUMBER

    Caution:

    • When making this directory, use only the Support Request number. Do not preface the number with anything. For example, do not use SR########## , as the SR prefix affects the tools used by support to access these files once uploaded. For example, use – mkdir 12345678910
    • If the directory was previously created, mkdir will report errors. Simply continue on to the next step.

  6. Change your working directory to the remote directory that you created by running this command:

    cd YOUR_SUPPORT_REQUEST_NUMBER

  7. Change the local directory to the folder that contains the files you wish to upload. If the full path is not specified, the path used defaults to the path from where you executed ftp . Run:

    lcd FULL_LOCAL_PATH

    Notes:

    • In Windows, this step is optional. The full path can be specified in the next step, at the time of the file transfer. If your path includes spaces, be sure to enclose the entire path within quotation marks.
    • In Mac OS and Linux, you must use the lcd command to navigate to the directory on your system where the file is saved. If your path includes spaces, be sure to escape each space with a backslash before it. Alternatively, you can simply drag the file into the terminal window and erase the file name while keeping the directory path.

  8. To upload a file from the local directory to the remote directory, run:

    put YOUR_LOG_FILE_NAME

    where YOUR_LOG_FILE_NAME is the name of the file you are uploading.

    Notes:

    • You can also use mput * to upload all log files from the current local directory.
    • If you are using Windows, you may include the file path with the file name. If your path includes spaces, ensure you enclose the entire path within quotation marks. Alternatively, you can simply drag the file into the terminal window.
    • If you are using Mac OS or Linux, and your path includes spaces, be sure to escape each space with a backslash before it or enclose the entire path within quotation marks. Alternatively, you can drag the file into the terminal window.

  9. To close the FTP session, type bye and press Enter.
  10. Notify the technical support engineer that the logs have been uploaded. To do this, send an email to webform@vmware.com and ensure that the subject line contains:

    VMware Support Request SR# YOUR_SUPPORT_REQUEST_NUMBER

    Or you can update the support request through My VMware with a note indicating you have uploaded files via FTP.

Additional Information

There are many third-party GUI-based FTP clients that run on multiple platforms. These clients are able to perform the operations in this article using an intuitive GUI interface. Feel free to use the FTP client of your choice.

Some platforms also have integrated FTP capabilities. For example, Microsoft Windows allows FTP through Windows Explorer. Using ftp://inbound:inbound@ftpsite.vmware.com/ as the address will open the FTP site as if it were a local Windows folder.

FileZilla is a popular third party FTP client.

To upload log files to the VMware FTP using FileZilla:

  1. Open the FileZilla client.
  2. Set the transfer mode to binary:

    Go to the Transfer menu > Transfer type > Binary

  3. Go to the File menu > Site Manager.
  4. Add the VMware FTP site to My Sites using the Site Manager. The credentials are:

    Address = ftpsite.vmware.com
    Logon Type = normal
    User = inbound
    Password = inbound

  5. Click Connect.
  6. Change to the correct destination directory for your Support Request:
    1. If this is the first time you are uploading files to the VMware FTP for this case, create a directory in the root of the VMware FTP. To do this, right click the root directory on the remote site in the right pane and choose Create directory.
    2. If this is not the first time you are uploading files for this case, proceed to the step 7.

  7. Change to your SR directory using the Remote site field.
    For example:

    Remote site: /12345678901

    Notes:

    • For security reasons, you do not see any files or directories on the VMware FTP server, including files you have uploaded.
    • The destination directory should contain numbers only. Do not enter letters or other characters.


  8. Once you connect to the correct destination directory, browse to the location of the log files on your local system using the file browser in the left pane or enter the full path in the Local site field.
  9. Right click the file and select Upload to start the transfer.
  10. Monitor the transfer progress in the Queued files pane.
For further guidance, see the FileZilla screen shots in the 1008525_FZ_screenshots.zip file attached to this article.

See Also


May 25

Location of vCenter Server log files (KB: 1021804)

Purpose

This article provides the default location of the vCenter Server logs.

Resolution

The vCenter Server logs are placed in a different directory on disk depending on vCenter Server version and the deployed platform:

  • vCenter Server 5.x and earlier versions on Windows XP, 2000, 2003: %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\Logs\
  • vCenter Server 5.x and earlier versions on Windows Vista, 7, 2008: C:\ProgramData\VMware\VMware VirtualCenter\Logs\
  • vCenter Server 5.x Linux Virtual Appliance: /var/log/vmware/vpx/ 
  • vCenter Server 5.x Linux Virtual Appliance UI: /var/log/vmware/vami
     

    Note: If the service is running under a specific user, the logs may be located in the profile directory of that user instead of %ALLUSERSPROFILE%.

vCenter Server logs are grouped by component and purpose:

  • vpxd.log: The main vCenter Server logs, consisting of all vSphere Client and WebServices connections, internal tasks and events, and communication with the vCenter Server Agent (vpxa) on managed ESX/ESXi hosts.
  • vpxd-profiler.log, profiler.log and scoreboard.log: Profiled metrics for operations performed in vCenter Server. Used by the VPX Operational Dashboard (VOD) accessible at https://VCHostnameOrIPAddress/vod/index.html.
  • vpxd-alert.log: Non-fatal information logged about the vpxd process.
  • cim-diag.log and vws.log: Common Information Model monitoring information, including communication between vCenter Server and managed hosts’ CIM interface.
  • drmdump\: Actions proposed and taken by VMware Distributed Resource Scheduler (DRS), grouped by the DRS-enabled cluster managed by vCenter Server. These logs are compressed.
  • ls.log: Health reports for the Licensing Services extension, connectivity logs to vCenter Server.
  • vimtool.log: Dump of string used during the installation of vCenter Server with hashed information for DNS, username and output for JDBC creation.
  • stats.log: Provides information about the historical performance data collection from the ESXi/ESX hosts
  • sms.log: Health reports for the Storage Monitoring Service extension, connectivity logs to vCenter Server, the vCenter Server database and the xDB for vCenter Inventory Service.
  • eam.log: Health reports for the ESX Agent Monitor extension, connectivity logs to vCenter Server.
  • catalina.<date>.log and localhost.<date>.log: Connectivity information and status of the VMware Webmanagement Services. 
  • jointool.log: Health status of the VMwareVCMSDS service and individual ADAM database objects, internal tasks and events, and replication logs between linked-mode vCenter Servers.
  • Additional log files:
    • manager.<date>.log
    • host-manager.<date>.log
Note: As each log grows, it is rotated over a series of numbered component-nnn.log files. On some platforms, the rotated logs are compressed.

vCenter Server logs can be viewed from:

  • The vSphere Client connected to vCenter Server 4.0 and higher – Click Home > Administration > System Logs.
  • The Virtual Infrastructure Client connected to VirtualCenter Server 2.5 – Click Administration > System Logs.
  • From the vSphere 5.1 and 5.5 Web Client – Click Home > Log Browser, then from the Log Browser, click Select object now, choose an ESXi host or vCenter Server object, and click OK.