MIBs Depot

TCP-MIB

Registered at
1.3.6.1.2.1.6
1.3.6.1.2.1.49
Last updated
2005-02-18 00:00
Organization
IETF IPv6 MIB Revision Team http://www.ietf.org/html.charters/ipv6-charter.html
Revisions
2005-02-18 00:00, 1994-11-01 00:00, 1991-03-31 00:00
Namespace
standard
Source file
TCP-MIB
Digest
sha256:1362c1b71b59befcdac7186c7649e56e781634f0cc74576bbfe8ead691c138ac

Description

The MIB module for managing TCP implementations. Copyright (C) The Internet Society (2005). This version of this MIB module is a part of RFC 4022; see the RFC itself for full legal notices.

Contact

Rajiv Raghunarayan (editor) Cisco Systems Inc. 170 West Tasman Drive San Jose, CA 95134 Phone: +1 408 853 9612 Email: <raraghun@cisco.com> Send comments to <ipv6@ietf.org>

Imports

FromSymbols
INET-ADDRESS-MIBInetAddress, InetAddressType, InetPortNumber
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-SMICounter32, Counter64, Gauge32, Integer32, IpAddress, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso, mib-2
SNMPv2-TCDisplayString, TEXTUAL-CONVENTION

Imported by

5 module(s) in this corpus import this one.

Load order

Every file a consumer needs in order to load this module, dependencies first.

INET-ADDRESS-MIB
SNMPv2-CONF
SNMPv2-SMI
SNMPv2-TC
TCP-MIB

Objects

