new1234.jpg

Archive

Posts Tagged ‘vSphere 5.5’

VMware: How to upgrade vCenter appliance 5.1 to 5.5

July 20th, 2014 No comments

Few months ago I ‘ve upgrade our vCenter appliance from version 5.1 to 5.5, here are the installation steps

image

image

image

image

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: VMware Data Protection (VDP) 5.5 IP/DNS could not be resolved

March 18th, 2014 1 comment

During the network configuration at the VMware Data Protection (VDP) appliance I received this warning message:

IP/DNS could not be resolved. Please check the hostname, domain, and DNS values for forward and reverse lookup validation

 

image 

 

Troubleshoot:

VMware VDP whitepaper: Before you deploy vSphere Data Protection, an entry needs to be added to the DNS Server for the appliance IP address and FQDN. This DNS Server must support forward and reverse lookup. Failure to have DNS set up properly can cause many runtime or configuration issues.

As you can see, the nslookup failed:

  image

Solution:

Add the domain and search domain in the /etc/resolv.conf file

 image

And make sure you’ve created a correct PTR record at the DNS server for reverse DNS functionality, at the DNS server:

 image

Select: Create associated pointer (PTR) record

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: VMware vSphere 5.5 & vCenter Server 5.5 Update 1 released

March 12th, 2014 No comments

 

The release of VMware vSphere vCenter 5.5 Update 1 contains the following enhancements: 

vCloud® Hybrid Service™ vSphere® Client Plug-in, is now available in vSphere Web Client.
The plug-in installer icon appears in the Home page, under Inventories. Click the installer icon to install the plug-in. The vCloud Hybrid Service plug-in lets you view and manage your vCloud Hybrid Service resources in the vSphere Web Client. After you install the plug-in and register your vCloud Hybrid Service account with it, you can view all your Dedicated Cloud and Virtual Private Cloud instances in the vSphere Web Client. You can browse each cloud instance and manage its inventory of virtual data centers, gateways, networks, and virtual machines. See the vCloud Hybrid Service vSphere Client Plug-in documentation at https://www.vmware.com/support/pubs/vchs_plugin_pubs.html for more information.

vCenter Server is now supported on Windows Server 2012 R2.

Resolved Issues – This release delivers a number of bug fixes that have been documented in the Resolved Issues section.

 

The release of VMware vSphere ESXi 5.5 Update 1 contains the following enhancements:

VMware Virtual SAN Virtual SAN 5.5 is a new hypervisor-converged storage tier that extends the vSphere Hypervisor to pool server-side magnetic disks (HDDs) and solid-state drives (SSDs). By clustering server-side HDDs and SSDs, Virtual SAN creates a distributed shared datastore designed and optimized for virtual environments. Virtual SAN is a standalone product that is sold separate from vSphere and requires its own license key 

Resolved Issues This release delivers a number of bug fixes that have been documented in the Resolved Issues section.

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Configure vSphere hosts to VMware Syslog Collector with PowerCLI

December 18th, 2013 2 comments

PowerCLI script:

 

#====================================================================#
#   SCRIPT:        PowerCLI_configure_syslog_settings_host.ps1       #
#   FUNCTION:      Add remote syslog server, settings and  open      #
#                  firewall ports in cluster                         #
#   OWNER:         Sander Daems                                      #
#   VSPHERE:       5.5 build 1331820                                 #
#   CREATED:       18/12/2013                                        #
#   MODIFIED:      18/12/2013                                        #
#   VERSION:       v.1.0                                             #
#====================================================================#
#   CHANGELOG:                                                       #
#                                                                    #
#    v.1.0                                                           #
#    - Script created;                                               #
#                                                                    #
#====================================================================#
# CUSTOM DEFINITIONS                                                 #
#====================================================================#
$vCenterServer = Read-Host "Enter vCenter Hostname / IP"
$vmhost = Get-VMHost
#====================================================================#
# HOST - Specify host and connect                                    #
#====================================================================#
Connect-VIServer $vCenterServer
#====================================================================#
# SCRIPT - SYSLOG - Update Syslog settings                           #
#====================================================================#
$vmhost | Set-VMHostAdvancedConfiguration -NameValue @{'Config.HostAgent.log.level'='info';'Vpx.Vpxa.config.log.level'='info';'Syslog.global.logHost'='udp://10.180.200.18:514'}
#====================================================================#
# SCRIPT - FIREWALL - Open ESXi firewall port                        #
#====================================================================#
$vmhost | Get-VMHostFirewallException -VMhost $vmhost -name syslog | Set-VMHostFirewallException -Enabled $true
#====================================================================#

 

vCenter Syslog Collector settings:

 

image


Script result:

image

image

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Upgrade vSphere ESXi local flash drive

December 18th, 2013 No comments

Last week I’ve upgraded some vSphere diskless hosts from version 4.1 to 5.5, to upgrade the vSphere version at local flash drive I followed this steps:

 

clip_image001

– Press [enter] to continue

 

clip_image002

– Press [F11] Accept and Continue

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Quick stats on “hostname” is not up-to-date

December 18th, 2013 No comments

Today I received some warnings at my new installed vSphere 5.5 hosts, the warning message:

Configuration issues. "Quick stats on hostname is not up-to-date"

VMpros

 

Solution:

This is a known issue in vCenter Server 5.5.

To work around this issue, add these quickStats parameters to the Advanced Settings of the vCenter Server:

  • vpxd.quickStats.HostStatsCheck
  • vpxd.quickStats.ConfigIssues

image

 

Note: Adding these parameters to the vCenter Server will not affect future upgrades.

