HCI 6.11.3 beta pre-upgrade check failed due to undetected network interfaces

MartinL Lv1Posted 2026-May-13 10:06

Hi all,

I ran HCI Upgrade Navigator 1.0.26 to perform pre-upgrade check. The check failed with error below and disallowed upgrade:

Cause: [node_ip_addr] Network interface eth10 eth11 not detected, posing a risk of network disconnection after the upgrade.
Solution: It is recommended to troubleshoot the cause of the uninitialized network interface according to the KB link: /cases/list?product_id=33&type=1&category_id=30797. Please resolve the issue before proceeding with the upgrade.

Nodes > Physical Interfaces showed eth10/11 with Driver Type unknown and I think the 2 interfaces didn't exist anymore.

How may I fix or skip the error and continue with the upgrade?

Best Regards,
Martin

pbeugenio has solved this question and earned 20 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

you can create ticket with TAC and include the pre-upgrade check error
Is this answer helpful?
Prosi Lv3Posted 2026-May-13 12:34
  
The pre-upgrade check still lists the old NIC in the HCI database/configuration, even though the physical interfaces (eth10, eth11) are no longer present on the node.
Upgrade Navigator blocks the upgrade, believing those NICs might be needed for cluster networking after a reboot.
- Physically remove/replace NICs
- BIOS/PCI enumeration changes
- Mellanox/Intel card interface numbers changed in firmware
- Legacy bond/vSwitch mappings still refer to eth10/eth11
- Historical NIC records persist after hardware migration
pbeugenio Lv2Posted 2026-May-13 13:22
  
you can create ticket with TAC and include the pre-upgrade check error
Zonger Lv5Posted 2026-May-13 18:43
  
This is a real upgrade blocker not a harmless warning. The pre-upgrade check is flagging stale physical-interface records for eth10/eth11 as a possible post-upgrade network-disconnection risk and Sangfor's HCI docs show that physical interfaces can be added, deleted or edited in the Edge settings so the right fix is to remove or correct those obsolete NIC mappings in the HCI UI and then rerun the pre-upgrade check until it passes. There is no skip option for this specific check so if the old NIC entries cannot be reconciled cleanly the safe path is to open a TAC case with the exact precheck error rather than forcing the upgrade.
net_specialist Lv2Posted 2026-May-14 07:34
  
thank you for the information
Doll Lv2Posted 2026-May-14 13:09
  
This is not a trivial warning, but a true upgrade barrier. Stale physical-interface records for eth10/eth11 are being flagged by the pre-upgrade check as a potential post-upgrade network-disconnection risk. According to Sangfor's HCI documents, physical interfaces can be added, removed, or modified in the Edge settings. Therefore, the best course of action is to remove or update those outdated NIC mappings in the HCI UI before rerunning the pre-upgrade check until it passes. Since this particular check has no skip option, it is safer to create a TAC case with the precise precheck issue rather than forcing the upgrade if the old NIC entries cannot be reconciled neatly.
Newbie A4 Lv1Posted 2026-May-20 00:00
  
This is a real upgrade blocker not a harmless warning. The pre-upgrade check is flagging stale physical-interface records for eth10/eth11 as a possible post-upgrade network-disconnection risk and Sangfor's HCI docs show that physical interfaces can be added, deleted or edited in the Edge settings so the right fix is to remove or correct those obsolete NIC mappings in the HCI UI and then rerun the pre-upgrade check until it passes. There is no skip option for this specific check so if the old NIC entries cannot be reconciled cleanly the safe path is to open a TAC case with the exact precheck error rather than forcing the upgrade.
MartinL Lv1Posted 2026-May-26 10:00
  
Thanks everyone. I’ve opened a support ticket, and a TAC engineer assisted in removing the two non-existent physical interfaces. I was then able to proceed with the upgrade, which completed successfully.

I Can Help:

Change

Board Leaders

George ...

Weekly Advisers

George ...

Weekly Sharers