NameOIDSyntaxAccessStatus
tcp
OBJECT-IDENTITY
1.3.6.1.2.1.6
tcpRtoAlgorithm
OBJECT-TYPE
The algorithm used to determine the timeout value used for retransmitting unacknowledged octets.
1.3.6.1.2.1.6.1INTEGER {other(1), constant(2), rsre(3), vanj(4), rfc2988(5)}read-onlycurrent
tcpRtoMin
OBJECT-TYPE
The minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend on the algorithm used to determine the retransmission timeout; in particular, the IETF standard algorithm rfc2988(5) provides a minimum value.
1.3.6.1.2.1.6.2Integer32 (0..2147483647)read-onlycurrent
tcpRtoMax
OBJECT-TYPE
The maximum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend on the algorithm used to determine the retransmission timeout; in particular, the IETF standard algorithm rfc2988(5) provides an upper bound (as part of an adaptive backoff algorithm).
1.3.6.1.2.1.6.3Integer32 (0..2147483647)read-onlycurrent
tcpMaxConn
OBJECT-TYPE
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.
1.3.6.1.2.1.6.4Integer32 (-1 | 0..2147483647)read-onlycurrent
tcpActiveOpens
OBJECT-TYPE
The number of times that TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state. Discontinuities in the value of this counter are indicated via discontinuities in the value of sysUpTime.
1.3.6.1.2.1.6.5Counter32read-onlycurrent
tcpPassiveOpens
OBJECT-TYPE
The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state. Discontinuities in the value of this counter are indicated via discontinuities in the value of sysUpTime.
1.3.6.1.2.1.6.6Counter32read-onlycurrent
tcpAttemptFails
OBJECT-TYPE
The number of times that 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 that TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state. Discontinuities in the value of this counter are indicated via discontinuities in the value of sysUpTime.
1.3.6.1.2.1.6.7Counter32read-onlycurrent
tcpEstabResets
OBJECT-TYPE
The number of times that TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state. Discontinuities in the value of this counter are indicated via discontinuities in the value of sysUpTime.
1.3.6.1.2.1.6.8Counter32read-onlycurrent
tcpCurrEstab
OBJECT-TYPE
The number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT.
1.3.6.1.2.1.6.9Gauge32read-onlycurrent
tcpInSegs
OBJECT-TYPE
The total number of segments received, including those received in error. This count includes segments received on currently established connections. Discontinuities in the value of this counter are indicated via discontinuities in the value of sysUpTime.
1.3.6.1.2.1.6.10Counter32read-onlycurrent
tcpOutSegs
OBJECT-TYPE
The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets. Discontinuities in the value of this counter are indicated via discontinuities in the value of sysUpTime.
1.3.6.1.2.1.6.11Counter32read-onlycurrent
tcpRetransSegs
OBJECT-TYPE
The total number of segments retransmitted; that is, the number of TCP segments transmitted containing one or more previously transmitted octets. Discontinuities in the value of this counter are indicated via discontinuities in the value of sysUpTime.
1.3.6.1.2.1.6.12Counter32read-onlycurrent
tcpConnTable
OBJECT-TYPE
A table containing information about existing IPv4-specific TCP connections or listeners. This table has been deprecated in favor of the version neutral tcpConnectionTable.
1.3.6.1.2.1.6.13not-accessibledeprecated
tcpConnEntry
OBJECT-TYPE
A conceptual row of the tcpConnTable containing information about a particular current IPv4 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.
1.3.6.1.2.1.6.13.1not-accessibledeprecated
tcpConnState
OBJECT-TYPE
The state of this TCP connection. The only value that 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 the TCB (as defined in [RFC793]) of the corresponding connection on the managed node is deleted, 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.3.6.1.2.1.6.13.1.1INTEGER {closed(1), listen(2), synSent(3), synReceived(4), established(5), finWait1(6), finWait2(7), closeWait(8), lastAck(9), closing(10), timeWait(11), deleteTCB(12)}read-writedeprecated
tcpConnLocalAddress
OBJECT-TYPE
The local IP address for this TCP connection. In the case of a connection in the listen state willing to accept connections for any IP interface associated with the node, the value 0.0.0.0 is used.
1.3.6.1.2.1.6.13.1.2IpAddressread-onlydeprecated
tcpConnLocalPort
OBJECT-TYPE
The local port number for this TCP connection.
1.3.6.1.2.1.6.13.1.3Integer32 (0..65535)read-onlydeprecated
tcpConnRemAddress
OBJECT-TYPE
The remote IP address for this TCP connection.
1.3.6.1.2.1.6.13.1.4IpAddressread-onlydeprecated
tcpConnRemPort
OBJECT-TYPE
The remote port number for this TCP connection.
1.3.6.1.2.1.6.13.1.5Integer32 (0..65535)read-onlydeprecated
tcpInErrs
OBJECT-TYPE
The total number of segments received in error (e.g., bad TCP checksums). Discontinuities in the value of this counter are indicated via discontinuities in the value of sysUpTime.
1.3.6.1.2.1.6.14Counter32read-onlycurrent
tcpOutRsts
OBJECT-TYPE
The number of TCP segments sent containing the RST flag. Discontinuities in the value of this counter are indicated via discontinuities in the value of sysUpTime.
1.3.6.1.2.1.6.15Counter32read-onlycurrent
tcpHCInSegs
OBJECT-TYPE
The total number of segments received, including those received in error. This count includes segments received on currently established connections. This object is the 64-bit equivalent of tcpInSegs. Discontinuities in the value of this counter are indicated via discontinuities in the value of sysUpTime.
1.3.6.1.2.1.6.17Counter64read-onlycurrent
tcpHCOutSegs
OBJECT-TYPE
The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets. This object is the 64-bit equivalent of tcpOutSegs. Discontinuities in the value of this counter are indicated via discontinuities in the value of sysUpTime.
1.3.6.1.2.1.6.18Counter64read-onlycurrent
tcpConnectionTable
OBJECT-TYPE
A table containing information about existing TCP connections. Note that unlike earlier TCP MIBs, there is a separate table for connections in the LISTEN state.
1.3.6.1.2.1.6.19not-accessiblecurrent
tcpConnectionEntry
OBJECT-TYPE
A conceptual row of the tcpConnectionTable 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.
1.3.6.1.2.1.6.19.1not-accessiblecurrent
tcpConnectionLocalAddressType
OBJECT-TYPE
The address type of tcpConnectionLocalAddress.
1.3.6.1.2.1.6.19.1.1InetAddressTypenot-accessiblecurrent
tcpConnectionLocalAddress
OBJECT-TYPE
The local IP address for this TCP connection. The type of this address is determined by the value of tcpConnectionLocalAddressType. As this object is used in the index for the tcpConnectionTable, implementors should be careful not to create entries that would result in OIDs with more than 128 subidentifiers; otherwise the information cannot be accessed by using SNMPv1, SNMPv2c, or SNMPv3.
1.3.6.1.2.1.6.19.1.2InetAddressnot-accessiblecurrent
tcpConnectionLocalPort
OBJECT-TYPE
The local port number for this TCP connection.
1.3.6.1.2.1.6.19.1.3InetPortNumbernot-accessiblecurrent
tcpConnectionRemAddressType
OBJECT-TYPE
The address type of tcpConnectionRemAddress.
1.3.6.1.2.1.6.19.1.4InetAddressTypenot-accessiblecurrent
tcpConnectionRemAddress
OBJECT-TYPE
The remote IP address for this TCP connection. The type of this address is determined by the value of tcpConnectionRemAddressType. As this object is used in the index for the tcpConnectionTable, implementors should be careful not to create entries that would result in OIDs with more than 128 subidentifiers; otherwise the information cannot be accessed by using SNMPv1, SNMPv2c, or SNMPv3.
1.3.6.1.2.1.6.19.1.5InetAddressnot-accessiblecurrent
tcpConnectionRemPort
OBJECT-TYPE
The remote port number for this TCP connection.
1.3.6.1.2.1.6.19.1.6InetPortNumbernot-accessiblecurrent
tcpConnectionState
OBJECT-TYPE
The state of this TCP connection. The value listen(2) is included only for parallelism to the old tcpConnTable and should not be used. A connection in LISTEN state should be present in the tcpListenerTable. The only value that 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 the TCB (as defined in [RFC793]) of the corresponding connection on the managed node is deleted, 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.3.6.1.2.1.6.19.1.7INTEGER {closed(1), listen(2), synSent(3), synReceived(4), established(5), finWait1(6), finWait2(7), closeWait(8), lastAck(9), closing(10), timeWait(11), deleteTCB(12)}read-writecurrent
tcpConnectionProcess
OBJECT-TYPE
The system's process ID for the process associated with this connection, or zero if there is no such process. This value is expected to be the same as HOST-RESOURCES-MIB:: hrSWRunIndex or SYSAPPL-MIB::sysApplElmtRunIndex for some row in the appropriate tables.
1.3.6.1.2.1.6.19.1.8Unsigned32read-onlycurrent
tcpListenerTable
OBJECT-TYPE
A table containing information about TCP listeners. A listening application can be represented in three possible ways: 1. An application that is willing to accept both IPv4 and IPv6 datagrams is represented by a tcpListenerLocalAddressType of unknown (0) and a tcpListenerLocalAddress of ''h (a zero-length octet-string). 2. An application that is willing to accept only IPv4 or IPv6 datagrams is represented by a tcpListenerLocalAddressType of the appropriate address type and a tcpListenerLocalAddress of '0.0.0.0' or '::' respectively. 3. An application that is listening for data destined only to a specific IP address, but from any remote system, is represented by a tcpListenerLocalAddressType of an appropriate address type, with tcpListenerLocalAddress as the specific local address. NOTE: The address type in this table represents the address type used for the communication, irrespective of the higher-layer abstraction. For example, an application using IPv6 'sockets' to communicate via IPv4 between ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would use InetAddressType ipv4(1)).
1.3.6.1.2.1.6.20not-accessiblecurrent
tcpListenerEntry
OBJECT-TYPE
A conceptual row of the tcpListenerTable containing information about a particular TCP listener.
1.3.6.1.2.1.6.20.1not-accessiblecurrent
tcpListenerLocalAddressType
OBJECT-TYPE
The address type of tcpListenerLocalAddress. The value should be unknown (0) if connection initiations to all local IP addresses are accepted.
1.3.6.1.2.1.6.20.1.1InetAddressTypenot-accessiblecurrent
tcpListenerLocalAddress
OBJECT-TYPE
The local IP address for this TCP connection. The value of this object can be represented in three possible ways, depending on the characteristics of the listening application: 1. For an application willing to accept both IPv4 and IPv6 datagrams, the value of this object must be ''h (a zero-length octet-string), with the value of the corresponding tcpListenerLocalAddressType object being unknown (0). 2. For an application willing to accept only IPv4 or IPv6 datagrams, the value of this object must be '0.0.0.0' or '::' respectively, with tcpListenerLocalAddressType representing the appropriate address type. 3. For an application which is listening for data destined only to a specific IP address, the value of this object is the specific local address, with tcpListenerLocalAddressType representing the appropriate address type. As this object is used in the index for the tcpListenerTable, implementors should be careful not to create entries that would result in OIDs with more than 128 subidentifiers; otherwise the information cannot be accessed, using SNMPv1, SNMPv2c, or SNMPv3.
1.3.6.1.2.1.6.20.1.2InetAddressnot-accessiblecurrent
tcpListenerLocalPort
OBJECT-TYPE
The local port number for this TCP connection.
1.3.6.1.2.1.6.20.1.3InetPortNumbernot-accessiblecurrent
tcpListenerProcess
OBJECT-TYPE
The system's process ID for the process associated with this listener, or zero if there is no such process. This value is expected to be the same as HOST-RESOURCES-MIB:: hrSWRunIndex or SYSAPPL-MIB::sysApplElmtRunIndex for some row in the appropriate tables.
1.3.6.1.2.1.6.20.1.4Unsigned32read-onlycurrent
tcpMIBConformance
OBJECT-IDENTITY
1.3.6.1.2.1.49.2
tcpMIBCompliances
OBJECT-IDENTITY
1.3.6.1.2.1.49.2.1
tcpMIBGroups
OBJECT-IDENTITY
1.3.6.1.2.1.49.2.2

