In case this helps anyone in the future. I had this error message today. I am running Version 12.2[125 [build 3.0(0)A4(2.2)].
I appear to have caused it by inadvertantly reintroducing "alias" and "peer" statements into my context THEN shortly thereafter trying to delete the context (in order to recreate via a context restore to test a modified version of another server's configuration). The "no context ABC" caused the hang when it could not talk to this context's failover: nothing was configured on the other end! So the command line hung for 1-2 minutes before it spontaneously rebooted, resulting in the same message you listed.
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...