Translate

Total Pageviews

My YouTube Channel

My YouTube Channel

Friday, 6 September 2013

Opening a console to a virtual machine fails with the error: Unable to connect to the MKS: Console access to the virtual machine cannot be granted since the connection limit of 0 has been reached (2015407)

Symptoms

When you open the console of a powered on virtual machine from vCenter Server or directly on the ESXi/ESX host, you see a black screen with a message at the top of the console screen similar to:

Unable to connect to the MKS: Console access to the virtual machine cannot be granted since the connection limit of 0 has been reached.

Cause

The issue occurs because the limit on the number of simultaneous console connections set in the vSphere Web Client impacts the vSphere client console connection limit.

Resolution

To resolve this issue, deselect Limit the number of simultaneous connections to this Virtual Machine on the affected virtual machine.
 
To deselect Limit the number of simultaneous connections to this Virtual Machine:  
  1. Open a session to the vSphere Web Client.

    https:// vcenter_server_name:9443/vsphere-client
  2. After connecting, right-click the affected virtual machine.
  3. Click Configuration > Edit Settings.   
  4. Click VM options.
  5. Click VMware Remote Console Options, then deselect Limit the number of simultaneous connections to this Virtual Machine.
  6. Click OK.
  7. Open a new console window to the virtual machine in the vSphere Client to verify.

To work around this issue, add an entry to the configuration parameters of the virtual machine.
 
To add an entry to the configuration parameters of the virtual machine:
  1. Power off the virtual machine.
  2. Right-click the affected virtual machine and click Edit Settings.  
  3. Click the Options tab, then click General under Advanced.
  4. Click Configuration Parameters.
  5. Look for an entry named RemoteDisplay.maxConnections:

    • If the entry exists, set the Value to 1 or higher.
    • If the entry does not exist, click Add Row to add the parameter. The parameter details are:

      Name: RemoteDisplay.maxConnectionsValue: 10
      Note: Value can be set to 1 or more.
  6. Power on the virtual machine.
Source:-
Posted by at No comments:

Thursday, 5 September 2013

VMware vSphere Storage Appliance licensing information (2002309)

Purpose

This article provides licensing information about VMware vSphere Storage Appliance (VSA).

Resolution

Assigning a VSA license to vCenter Server

To assign a VSA license to vCenter Server:
 
Note: Ensure that you have downloaded and installed VSA on the vCenter Server.
  1. Log into vSphere Client.
  2. Click Home.
  3. Under the Administration section, click the Licensing icon.
  4. Click Manage vSphere Licenses.
  5. Click Add License Keys.

    Note: After clicking Add License Keys, you can review the license keys that you have added, as well as capacity counts, expiration dates, and labels associated with the license keys.

  6. Click Next to assign the license keys.
  7. Assign the VSA license key to the vCenter Server.

Licensing Information

When licensing VSA, consider these points:
  • VSA is licensed on a per-instance basis. Each VSA instance supports up to 3 nodes.
  • At least two nodes need to be part of a VSA deployment.
  • VSA is supported by all vSphere 5 versions.
  • There are no upgrades in VSA.
  • VSA can run with Essentials plus or higher version of vSphere.
  • VSA must be purchased for the vCenter Server edition on which it will run. The editions are:
    • vCenter Essentials (sold only with Essentials Plus)
    • vCenter Foundation
    • vCenter Server
  • If you apply the old vCenter Server license key after installing VSA, the VSA disappears.
  • You must reapply the VSA key if you upgrade from vCenter Foundation to vCenter Standard. You have to contact the Licensing Support team to get a new VSA key compatible with the new vCenter Server edition. This exchange is at no charge.
  • The vRAM used for VSA factors into your vRAM entitlement.
  • VSA must be deployed on the same vCenter Server.
  • The VSA virtual machine counts as a protected virtual machine.

FAQs

How is VSA licensed?
 
VSA is sold per instance (similar to vCenter Server). Each instance supports up to three nodes.
 
How can I buy VSA?
 
VSA can be purchased as a standalone or with the vSphere Essentials Plus Storage bundle.
 
Is there an evaluation key for VSA?
Yes. VSA is part of the vSphere evaluation, which is valid for 60 days.
Can I buy more than one VSA?
 
Yes. You can buy more than one VSA. However, only one VSA instance is supported per vCenter Server.
 
What happens if I do not provide a license during VSA Manager installation?
 
If you do not provide a license during VSA Manager installation, the VSA is installed under evaluation.
 
How do I determine if the VSA license key I have is an evaluation key?
 
To check the license:
  1. Log in to the machine the vCenter Server is installed.
  2. Open a browser and open the link http://localhost/mob/?moid=LicenseManager.
  3. Enter the Username and Password for the vCenter Server when prompted.
  4. Under the Methods table, click DecodeLicense.
  5. Enter the license key and click Invoke Method.
