Professional Documents
Culture Documents
2XX Success
3XX Redirectional
4XX Client Error
5XX Server Error
Set the desired configuration (offload or any other option) to the VS_NAME
1) Enable TCP RST cause on the BIG-IP --> tmsh modify sys db tm.rstcause.pkt value
enable
2) Since the traffic is encrypted with SSL, then you will need to create an iRule
such as below.
when CLIENTSSL_HANDSHAKE
{
if { [clientside {IP::remote_addr}] equals xxx.xxx.xxx.xxx }
{ log local0. "[TCP::client_port] :: RSA Session-ID:[SSL::sessionid] Master-
Key:[SSL::sessionsecret]" } }
when SERVERSSL_HANDSHAKE {
if { [clientside {IP::remote_addr}] equals xxx.xxx.xxx.xxx }
{ log local0. "[TCP::client_port] :: RSA Session-ID:[SSL::sessionid]
Master-Key:[SSL::sessionsecret]" } }
Note 1: change xxx.xxx.xxx.xxx with the client IP used to access the Virtual Server
(aka VS_NAME).
Note 2: if you are not using server ssl profile attached to the VS_NAME, you will
be require to remove SERVERSSL_HANDSHAKE, since no suce profile attached to it
Note: replace xxx.xxx.xxx.xxx with the correct client IP. This should be the same
as in the iRule on point 2 above.
5) While the trace is running, please reproduce the problem. Once the problem is
seen, stop the trace hitting CTRL+C
7) Stop TCP RST logging --> tmsh modify sys db tm.rstcause.pkt value disable
8) If SSL was in use, then remove decrypt iRule from Virtual Server
9) Using Software such as WinSCP, please fetch below 2x files from the BIG-IP:
- /var/tmp/CASE_NUMBER_pcap.pcap
- /var/tmp/CASE_NUMBER_qkview.qkview