The MIB module for managing TCP implementations. read-only current 1.3.6.1.2.1.6.1 The algorithm used to determine the timeout value used for retransmitting unacknowledged octets. 1 -- none of the following 2 -- a constant rto 3 -- MIL-STD-1778, Appendix B 4 -- Van Jacobson's algorithm [5] read-only current 1.3.6.1.2.1.6.2 "milliseconds" The minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the LBOUND quantity described in RFC 793. read-only current 1.3.6.1.2.1.6.3 "milliseconds" The maximum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the UBOUND quantity described in RFC 793. read-only current 1.3.6.1.2.1.6.4 The limit on the total number of TCP connections the entity can support. In entities where the maximum number of connections is dynamic, this object should contain the value -1. read-only current 1.3.6.1.2.1.6.5 The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state. read-only current 1.3.6.1.2.1.6.6 The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state. read-only current 1.3.6.1.2.1.6.7 The number of times TCP connections have made a direct transition to the CLOSED state from either the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state. read-only current 1.3.6.1.2.1.6.8 The number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state. read-only current 1.3.6.1.2.1.6.9 The number of TCP connections for which the current state is either ESTABLISHED or CLOSE- WAIT. read-only current 1.3.6.1.2.1.6.10 The total number of segments received, including those received in error. This count includes segments received on currently established connections. read-only current 1.3.6.1.2.1.6.11 The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets. read-only current 1.3.6.1.2.1.6.12 The total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted octets. read-only current 1.3.6.1.2.1.6.14 The total number of segments received in error (e.g., bad TCP checksums). read-only current 1.3.6.1.2.1.6.15 The number of TCP segments sent containing the RST flag. read-only current 1.3.6.1.2.1.6.1 The algorithm used to determine the timeout value used for retransmitting unacknowledged octets. 1 -- none of the following 2 -- a constant rto 3 -- MIL-STD-1778, Appendix B 4 -- Van Jacobson's algorithm [5] read-only current 1.3.6.1.2.1.6.2 "milliseconds" The minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the LBOUND quantity described in RFC 793. read-only current 1.3.6.1.2.1.6.3 "milliseconds" The maximum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the UBOUND quantity described in RFC 793. read-only current 1.3.6.1.2.1.6.4 The limit on the total number of TCP connections the entity can support. In entities where the maximum number of connections is dynamic, this object should contain the value -1. read-only current 1.3.6.1.2.1.6.5 The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state. read-only current 1.3.6.1.2.1.6.6 The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state. read-only current 1.3.6.1.2.1.6.7 The number of times TCP connections have made a direct transition to the CLOSED state from either the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state. read-only current 1.3.6.1.2.1.6.8 The number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state. read-only current 1.3.6.1.2.1.6.9 The number of TCP connections for which the current state is either ESTABLISHED or CLOSE- WAIT. read-only current 1.3.6.1.2.1.6.10 The total number of segments received, including those received in error. This count includes segments received on currently established connections. read-only current 1.3.6.1.2.1.6.11 The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets. read-only current 1.3.6.1.2.1.6.12 The total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted octets. not-accessible current 1.3.6.1.2.1.6.13.1 A conceptual row of the tcpConnTable containing information about a particular current TCP connection. Each row of this table is transient, in that it ceases to exist when (or soon after) the connection makes the transition to the CLOSED state. read-only current 1.3.6.1.2.1.6.14 The total number of segments received in error (e.g., bad TCP checksums). read-only current 1.3.6.1.2.1.6.15 The number of TCP segments sent containing the RST flag. read-write current 1.3.6.1.2.1.6.13.1.1 The state of this TCP connection. The only value which may be set by a management station is deleteTCB(12). Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to set this object to any other value. If a management station sets this object to the value deleteTCB(12), then this has the effect of deleting the TCB (as defined in RFC 793) of the corresponding connection on the managed node, resulting in immediate termination of the connection. As an implementation-specific option, a RST segment may be sent from the managed node to the other TCP endpoint (note however that RST segments are not sent reliably). 1 2 3 4 5 6 7 8 9 10 11 12 read-only current 1.3.6.1.2.1.6.13.1.2 The local IP address for this TCP connection. In the case of a connection in the listen state which is willing to accept connections for any IP interface associated with the node, the value 0.0.0.0 is used. read-only current 1.3.6.1.2.1.6.13.1.3 The local port number for this TCP connection. read-only current 1.3.6.1.2.1.6.13.1.4 The remote IP address for this TCP connection. read-only current 1.3.6.1.2.1.6.13.1.5 The remote port number for this TCP connection.