new1234.jpg

Archive

Posts Tagged ‘vSphere 5.5’

VMware: Perf Charts service experienced an internal error

December 16th, 2015 No comments

A few weeks ago a customer asked me to take a look at the following warning message in VMware vCenter when the Performance Tab in the vSphere client is being opened.

  

Perf Charts service experienced an internal error.

Message: Report application initialization is not completed successfully. Retry in 60 seconds

 
image


Troubleshooting time

Global checks:

  • The Windows Event logs are clean
  • VMware vSphere (web-) services are started with normal credentials
  • I was able to restart service accounts with domain based credentials (no locking)
  • Windows Firewall was enabled but no drops in the logging
  • No recent installed Windows Updates
  • No unplanned restarts or crashes
  • The installed certificate was not expired
  • The installed certificate was 2048 bit
  • No conflicting webserver ports at the vCenter server
    ..some more troubleshooting

I checked the wrapper.log and stas.log files located at the following location:

Path: C:\ProgramData\VMware\VMware VirtualCenter\Logs\

clip_image002

 

 

 

 

 

 

 

 

 

  

clip_image002[5]

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Hmm, he logging shows that there are problems with the installed vCenter SSL certificate:
 

Error constructing private key..

..Error decrypting password

After some troubleshooting I saw that every time I open the Performance tab a new webserver SSL private key decrypting error was written in the stats.log.

I already had checked the expire date of the installed SSL certificate, it was a normal 2048 bit wildcard certificate.. oh, eh, wildcard..?? Let’s see if it is supported:

“The use of wildcard certificates are not supported with vCenter Server and its related services. Each service must have its own unique certificate”

Nope, it is not! Maybe this is the root cause.

After checking the SSL requirements at the VMware KB  I found the SSL format which is needed to generate the certificate: OpenSSL Version 0.9.8 must be used. If you do not use this version, the SSL implementation fails. <– I couldn’t check this because there was no documentation of the SSL generation

 

Solution

The customer used a wildcard SSL certificate which is not supported

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Quick stats on [SERVERNAME] is not up-to-date

June 4th, 2015 No comments

Few weeks ago I upgraded for a customer vCenter Server 5.5. to 6.0, today I received a yellow warning in the Summary tab:

Quick stats on [SERVERNAME] is not up-to-date

image

 

Solution

This is a known issue in vCenter Server 5.5 and 6.0.

  • This issue is resolved in VMware vCenter Server 5.5.0b.
  • Currently there is no resolution for vCenter Server 6.0.

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

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

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

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

  1. Connect to the vCenter Server using the vSphere Client and administrator credentials.
  2. Select Administration > vCenter Server Settings to display the vCenter Server Settings dialog box.
  3. In the settings list, select Advanced Settings.
  4. Add the following parameters:
  5. vpxd.quickStats.HostStatsCheck = False

    vpxd.quickStats.ConfigIssues = False

      
    image

  6. Restart the vCenter Server services. For more information, see:

    More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

[VMware] Could not start VMX: msg.vmk.status.VMK_NO_MEMORY

March 29th, 2015 4 comments

Last week I had some issues with starting virtual machines on vSphere 5.5 hosts (enough capacity available), when I try to start up the VM I receive message:

Could not start VMX: msg.vmk.status.VMK_NO_MEMORY”

An error was received from the ESX host while powering on VM [name]
Head globalCartel-1 already at its maximum size of 7869288. Cannot expand
Could not start VMX: msg.vmk.status.VMK_NO_MEMORY

image

 

Cause

This issue is caused by a memory leak in the driver which fills the SWAP memory of the ESXi host, making it unable to response to any requests at all. This issue occurs with ESXi hosts running on HP hardware with these versions of AMS:

  • hp-ams 500.9.6.0-12.434156
  • hp-ams-550.9.6.0-12.1198610
  • hp-ams 500.10.0.0-18.434156
  • hp-ams-550.10.0.0-18.1198610


Solution

This is a known issue affecting ESXi 5.x. To resolve this issue, upgrade to AMS version 10.0.1.

For ESXi 5.0 and 5.1, see:

For ESXi 5.5, see:

 

Note: In some cases, commands running on the ESXi host fails with cant’t fork.  In this case the virtual machines running on the ESXi host needs to be powered off and the ESXi host rebooted. To verify the installed versions of AMS, run this command:

esxcli software vib list | grep ams

To remove the package on all hosts running on these AMS versions:

  1. Log in to the host using SSH. For more information, see Using ESXi Shell in ESXi 5.x and 6.0 (2004746).
  2. Run this command to stop the HP service (does not persist on reboot):
    /etc/init.d/hp-ams.sh stop
  3. Run this command to remove the VIB:
    esxcli software vib remove -n hp-ams
  4. Reboot the host.
    More information:

VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Host IPMI System Event Log Status alarm is triggered repeatedly in VMware vCenter Server

January 22nd, 2015 2 comments

image

 

Solution

To resolve this issue, stop the alarm from triggering repeatedly and clear the IPMI System Event.log file and reset the sensors.

