Why would suspend/activate fix a pinglist service?
This one seemed a bit odd so I thought I'd throw it out here.
On a CSS 11051 that had been running well, a 'pinglist' type service went down. Manual pings from the CSS to one of the IP addresses in the pinglist failed. After troubleshooting the LAN and finding no problems, I suspended the service and then the manual pings worked. I reactivated the service and then service came up and all is working well.
Has anyone seen anythign like this? Any ideas what may have caused this problem and why suspending and reactivating the service would fix it?
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...