ACE-2-302032: POST Debug 2013:10:16 08:37:47:tcp_send_packet:1403, PktCount: 1, BufChLen: 24, Core#4, fp msg_flags: 0x0, proxyId: 43234, SEQ : 1990829414 , ACK: 0, TCP FLG:0x2
This message is not documented in our system message guides:
We need to update the guide with the appropriate description, stating that customers should only open TAC case if they notice any functional impact.
This log message was created to investigate wrong re-ordering of TCP packets ( "CSCud62073 ACE wrong re-ordering of TCP packets.") and is purely informational.
The fact that we set this message for level 2(critical) induces customers in error.
The code is added into A5(2.1) and later and with logging enabled, customer will see the message present in the syslog. It is not an indication of an issue, just additional output to troubleshoot if the POST reordering occurs.
So that the message is just indicative and wants to tell us, that reordering of TCP packets has occurred, right?
Does it mean, we can disable the message using "no logging message 302032" on the ACE module? The customer didn't have issues with traffic going through the loadbalancer, but the message fills up the logging buffer.
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...