Posts filed under ‘VMware’

ESXi 6.5 changes to HA

Hi All

With the latest release of ESXi 6.5 , VMware have made lots of changes to the HA Capability.

Below article provides a detailed description about these improvements:

source: http://blog.servercentral.com/high-availability-redundancy-features-vsphere-6.5.

Also this articles clarifies the correct method  of calculating the Percentage method based Admission control as well.

Screenshot extract from the article mentioned.

October 23, 2017 at 3:05 pm Leave a comment

ESXi Host Disconnects from vCenter Server

Hi All

Recently we had an issue in one of customer environment where he is    hosting 3 nodes ESXi Cluster on Nutanix. Suddenly one of the host was showing not responding and disconnected from the VCenter. But luckily there was no impact to the production VM ‘s hosted in that node since it was only the Management Network was having issue with it. After several hours of troubleshooting we decided to call the VMware Support and found out the issue is related to KB 2145611)

Below is the extract from the vmkernel.log
——————————————————————————-
2017-03-19T05:35:01.871Z cpu26:7190268)ALERT: hostd detected to be non-responsive
2017-03-19T06:00:01.988Z cpu2:7192142)ALERT: hostd detected to be non-responsive
2017-03-19T06:02:53.474Z cpu6:36416)StorageApdHandler: 1204: APD start for 0x4305932c3770 [8c9d039d-452d1170]
2017-03-19T06:02:53.474Z cpu6:36416)StorageApdHandler: 1204: APD start for 0x4305932c4fd0 [fa49f8b0-fa322ecd]
2017-03-19T06:02:59.369Z cpu18:32953)StorageApdHandler: 1292: APD bounce-exit for 0x4305932c4fd0 [fa49f8b0-fa322ecd]
2017-03-19T06:02:59.369Z cpu18:32953)StorageApdHandler: 1292: APD bounce-exit for 0x4305932c3770 [8c9d039d-452d1170]

2017-03-19T09:40:04.774Z cpu44:7213651)WARNING: LinuxFileDesc: 5637: Unrecoverable exec failure: Failure during exec while original state already lost
2017-03-19T09:40:06.784Z cpu24:7213652)WARNING: UserParam: 1301: could not change group to <host/vim/vimuser/terminal/ssh>: Admission check failed for memory resource
2017-03-19T09:40:06.784Z cpu24:7213652)WARNING: LinuxFileDesc: 5637: Unrecoverable exec failure: Failure during exec while original state already lost
2017-03-19T09:40:06.986Z cpu29:7213653)WARNING: UserParam: 1301: could not change group to <host/vim/vimuser/terminal/ssh>: Admission check failed for memory resource
2017-03-19T09:40:06.986Z cpu29:7213653)WARNING: LinuxFileDesc: 5637: Unrecoverable exec failure: Failure during exec while original state already lost
2017-03-19T09:41:39.969Z cpu16:37557)WARNING: LinuxThread: 340: Error cloning thread: -28 (bad0081)
2017-03-19T09:45:52.490Z cpu43:7214205)WARNING: User: 5366: Error in exec’d cartel setup: Failed to map section: Admission check failed for memory resource
2017-03-19T09:45:52.490Z cpu43:7214205)WARNING: LinuxFileDesc: 5637: Unrecoverable exec failure: Failure during exec while original state already lost
2017-03-19T09:46:06.930Z cpu30:7214223)WARNING: LinuxThread: 340: Error cloning thread: -28 (bad0081)
2017-03-19T09:46:07.236Z cpu41:7214225)WARNING: LinuxThread: 340: Error cloning thread: -28 (bad0081)
2017-03-19T09:46:46.417Z cpu22:7214286)WARNING: User: 5366: Error in exec’d cartel setup: Failed to map section: Admission check failed for memory resource
2017-03-19T09:46:46.417Z cpu22:7214286)WARNING: LinuxFileDesc: 5637: Unrecoverable exec failure: Failure during exec while original state already lost
2017-03-19T09:47:11.461Z cpu26:37558)WARNING: LinuxThread: 340: Error cloning thread: -28 (bad0081)
2017-03-19T09:49:19.688Z cpu5:7214435)WARNING: LinuxThread: 340: Error cloning thread: -28 (bad0081)
————————————————————————————-

The support engineer suggested that we could try it by clear the likewise cache(where the ESXI host the AD authentication related data) before applying the patch.

The commands he used are:(Take a Putty Session to the ESXi host impacted)

# /usr/lib/vmware/likewsie/lw-lsa ad-cache –delete all

The above command will produce an error (file not found) if there is no cache.

Good luck.

 

 

 

March 20, 2017 at 11:06 am 2 comments

How to Configure VSphere Update Manager 6.0

This article provide a detailed screencast for installing the latest Vsphere Update Manager on ESXi6 , the new version comes with it’s own embedded Microsoft SQL 2012  Express.(As the VCenter uses the built-in Postgres Database)

For those who deploy the Vsphere Update Manager in a controlled environment with no internet access can make use of Update Manger Download Service(UMDS) component which can be installed on the internet facing machine and the Update Manager Server can collect the update from UMDS

You could download the latest package via your VMware account and mount it on a Windows Operating System(Please avoid installing on a Domain Controller)

NOTE: You must install the prerequisite of .Net 3.5 Framework SP1 prior installing the package.

update_manager_1 update_manager_2 update_manager_3 update_manager_4 update_manager_5 update_manager_6 update_manager_7 update_manager_8 update_manager_9 update_manager_10 update_manager_11 update_manager_12 update_manager_13 update_manager_14 update_manager_15

Finally once installed log in to Vsphere Web Client and enable the Vsphere Update Manager Web Client-Plugin via Administration –> Solutions–>Client-Plugiuns(incase the Web Client Plugin is not visible click on “Check for New Plug-ins)

update_manager_16

 

April 22, 2015 at 9:08 am Leave a comment

Error in Active Directory Operations when Joining ESXi 6 to Active Directory

Hi

Recently when I was testing the ESXi 6 on my LAB running on VMware Workstation 11 I faced a nightmare when I tried to join the ESXi to the Active Directory.

As I started troubleshooting I re-assured all the prerequisites are met (such as NTP, DNS resolution) but the problem was haunting me.

As per the VMware guidelines when I tried to restart the lwsmd service via Tech Support Mode it was throwing the below errors

– lwsmd is not fully started

– likewise service manager [failed to set memory reservation] esxi

Then it clicked on me that may be this behaviour could be due to insufficient memory and after increasing the memory voila everything turned out to be working normally.

April 21, 2015 at 12:14 pm Leave a comment

ESXi 5.5 Update Manager hangs at 33%

Dear Folks

Recently I have been deploying an ESXi Cluster based on 5.5 ,when we configured the Update Manager and tried to scan the Hosts the process hangs at 33%.

We solved this issue by adding the “Vsphere Update Manager” on the Security Profile.

Steps
> Login to Vsphere Client

> Select the ESXi Host and Click on Configuration

> Select Security Profile

> Select the Firewall and click on Properties

> Click on Vsphere Update Manager to make it selected.

Press OK.

vcenter

November 9, 2014 at 2:59 pm Leave a comment

Newer Posts


Archives

Categories

Follow Hope you like it.. on WordPress.com

Blog Stats

  • 30,385 hits

%d bloggers like this: