但是一台测试台式机7.0的网卡没驱动，蛋疼，只能买网卡。
另外一台X3250不支持6.7 8169922更高版本，
这个是逼着升级7.0啊，博通这个是要往死里整我们这些穷屌丝啊。。。
Upgrading vCenter Server 7.0 fails during precheck with "Host(s) were found in the vCenter Inventory, that are potentially problematic for a vCenter upgrade"
Upgrading vCenter Server 7.0 fails during precheck with "Host(s) were found in the vCenter Inventory, that are potentially problematic for a vCenter upgrade"
Article ID: 318867
Updated On: 05-20-2024
Products
Issue/Introduction
Upgrading to vCenter Server 7.0U3c+ now requires an additional precheck. This precheck ensures that the ESXi hosts managed by the vCenter Server are at the correct ESXi versions and will not have any issues related to driver conflicts. There are two situations that can cause the vCenter precheck to fail:
ESXi hosts running 7.0 U3/U3a exist anywhere in the VC inventory
ESXi hosts running 7.0 U2c/U2d exists in a vSphere Lifecycle Manager (vLCM) image-enabled cluster
If the precheck detects versions of ESXi that could potentially have dual i40en driver conflicts, a more detailed check of these hosts is automatically triggered to detect if the dual-driver condition truly exists on the hosts flagged by the VC precheck.
Note that the precheck will fail and an error similar to the below will be reported in the VMware vCenter VAMI.
(Please see KB 87319 for details on the errors reported by the CLI upgrade option)
Environment
VMware vSphere ESXi 7.x
VMware vSphere ESXi 7.0.3
VMware vCenter Server 7.0.3
Resolution
Option 1 (Recommended)
Upgrade the hosts listed in dual_driver_check_faulty_hosts_<timestamp>.txt to 7.0 U3c+ with an ISO upgrade baseline (refer to Related information section of the Knowledge Base article - Post vSphere 7.0 Update 3c Notes for ESXi releases with no ISO) or vLCM image before upgrading the vCenter Server. Although this is not the normally recommended order, it's necessary for this circumstance and fully supported by VMware. The hosts must be upgraded using an ISO image instead of a rollup patch baseline in vSphere Lifecycle Manager.Also note that ISO import depend on respective VC version.Upgrading ESXi using an ISO Upgrade Baseline
Download the ISO image via the VMware Downloads Portal in Customer Connect.
Upload the ISO into the Lifecycle Manager Depot.
Create a baseline that uses the imported ISO image.
Upgrade the host using the ISO baseline.
Repeat this for every host listed in the /var/log/vmware/applmgmt/dual_driver_check_faulty_hosts_<timestamp>.txt file generated by the script.
Once all affected hosts are corrected, restart the upgrade process.
Please review the documentation for Using vSphere Lifecycle Manager Images to find instructions on upgrading the hosts via a vLCM desired-state image.
Repeat this for every host listed in the /var/log/vmware/applmgmt/dual_driver_check_faulty_hosts_<timestamp>.txt file generated by the script.
Once all affected hosts are corrected, restart the upgrade process.
Option 2
Alternatively, you can manually correct the i40en driver conflict on each host before restarting the upgrade. This isn’t the recommended option because the precheck will fail one more time before being able to upgrade. To understand why, see the precheck flowchart in Related Information.Put the ESXi host in maintenance mode, then run the following command from an SSH session to remove the obsolete i40enu VIB :
Once the VIB has been removed, reboot the ESXi host.
Repeat this for every host listed in the /var/log/vmware/applmgmt/dual_driver_check_faulty_hosts_<timestamp>.txt file generated by the script.
Once all affected hosts are corrected, restart the upgrade process
Important Upgrade Notes
2. Once vCenter has been upgraded, it's important NOT to use the non-critical patch baseline to upgrade any hosts that are 7.0 GA - 7.0 U3a, as it has the potential of re-introducing the issue or fail during remediation with an esxupdate error. Ensure that an image-based upgrade baseline or the predefined critical host patch baseline is used to upgrade them. A banner has been added on the Updates tab as a reminder of this.
Additional Information
Background
This issue originated when the Intel driver was renamed to i40enu in ESXi 7.0u2 and back to i40en in 7.0u3. During those renames, the relationship between the drivers was not created correctly, which led to both drivers being present on the same system. These conflicting drivers would cause solutions that installed agent vibs to fail, such as HA, WCP, and NSX on the hosts. The fix for this problem is included in ESXi 7.0 U3c. However, because these agent vibs can be pushed to the ESXi hosts as soon as vCenter gets upgraded, this issue would still manifest during the normal upgrade order (vCenter -> ESXi), as the ESXi hosts may still be running affected versions.
The vCenter precheck was created to notify users whether potentially affected ESXi versions existed in the vCenter inventory pre-upgrade. The automated script was added to help users narrow down the scope of truly affected hosts, so they can remediate the issue by either upgrading them or manually removing the duplicate i40enu driver.
For other information related to this issue see:
Post vSphere 7.0 Update 3c Notes –
The scenario mentioned in the Details section of this KB, is applicable to future vSphere 7.0 patch releases post 7.0 Update 3c.
If the source system is of version between ESXi 7.0 Update 2 and Update 3c, before upgrading to future vSphere patch release, ensure VMware vCenter server upgraded to 7.0 Update 3c or later to avoid potential vSphere HA failure due to dual i40en driver conflicts condition.
The above solution section is applicable for all 7.x future patch releases regardless of patch being ESXi-only or VC-only or both, but with additional instructions to Solution 1 as applicable:
In case of *no* ISO deliverable in the target ESXi patch post 7.0 Update 3c, then follow either of the options below:
Create custom/stock ESXi ISO using the target ESXi patch ZIP bundle referring to the steps mentioned in the Create a Custom ESXi ISO Image with PowerCLI Cmdlets documentation.
In vSphere Lifecycle Manager, use Baseline Group upgrade method to create and combine the baselines as described below:
Create baseline say “baseline-A” of ESXi ISO (custom/stock) from the last release (example: ESXi 7.0 Update 3d)
Create baseline say “baseline-B” of target ESXi patch using rollup
Create baseline Group say “ baselineGroup-C” to combine baselines – “baseline-A” and “baseline-B”
Remediate the baseline group “ baselineGroup-C” against the intended ESXi hosts or Cluster.
推荐本站淘宝优惠价购买喜欢的宝贝:
本文链接：https://hqyman.cn/post/6594.html 非本站原创文章欢迎转载，原创文章需保留本站地址！
微信支付宝扫一扫，打赏作者吧～休息一下~~
官码2024000195号
萌ICP备20248119号
