Symptom
Consider a scenario wherein a DCNM-managed fabric has two devices (hostnames Leaf-10 and Leaf-250) with duplicate management IP addresses. While the duplicate IP address scenario exists, DCNM will intermittently detect both Leaf-10 and Leaf-250 within the Fabric Builder interface. Once the duplicate IP address scenario is resolved (meaning, one of the management IP addresses is changed to a unique value), DCNM will only detect the presence of the duplicate device (Leaf-250) instead of the device that owns the IP address (Leaf-10).
While in this state, DCNM is unable to apply configuration to the original device (Leaf-10) nor the duplicate device (Leaf-250).
Conditions
1. DCNM is managing a fabric
2. A duplicate management IP address scenario previously existed in a DCNM-managed fabric involving two devices that can be managed by DCNM.
Workaround
Removing the duplicate device (Leaf-250 in this scenario) from the DCNM fabric and re-adding the device will resolve this issue. This is a disruptive workaround, as the relevant device re-added to the fabric (Leaf-10) is reloaded.
