Why this warning is appearing in the faults?

[FedeSaraullo]

Hello everyone!! I have configured a VMM domain on ACI and the following warning appeared, but the VMM domain is working fine.

F0467 -> configuration failed due a invalid path configuration.

I attached some captures of the configuration and alarms

Thanks in advance!

[Robert Burns]

Is it possible you have another EPG with a static path binding to the same ports connecting to VMM hosts?
One of the reasons for this fault is due to an encap being assigned to an EPG, but it doens't exist within the relevant domain/VLAN Pool assigned to the AEP.  If may not be a problem with your VMM config, but there could be another policy (EPG) trying to used a shared interface with your VMM host which is mis-configured.

Robert

[FedeSaraullo]

Hello Robert! I am not sure, but it can be. Let me ask to the customer.

Anyway, Can we do that?

Thanks for your attention!

[Robert Burns · Accepted solution]

Yes its fine, but there just needs to be the correct VLAN Pools assigned to the relevant domain, and EPG.

Ex.

Let's say you want both VMs and Physical hosts using the same EPGs and/or Interfaces.

You'd need two Domains

1. VMM_Domain_X

2. Physical_Domain_Y

Each Domain points to a VLAN Pool (VMM domains need dynamnic Pools, Physical should use static VLAN pools)

1. VMM_VLANs_X (100-199)

2. Physical_VLANs_Y (200-299)

Now if your host is doing both VMM integration & non-VMM integration (Perhaps you have an APIC managed DVS, but also have a vSwitch using static path bindings using the same Leaf Port), both of these domains need to be bound to a single AEP. 

When creating the static path binding, you have to manually assign the VLAN encap - which needs to fall within the range of your Physical Domain's static VLAN Pool.  If you happen to use encap 300 by mistake, it would raise that fault.

Not saying 100% this is your issue, but its one possibility.  Here's a diagram showing how the various policies tie together.

Robert