Connectrix: SANnav discovered hosts with same FDMI name in the fabric discovery than vCenter discovery
Summary: SANnav discovered several hosts with the same FDMI name in the fabric discovery than vCenter discovery.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Error:
Source Address x.x.x.x
Description ESXi Host "xxxxx" discovery failed.
Actions: Check the same FDMI names of the hosts in the fabric and correct it to match the vCenter discovered hosts.
Cause
Probable Cause: discovered several hosts with the same FDMI name in the fabric discovery than vCenter discovery.
The problematic ESXI host ports would be mapped to other enclosures by the customer.
Broadcom will verify these using logs.
These host ports were mapped back to the original enclosures ('xxxxxx') which made those problematic ESXI hosts as part of a manual enclosure.
ESXI host discovery fails due to a conflict.
The vCenter discovery marks the ESXI hosts as a conflict if any of the ports are moved to the manual enclosure.
The problematic ESXI host ports would be mapped to other enclosures by the customer.
Broadcom will verify these using logs.
These host ports were mapped back to the original enclosures ('xxxxxx') which made those problematic ESXI hosts as part of a manual enclosure.
ESXI host discovery fails due to a conflict.
The vCenter discovery marks the ESXI hosts as a conflict if any of the ports are moved to the manual enclosure.
Resolution
Workaround: Delete the concerned vCenter and discover it again.
Resolution: Upgrading ESXi hosts that previously reported the problem (to 7.0.3 build 21424296) resolved the issue and are now listed as Monitored in SANnav.
The upgrades resolved the issue. This is because the manual enclosure associated with the two hosts was deleted.
When they rejoined the fabric, SANnav added them into a new auto enclosure.
Resolution: Upgrading ESXi hosts that previously reported the problem (to 7.0.3 build 21424296) resolved the issue and are now listed as Monitored in SANnav.
The upgrades resolved the issue. This is because the manual enclosure associated with the two hosts was deleted.
When they rejoined the fabric, SANnav added them into a new auto enclosure.
Article Properties
Article Number: 000218608
Article Type: Solution
Last Modified: 21 Nov 2025
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.