Module rasn_mib::tcp

source ·
Expand description

The Transmission Control Protocol (TCP) Group

Implementation of the TCP group is mandatory for all systems that implement the TCP.

Note that instances of object types that represent information about a particular TCP connection are transient; they persist only as long as the connection in question.

Structs§

  • The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.
  • 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.
  • Information about a particular current TCP connection. An object of this type is transient, in that it ceases to exist when (or soon after) the connection makes the transition to the CLOSED state.
  • 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.
  • The local port number for this TCP connection.
  • The remote IP address for this TCP connection.
  • The remote port number for this TCP connection.
  • The state of this TCP connection.
  • A table containing TCP connection-specific information.
  • The number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT.
  • 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.
  • The total number of segments received in error (e.g., bad TCP checksums).
  • The total number of segments received, including those received in error. This count includes segments received on currently established connections.
  • 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.
  • The number of TCP segments sent containing the RST flag
  • The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.
  • The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
  • The total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted octets.
  • The algorithm used to determine the timeout value used for retransmitting unacknowledged octets.
  • 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 RtoAlgorithm::RSRE, an object of this type has the semantics of the UBOUND quantity described in RFC 793.
  • 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 RtoAlgorithm::RSRE, an object of this type has the semantics of the LBOUND quantity described in RFC 793.