1. NP1/NP2 are the CPUs. The ports on the module are consoles for debugging. These ports should remain covered. I believe they are disabled.
2. You will want to use predictor hash source mask x.x.x.x. This will ensure that each client always balances to the same cache engine. This will better utilize your disk cache and increase your chances of cache hits.
In terms of L4 or L7, I would always try to keep the load balancing rules at layer4 if possible. This will maximize the performance of any load balancer since the LB decision can be made on the TCP syn packet.
3. Take a look at example A of this FWLB config. It is pretty much the same thing you would use for a cache:
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...