Category Archives: Virtualization

VMWARE SDDC Cloud Foundation 2.2.1 Initial configuration of Cloud Foundation fails at rack discovery

Rack discovery fails with the error message “Rack discovery get progress failed.Contact support for
more details.Refresh your browser once it is resolved.” The cause is a time difference between your
TORs and the SDDC Manager.
Workaround: Synchronize the clocks on the TORs switches to match the time on the SDDC Manager
Controller VM.
1. Using SSH, log it the SDDC Manager Controller VM as root.
2. Get the time:
root@sddc-manager-controller [ ~ ]# date
Wed Nov 22 06:42:43 UTC 2017
3. Log into both TOR switches as admin and verify that there is difference between the time setting
in the TOR and SDDC Manager Controller VM.
Tue Nov 21 18:43:07 2017
Timezone: UTC
Clock source: local

Continue reading →

vSphere Replication 6.1.2 plugin fails to load in vSphere Web Client (2149560)

Resolution

This is a known issue affecting vSphere Replication 6.1.2.
This issue is resolved in vSphere Replication 6.1.2.1, available at VMware Downloads.

Workaround

To work around this issue, you have two options:

Option 1: Grant Web Access.

Allow access to www.springframework.org from the impacted vCenter Server.
Option 2: Replacing the webclient plugin to remove the dependency on www.springframework.org.
There are two sets of instructions below, one for an SSO standalone domain (Option 2a) and one for Enhanced Linked Mode (Option 2b) environments.

Note: Steps in the procedures below will permanently delete webclient setup files using rm -rf commands, so caution is advised. However, the files are rebuilt when the Web Client services are restarted.

Option 2a: When the vCenter Server is using a standalone SSO Domain, download the 2149560_SSO_ngcplugin-60.zip file attached to this Knowledge Base article and rename it to ngcplugin-60.zip.
  1. Replace the existing ngcplugin-60.zip file with the downloaded plugin file to the following directory in the HMS appliance:
    /opt/vmware/share/htdocs/client/
  2. Remove the com.vmware.vcHms-6.1.2.605082273 downloaded plugin folder or any other vcHMS file:

    Note: Remove any file prefixed with com.vmware.vcHms from this location.

    vCenter Server Appliance – /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcHms-6.1.2.605082273

    To remove the old com.vmware.vcHms-6.1.2.605082273 plugin folder in the vCenter Sever Appliance:

    1. Run this command to view the list of folders in the /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity location:

      bpvappvc1 # cd /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity
      bpvappvc1:/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity # ls -l

      You see the output:

      total 8
      drwx—— 3 vsphere-client users 4096 Mar 2 10:49 com.vmware.vcDr-6.1.0.11034
      drwx—— 3 vsphere-client users 4096 Mar 3 15:13 com.vmware.vcHms-6.1.2.605082273

    2. Run this command to remove the downloaded com.vmware.vcHms-6.1.2.605082273 plugin folder or any other files:

      bpvappvc1:/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity #rm -rf com.vmware.vcHms-6.1.2.605082273

    3. Verify that the com.vmware.vcHms-6.1.2.605082273 folder is removed
      In VCSA, run this command:

      bpvappvc1:/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity # ls -l

      You see the output similar to:

      total 7
      drwx—— 3 vsphere-client users 4096 Mar 2 10:49 com.vmware.vcDr-6.1.0.11034

      In a Windows vCenter Server, the default plugin location is:
      C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity\com.vmware.vcHms 6.1.2.605082273

  3. Stop the webclient service by running this command:

    vCenter Server Appliance: service-control –-stop vsphere-client

    Windows vCenter Server: service-control –stop vspherewebclientsvc

  4. Note: Ensure that you run the #rm -rf or del *.* command only in the specified folder. If you run this command in the other folder, it may delete the content of that folder as well. Also, ensure you take a snapshot of the vCenter Server and a Full backup of the Current state preserved before you proceed further.
Clean the tomcat cache by removing all files and folders by running this command:

