I have a question regarding WAAS optimization of TSM traffic. I know there is a policy in the WAAS that applies TFO+LZ+DRE to TSM traffic on ports 1500-1502. On our network there are nightly TSM backups that kickoff and according to the WAAS its reducing this TSM traffic by 90%. However, when I look at the Netflow statics off the routers at the remote site and the core site I see a far different picture.
At the remote site the inside ethernet interface sees approximately 21GB of backup traffic between the two hosts over a two hour timeframe. The serial interface of the core site sees approximately 23GB of backup traffic between the two hosts over the same timeframe and the remote WAAS tells me it reduced approximately 20GB of backup traffic to approximately 1.75GB.
Something is obviously not right here. Does any one else have any similar experiences or things they think I might look at to reconcile this?
I think you may be seeing DDTS: CSCsm35350 which can create a phantom packet count for netflow when using gre-egress (negotiated return). Your interface stats would reflect seeing the actual traffic and also the return traffic (uncompressed) from the WAE, which would inflate your interface statistics.
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...