This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
protocol-tcp
The following operations can be performed on “protocol-tcp”:
stat protocol tcp
Displays statistics of the TCP protocol.
Synopsis
| stat protocol tcp [-detail] [-fullValues] [-ntimes |
full )] |
Arguments
detail Specifies detailed output (including more statistics). The output can be quite voluminous. Without this argument, the output will show only a summary.
fullValues Specifies that numbers and strings should be displayed in their full form. Without this option, long strings are shortened and large numbers are abbreviated
ntimes The number of times, in intervals of seven seconds, the statistics should be displayed. Default value: 1 Minimum value: 0
logFile The name of the log file to be used as input.
clearstats Clear the statsistics / counters
Possible values: basic, full
Output
Counters
Server active connections (ActSvrCo) Connections to a server currently responding to requests.
Opening server connections (SvrCxO) Server connections in the Opening state, which indicates that the handshakes are not yet complete.
Opening client connections (CltCxO) Client connections in the Opening state, which indicates that the handshakes are not yet complete.
Established client connections (CltCxE) Current client connections in the Established state, which indicates that data transfer can occur between the Citrix ADC and the client.
Established server connections (SvrCxE) Current server connections in the Established state, which indicates that data transfer can occur between the Citrix ADC and the server.
TCP packets received (TCPPktRx) TCP packets received.
TCP bytes received (TCPbRx) Bytes of TCP data received.
TCP packets transmitted (TCPPktTx) TCP packets transmitted.
TCP bytes transmitted (TCPbTx) Bytes of TCP data transmitted.
All client connections (CltCx) Client connections, including connections in the Opening, Established, and Closing state.
Closing client connections (CltCxCl) Client connections in the Closing state, which indicates that the connection termination process has initiated but is not complete.
Opened client connections (TotCltO) Client connections opened by the Citrix ADC since startup (after three-way handshake). This counter is reset when the Citrix ADC is restarted.
All server connections (SvrCx) Server connections, including connections in the Opening, Established, and Closing state.
Closing server connections (SvrCxCl) Server connections in the Closing state, which indicates that the connection termination process has initiated but is not complete.
Opened server connections (TotSvrO) Server connections initiated by the Citrix ADC since startup. This counter is reset when the Citrix ADC is restarted.
Surge queue (SQlen) Connections in the surge queue. When the Citrix ADC cannot open a connection to the server, for example when maximum connections have been reached, the Citrix ADC queues these requests.
Spare connections (SpConn) Spare connections available. To save time and resources in establishing another connection for a new client, the connection on the server is not closed after completing the request from the first client and is available for serving future requests.
Client idle flushed (ZomCltF) Client connections that are flushed because the client has been idle for some time.
Client half opened flushed (ZCltFHo) Half-opened client connections that are flushed because the three-way handshakes are not complete.
Client active half closed flushed (ZCltFAhc) Active half-closed client connections that are flushed because the client has closed the connection and there has been no activity on the connection.
Client passive half closed flushed (ZCltFPhc) Passive half-closed client connections that are flushed because the Citrix ADC has closed the connection and there has been no activity on the connection.
Server idle connections flushed (ZSvrF) Server connections that are flushed because there have been no client requests in the queue for some time.
Server half opened flushed (ZSvrFHo) Half-opened server connections that are flushed because the three-way handshakes are not complete.
Server active half closed flushed (ZSvrFAhc) Active half-closed server connections that are flushed because the server has closed the connection and there has been no activity on the connection.
Server passive half closed flushed (ZSrvFPhc) Passive half-closed server connections that are flushed because the Citrix ADC has closed the connection and there has been no activity on the connection.
Zombie cleanup calls (ZmbCall) Times the Zombie cleanup function is called. Every time a connection is flushed, it is marked for cleanup. The Zombie cleanup function clears all these connections at predefined intervals.
SYN packets received (TCPSYN) SYN packets received
Server probes (SYNProbe) Probes from the Citrix ADC to a server. The Citrix ADC sends a SYN packet to the server to check its availability and expects a SYN_ACK packet from the server before a specified response timeout.
FIN packets from server (SvrFin) FIN packets received from the server.
FIN packets from client (CltFin) FIN packets received from the clients.
Time wait to SYN (WaToSyn) SYN packets (packets used to initiate a TCP connection) received on connections that are in the TIME_WAIT state. Packets cannot be transferred on a connection in this state.
Data in TIME_WAIT (WaDat) Bytes of data received on connections that are in the TIME_WAIT state. Data cannot be transferred on a connection that is in this state.
SYN packets held (SYNHeld) SYN packets held on the Citrix ADC that are waiting for a server connection.
SYN packets flushed (SYNFlush) SYN packets flushed on the Citrix ADC because of no response from the server for three or more seconds.
TIME_WAIT connections closed (FinWaitC) Connections closed on the Citrix ADC because the number of connections in the TIME_WAIT state has exceeded the default value of 7000.
Bad TCP checksum (TCPBadCk) Packets received with a TCP checksum error.
Data after FIN (TCPDtFin) Packets received following a connection termination request. This error is usually caused by a reordering of packets during transmission.
SYN in SYN_RCVD state (TCPSYNRv) SYN packets received on a connection that is in the SYN_RCVD state. A connection goes into the SYN_RCVD state after receiving a SYN packet.
SYN in ESTABLISHED state (TCPSYNEs) SYN packets received on a connection that is in the ESTABLISHED state. A SYN packet is not expected on an ESTABLISHED connection.
SYN_SENT incorrect ACK packet (TCPBadAk) Incorrect ACK packets received on a connection that is in the SYN_SENT state. An incorrect ACK packet is the third packet in the three-way handshake that has an incorrect sequence number.
RST packets received (TCPRST) Reset packets received from a client or a server.
RST on not ESTABLISHED (TCPRSTNE) Reset packets received on a connection that is not in the ESTABLISHED state.
RST out of window (TCPRSTOW) Reset packets received on a connection that is out of the current TCP window.
RST in TIME_WAIT (TCPRSTTi) Reset packets received on a connection that is in the TIME_WAIT state. Packets cannot be transferred on a connection in the TIME_WAIT state.
Server out of order packets (SvrOOO) Out of order TCP packets received from a server.
Client out of order packets (CltOOO) Out of order TCP packets received from a client.
TCP hole on client connection (CltHole) TCP holes created on a client connection. When out of order packets are received from a client, a hole is created on the Citrix ADC for each group of missing packets.
TCP hole on server connection (SvrHole) TCP holes created on a server connection. When out of order packets are received from a server, a hole is created on the Citrix ADC for each group of missing packets.
Seq number SYN cookie reject (CSeqRej) SYN cookie packets rejected because they contain an incorrect sequence number.
Signature SYN cookie reject (CSigRej) SYN cookie packets rejected because they contain an incorrect signature.
Seq number SYN cookie drop (CSigDrp) SYN cookie packets dropped because the sequence number specified in the packets is outside the current window.
MSS SYN cookie reject (CMssRej) SYN cookie packets rejected because the maximum segment size (MSS) specified in the packets is incorrect.
Any IP port allocation failure (PortFal) Port allocations that have failed on a mapped IP address because the maximum limit of 65536 has been exceeded.
IP port allocation failure (PortFalI) Port allocations that have failed on a subnet IP address or vserver IP address because the maximum limit of 65536 has been exceeded.
Stray packets (StrayPkt) Number of stray or misrouted packets.
RST packets sent (SentRst) Reset packets sent to a client or a server.
Bad state connections (BadConn) Connections that are not in a valid TCP state.
RST threshold dropped (RstThre) Reset packets dropped because the default threshold of 100 resets per 10 milliseconds has been exceeded. This is a configurable value using the set rateControl command.
Packets out of window (OOWPkt) Packets received that are out of the current advertised window.
SYNs dropped (Congestion) (SynCng) SYN packets dropped because of network congestion.
Client retransmissions (TCPCltRe) Packets retransmitted by a client. This usually occurs because the acknowledgement from the Citrix ADC has not reached the client.
Full packet retransmissions (TCPFulRe) Full packets retransmitted by the client or the server.
SYN packet retries (TCPSYNRe) SYN packets resent to a server.
SYN packets timeout (TCPSYNG) Attempts to establish a connection on the Citrix ADC that timed out.
TCP retransmission (Retr) TCP packets retransmitted. The Citrix ADC attempts to retransmit the packet up to seven times, after which it resets the other half of the TCP connection.
1st retransmission (1stRetr) Packets retransmitted once by the Citrix ADC.
3rd retransmission (3rdRetr) Packets retransmitted three times by the Citrix ADC.
5th retransmission (5thRetr) Packets retransmitted five times by the Citrix ADC.
7th retransmission (7thRetr) Packets retransmitted seven times by the Citrix ADC. If this fails, the Citrix ADC terminates the connection.
Fast retransmits (FastRetr) TCP packets on which the Citrix ADC performs a fast retransmission in response to three duplicate acknowledgements or a partial acknowledgement. The Citrix ADC assumes that the packet is lost and retransmits the packet before its time-out.
Server retransmissions (TCPSvrRe) Packets retransmitted by a server. This usually occurs because the acknowledgement from the Citrix ADC has not reached the server.
Partial packet retransmissions (TCPParRe) Partial packet retransmits by a client or server due to congestion on the connection. This usually occurs because the window advertised by the Citrix ADC is not big enough to hold the full packet.
FIN packet retries (TCPFINRe) FIN packets resent to a server or a client.
FIN packets timeout (TCPFING) Connections that were timed out by the Citrix ADC because of not receiving the ACK packet after retransmitting the FIN packet four times.
2nd retransmission (2ndRetr) Packets retransmitted twice by the Citrix ADC.
4th retransmission (4thRetr) Packets retransmitted four times by the Citrix ADC.
6th retransmission (6thRetr) Packets retransmitted six times by the Citrix ADC.
TCP retransmission giveup (RetrG) Number of times Citrix ADC terminates a connection after retransmitting the packet seven times on that connection.Retrasnmission happens when recieving end doesn’t acknowledges the packet.
TCP level cip failure (CltHdrEr) Number of times TCP level client header insertion failure
Related Commands
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.