If anyone can help point me in the correct direction or a why to get around this error I'd be very grateful as I can't seem to find any documentation that explains any difference in behavior between these two releases.
Thanks for your reply. Do you see a problem with our original A1(6.3a) config version? I'm now wondering if its a bug in the code that allowed us to enter the additional lines, but perhaps they aren't even being used?
After further reading it suggests each PAT ip can support about 63k connections, so even just using 64 ips in a PAT pool could provide use with about 4millions connections (which is the limit on the ACE anyway). It may therefore seem that the original configuration was vastly over specified in terms of the amount of IPs allocated to the PAT pools. Does this seem correct or have I interpreted this wrong?
your interpretation is correct. Infact i found a BUG which says something like this "CLI not respecting the 64 IP limit in PAT pool" but affected version didn't shown yours (may be because A1 was quite old release)
Anways i am also looking for any documentation BUG to correct for what mention in wiki.
Your current version is not even on the download software page, anytime when you have an old version, you are more exposed to suffer the presence of bugs, then the recommendations is to have one of the latest which have most of bugs fixed
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...