The current cache resource is exactly 90% of the Max cache resource and the watermarks are all at 94%/95%. This figure never goes about 90% and I am seeing the same behaviour on multiple devices int he network, why is this not at least reaching 94% as per the low watermark and why is it causing eviction?
the Last evicted resource access time is exactly the same as the Last eviction time, but last evicted resourec age tells us that thsi resource is much older. Why is the last access time the same as eviction time, surely it should be at least a couple of msecs older? In all the outputs of this command I have ever seen (even on this forum), the last access time is the same as the eviction time, surely this is incorrect and is a bug?
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...