AES, SMGR: VMware tools not running after LSU deployment / SMGR showing "Trust establishment failed"

Doc ID    SOLN307476
Version:    5.0
Status:    Published
Published date:    02 Jan 2019
Created Date:    03 Apr 2017
Author:   
inabak
 

Details

SDM cannot refresh VM for AES after applied LSU.

BP check and confirm that vmware tools is not running on VM-AES.

Problem Clarification

the failing AES's vmnic seems updated.
> ・BAD AES dmesg
>> VMware vmxnet3 virtual NIC driver - version 1.4.2.0-k-NAPI
> ・GOOD AES dmesg
>> VMware vmxnet3 virtual NIC driver - version 1.1.32.0-NAPI

NOTE: BPE never touch for vmware tools. i.e. they do not update vmware tools manually.

 Some symptoms observed are:

[root@sgavp1aes ~]# status vmware-tools
vmware-tools stop/waiting

[root@sgavp1aes ~]# grep "vmxnet3 virtual NIC driver" /var/log/dmesg
VMware vmxnet3 virtual NIC driver - version 1.4.2.0-k-NAPI

 

/boot has both initrd-<version> image and initrd-<version>kdump image.

-see attachment 

Another case :

 SMGR showing trust establishment failed with AES.

Cause

The vmware-config tool in the LSU update did not run as expected.

Solution

Workaround: PLEASE KEEP IN MIND!! The versions of the initrd may be different from these commands. Please check /boot to make sure the versions strings are the same. If they aren't change the commands to match the version string of the initrd for the box you are working on.

As root, run the following command and reboot the server.

·         /sbin/depmod -a 2.6.32-642.13.1.el6.i686

·         /sbin/mkinitrd -f --with=pvscsi --with=pcnet32  --with=vmxnet --with=vmxnet3 --with=vmmemctl --with=vmci --with=vsock /boot/initrd-2.6.32-642.13.1.el6.i686.img 2.6.32-642.13.1.el6.i686

·         /usr/bin/vmware-config-tools.pl --clobber-kernel-modules=pvscsi,vmxnet,vmxnet3,vmmemctl,vmci,vsock -d

·         rm /boot/initrd-2.6.32-642.13.1.el6.i686kdump.img

 FYI: You cannot back out of these commands if there was to be an issue, you're just re-running the VMware tools RPM from the LSU patch which cannot be removed once installed.

For another case :

The scenario that I had SMGR was having trust establishment issues with AES server.

Attachment File

initrdimg.png
16K • < 1 minute @ 56k, < 1 minute @ broadband



Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy