We don't have a way to currently tell you whether or not the TCP Resets were executed or whether or not they were successful.
It has been requested by users and is being evaluated for inclusion in a future sensor version.
For a workaround you could try the following for a few specific instances:
Set the signature action to both TCP Resets and IPLOG.
Then when the signature fires the connection should be reset. After the signature fires all packets to and from the source address will be IPLOGGED. Then you can check the IPLOG with a program like ethereal (see ww.ethereal.com) to view the packets in the log file. See if any more packets came in on the same connection that the alarm fired on.
Note: There may be several connections from the source address that in the IPLOG file so you will need to check for the same addresses and ports from the connection that created the alarm.
