ACI - Failed to delete "Unmanaged Fabric Nodes"

[ju.mahieu]

Running version : 2.1(1h)

Hi,

I am unable to delete an "Unmanaged Fabric Node" entry. It was a catalyst Switch used for testing purposes. I don't know why this devices has been detected as a Fabric Node. Hence, how can I delete this 'fake' entry ?

I have tried 'modelete' and Gui without success.

Please find attached screenshot regarding the issue.

Any ideas ?

Thank you

Ju

[dpita]

Hello

Unmanaged Fabric Nodes are devices that ACI detects via CDP/LLDP and create entries using their management IP address. Its not that its detected as a Fabric Node, the name lets you know that its not managed by the APIC. Its a outside device that ACI needs to be aware of. 

In the case that you have a hypervisor behind those unmanaged devices, ACI should still be able to dynamically program VLANs as needed. This is the single hop away rule for VMM domains. Its the same if it was a blade switch chassis like a UCS Fabric Interconnect. 

The only way to remove the unmanaged device would be either to unplug it from the fabric and wait a certain timeout period OR disabled LLDP/CDP on the interface policy group related to the connected device. 

[ju.mahieu]

Thank you for the explanation.

Unfortunately, the device is not anymore connected to the Fabric. And the interface (1/10) is not associated to any policy group.

Do you have another suggestion ?

Regards

Ju

[Robert Burns · Accepted solution]

Please open a TAC case so we can track if this is a new/known bug.  We have a utility we can use to forcefully delete the object from the fabric's DB.

Robert

[ju.mahieu]

Thank you Robert.

The case has been opened -> 681728724

Ju

[ju.mahieu]

Robert,

FYI, the issue has been resolved by Denis from the TAC team :-)

Below the explanation :

It’s described in internal bug CSCuz97164

"When non-ACI products are connected to Leaf with LLDP enabled,  they can be seen as Unmanaged Fabric Node,   when they are disconnected from Leaf,   stale fabricLooseNode MO left there forever.”

Ju

[Robert Burns]

Thanks Ju -  I was JUST checking up on this minutes ago :)  I've asked Denis to make this bug externally visible.  By end of day, you'll be able to view this bug on the Cisco Bug Toolkit portal.

Regards,

Robert