Skip to content

Commit cc4e952

Browse files
committed
Troubleshooting FAQ: CDC devices exposed by some BMCs
Signed-off-by: Dmitry Tantsur <[email protected]>
1 parent be4c688 commit cc4e952

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed

docs/user-guide/src/troubleshooting.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -159,6 +159,28 @@ You have options:
159159
- Update your BareMetalHost definition with the `bootMode` value that matches
160160
what your hardware supports.
161161

162+
### Duplicate network interfaces
163+
164+
If inspection succeeds on a subset of the hosts and fails for the rest, and you
165+
see the following message in the Ironic logs:
166+
167+
```text
168+
DuplicateNodeOnLookup: Multiple nodes with port addresses [...] were found
169+
```
170+
171+
there may be at least two different reasons for that:
172+
173+
1. One host has `bootMacAddress` from a wrong host.
174+
1. Hosts have virtual network devices with a hardcoded MAC address (the same
175+
for all of them).
176+
177+
The latter is a common case with virtual devices provided by BMCs. Such devices
178+
are represented to the operating system similarly to USB ethernet dongles. They
179+
use drivers like `cdc_ether` or `cdc_ncm`, and names like "HPE Virtual NIC
180+
(NCM)". You should disable these devices in the BMC. Not only do they break
181+
inspection, they may provide local users of the machine with direct access to
182+
the BMC.
183+
162184
## Provisioning errors
163185

164186
Errors during provisioning will be visible when listing the BareMetalHosts:

0 commit comments

Comments
 (0)