rothb Tracker

Re: Skyline "Could not execute Online health checks." after 7.0 U3d update

rothb — Fri, 13 May 2022 13:46:05 GMT

vSphere 7.0 Update 3e was released yesterday with a fix for the problem.

https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3e-release-notes.html

Regards,

Bjoern

Re: Skyline "Could not execute Online health checks." after 7.0 U3d update

rothb — Wed, 04 May 2022 21:49:03 GMT

Found the following KB: https://kb.vmware.com/s/article/88254

But nothing new at the moment.

Re: Two Factor Authentication bypass through login on to "communities.vmware.com" first?

rothb — Wed, 13 Apr 2022 07:54:58 GMT

Hi,

sorry for not getting back. Complete lost focus on this topic

Yes it is still working that way. Logged in on community forums without 2FA and can access https://customerconnect.vmware.com/dashboard which should require 2FA.

Thanks

Bjoern

Re: Skyline "Could not execute Online health checks." after 7.0 U3d update

rothb — Wed, 13 Apr 2022 07:50:05 GMT

After filing a support request. I got the follwing answer:

Listed as a known issue for 7.0 U3d, fix is planned come for release 7.0 P5 [scheduled for late Q2, early Q3 2022]

So I guess we have to wait a "little" longer.

Two Factor Authentication bypass through login on to "communities.vmware.com" first?

rothb — Fri, 21 May 2021 07:12:13 GMT

Hi all,

I've noticed that I can actively bypass the enabled 2FA Authentication of my "My VMware" Account.

When I login on "communities.vmware.com" first, I don't get asked to provide the 2FA code. Then accessing "my.vmware.com" gets me right in my "My VMware" account, which usually asks for 2FA codes when accessed directly. I think this is an issue.

Best regards,
Bjoern

Re: DEVICES deprecated and unsuppoted in ESXi 7.0

rothb — Thu, 20 May 2021 12:36:32 GMT

I got confirmation from VMware Skyline Advisor TSE that the engineering team is aware of this false positive. VMware will update this rule by end of June 2021. The workaround is to mark this recommendation as a hidden finding.

Re: DEVICES deprecated and unsuppoted in ESXi 7.0

rothb — Tue, 11 May 2021 14:24:00 GMT

As mentioned by Duncan vSphere Skyline Health report is now fine, but as noted in the Spreadsheet "7.0 VMKlinux deprecated devices.xlsx", which is attached to KB77304, our BOSS S1 Adapter (VID 1b4b/DID 9230) is still deprecated. Also a "moderate" warning shows up in Skyline Advisor because of this. The latest update of the file was in March, where the Intel Lewisburg SATA AHCI Controller was removed from the deprecated devices list.

So it seems that Skyline Advisor and the file in the KB article are still reflecting the deprecated status of the Dell BOSS-S1 Adapter. Hope this will get fixed soon.

Re: vmware-dataservice-sca status changed from yellow to green

rothb — Fri, 06 May 2016 06:43:27 GMT

Hello,

seems to be a known issue and sadly there is no workaround yet.

VMware KB: In vCenter Server 6.0 the vmware-dataservice-sca and vsphere-client status change from green to yellow co…

Best regards,

Bjoern

ESXi 5.5 with NetApp FC attached Storage not on HCL yet?!

rothb — Wed, 09 Oct 2013 08:36:05 GMT

Hello community,

I am eager to test the new ESXi 5.5 on four of our development machines. As I have browsed the HCL I was a bit disillusioned because none of our NetApp Filers (FAS 3040 and FAS 2240-4) is on the HCL yet, at least if attached to FC as we have. Anyone here with inside news when we can expect the FC attached Netapp Filers with DataONTAP in the HCL for use with ESXi 5.5?

Thanks in advance.

Best regards,

Bjoern

Re: VDP creating multiple user sessions

rothb — Thu, 02 May 2013 07:12:17 GMT

Hello dhayashi,

is your problem solved? If yes what have you done to solve it? I have one VDP Appliance and also a lot of active user sessions here. The VDP is newly deployed and configured as described in the VDP Admin Guide. I wonder if these many active user sessions are by design or is something wrong with my setup?

Best regards,

Bjoern

Re: vSphere Web Client occasional "For input string" error

rothb — Thu, 28 Feb 2013 12:06:55 GMT

Stumbled upon this error also. Seems to be a known issue (KB Article) with vSphere 5.1 + Web Client.

Best regards,

Bjoern

Re: Scanning ESXi host with VUM fails after installing Dell OMSA 6.5 A02

rothb — Tue, 14 Feb 2012 12:04:26 GMT

Sehr geehrte Damen und Herren,

ich bin bis einschließlich 17.02.2012 nicht im Haus.

In dringenden Fällen wenden Sie sich bitte an unseren Service Desk (Tel.: 2098 oder hotline@klilu.de).

Vielen Dank.

Björn Roth

Administration

Z.E.N.works / Windows

Informationstechnologie

Re: Scanning ESXi host with VUM fails after installing Dell OMSA 6.5 A02

rothb — Wed, 14 Dec 2011 15:32:02 GMT

Hello,

first of all thanks for trying helping me out.

I solved the problem by myself. The problem was not the ESXi Server rather the Update Manager had a problem. First I installed a ESXi5 VM in VMware Workstation 8 and the VM ESXi Server had the same problem than the other Server. Then i quickly uninstalled VUM and reinstalled it, with a clean VUM DB.

Afterwards everything was fine again. Even with installed OMSA Agent. Seems like anything other was causing this. Had nothing to do with OMSA VIB.

Thanks again for your help.

Regards,

Bjoern

Scanning ESXi host with VUM fails after installing Dell OMSA 6.5 A02

