Deletion of default BD in 'common' Tenant and Path Errors

[petar.forai1]

Hi,

As part of exploring our ACI infra eval and playing around, we've deleted the default bridge domain in the 'common' tennant. This generated fault events in the tenant about invalid paths (in this case this is an Cisco UCS attached). I'm not sure what 'Invalid Path Configuration' means here, because the port groups [pg-UCS-FI-1/2] -- removed the other FI PG as part of shotgun debugging -- don't reference any BD. 

My question now is how are BDs related to external L2 physical domains (like an UCS or a bare metal server) and if there's a way to restore the default BD in the common tenant? Or what do I have to change to get rid of this?  The EPG 'Services' here uses a different BD actually.

I'm running 1.1(3f) on the APIC and 11.1(3f) on the N9Ks.

Affected Object:

topology/pod-1/node-101/local/svc-policyelem-id-0/uni/epp/fv-[uni/tn-common/ap-AP-Services/epg-EPG-Services]/node-101/stpathatt-[pg-UCS-FI-1]/nwissues

Description:
Configuration failed for uni/tn-common/ap-AP-Services/epg-EPG-Services node 101 pg-UCS-FI-1 due to Invalid Path Configuration

[petar.forai1]

OK, I think I figured it out. I didn't have the physical domain associated with the EPG and the deletion of the default BD in the common tenant has nothing to do with this at all. I just noticed the fault after the deletion of the BD AFAIR.

[Robert Correiro · Accepted solution]

Hi petar.forai1,

You are correct. The "Invalid Path Configuration" fault is raised when there isn't a Physical Domain associated to an EPG using static paths.

As for restoring the default BD in the common tenant, you will have to create a new Bridge Domain and give it the name default. There isn't a special procedure to restore "default" policies.

Hope this helps.