tcpRtoAlgorithm |
.1.3.6.1.2.1.6.1 |
The algorithm used to determine the timeout value used for
retransmitting unacknowledged octets.
|
tcpRtoMin |
.1.3.6.1.2.1.6.2 |
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.
|
tcpRtoMax |
.1.3.6.1.2.1.6.3 |
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).
|
tcpMaxConn |
.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.
|
tcpActiveOpens |
.1.3.6.1.2.1.6.5 |
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.
|
tcpPassiveOpens |
.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.
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime.
|
tcpAttemptFails |
.1.3.6.1.2.1.6.7 |
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.
|
tcpEstabResets |
.1.3.6.1.2.1.6.8 |
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.
|
tcpCurrEstab |
.1.3.6.1.2.1.6.9 |
The number of TCP connections for which the current state
is either ESTABLISHED or CLOSE-WAIT.
|
tcpInSegs |
.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.
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime.
|
tcpOutSegs |
.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.
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime.
|
tcpRetransSegs |
.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.
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime.
|
tcpInErrs |
.1.3.6.1.2.1.6.14 |
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.
|
tcpOutRsts |
.1.3.6.1.2.1.6.15 |
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.
|
tcpHCInSegs |
.1.3.6.1.2.1.6.17 |
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.
|
tcpHCOutSegs |
.1.3.6.1.2.1.6.18 |
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.
|
tcpConnectionEntry |
.1.3.6.1.2.1.6.19.1 |
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.
|
tcpListenerEntry |
.1.3.6.1.2.1.6.20.1 |
A conceptual row of the tcpListenerTable containing
information about a particular TCP listener.
|
tcpConnEntry |
.1.3.6.1.2.1.6.13.1 |
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.
|
tcpConnectionLocalAddressType |
.1.3.6.1.2.1.6.19.1.1 |
The address type of tcpConnectionLocalAddress.
|
tcpConnectionLocalAddress |
.1.3.6.1.2.1.6.19.1.2 |
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.
|
tcpConnectionLocalPort |
.1.3.6.1.2.1.6.19.1.3 |
The local port number for this TCP connection.
|
tcpConnectionRemAddressType |
.1.3.6.1.2.1.6.19.1.4 |
The address type of tcpConnectionRemAddress.
|
tcpConnectionRemAddress |
.1.3.6.1.2.1.6.19.1.5 |
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.
|
tcpConnectionRemPort |
.1.3.6.1.2.1.6.19.1.6 |
The remote port number for this TCP connection.
|
tcpConnectionState |
.1.3.6.1.2.1.6.19.1.7 |
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).
|
tcpConnectionProcess |
.1.3.6.1.2.1.6.19.1.8 |
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.
|
tcpListenerLocalAddressType |
.1.3.6.1.2.1.6.20.1.1 |
The address type of tcpListenerLocalAddress. The value
should be unknown (0) if connection initiations to all
local IP addresses are accepted.
|
tcpListenerLocalAddress |
.1.3.6.1.2.1.6.20.1.2 |
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.
|
tcpListenerLocalPort |
.1.3.6.1.2.1.6.20.1.3 |
The local port number for this TCP connection.
|
tcpListenerProcess |
.1.3.6.1.2.1.6.20.1.4 |
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.
|
tcpConnLocalAddress |
.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 willing to
accept connections for any IP interface associated with the
node, the value 0.0.0.0 is used.
|
tcpConnLocalPort |
.1.3.6.1.2.1.6.13.1.3 |
The local port number for this TCP connection.
|
tcpConnRemAddress |
.1.3.6.1.2.1.6.13.1.4 |
The remote IP address for this TCP connection.
|
tcpConnRemPort |
.1.3.6.1.2.1.6.13.1.5 |
The remote port number for this TCP connection.
|
tcpConnState |
.1.3.6.1.2.1.6.13.1.1 |
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).
|