11-23-2023 09:47 AM - edited 11-23-2023 09:48 AM
First of all, I have been design and implementing ACI for a number of years now and I still find the overall monitoring setup is totally confusing within APIC...
I have this simple question: Under Fabric -> Fabric Policies -> Policies -> Monitoring, there are two sub-menus: Common Policy and default... What are the difference between the two and when to use each for monitoring configuration?
According to help guide, the Common Policy is the monitoring policy model for the common semantic scope, which is used when there is no corresponding policy under the more specific infra or tenant scopes. In such cases, these policies are used throughout the fabric except for objects attached to their own specific policies.
But honestly, this sounds like what the default is supposed to be for me...
Any advices?
Solved! Go to Solution.
11-24-2023 05:12 AM - edited 11-24-2023 05:15 AM
There are three heirarchies you can apply policies to in ACI: Access Policies, Fabric Policies & Tenant Policies.
Within each of these heirachies (Access, Fabric, Tenant) there is a default monitoring policy which as you know contains the initial values for any policies created within that respective heirarchy. This would be used if/when you wanted to create a monitoring policy for ONLY Access Policies OR Fabric Policies OR Tenant level.
If instead you want a fabric-wide monitoring policy, that applies across ALL heirarchies, this is where the "Common" monitoring policies comes in. Think of this askin to the "common" tenant logic, but applies for monitoring policies across the entire fabric (access/fabric policies & tenant)
Fabric Wide: includes both fabric and access objects <<< Fabric Policies - Monitoring - Common PolicymonCommonPol
(uni/fabric/moncommon): applies to all fabric, access, and tenant hierarchies
Access (also known as infrastructure): access ports, FEX, VM controllers, and so on <<< Access Policies - Monitoring - default
(uni/fabric/monfab-default): applies to fabric hierarchies
monFabricPol
Fabric: fabric ports, cards, chassis, fans, and so on <<< Fabric Policies - Monitoring - default
(uni/infra/monifra-default): applies to the access infrastructure hierarchy
monInfraPol
Tenant: EPGs, application profiles, services, and so on <<< TenantX - Monitoring - defaultmonEPGPol
(uni/tn-common/monepg-default): applies to tenant hierarchies
Hope this helps,
Robert
11-24-2023 05:12 AM - edited 11-24-2023 05:15 AM
There are three heirarchies you can apply policies to in ACI: Access Policies, Fabric Policies & Tenant Policies.
Within each of these heirachies (Access, Fabric, Tenant) there is a default monitoring policy which as you know contains the initial values for any policies created within that respective heirarchy. This would be used if/when you wanted to create a monitoring policy for ONLY Access Policies OR Fabric Policies OR Tenant level.
If instead you want a fabric-wide monitoring policy, that applies across ALL heirarchies, this is where the "Common" monitoring policies comes in. Think of this askin to the "common" tenant logic, but applies for monitoring policies across the entire fabric (access/fabric policies & tenant)
Fabric Wide: includes both fabric and access objects <<< Fabric Policies - Monitoring - Common PolicymonCommonPol
(uni/fabric/moncommon): applies to all fabric, access, and tenant hierarchies
Access (also known as infrastructure): access ports, FEX, VM controllers, and so on <<< Access Policies - Monitoring - default
(uni/fabric/monfab-default): applies to fabric hierarchies
monFabricPol
Fabric: fabric ports, cards, chassis, fans, and so on <<< Fabric Policies - Monitoring - default
(uni/infra/monifra-default): applies to the access infrastructure hierarchy
monInfraPol
Tenant: EPGs, application profiles, services, and so on <<< TenantX - Monitoring - defaultmonEPGPol
(uni/tn-common/monepg-default): applies to tenant hierarchies
Hope this helps,
Robert
11-24-2023 05:19 AM
Thanks @Robert Burns! Appreciated! Wish all ACI documents are this easy to read
Copied and Saved!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide