Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi All,We have a MultiPod fabric with multiple L3Outs and wish to enforce contracts consistently between EPGs and hosts external to the fabric. For example; an administrator on the access layer external to the fabric registers the IP address of their...
Hi All, Just wondering if many people out there are using subject and EPG labels within Cisco ACI to enforce policy? They seem like a really neat and powerful idea, however I'm finding that the lack of in-depth documentation combined with the number ...
Hi,
Since upgrading to APIC v3.0(1k), the topology of a Pod is no longer displayed under the Fabric -> Inventory screen.
Using the API inspector tool when viewing this page, no API calls appear to be made to retrieve the fabric:Link object which ...
Hi All,
In writing some scripts to retrieve fabric utilisation data (i.e. the data in the Capacity Dashboard screen) so that we can integrate the same into our monitoring system, I'm trying to figure out from where the upper limit values for BD and...
Hi All, I have a Multipod environment containign two pods that is operating nominally. After some thought on future expansion considerations, we decided to renumber the node IDs in the second pod to accomodate future expansion. After doing so, our m...
Thanks Dan, I can't believe that it was as simple as configuring the external network under a single L3Out only.I noticed that the section to which you referred in the best practices guide has been slightly revised to clarify this behavior when compa...
Hi Jayesh,Thanks for the reply.We have previously considered placing all connections under a single L3Out as this appears to be the only way in which to consistently enforce policy for an external network, however (as mentioned previously) the reason...
Hi Jayesh, What we are trying to achieve by using two different L3Outs within the same VRF is some level of traffic engineering for each pod in the fabric. Essentially, in our fabric each pod can be thought of as equivalent to a datacenter and with ...
Hi Jayesh,Thanks for the reply explaining the behaviour - per my original question; is there any way in which to consistently enforce contracts for external EPGs when using multiple L3Outs?Cheers,-Luke
I'm currently encountering the same concerns as the posters above regarding the warning message as it would appear to unambiguously indicate that any interfaces associated with EPGs that are associated with the BD will bounce.
Consequently, as almo...