Can I use VSA under evaluation with any edition of vCenter Server?
 
Yes. You can install VSA under evaluation with any edition of the vCenter Server. However, you cannot use a permanent license of VSA that is compatible with vCenter Server Essentials on a vCenter Server Standard. In this case, contact Licensing Support to get a new VSA key compatible with the vCenter Server edition.

Source:-
Posted by at No comments:

Troubleshooting a Windows XP guest warning about BusLogic SCSI drivers (1007122)

Symptoms

  • A Windows XP guest generates a warning about BusLogic SCSI drivers during power on
  • You receive this warning:

    Your guest operating system is Windows XP and you have one or more virtual SCSI devices installed in your virtual machine.

    Please be aware that Windows XP does not support the BusLogic SCSI adapter that VMware Fusion currently uses for its virtual SCSI devices. If you have not done so already, you will need to install our driver in the virtual machine. You can download the driver from our Web site at "http://www.vmware.com/info?id=43".

    Click OK to continue or Cancel to abort.

Resolution

When a virtual device is added to the virtual machine that requires the BusLogic SCSI controller drivers to be installed in the guest operating system, this message appears.
To resolve this issue, you must download and apply the VMware-supplied SCSI drivers.
  1. Download the SCSI driver floppy from http://download3.vmware.com/software/vmscsi-1.2.0.4.flp.

    Notes:

    • Do not try to open that link. Instead, right-click the link, and choose Save Link As or Download Linked File As.
    • When downloading in Google Chrome, the final extension may be doubled. Ensure that this fle is saved as vmscsi-1.2.0.4.flpand not vmscsi-1.2.0.4.flp.flp.
  2. Add a floppy drive to the virtual machine and mount the floppy image:

    • If you are using Fusion 4.x and above:

      1. Shut down the virtual machine.
      2. Go to Virtual Machine > Settings > Add Device.
      3. Choose Floppy Drive and click Add.

        A dialog appears asking you to choose a floppy image file.
      4. Browse to the location of the .flp file that you downloaded and select the file.
      5. Beside Enable Floppy Drive, change the switch to Off.
    • If you are using Fusion 3.x:

      1. Shut down the virtual machine.
      2. Go to Virtual Machine > Settings > Other Device.
      3. Click + and choose Add Floppy.

        A dialog appears asking you to choose a floppy image file.
      4. Browse to the location of the .flp file that you downloaded and select the file.
      5. De-select Connected.
    • If you are using Workstation:

      1. Shut down the virtual machine.
      2. Go to VM > Settings, then select Floppy.
      3. Select Use floppy image file and navigate to the downloaded .flp file.
      4. Select Connect at power on.
  3. If the virtual hard disk is set to use the SCSI option, you must supply the VMware SCSI drivers diskette image during installation of Windows XP, when prompted. 
In very specific circumstances, you may choose to proceed without installing the driver.
To suppress the warning message:
  1. Open the virtual machine settings file (.vmx) for editing. Fusion users, for more information, see Editing the .vmx file for your Fusion virtual machine (1014782).
  2. Add this line to the file:

    buslogic.noDriver = "FALSE"
  3. Save the file.
Source:-
Posted by at No comments:

Removing recent connections from the vSphere Client vSphere Client IP address/ Name dropdown (1032988)


Purpose

This article provides steps to remove recent connections from the vSphere Client IP address / Name dropdown, which is visible when logging in.

Resolution

To remove recent connections from the vSphere Client IP address / Name dropdown:
  1. Click Start > Run , type regedit, and click OK.
  2. You have two options:
    • Click Edit > Find, enter the IP address of the connection you want to remove from the dropdown menu.

      Or
    • Navigate to HKEY_CURRENT_USER\Software\VMware\VMware Infrastructure Client\Preferences, right-click RecentConnections, export it as a backup. Then right-click RecentConnections and choose Modify. Delete any appropriate entries, and click OK.

      Note: The sub-key HKEY_USERS\<subkey for profile actively loaded on machine>\Software\VMware\VMware Infrastructure Client\Preferences. reflects any changes you make toHKEY_CURRENT_USER\Software\VMware\VMware Infrastructure Client\Preferences.
Source:-
Posted by at No comments:

vSphere 5.5 Links

VMware What’s New Links

Documentation Links

Will update soon

Download Links

Will update soon

ESXi Links

General Links

HA & DRS

Installing & Upgrading

Latency Sensitive Apps

Licensing Links

Networking Links

NSX Links

Operations Management

Performance

Power Management

Scripting Links

PowerCLI 5.5 What’s New-Overview (VMware PowerCLI Blog)