To add the quickStats parameters to the Advanced Settings of the vCenter Server:

  1. In the vSphere Web Client, navigate to the vCenter Server instance.
  2. Select the Manage tab.
  3. Select Settings > Advanced Settings.
  4. Click Edit.
  5. In the Key field, enter this key: vpxd.quickStats.HostStatsCheck
  6. In the Value field, enter: False
  7. Click Add.
  8. In the Key field, enter this key: vpxd.quickStats.ConfigIssues
  9. In the Value field, enter: False
  10. . Click Add.
  11. . Click OK.
  12. . Restart the vCenter Server service.

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

XP can’t connect via vSphere 5.5 client

December 16th, 2013 9 comments

Last week I added some new vSphere 5.5 host in a new configured cluster, the customer is still using Windows XP SP3 32-bit, he received this error message:

 

image

An unknown connection error occurred. (The Client could not send a complete request to the server. (The underlying connection was closed: An unexpected error occurred on a send.

 

Reason:

This issue occurs due to increased security of the cipher strengths which are, by default, used by the VMware Management Web Services components. Due to this change that was introduced in vSphere 5.1, the host operating system is required to support a higher cipher strength to be able to connect to these components.

In Windows Vista and Windows Server 2008, the proper cipher strengths are built into the operating system. However, for older Windows operating systems, a Microsoft hotfix must be applied to add the supported cipher strengths.

For more information on the cipher strengths that get added with the hotfix, see the Microsoft Knowledge Base article 948963.

 

 

Solution:

Windows 2003 (32-bit and 64-bit Edition)

For Windows Server 2003 (32-bit and 64-bit), apply the appropriate hotfix to the machine on which the vSphere Client is installed.

Note: If the vSphere Client is installed on the Windows Server where vCenter Server is installed, you must also apply the patch to that Windows Server.
To download the hotfix for your system, see the Microsoft Knowledge Base article 948963.

Notes:

  • You must reboot the machine after applying the hotfix.
  • Non-English versions of the hotfixes are also available on the Microsoft site. Click the Show hotfixes for all platforms and languageslink on the Hotfix Request page to view the available versions.

Windows XP (32-bit)

There is no hotfix available for Windows XP (32-bit). Microsoft currently only provides limited support for Windows XP, and as a result the hotfix has not been released for it. To resolve this issue, you must upgrade your host operating system to Windows Vista or later, which support the use of high cipher strengths.

If you are unable to upgrade your environment, you may try adding less secure cipher strengths back to the configuration, which allows communication to proceed successfully.

To add less secure cipher strengths back to the configuration:

Caution: This is not a recommended configuration and is provided for backward compatibility purposes only. This is not extensively tested and is supported on a best effort basis only.

  1. Log in as an administrator to the server where vCenter Server 5.1 is installed.
  2. Navigate to the tomcat configuration directory.
    Note: By default, this directory is located at C:\Program Files\VMware\Infrastructure\tomcat\conf\. In vCenter Server Appliance, the file is located at /ur/lib.vmware-vpx/tomcat/conf.
  3. Open the server.xml file using a text editor.
  4. Change the Connector text to add support for weaker ciphers by changing it from:
    <Connector SSLEnabled="true" acceptCount="100" ciphers="TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_256_CBC_SHA, TLS_DH_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DH_RSA_WITH_AES_128_CBC_SHA, TLS_DH_DSS_WITH_AES_128_CBC_SHA" connectionTimeout="20000" executor="tomcatThreadPool" keystoreFile="${bio-vmssl.keyFile.name}" keystorePass="${bio-vmssl.SSL.password}" keystoreType="PKCS12" maxKeepAliveRequests="15" port="${bio-vmssl.https.port}" protocol="HTTP/1.1" redirectPort="${bio-vmssl.https.port}" scheme="https" secure="true"></Connector>
    To:
    <Connector SSLEnabled="true" acceptCount="100" ciphers="TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_256_CBC_SHA, TLS_DH_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DH_RSA_WITH_AES_128_CBC_SHA, TLS_DH_DSS_WITH_AES_128_CBC_SHA ,SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA" connectionTimeout="20000" executor="tomcatThreadPool" keystoreFile="${bio-vmssl.keyFile.name}" keystorePass="${bio-vmssl.SSL.password}" keystoreType="PKCS12" maxKeepAliveRequests="15" port="${bio-vmssl.https.port}" protocol="HTTP/1.1" redirectPort="${bio-vmssl.https.port}" scheme="https" secure="true"></Connector>
    Note: Add only the red text as indicated and do not change any other options. This adds back support for less secure cipher strengths for backward compatibility purposes.
  5. Restart the VMware VirtualCenter Management Web Services service. For more information, see  Stopping, starting, or restarting vCenter services (1003895).

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: VCVA: Invalid Hostname. FQDN is required for joining a domain.

October 10th, 2013 1 comment

Last week I upgraded my lab to vSphere 5.5, during the install I entered the hostname to configure domain authentication but I received this error:

image

Error: Invalid hostname. FQDN is required for joining a domain

 

Solution:

Goto Network > Address > Hostname

Add the domain information in the hostname box, sample:

image

After this change I was able to configure AD authentication:

 

image

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Quick stats on [hostname.domain.local] is not up-to-date

October 10th, 2013 1 comment

After upgrading my vCenter appliance 5.1 to 5.5 I noticed the following warning message at one of my 5.1 hosts:

image

Configuration issues. "Quick stats on hostname.domain.local is not up-to-date"

 

Solution:

This is a known issue in vCenter Server 5.5.

To work around this issue, add these quickStats parameters to the Advanced Settings of the vCenter Server:

  • vpxd.quickStats.HostStatsCheck
  • vpxd.quickStats.ConfigIssues

image

After I restarted the vCenter services the message disappeared

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn