I am having the same issue.. But it's not credential related.. $ python aci-doc.py Traceback (most recent call last):   File "aci-doc.py", line 4, in <module>     import cobra.mit.access ImportError: No module named cobra.mit.access I've searched and I don't appear to have this module anywhere..  Does anyone know a location to download it from? I've seen it on "ReadTheDocs" website, but nothing official that I can find on Cisco. ... View more

stcorry, It maybe trivial to you, but customers that don't have the technical prowess that yours did or do will look at you and ask, "I'd like this simpler so we can adapt over time" something your construct does not provide.  As such, your view of trivial is not aligned with theirs when they are taking what they view to be is a "leap-of-faith" to getting to a structure that they already know and then migrating over to newer configurations and capabilities. Now if your answer and the other Cisco people in this thread is "Well we can't do that way cause we're limited to doing it like this" then fine, we can explain that and tell them about this "limitation". ... View more

Ipember, The reason for this is somewhat simple. Say I have a customer that has two set's of switches which are span across to one another and both have the same VLAN's Normally the host devices in each VLAN always talk to one another and hosts in other VLANs.. In order to make the migration to ACI smoother, I would extend the infrastructure into the fabric and have the fabric become the Layer 3 gateway for each inbound.  Then simply a single EPG can be created to put all of the hosts in for the time being while they are migrated over.. Then I don't need to use 4+ interfaces across the the fabric to bring them into the network and I don't have to have multiple EPG's upfront for this migration activity. This allows for a quicker migration for customers that may have older sketchy Cisco hardware that is going EoL and then want to get the initial migration steps started without making it complicated. ACI based on what I ready, makes it complicated and customers don't think that it should. IMHO this should be a simple exercise to perform and use a limited number of interfaces and configuration..  L8r ... View more

So in essence, if we have an external Layer 2 switch that has hosts on two separate VLANs (503 & 504 as Dodger is saying) and the fabric is the def g/w, then we can put them in the same EPG and have to take the additional step to put them into an any-any contract between the external VLANs.. Correct? If so, when will this get corrected? For I'll have several customers that will have this requirement as part of the migration ... View more