Dear,
1.
Sorry for the trouble. I just tried and it seemed to find the correct server (33818) for me. Could you please let me know the ESXi version that is currently running? I tried a few versions randomly.
Just in case, you may have incorrect info in the cache, could you please try the "-c" option to clean your cache?
2.
No, the CPU feature validation and BIOS version check are separated. it just means the specified CPU series is not certified for the server.
Thanks,
Heejeong
Hi Heejeong,
1. No trouble at all. We are running 5.5 build 2068190. I have reran the script with -c option. It's still picking server ID 19267. This server has BIOS 2.2.10. Another host in the cluster has BIOS 2.7.0 (running same version ESXi) and it's reporting all okay (compatible with 6.5.0 U2).
2. That's interesting. So VCG lists this CPU series (server id 33818) and it states it's certified. Why does script claim that CPU series is not supported? This is on server with BIOS 2.2.10. On the server with more recent BIOS version (2.7.0) it's reported all good.
I've been asked to confirm hardware compatibility with 6.5.0 U2 so just wanted to be absolutely sure before we start the upgrades.
Thanks,
Ermin
Dear Ermin,
Could you please clean your cache and try again? The fix has been deployed.
Thanks,
Heejeong
Works great! Many thanks.
[SERVER: OK] Server 'PowerEdge M620' is compatible for ESX 6.5.0 U2
[IO: Warnings] Some IO devices may not be compatible for ESX 6.5.0 U2
Compatibility issues:
- Server Model 'PowerEdge M620' with Intel Xeon E5-2600-v2 Series (ID:33818 ) is certified
but Certified BIOS versions are higher than 2.2.10
More information: http://www.vmware.com/resources/compatibility/detail.ph p?deviceCategory=server&productid=33818
Thanks, Ermin!
I looked into more and it seemed a bug in the validation code.
I will get back to you with the fix. Sorry for the trouble.
Heejeong
This is amazing. Excited to check it out.
I'm running into an issue where the vcenter box this is running on runs multiple services. vCenter is not the default port, but another service is. It must be running a thumbprint check on the default port, but then afterwards use the specified port because the connection process fails due to mismatching thumbprints. I would imagine this situation is unique in that the default port service is indeed running, but just for another service.
This is the output(with thumbprints removed):
[ERROR] Caught VMODEL fault : Server has wrong SHA1 thumbprint: (otherservicethumbprint) (required) != (vcenterthumbprint) (server)
Any thoughts? I tried manually editing the ras_hosts file as well and that didn't allow me through.
Thanks!
I may have solved this by replacing the hard coded port in line 48 of the sshcert.py to my custom port. I can get to the authentication part at least. I will trial run later today.
I did try the -n option and it didn't allow me past the thumbprint issue I was having. I tried clearing the ras_host file, manually editing it, etc while doing so in multiple combinations just in case my tinkering messed with something.
However, manually changing that port DID resolve my issue. I'm happily looking at a report right in front of me.
Thank you so much!
This is really useful, is this API publicly available by any chance? I'm in the process of automating a driver/firmware check for our physical hosts, this script gives me the hardware and driver check but if we can get the compatible firmware included then it'd be perfect.
Hi,
My python -m pip install pyvmomi fails even my pc is connected to the internet any idea?
Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None))
after connection broken by 'ProxyError('Cannot connect to proxy.', OSError('Tun
nel connection failed: 407 Proxy Authentication Required'))': /simple/pyvmomi/
Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None))
after connection broken by 'ProxyError('Cannot connect to proxy.', OSError('Tun
nel connection failed: 407 Proxy Authentication Required'))': /simple/pyvmomi/
thank you :-)
Dear amine,
It seems that you need the proxy server setting
set http_proxy=http://username:password@proxyAddress:port
or in pip.ini
...
[global]
proxy = [proxy address]:[proxy port]
...
Also, please refer to the video from David: https://youtu.be/ataRS4I4dvs
Thanks,
Heejeong
Very useful tool.
I'm running the script against Poweredge M620 server with Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz CPU.
The script is reporting:
Compatibility issues:
- Server Model 'PowerEdge M620' with Intel Xeon E5-2600 Series (ID:19267) is certified
but current CPU Series (features:0x306e4) is not supported
Certified BIOS versions are higher than 2.2.10
More information: http://www.vmware.com/resources/compatibility/detail.php?deviceCategory=server&productid=19267
Q1. I believe the script got the wrong entry in VCG (should be https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=server&productid=33818 since it's v2 CPU).
Q2. I'm curious about 'current CPU Series is not supported' statement. Is that because it's not running certified BIOS version?
Many thanks.