Re: TCP RESET-ACK message without RESET in Capture.
This is my understanding with regards to your above packet capture.
61: 192.168.249.69 sends SYN to 192.168.249.21
65: 192.168.249.21 sends SYN ACK to 192.168.249.69
66: 192.168.249.69 sends ACK to 192.168.249.21
67: 192.168.249.69 sends a PUSH to 192.168.249.21 (data/payload transfer)
68: 192.168.249.69 sends a PUSH to 192.168.249.21 (DUPLICATE PACKET BECAUSE 67 AND 68 IS THE SAME THING, same packet size!!)
69: 192.168.249.21 sends a RESET to 192.168.249.69
65: TCP Sequence Number = 1457523457
66: TCP Sequence Number = 1457523458
67: TCP Sequence Number = 1457523458
68: TCP Sequence Number = 1457523458
69: TCP Sequence Number = 1457523458
The question here should be why is your backup appliance sending a RESET to the server? I guess you'll need to check with the backup appliance vendor/principal on this. Just out of curiousity, if your backup appliance and the server were in the same network address, no Cisco ASA FW in between, will this work fine?
Ramraj Sivagnanam Sivajanam
Technical Specialist/Service Delivery Manager – Managed Service Department
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...