Conformance

NameOIDStatus
tcpMIBCompliance
MODULE-COMPLIANCE
The compliance statement for IPv4-only systems that implement TCP. In order to be IP version independent, this compliance statement is deprecated in favor of tcpMIBCompliance2. However, agents are still encouraged to implement these objects in order to interoperate with the deployed base of managers.
1.3.6.1.2.1.49.2.1.1deprecated
tcpMIBCompliance2
MODULE-COMPLIANCE
The compliance statement for systems that implement TCP. A number of INDEX objects cannot be represented in the form of OBJECT clauses in SMIv2 but have the following compliance requirements, expressed in OBJECT clause form in this description clause: -- OBJECT tcpConnectionLocalAddressType -- SYNTAX InetAddressType { ipv4(1), ipv6(2) } -- DESCRIPTION -- This MIB requires support for only global IPv4 -- and IPv6 address types. -- -- OBJECT tcpConnectionRemAddressType -- SYNTAX InetAddressType { ipv4(1), ipv6(2) } -- DESCRIPTION -- This MIB requires support for only global IPv4 -- and IPv6 address types. -- -- OBJECT tcpListenerLocalAddressType -- SYNTAX InetAddressType { unknown(0), ipv4(1), -- ipv6(2) } -- DESCRIPTION -- This MIB requires support for only global IPv4 -- and IPv6 address types. The type unknown also -- needs to be supported to identify a special -- case in the listener table: a listen using -- both IPv4 and IPv6 addresses on the device. --
1.3.6.1.2.1.49.2.1.2current
tcpGroup
OBJECT-GROUP
The tcp group of objects providing for management of TCP entities.
1.3.6.1.2.1.49.2.2.1deprecated
tcpBaseGroup
OBJECT-GROUP
The group of counters common to TCP entities.
1.3.6.1.2.1.49.2.2.2current
tcpConnectionGroup
OBJECT-GROUP
The group provides general information about TCP connections.
1.3.6.1.2.1.49.2.2.3current
tcpListenerGroup
OBJECT-GROUP
This group has objects providing general information about TCP listeners.
1.3.6.1.2.1.49.2.2.4current
tcpHCGroup
OBJECT-GROUP
The group of objects providing for counters of high speed TCP implementations.
1.3.6.1.2.1.49.2.2.5current