We have an application which uses HTTP chunking which as far as I know supports multiple get requests from the server with one 200 OK. This reduce the overhead and is considered to be more efficient.
The problem we are facing is that with the CSS this application works fine but with the CSM we have to disable this option in the server. Has anyone seen a similar issue or is there anyway the CSM can be made to support chunking?
if you do not have the command 'no persistent' on the CSS, it would work as it wors on the CSM with 'no persistent rebalance'.
With 'no persistent rebalance' the CSM will make its loadbalancing decision on the first http request then setup a flow in fastpath so that after that the traffic is simply fastswitched [no inspection anymore].
The CSS also has persistence as I can not see "no persistent" in the content:
vip address xxx.xxx.xxx.xxx
add service DESAP008_DOCUMENTUM_8181
add service DESAP008_DOCUMENTUM_8282
add service DESAP507_DOCUMENTUM_8181
add service DESAP507_DOCUMENTUM_8282
BTW I know that on a Cat switch it is the best practice to use hardware switching. Is it the same case for the CSM. In other words should all vservers normally be configured with "no persistent rebalance" for fastpath switching?
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...