cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2158
Views
5
Helpful
1
Replies

AEPs and VLANs - need some clarifications

neroshake
Level 1
Level 1

Good morning all!

I would like to ask some help in making clear concepts of AEP and bindings.

1. Somehow I forgot to link AEP in IPG (attached 'no_AEP_in_IPG') and did static port binding for corresponding EPG. As a result the traffic flows correctly in EPG but in port status under Fabric Inventory no AEP is being listed (attached 'no_AEP'). However the VLAN for which static binding is configured is tied to physical domain which is associated to the AEP. The question is why AEP is not being displayed in port status?

 

2. I have another EPG which is also being static binded. In this case there is an AEP linked to the EPG and static port binding has been done under EPG settings. The thing is that for some ports I can see correct VLANs in Port Status page and for some other ports which are being connected the same way VLAN tab in port Statuses under Fabric inventory is empty (see attachment 'empty_VLAN'). Any idea why this can happen?


Thanks!
Nero

1 Accepted Solution

Accepted Solutions

Waruna Rasanga
Level 1
Level 1

Hi,

1. First thing you have to clear out that is in EPG, we are not define an attachable entity profile (AEP). what we are doing is assign a domain to the EPG. This domain is link to the AEP. This domain is the one which tie up ACI Physical construct (Interfaces) and the Logical Construct(EPGs). 

Therefore, even tough you have add domain in EPG and add static path toward interface by ecap the VLAN, the AEP will be not show in the interface if you are not add AEP to the policy which uses that interface. Interface will not inherit policy from the EPG since they are 2 different constructs.

 

2. In this scenario, if you have configured correctly by adding AEP to the interface policy group and add domain to the EPG, bellow can be some reason not showing the VLANs

  a. encap VLAN is not define in the VLAN Pool.

  b. VLAN pool is not defined in the correct Domain

  c. Domain not assigned to correct AEP

you can verify these with the faults which raised in the EPG

 

Hope this is helpful to clear your question

 

Thanks

Waruna

View solution in original post

1 Reply 1

Waruna Rasanga
Level 1
Level 1

Hi,

1. First thing you have to clear out that is in EPG, we are not define an attachable entity profile (AEP). what we are doing is assign a domain to the EPG. This domain is link to the AEP. This domain is the one which tie up ACI Physical construct (Interfaces) and the Logical Construct(EPGs). 

Therefore, even tough you have add domain in EPG and add static path toward interface by ecap the VLAN, the AEP will be not show in the interface if you are not add AEP to the policy which uses that interface. Interface will not inherit policy from the EPG since they are 2 different constructs.

 

2. In this scenario, if you have configured correctly by adding AEP to the interface policy group and add domain to the EPG, bellow can be some reason not showing the VLANs

  a. encap VLAN is not define in the VLAN Pool.

  b. VLAN pool is not defined in the correct Domain

  c. Domain not assigned to correct AEP

you can verify these with the faults which raised in the EPG

 

Hope this is helpful to clear your question

 

Thanks

Waruna

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

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