Perfect!!! Just scrolled over this document. I guess that convers everything, which was included in the old whitepaper. I'm still confused why this is not published as an "official" documentation in the corresponding listings ... anyway ... ... View more

Hey micgarc2, thanks for the explaination. I did this and got another error. My L3Out physical ports are trunks, consisting of routed sub-interfaces (muliple l3outs of different VRFs are using the same physical port...each VRF L3out has dedicated transit VLANs / typical firewall-on-a-stick design).   Fault delegate: Configuration failed for node <NODE-ID> due to Interface Configured as L3, debug message: port-configured-as-l3: Port has one or more layer3 sub-interfaces;   My Access Policy (infraAccPortGrp) just consists of a CDP and LLDP policy (both enabled) and the AEP, holding the l3 domain with the correct VLAN pool (containing the l3out transit VLAN IDs). ... View more

Just to follow up. For the mPod L3out I'm obiously hitting CSCvh06474 / CSCvb46222 This doesn't explain the errors for the other (non-mPod) l3outs ... View more

I second that.. I checked out Cobra, native JSON and Ansible. In terms of readability and low complexity, Ansible is (currently) my choice. The only thing that bugs me with the predefined ACI modules is the approach one HTTP post per object. So each EPG, contract, bridge domain, fabric policy etc. needs one HTTPS POST operation. When deploying a fabric from scratch, maybe this is time consuming. On the other hand, the pre built ACI modules only covers some parts of the ACI configuation. Currently I'm writing reusable roles using the aci_rest module. They are designed in a "bulky" manner - meaning you may post multiple childrens in of one instance in one go.   The challenge with Ansible is to figure out a proper way of doing and designing it. There are so (too) many ways to dead with things in Ansilble. Took me three fresh starts until I got the (hopefully) right structure for my use case. So it makes sense to think about the whole thing and structure it from the beginning before  programming a playbook.   One word to the ACI CLI (which could be used for automation as well)... don't do it ... it's a piece of crap for configuration, because it doesn't understand and populate the MO tree correctly. Very important ACI concepts like AEPs, policies etc. are not known by the CLI resulting in a config "mess". ... View more