cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
8931
Views
1
Helpful
3
Replies

Error 4067 Invalid Path Configuration,Invalid VLAN Configuration

Trinh Nguyen
Level 1
Level 1

I created a new EPG “NEW” and Vlan for VM team, adding Leaf interfaces to them.  All of these port threw me error code 4067 due to Invalid Path Configuration,Invalid VLAN Configuration. 

First I thought it is a piece of cake, which I have been there done that, but I could not locate this error this time. 

I know they are NOT invalid VLAN because I created VLAN and checked the AAEP to make sure this VLAN is there

I know they are NOT invalid path because these ports are in production and they are working without error in another EPG named “SERVER”

These ports are NOT in port channel

These ports are in leaves, not in FEX

 

This CLI for one of the ports with this error

APIC1# show running-config leaf 111 int eth 1/11
# Command: show running-config leaf 111 int eth 1/11
# Time: Thu Dec 21 08:15:46 2017
  leaf 111
    interface ethernet 1/11
      # policy-group Switch111-112_BU-DD02_PolGrp
      switchport trunk allowed vlan 99 tenant Production application AP-Prod epg NEW
      switchport trunk native vlan 1502 tenant Production application AP-Prod epg SERVER
      exit
    exit
APIC1#

I am looking for suggestions to get rid of this error.  My ACI version 2.2(1o)

Best Regards,

 

1 Accepted Solution

Accepted Solutions

RedNectar
VIP Alumni
VIP Alumni

Hi Trin,

You haven't linked the EPG to the Physical Domain yet

 

Tenant > YourTenant > Applicaiton Profiles > YourApplicationProfile > Application EPGs > YourEPG > Domains (VMs and Bare Metals) >+ Add Physical Domain Association.  Select the Physical Domain you created for the VLANs you mapped to the EPG. [>+ means Right-Click]

 

Job done. I hope.  If not check out the wierd thing that happened to me one day, where I had the same problem.

 

I hope this helps

 



Don't forget to mark answers as correct if it solves your problem. This helps others find the correct answer if they search for the same problem


 

 

RedNectar aka Chris Welsh.
Forum Tips: 1. Paste images inline - don't attach. 2. Always mark helpful and correct answers, it helps others find what they need.

View solution in original post

3 Replies 3

RedNectar
VIP Alumni
VIP Alumni

Hi Trin,

You haven't linked the EPG to the Physical Domain yet

 

Tenant > YourTenant > Applicaiton Profiles > YourApplicationProfile > Application EPGs > YourEPG > Domains (VMs and Bare Metals) >+ Add Physical Domain Association.  Select the Physical Domain you created for the VLANs you mapped to the EPG. [>+ means Right-Click]

 

Job done. I hope.  If not check out the wierd thing that happened to me one day, where I had the same problem.

 

I hope this helps

 



Don't forget to mark answers as correct if it solves your problem. This helps others find the correct answer if they search for the same problem


 

 

RedNectar aka Chris Welsh.
Forum Tips: 1. Paste images inline - don't attach. 2. Always mark helpful and correct answers, it helps others find what they need.

Done, many thanks Chris!

Manuel Velasco
Cisco Employee
Cisco Employee

Hi Trinh,

 

How did you add this vlan to the EPG?   Are you doing static for those interfaces or are you doing it from AAEP, or this is part of a vmm integration?

 

Did you add the proper domain to the EPG?

 

Can you double click on the fault and provide a screenshot with the full description?

Review Cisco Networking for a $25 gift card

Save 25% on Day-2 Operations Add-On License