How maintaining the connection table for sticky/persistent/non-persistent?
Question about how to maintain the connection table for the source(client) and destination(server) in the CSM(or CSS).
I know the sticky has the table and max size such as 128K(css11501)as per CCO but not clear how works the persistant and non-persistant case.
Q1) persistant. does it maintain the conntion table to tracking the session? then, any information the table size?
Q2) non-persistant. is this also have connection table? then, how it works?
why I'm asking is want to understand how the session keep tracking. for example, the router based on the routing table(stateless) versus PIX firewall has stateful table. As analogue, is the non-persistnet stateless and statefull for the persistent and sticky?
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...