To clear the IPMI System Event.log file and reset the sensors:

  1. Open vCenter Server using vSphere Client.
  2. In the vCenter Inventory, select the ESXi/ESX host.
  3. Click the Hardware Status tab.
  4. Click System Event log under View.
  5. Click Reset Event Log. The red alert is removed from the System Event log.
  6. Click Reset Sensors to reset the host sensors.

Introduced in ESXi 5.1 Update 2 (Build Number: 1483097) and ESXi 5.5 Patch 1 (Build Number:  1474528), there is a new localcli command line to clear the IPMI SEL logs:

localcli hardware ipmi sel clear

To run localcli command on the ESXi 5.1 or 5.5 host:

  1. Connect to the ESXi host via SSH. For more information, see Using Tech Support Mode in ESXi 4.1 and ESXi 5.x (1017910).
  2. Run this command:
  3. localcli hardware ipmi sel clear

image   
More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

Veeam: Client error: NFC storage connection is unavailable

December 10th, 2014 1 comment

Last week I added a new vSphere host in my homelab, after I configured and started my backup job in the Backup & Replication 7.0 patch 4 environment I received this error messages:

Processing ‘DC01’ Error: Client error: NFC storage connection is unavailable. Storage: [stg:datastore-12,nfchost:host-10,conn:vce01.vmpros.local]. Storage display name: [ESX01_VMFS02].
Failed to create NFC download stream. NFC path: [nfc://conn:vce01.vmpros.local,nfchost:host-10,stg:datastore-12@DC01/DC01.vmx].

image

 

Solution

When you look at the Backup Job log file you can see the details, logfile location: C:\ProgramData\Veeam\Backup\VMpros_-_Backup_01

In my case Veeam Backup could resolve my VMware vCenter 5.5 server but when he try to contact the vSphere host with some local datastores the backup failed. I tried to ping the hosts and couldn’t resolve the hostname of my vSphere host.

Make sure you have:

– Added the vSphere host in DNS, create a A record in your DNS server

Optionally: Add the vSphere hostsname(s) and IP-address(es) in the hostfile at your Veeam Backup server

 

End result

 

image

 

More information: Veeam

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: vRealize Operations Manager vApp deployment fails with error: This operation is not supported on the object

December 10th, 2014 2 comments

Today I was installing VMware vCenter Operations 5.8.4.0 in my vSphere 5.5 update 1 homelab, during deployment I received this warning message:
   

The OVF package is invalid and cannot be deployed.

This operation is not supported on the object.

   

VMpros

Cause

vRealize Operations Manager vApp 5.x can only deploy to a host inside a cluster if DRS is enabled.

 

Solution

My homelab is running a VMware vCenter 60 day trial version, after I enabled DRS in my cluster with 2 hosts I was able to deploy vCO 5.8

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Nesting Hyper-V 2012 R2 on vSphere ESXi 5.5

August 28th, 2014 3 comments

In my test environment I configured tree Hyper-V 2012R2 servers nested on vSphere 5.5,  the configuration was very easy, here some details:

1. Deploy a Windows 2012R2 server, use GuestOS Windows 2012 (64-bit)

2. Upgrade hardware level to version 10

3. Remove the virtual machine from the vCenter inventory

4. Download and edit the .vmx file, add the following lines:

vhv.enable = “TRUE”
hypervisor.cpuid.v0 = “FALSE”
mce.enable = “TRUE”

 image

5. Upload and re-add the .vmx file to the vCenter inventory

6. Edit the virtual machine hardware > CPU > Hardware virtualization> select: Expose hardware assisted virtualization to the guest OS

*Note: you need to upgrade to HW level 10, otherwise the hardware virtualization tab is grayed out.

 image

7. Power on the virtual machine

8. Now you are able to select the Hyper-V role, finish the setup

image

 

Ejoy!

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Cannot remove a License Key from VMware vCenter Server

August 23rd, 2014 5 comments

Last week I upgraded a vCenter Server from version 5.1 to 5.5, I also added a 4th hosts to the cluster, so I need to upgrade the host license keys. But after upgrade I couldn’t remove the license files in vCenter Licensing section:

image

 

Solution:

To connect to the ADAM database:

  1. Log in to the vCenter Server.
  2. To open ADSI Edit, click Start > Run, type adsiedit.msc, and press Enter.
  3. Right-click ADSI Edit and click Connect to.
  4. In the Connection point section, click Select or type a Distinguished Name or Naming Context.
  5. Enter dc=virtualcenter, dc=vmware, dc=int
  6. In the Computer section, click Select or type a domain or server: (Server | Domain [:port]).
  7. Enter localhost
  8. Click OK.
  9. Drill down to DC=virtualcenter,DC=vmware,DC=int, OU=Licensing, OU=LicenseEntities.You see the CN="license key" containers.
  10. Right-click the container that shows the the serial number of the key that is negative within the vCenter Server Licensing page.
  11. Click Delete.

image

 

Result:

When you restart he vSphere client and navigate to the Licensing page the old license keys are removed and you can re-assign license keys to the hosts

image

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Upgrade VMware vCenter 5.0 to 5.5

August 13th, 2014 No comments

Last week I upgraded for a customer VMware vCenter server to from version 5.0 to 5.5 Update 1c, here some details:

clip_image003

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn