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.
The indexes of the table are tcpConnectionLocalAddressType, tcpConnectionLocalAddress, tcpConnectionLocalPort, tcpConnectionRemAddressType, tcpConnectionRemAddress, tcpConnectionRemPort.
OID |
Object |
Syntax |
Max Access |
Description |
Implemented Specifications |
---|---|---|---|---|---|
1.3.6.1.2.1.6.19.1.1 |
tcpConnectionLocalAddressType |
INTEGER{unknown(0),ipv4(1),ipv6(2),ipv4z(3),ipv6z(4),dns(16)} |
not-accessible |
The address type of tcpConnectionLocalAddress. |
The actually supported value range is IPv4(1); IPv6(3);IPv6z(4). Only supports IPv4(1), IPv6(3) and IPv6z(4)types |
1.3.6.1.2.1.6.19.1.2 |
tcpConnectionLocalAddress |
OCTET STRING{(0,255)} |
not-accessible |
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. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.6.19.1.3 |
tcpConnectionLocalPort |
Unsigned32{(0,65535)} |
not-accessible |
The local port number for this TCP connection. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.6.19.1.4 |
tcpConnectionRemAddressType |
INTEGER{unknown(0),ipv4(1),ipv6(2),ipv4z(3),ipv6z(4),dns(16)} |
not-accessible |
The address type of tcpConnectionRemAddress. |
The actually supported value range is IPv4(1); IPv6(3);IPv6z(4). Only supports IPv4(1), IPv6(3) and IPv6z(4)types |
1.3.6.1.2.1.6.19.1.5 |
tcpConnectionRemAddress |
OCTET STRING{(0,255)} |
not-accessible |
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. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.6.19.1.6 |
tcpConnectionRemPort |
Unsigned32{(0,65535)} |
not-accessible |
The remote port number for this TCP connection. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.6.19.1.7 |
tcpConnectionState |
INTEGER{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-write |
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). |
The actually supported access is read-only. |
1.3.6.1.2.1.6.19.1.8 |
tcpConnectionProcess |
Unsigned32 |
read-only |
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. |
This object is implemented as defined in the corresponding MIB files. |