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.
See published document here: https://www.cisco.com/c/en/us/support/docs/cloud-systems-management/application-policy-infrastructure-controller-apic/200964-Configure-Access-Polices-Static-Binding.html
Hi,
The naming convention can be mostly found in this doc: https://www.cisco.com/c/en/us/products/collateral/switches/nexus-9000-series-switches/white-paper-c11-739134.html#_Toc484532920
Following the naming conventions for the Cisco Nexus 9000...
Hi Marcelo,
In my opinion, configuring the interface under the Access Policies is the best method. It allows you to reuse policies and customize your configuration. In addition, you will be able to track down the objects you created and understand ...
Hi Serhii,
Although you were able to get it to work, please be aware that this is not a Cisco supported method for VMM integration. If anything was not to work in the future, we would not be able to resolve the issue without you creating the DVS via ...
Hi Serhii,
Unfortunately, you cannot have the APIC manage existing vDS. However, you can still connect your existing vDS into ACI by using static paths, just like any other server.
The APIC can only manage DVS/AVS created from the VMM Domain.
Thanks,...
Hi Ziad,
Endpoint tables are local to each switch. So if you view an endpoint table from one switch, you will only see the locally attached endpoints. Therefore, when you run the command on a spine, you will not see any endpoints since there are no e...