rm -rf /usr/lib/vmware-vsphere-client/server/work/*

Windows vCenter Server: C:\Program Files\VMware\vCenter Server\WebClient\server\work

Open Command prompt for the C:\Program Files\VMware\vCenter Server\WebClient\server\work location

Run the del *.* command.
  1. Clear the serenity database by running this command:

    /storage/vsphere-client/SerenityDB/serenity# rm -rf *

    • Windows vCenter Server: C:\programdata\vmware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity
    • Open Command prompt and navigate to the directory: C:\programdata\vmware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity

Run the del *.* command.

  • Remove/rename the old hmsJARs in /usr/lib/vmware-virgo/server/pickup/.

    Files to be removed/renamed:

    hms-vmodl-6.1.2.5082273.jar
    topology-service-6.1.2.5082273.jar
    vr-service-6.1.2.5082273.jar
    vr-ui-war-6.1.2.5082273.war

    Command for VCSA: mv [hmsJARs] [hmsJARs.bak]

    Windows vCenter Server file location: C:\Program Files\VMware\vCenter Server\virgo\server\pickup\

  • Remove/clear the contents of the cmCatalog directory:

    In VCSA: /etc/vmware/vsphere-client/cmCatalog
    Windows vCenter: C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\cmCatalog

  • Start the vSphere Client service by running this command (VCSA):

    service-control –-start vsphere-client

    Windows vCenter Server: service-control –start vspherewebclientsvc

Option 2b: When the vCenter Server is using a EnhancedLinkedMode configuration</u>, download the

2149560_LinkedMode_ngcplugin-60.zip file attached to this Knowledge Base article and rename it to ngcplugin-60.zip. Run all steps for Group 1-3:

Group 1
  1. Open an ssh session to the vSphere Replication appliance, see Connecting to VMware vSphere Replication 6.0.x Appliance (2112307).
  2. Replace the existing ngcplugin-60.zip file with the downloaded plugin file to the following directory in ALL HMS appliance:
    /opt/vmware/share/htdocs/client/
Group 2

In all the linked vCenter Servers, run these steps:

  1. Remove the com.vmware.vcHms-6.1.2.605082273 downloaded plugin folder or any other files:
    Note: Remove any file prefixed with com.vmware.vcHms from this location.
    vCenter Server Appliance – /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcHms-6.1.2.605082273
    To remove the downloaded com.vmware.vcHms-6.1.2.605082273 plugin folder in the vCenter Sever Appliance:

    1. Run this command to view the list of folders in the /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity location:

      bpvappvc1:/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity # ls -l

      You see the output:

      total 8
      drwx—— 3 vsphere-client users 4096 Mar 2 10:49 com.vmware.vcDr-6.1.0.11034
      drwx—— 3 vsphere-client users 4096 Mar 3 15:13 com.vmware.vcHms-6.1.2.605082273

    2. Run this command to remove the downloaded com.vmware.vcHms-6.1.2.605082273 plugin folder or any other files:

      bpvappvc1:/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity #rm -rf com.vmware.vcHms-6.1.2.605082273

    3. Verify that the com.vmware.vcHms-6.1.2.605082273 folder is removed by running this command:

      bpvappvc1:/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity # ls -l

      You see the output similar to:
      total 7
      drwx—— 3 vsphere-client users 4096 Mar 2 10:49 com.vmware.vcDr-6.1.0.11034
      Windows vCenter Server – C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity\com.vmware.vcHms 6.1.2.605082273

  2. Stop the service by running this command:
    VCSA: service-control –-stop vsphere-client
    Windows vCenter Server: service-control –stop vspherewebclientsvc
  3. Clean the tomcat cache by removing all files and folders.
    In VCSA, run this command:
    /usr/lib/vmware-vsphere-client/server/work# rm -rf *

    In a Windows vCenter Server, the path is:
    C:\Program Files\VMware\vCenter Server\WebClient\server\work

    Open Command prompt for the C:\Program Files\VMware\vCenter Server\WebClient\server\work location and run the del *.* command.

    Note: Ensure that you run the #rm -rf or del *.* command only in the specified folder. If you run this command in the other folder, it may delete the content of that folder as well.

  4. Clear the serenity database:
    • In VCSA, run this command:
      /storage/vsphere-client/SerenityDB/serenity# rm -rf *
    • Windows vCenter Server path is:
      C:\programdata\vmware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity

      Open Command prompt and navigate to the directory: C:\programdata\vmware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity

      Run the del *.* command.

  5. Remove/rename the old hmsJARs in /usr/lib/vmware-virgo/server/pickup/.
    Files to be removed/renamed:

    hms-vmodl-6.1.2.5082273.jar
    topology-service-6.1.2.5082273.jar
    vr-service-6.1.2.5082273.jar
    vr-ui-war-6.1.2.5082273.war

    Command example for VCSA: mv [hmsJARs] [hmsJARs.bak]
    Windows vCenter Server file location: C:\Program Files\VMware\vCenter Server\virgo\server\pickup\

  6. Remove/clear the contents of the cmCatalog directory:
    In VCSA: /etc/vmware/vsphere-client/cmCatalog
    In Windows vCenter: C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\cmCatalog



Group 3

In all Linked vCenter Servers, start the vSphere Client service.
In VCSA, run this command:
service-control –-start vsphere-client

In a Windows vCenter Server, run this command:
service-control –start vspherewebclientsvc

Continue reading →

How to Install vSphere vCenter Appliance 6.5 U1 with external Platform Service Controller

 

We will be installing vSphere 6.5 U1 with external PSC’s and vCenter Server Appliance .

Installation flow is as below

  • Create DNS entries.
  • Deploy PSC 1 with a new SSO domain.
  • Deploy PSC 2 and join to existing SSO domain created in previous step.
  • Deploy Vcenter and woth the SSO domain created in previous steps.

Below are the screenshots with possible errors and resolution .

  • Run the installer. Machine generated alternative text: Home * Quick access Downloads Scanplus Storage VMware ANUJ DELL Build Docs Desktop - Documents Downloads Share View vcsa UI installer win32 Type File folder File folder PAK File PAK File PAK File Application extens... Application extens... DAT File Application Application extens... Application extens... File HTML Document BIN File Application extens... BIN File PAK File File PAK File Application extens... Size 25 KB 1 KB 9,882 KB 3,386 KB 1,849 KB 9,894 KB 55,542 KB 94 KB 1,893 KB 2 KB 1,702 KB 335 KB 14,693 KB 795 KB 85 KB 1 KB 59 KB 80 KB ANUJ DELL DVD Drive CDROM Name locales resources Date modified 7/8/2017 1:50 AM 7/8/2017 1:50 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM 5/27/2017 4:48 AM blink image_resources 200_percent.pak content resources 200_percent.pak content shell.pak d3dcompiler 47.dll ffmpeg.dll icudtl.dat installer libEGL.dll libGLESv2.dll LICENSE LICENSES.chromium natives blob.bin node.dll snapshot blob.bin ui resources 200_percent.pak version views resources 200_percent.pak xinputl 3.dll Global Projects Music Pictures Videos osc:) DVD Drive CDR Network

 

Continue reading →

Virtual Machine shows up in both Standard Port Group and DVPort Group after migration to DVPort Group.

Virtual Machine shows up in both Standard Port Group and DVPort Group after migration to DVPort Group.

After migration from a standard port group to a dvportgroup virtual machine shows up on both Standard Switch as well as Distributed Switch in Vsphere Webclient and Vsphere client .

To resolved this make sure that all the snapshots of this vm are deleted as a previous snapshot can have a reference to the standard switch port group.

 

Storage vMotion Stuck at 32% when migrating from One Vplex to Other

Storage vMotion Stuck at 32% when migrating from One Vplex to Other

Recently I faced an issue where we were able to Storage vMotion from VPLEX to VMAX but not from VPLEX 1 to VPLEX 2. After some troubleshooting we found out that it was the VAAI that was giving issues and had to disable below parameters for the datamover.

DataMover.HardwareAcceleratedMove
DataMover.HardwareAcceleratedInit

The reason for this was VAAI incompatibility  of the source VPLEX .  Both the above can be disabled by selecting the host –>Configuration –> Advanced Settings (Software)> DataMover. Change both parameters to 0 to disable.

Below is the excerpt from VMware KB about VAAI

Continue reading →

vCenter Backend SQL Host Rename Process

I recently faced a situation where customer requested to change the hostname of backend SQL DB Virtual Machine . I followed the below procedure

  • Take the Backup of vCenter Database
  • Shutdown vCenter Services
  • Shutdown SQL Services on SQL Server.
  • Rename the SQL Server Hostname to desired hostname.
  • Restart SQL Server.
  • Validate the SQL services are up and running after the restart.
  • Connect to SQL Management Studio to validate the connection to DB.
  • On the vCenter Server open ODBC Connections and reconfigure the current odbc connection to point to new hostname.
  • Then edit SQL Server Hostname in the vcdb.properties file which is located at:
    • For vCenter Server 5.5 and earlier:
      • Windows 2008 – C:\ProgramData\VMware\VMware VirtualCenter
      • Other Windows versions – C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\

    • For vCenter Server 6.0:
      • C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx
  • Start the vCenter Services and you are ready to ROCK N ROLL 🙂

More information can be found on the below VMware KB

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=7960893

ESXi Hosts showing as unlicensed in Nexus 1000 despite of licenses being available.

Cause

This issue can occur when the Nexus 1000V VSM recognizes a host/VEM module as a new module and not an existing one. The VSM assigns the host a new module ID number.

In this situation, the VEM license is still in use and associated with the old VEM module number in the system. This can sometimes occur after ESXi host or VEM module upgrades, as well as host firmware/BIOS updates.

Resolution

To resolve this issue, transfer the VEM license from the old VEM module number to the new one.

To transfer the VEM license:

  1. Run these commands:

    n1k# show module
    n1k# show license usage NEXUS1000V_LAN_SERVICES_PKG

    Compare the output of the two commands and identify the VEM module that is present in the show license usage output, but not present in the show module output. Make a note of this module number.

  2. The license of the identified module must be transferred to the unlicensed VEM by running these commands:

    n1k# configure terminal
    n1k(config)# svs license transfer src-vem vem_number dst-vem vem_number

    Where vem_number the module numbers identified earlier in this procedure.

  3. Ensure the VEM module is now licensed by running the command:

    n1k# show module