PT in Progress means that one of the WAEs did not see the SYN packet for the connection.
First packet the WAAS received redirected for the particular connection it was already in progress, so optimization could not get applied.
Open a new test connection via the setup and check if it gets optimized or not.
If it works, close the in progress' ones and open new ones as well. In case new connection also does not optimize, you will have to check the routing for assymetry or failure to redirect frames at both sides.
It is also possible that one of the WAEs reached connection limit for used platform and returns the packet untouched. Check the syslog for possible messages in this sense.
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...