Aep change in IPG - outtage ?

[prestigio391]

Hello guys.

We want create better granularity in ACI so  We want separate AEPs per Server and relate them to pdms. Those changes are related to many already created aep with wide range of vlan pools in pdm....Is there data flow affected with aep change in IPG..Removed/added with ansible...

Thanks for answer...

[RedNectar · Accepted solution]

Hi @prestigio391 ,

Firstly, I have no idea what pdms is (Google suggests Polydimethylsiloxane but I don't think you are using ACI to make polymers) but it probably doesn't matter - your question is

Is there data flow affected with aep change in IPG

[Edit: Just WHY you'd want to do this is a completely different discussion we could have.... but for now I'll just answer the question]

By the sound of it you already have the new AAEPs created and linked to the appropriate Domains and VLAN Pools. 

SO -

IF this is true (you already have the new AAEPs created and linked to the appropriate Domains and VLAN Pools)

AND there will be no change with VLAN ID for the linked EPGs

THEN you shouldn't have a problem.

I did a quick test and found that no pings were dropped when I changed the AAEP association for an Access Port Policy group that kept the same Domain associations.  You can see my testing here, but I had a problem with a browser cache and had to change browsers part way through - so there is a LOT of wasted time between 2:18 and 7:00 - just skip over that bit (If I wasn't lazy I'd edit it out. But I'm too lazy)

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.

---

[prestigio391]

Hello,Thank you so much  for answer.pdms - Physical domainS -- iam sorry iwll use physDom next time..

Becaus before this change was question: Is better create separate aep for service and provide changesto link physdom or vmmdom related to this aep and affec traffic

or is not neccesary do it this way and we can use one bigger aep for several interfaces in different services without worries

And big thanks for your video.Its clear and easy to understand result.

[RedNectar]

Hi @prestigio391 ,

I've just been cleaning up old emails and realised you put another question in there:

Is better create separate aep for service and provide changesto link physdom or vmmdom related to this aep and affec traffic or is not neccesary do it this way and we can use one bigger aep for several interfaces in different services without worries

Here are my Best Practices for AAEPs

1. Keep the number of AAEPs to a minimum, but implementing this might be different in every scenario
2. Remember, it is a way to group a lot of interfaces with similar traffic together,

so:

• One AAEP per tenant might work for Physical/L3 Domains, but if there are any interfaces that are shared between tenants you might put those in their own shared AAEP instead
• Similarly, one AAEP per VMM Domain might work - but if VMs are shared across multiple VMM Domains then you might consider using a shared AAEP
• IF NONE of your ESXi (or other hypervisor) hosts share trunk links with any Physical Domain, keep them in their own AAEP, especially if you use the Pre-Provision resolution immediacy option for when assigning EPGs to VMM Domains.

Every situation is different, so these are guidelines, not rules.