SRM/vSphere Replication

Storage Links

vCenter Orchestrator

vCenter Server Links

vCenter Server Single Sign-On

vCloud Director

vCloud Hybrid Service

vFlash Links

vSAN Links

VSAN Part 1 - A first look at VSAN (Cormac Hogan)
VSAN Part 2 - What do you need to get started? (Cormac Hogan)
VSAN Part 3 - It is not a Virtual Storage Appliance (Cormac Hogan)
VSAN Part 4 – Understanding Objects and Components (Cormac Hogan)
VMworld 2013: What’s New in 5.5 – vSAN (Mike Laverick)
VSAN Observer (Punching Clouds)
vSphere 5.5: Using RVC VSAN Observer Pt1 (Punching Clouds)
vSphere 5.5: Using RVC VSAN Observer Pt2 (Punching Clouds)
VMware’s VSAN in the Home Lab (Sean Crookston)
vSphere 5.5 VSAN, Introducing Your New Storage Vendor VMware (vClouds)
VMware VSAN - Virtual SAN - How to configure (Virtual-blog)
Configure Disk Redundancy VMware VSAN - Virtual SAN (Virtual-blog)
How to quickly setup and test VMware VSAN (Virtual SAN) using Nested ESXi (Virtually Ghetto)
What’s New in VMware Virtual SAN (VSAN) (VMware Tech Paper)
vSphere 5.5 Improvements Part 4 - Virtual SAN (VSAN) (Wahl Network)
What’s New in vCloud Suite 5.5: Virtual SAN (VSAN) (WoodITWork)
Introduction to VMware vSphere Virtual SAN (Yellow Bricks)
Testing vSphere Virtual SAN in your virtual lab with vSphere 5.5 (Yellow Bricks)

vSphere Data Protection

Virtual Machine

vSphere Storage Appliance


Thanks to vSphere-Land
Posted by at No comments:

Sunday, 1 September 2013

Configuring SNMP Traps in ESXi/ESX (1008065)

Details

To generate virtual machine and environmental traps from ESXi/ESX 3.5, 4.x, and ESXi 5.x hosts, you must configure and enable the embedded SNMP agent. You cannot use the Net-SNMP-based agent to generate these traps, although it can receive GET transactions and generate other types of traps.

This represents a change in behavior from ESX 3.0.x, in which the configuration file for the Net-SNMP-based agent controlled the generation of virtual machine traps. For more information, see Configuring SNMP on an ESX 3.0.x host (1008186).

In ESXi 5.1, SNMP is configured using esxcli rather than vicfg-snmp. In addition, you have the option to configure SNMP v3 traps and informs as well as the SNMP v1 and v2c traps available with previous versions of ESXi.

For instructions on:

Solution

Use the vicfg-snmp.pl command from the Remote CLI or vSphere CLI to enable the SNMP agent and configure trap destinations. Each time you specify a target with the vicfg-snmp.pl command, the settings you specify overwrite all previously specified settings. To specify multiple targets, specify them in a single command, separated by commas.

To enable and configure SNMP traps:

Notes:
  1. Navigate to the directory where vicfg-snmp.pl is stored. By default, vicfg-snmp.pl is located in:

    C:\Program Files\VMware\VMware vSphere CLI\bin
  2. Run this command:

    vicfg-snmp.pl --server hostname --username username --password password --show

    Note: Run the vicfg-snmp.pl --help command for a full list of options.
  3. Specify the communities and trap targets with this command:

    vicfg-snmp.pl --server hostname --username username --password password -t hostname@port -c community

    Note: In ESX 3.5, you may need to use vicfg-snmp.pl --server hostname --username username --password password -t hostname@port/community.

    Example: To send SNMP traps from the host host.example.com to port 162 on target.example.com, using the public community, use this command:

    vicfg-snmp.pl --server host.example.com --username root --password password -t target.example.com@162 -c public

    For ESXi 5.0:

    vicfg-snmp.pl --server host.example.com --username root --password password -t target.example.com@162/community

    Note: To prevent clear text display of the user password, remove the --password password portion. You are then prompted to enter the password, and the entry is hidden.
  4. To enable the SNMP service, run this command:

    vicfg-snmp.pl --server hostname --username username --password password --enable

    Note: To verify SNMP settings, run this command:

    vicfg-snmp.pl --server hostname --username username --password password --show
  5. (Optional) To send a test trap to verify that the agent is configured correctly, run this command:

    vicfg-snmp.pl --server hostname --username username --password password --test

    The test trap generated is a warmStart trap.

    Note: Changes to the SNMP configuration are stored on the ESXi/ESX host in /etc/vmware/snmp.xml.
Source:-
Posted by at No comments:
Subscribe to: Posts (Atom)