The TCP tab of the data table excludes non-TCP packets and displays the data that CA Application Delivery Analysis and CA APM monitor from all Multi-Port Monitor logical ports. Only the columns applicable to the selected view are shown in the table. The following list describes all possible columns for the TCP tab.
Application names are derived from CA Application Delivery Analysis configuration or from well-known port usage. Where available, the application name is supplied. Otherwise, the port number is shown in parentheses.
The second value in a pair of values that identifies an application. An internal identifier.
Identifies an application in the Multi-Port Monitor database. In most cases, conveys the state of this application as it pertains to CA Application Delivery Analysis. One of the following types:
If multiple collection devices report to one CA Application Delivery Analysis management console, it is possible that a different collection device monitors this application for CA Application Delivery Analysis. The Application Type designation refers to items that only this Multi-Port Monitor actively monitors.
The IP address of the client computer in the client-server session.
The host name of the client computer in the client-server session (a conversation pair).
The port on the client that sent or received the data.
Connection Time Observations. The number of monitored TCP connections occurring during the selected time interval. A good indication of usage levels and a gauge of metric significance. For example, many observations can indicate an event that can affect users.
Data Transfer Time. Elapsed time between when the server starts responding and when it finishes sending data. Several factors affect this value, such as response size, available bandwidth, and interaction between the application and the network. Excludes the initial server response time and includes only NRTT if there is more data to send than fits in the TCP window. This value is related to the number of network round trips required to deliver all data and the delay per round trip.
Effective Network Round-Trip Time. Includes NRTT and Retransmission Delay, which is the delay that retransmissions cause for a transaction. Reflects the latency that users actually experience and serves as an indicator of the performance degradation that retransmissions cause.
The name of the Network Layer protocol (IP or ARP), or an ID number from the Ethertype field in the packet header. Indicates “Ethertype=X” when an IEEE 802 Ethertype value is found.
The decimal registry number of a Network Layer protocol, such as 2048 for IPv4.
The name of the Transport Layer protocol, such as TCP.
The decimal registry number of a Transport Layer protocol, such as 6 for TCP.
The logical port and port number on the Multi-Port Monitor appliance that is the source of the data in the table.
Network Connection Time. The amount of time that it takes the client to confirm the server connection acknowledgment. In general, network latency causes delay in connection times. NCT serves as a baseline for carrier latency and comparison to NRTT values.
Network Round-Trip Time. The amount of time it takes for a packet to travel to and from the server and clients on a network, excluding latency from retransmissions. Application and server processing times are excluded from this value. This value is often useful when compared to the NCT value.
Retransmission Delay. The additional delay in the NRTT that retransmission cause. Retransmissions are packets that are retransmitted after data loss. The data is expressed as an average across all observations, not the actual retransmission time for each transaction. The NRTT value increases when Retransmission Delay causes a delay in client acknowledgment. This metric does not reveal the impact of losses on the DTT because of TCP congestion. This metric reflects only data loss from the server to the clients, not from clients to the server.
Server Connection Time. The amount of time from when the server receives the SYN packet from the client until the server sends the first SYN/ACK.
Opening a TCP connection involves exchanging three packets: SYN, SYN/ACK, and ACK. The TCP header has SYN (synchronize) and ACK (acknowledge) bits. The first packet has the SYN bit set. The second packet has both bits set. The third packet has only the ACK bit set. This exchange establishes the initial sequence numbers of the connection.
SCT and NCT comprise the Connection Setup Time metric.
The IP address of the server in the client-server session.
The unique Media Access Control address that identifies a host.
The host name of the server in the client-server session (a conversation pair).
The name of a network as it is defined for monitoring in CA Application Delivery Analysis. The “Client” or “Server” designation appears for the paired data views and indicates the direction of data flow between networks.
The IP address of a network subnet. The “Client” or “Server” designation appears for the paired data views and indicates the direction of data flow between subnets.
The port on the server that sent or received the data.
Server Response Time. The amount of time a server takes to respond to a client request. Server speed, application design, and volume of requests affect SRT.
Data loss, expressed as a percentage of TCP bytes sent and received.
TCP throughput in bits. The data rate in bits per second (bytes per second x 8) between the selected server and clients during the selected time period.
Ratio of retransmitted data to total data, percentage of data that was lost on the monitored network, and loss rate in bits per second.
TCP data volume in bytes. The total number of Application-Layer bytes seen on the network during the selected time period.
TCP data volume in bytes. Total number of Application-Layer bytes that the selected server sent to or received from clients during the selected time period.
Data loss, expressed as a percentage of TCP packets that were sent and received.
TCP throughput in packets. The data rate in packets per second during the selected time period. ADA reports use the term Data Rate.
TCP throughput in packets. The data rate in packets per second from the selected server to clients, or from clients to the server, during the selected time period.
Ratio of retransmitted data to total data, percentage of data that was lost on the monitored network, and loss rate in packets per second.
TCP data volume in packets. The total number of packets on the network during the selected time period. Includes zero-byte packets, such as TCP acknowledgments.
TCP throughput in bits. The data rate (bytes per second x 8) during the selected time period. CA Application Delivery Analysis reports use the term Data Rate.
The number of TCP bytes that were retransmitted due to data loss.
The number of TCP packets that were retransmitted due to data loss.
The bit setting for the Type of Service field in the IPv4 header.
A standard description of the TOS setting, such as “Default Traffic” or “Max throughput.”
The amount of time from the moment a client sends the request (packet-level or transaction-level) to the moment the client receives the last packet in the response.
Transaction Time Observations. The number of monitored TCP transactions that occurred during the selected interval. A good indication of usage levels and a gauge of metric significance. For example, many observations can indicate an event that can affect many users.
The ID number of the Virtual Local Area Network.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|