Explanation of TIM OOO Statistics in TIM Logs.

book

Article ID: 38310

calendar_today

Updated On:

Products

APPLICATION DELIVERY ANALYSIS SUPERAGENT APP PERF MANAGEMENT CA Application Performance Management Agent (APM / Wily / Introscope) CUSTOMER EXPERIENCE MANAGER INTROSCOPE

Issue/Introduction

  Question:

   In the TIM logs, there are these statistics:

    Tue Jan 26 06:45:27 2016 6511 ConnManager: out-of-order TCP queues containing data: 66
    Tue Jan 26 06:45:27 2016 6511 ConnManager: out-of-order TCP total queued bytes: 1106116
    Tue Jan 26 06:45:27 2016 6511 ConnManager: out-of-order TCP total queued packets: 9734
    Tue Jan 26 06:45:27 2016 6511 ConnManager: out-of-order TCP max queue size in bytes: 346166
    Tue Jan 26 06:45:27 2016 6511 ConnManager: out-of-order TCP max queue size in packets: 3414
    Tue Jan 26 06:45:27 2016 6511 ConnManager: out-of-order TCP queues containing FIN: 0

    On the MTP, they look like this for each worker:

    Tue Feb 16 14:38:05 2016  4541   w11: ConnManager: out-of-order TCP queues containing data: 18
    Tue Feb 16 14:38:05 2016  4541   w11: ConnManager: out-of-order TCP total queued bytes: 4786885
    Tue Feb 16 14:38:05 2016  4541   w11: ConnManager: out-of-order TCP total queued packets: 5401
    Tue Feb 16 14:38:05 2016  4541   w11: ConnManager: out-of-order TCP max queue size in bytes: 878876
    Tue Feb 16 14:38:05 2016  4541   w11: ConnManager: out-of-order TCP max queue size in packets: 959
    Tue Feb 16 14:38:05 2016  4541   w11: ConnManager: out-of-order TCP queues containing FIN: 0

  

    What are these values?

  

    Environment:

    This should be in the logs for APM 9.x, and 10.x TIMs and MTP TIMs.

   

   Answer:

   While operational, the TIM is monitoring continuously TCP connections while looking for HTTP/HTTPS/FLEX traffic.

    As it does this, it keeps a running counter of the TIM packets that are not arriving in order that are queued up for processing.

    This is captured in 6 statistics every 5 minutes by default.

 

    - out-of-order TCP queues containing data      -- Number of out-of-order connections in the queue.

    - out-of-order TCP total queued bytes              -- Total number of out-order bytes in the queue

    - out-of-order TCP total queued packets           -- Total number of out-order packets in the queue

    - out-of-order TCP max queue size in bytes      -- The highest number of bytes received during one out-of-order connection.

    - out-of-order TCP max queue size in packets   -- The highest number of packets received during one out-of-order connection.

    - out-of-order TCP queues containing FIN         -- The number of out-of-order connections having received a TCP FIN packet from the server.

                                                                                   (Starting the TCP close connection process)

 

   So by looking at this data in the TIM log (as well as in the TIM Status page or the TIM unsupported Packet Statistics page), you can see such things as:

    - If your out of order queued data is high or low.

    - If there are a lot or few out-of-order connections

   -  If there are few or many out of order connections starting to close.

 

   All this gives you a snapshot of your TIM/MTP network data health that you can discuss and analyze with your network team.

   

   Additional Information:

   1. TEC595880 TIM stopped due to Kernel panic not syncing: OOM and no killable process. --

        http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec595880.aspx

 

 2. TEC1895461 Not seeing all transactions due to late SSL packets -- 
       http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1895461.aspx

Environment

Release: SAMCNS99000-10.2-NetQoS-SuperAgent-Management Console
Component: