The one I mentioned before was just configured for 1400 MTU size on gig 1/0 and gig 2/0. I'll wait a little bit and see if it is still incrementing. I just noticed it increment right after I brought WCCP back online. Now for our other locations, we have it incrementing all the time, and they're using the default MTU size of 1500. Would you want to modify it for 1400 or modify the MSS value from 1432 to say 1300?
Other location where the packets fragmented are high:
GRE fragments redirected: 114041
Packets fragmented for egress: 114041 Packet pullups needed: 114082
I wouldn't recommend modifying the MTU. It should be left at 1500 on the WAAS devices. For TCP traffic where WAAS sees the connection setup (SYN, SYN-ACK), the TCP MSS should be adjusted to account for the WCCP GRE overhead.
Can you share a copy of the configuration where WCCP is enabled?
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...