rothb — Wed, 14 Dec 2011 12:52:43 GMT

Hello,

after installing the Dell OMSA 6.5 A02 VIB (esxcli software vib install -d /.../omsa.zip) I can no longer scan the Host with Update Manager. I get the error message:

The host returns esxupdate error code:99. An unhandled exception was encountered. Check the Update Manager log files and esxupdate log files for more details.

After looking in /var/log/esxupdate.log I see the following lines, which could be the Reason why the scanning of the Host fails:

2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR: An unexpected exception was caught:
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR: Traceback (most recent call last):
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR:   File "/usr/sbin/esxupdate", line 216, in main
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR:     cmd.Run()
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-474610/bora/build/esx/release/python-2.6-lib-zip-stage/474610/visor/pylib/python2.6/site-packages/vmware/esx5update/Cmdline.py", line 106, in Run
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-474610/bora/build/esx/release/python-2.6-lib-zip-stage/474610/visor/pylib/python2.6/site-packages/vmware/esximage/Transaction.py", line 78, in DownloadMetadatas
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-474610/bora/build/esx/release/python-2.6-lib-zip-stage/474610/visor/pylib/python2.6/site-packages/vmware/esximage/VibCollection.py", line 60, in __add__
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-474610/bora/build/esx/release/python-2.6-lib-zip-stage/474610/visor/pylib/python2.6/site-packages/vmware/esximage/VibCollection.py", line 77, in AddVib
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-474610/bora/build/esx/release/python-2.6-lib-zip-stage/474610/visor/pylib/python2.6/site-packages/vmware/esximage/Vib.py", line 625, in MergeVib
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR: ValueError: Cannot merge VIBs Dell_bootbank_OpenManage_6.5-0000, Dell_bootbank_OpenManage_6.5-0000 with unequal payloads attributes
2011-12-14T12:40:39Z esxupdate: esxupdate: DEBUG: <<<

Now I thought "Ok lets remove the VIB ("esxcli software vib remove OpenManage:6.5-000" afterwards "reboot") then everything will work again" but sadly it didn´t . The VIB is no longer listed (esxcli software vib list) but the error and log entrys stayed the same.

Someone else having the same or similar problem or know a way to get out of this mess?

Best regards,

Bjoern

Re: ESXi 5 vSwitch bug ?

rothb — Thu, 27 Oct 2011 07:21:33 GMT

Hi LS,

have you set the Failback option correctly? It should be set to "Yes" for your case.

Best regards,

Bjoern

Re: Moved some VM's from ESX3 to 4.1, getting cpu errors.

rothb — Sun, 23 Oct 2011 21:40:36 GMT

Hi Greg,

EVC is very likely not the reason for the failing VMs. The only thing EVC does is to mask CPU Functions when you have different CPUs in your Cluster, for example a Intel XEON Core 2 and Intel XEON Nehalem, this would mask/hide the higher functions of the XEON Nehalem to the VMs.

From the error message it could be possible that you try to revert to an old VM Hardware State not supported by that Host. You have written that you want to make sure that the Snapshot is taken after the VM Hardware Update, please let us know if this is defenitely the Case.

What is also possible is, that you have taken a snapshot directly after ugrading VM Hardware Version. If this is the Case please revert to that Snapshot. Start the VM, confirm the warning (with the default CMOS Values been written). Then shutdown OS and take a second Snapshot. Try to revert to second Snapshot to see if the error is gone. If error is gone delete the first Snapshot.

Updating VM Tools and VM Hardware are the only steps you need to do after you move VMs from older Hosts.

Best regards,

Bjoern

Re: Simplistic failover test for Virtual Centre

rothb — Thu, 20 Oct 2011 22:35:53 GMT

Hi Kevin,

you have to make sure that your SSL Certs, IP Address, hostname of the second vCenter Server are the same as on the first. Otherwise you have to reconnect all esx(i) hosts in case of a disaster to the new vCenter Server. Keep vCenter Server Versions in sync otherwise you will run into problems connecting to the DB.

This is a ugly way of implementing a failover vCenter with many manual steps to be taken, if you can afford you should try vCenter Heartbeat instead.

I didn´t recommend doing this.

Best regards,

Bjoern

Re: How to set up "Multi NIC vMotion" in vSphere 5?

rothb — Thu, 20 Oct 2011 11:31:27 GMT

Hello,

strange things happend. Our Cluster lost overnight the HA and DRS Settings. HA and DRS where disabled and after enabling HA and DRS again, the vMotion process now work fine, from and to the particular Host which didn´t vMotion anymore after enabling multi NIC vMotion.

So everything seems fine now.

Best regards,

Bjoern

Re: Questions about moving HA/DRS enabled hosts to a new vCenter server

rothb — Wed, 19 Oct 2011 12:59:12 GMT

Ok, that is normal behavior that the hosts show up disconnected. You have to reconnect all of them. DRS will not kick in because vCenter can not reach the other Hosts until reconnected. It is possible as soon as you reconnect the Hosts, that a few vMotions will occur.

To be safe you can make sure that the "host isolation response" option in "vSphere HA" -> "Virtual Machine Options" is set to "leave powered on".

Regards,

Bjoern

Re: Questions about moving HA/DRS enabled hosts to a new vCenter server

rothb — Wed, 19 Oct 2011 09:28:24 GMT

Hi Lou,

if I remember correctly the the Virtual Machines automatically will be placed in the Cluster Object if you add the ESX Server to the Cluster.

If you upgraded your vCenter to a new Version and pointed to the old DB and updated the DB, you should have all hosts under the Cluster Object (as before the upgrade) and you only have to reconnect the Hosts.

Best regards,

Bjoern