Layer 3 network issues

[roysm]

Hi

I am working on creating an L3 external routed network. Everything is fine until I add the logical interface profile. This is a test environment at the moment, so I have a single interface from a leaf to a 3560 switch. Once I add the interface profile I get the following fault

F0467

Configuration failed for uni/tn-CCC/out-DC-Test-L3-Out/instP-Test-L3-NW node 101 eth1/48 due to Invalid Path Configuration

I have the connection between the leaf and 3560 configured with /30 ip addresses. Both switch and leaf can ping each other.

The epg has an external routed domain attached to it so I'm not sure what it means by invalid path. Can anyone shed any light on this for me please?

Many thanks

Roy

[stcorry]

Hello Roy! 

There can be a couple of things here. For L3 Externals, this Fault is just cosmetic, it doesn't actually prevent the configuration of the resources unlike the same type of fault for a regular EPG (usually). 

The first thing I would check is if the L3 External Domain is applied to the port by being associated with an AAEP that is applied through a Port-Group.  

[roysm]

I am trying to run OSPF over this connection and the adjacency fails to come up. I suspect it is because of a misconfiguration somewhere but I'm not sure where. 

When I create the port association, I get new messages complaining about a conflict with the L3 config and the fact that the port is L2. The message makes sense to me in that in one area I set an IP address on the interface and but to do the assoication I seem to have to assign a vlan. 

I'm obviously doing something wrong here, so any help would be great.

Thanks

[Mr. Vega]

Hello Roy! There should be no need to assign a VLAN on a L3 Port configuration. Where have you configured the VLAN on the Port configuration?

[Tomas de Leon]

Thank you for using the Cisco Support Community for ACI.  As some have already mentioned, please verify your configuration:

• Is EPG is related to any domains? If so is it related to the correct domain?
• The domain associated with the EPg is not allowed to use the specified encap. Check the Attachable Profile and VLAN/VXLAN Namespace (fvns:VlanInstP and fvns:VxlanInstP) configurations associated with the domain
• Check Access Policies for this interface profile (vlan pool, AEP, Domains, etc)
• Is Port is Member of Port Channel or missing VPC member?
• Is there a Domain associated?

[roysm]

I did manage to get this resolved in the end by removing the config objects and recreating the connection. I must have been missing a step, as this time it all worked.