You can try looking at the crash files (/local/local1/crash//4/analysis.x) and see if there is anything there, however I don't see anything in the syslog that stands out as to why it's stopping responding. The crash files may contain the reason your box is crashing and should probably be looked at by the cisco TAC. This could also be a problem where the device stops responding due to an issue with the hardware, and then the files are created when the device boots. Reguardless, the TAC can decode the crash files and get some more answers on it for you.
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...