The obsolete MIB module for entities implementing TCP over IPv6. Use the TCP-MIB instead.
Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
A table containing TCP connection-specific information, for only those connections whose endpoints are IPv6 addresses.
This table is obsoleted by TCP-MIB::tcpConnectionTable.
ipv6TcpConnLocalAddress
1.3.6.1.2.1.6.16.1.1
Ipv6AddressThis data type is used to model IPv6 addresses. This is a binary string of 16 octets in network byte-order. SIZE (16) · OCTET STRING · hint 2x:
The local IPv6 address for this TCP connection. In the case of a connection in the listen state which is willing to accept connections for any IPv6 address associated with the managed node, the value ::0 is used.
This object is obsoleted by TCP-MIB::tcpConnectionLocalAddressType.
ipv6TcpConnLocalPort
1.3.6.1.2.1.6.16.1.2
INTEGER (0..65535) · Integer32
The local port number for this TCP connection.
This object is obsoleted by TCP-MIB::tcpConnectionLocalPort.
ipv6TcpConnRemAddress
1.3.6.1.2.1.6.16.1.3
Ipv6AddressThis data type is used to model IPv6 addresses. This is a binary string of 16 octets in network byte-order. SIZE (16) · OCTET STRING · hint 2x:
The remote IPv6 address for this TCP connection.
This object is obsoleted by TCP-MIB::tcpConnectionRemAddress.
ipv6TcpConnRemPort
1.3.6.1.2.1.6.16.1.4
INTEGER (0..65535) · Integer32
The remote port number for this TCP connection.
This object is obsoleted by TCP-MIB::tcpConnectionRemPort.
ipv6TcpConnIfIndex
1.3.6.1.2.1.6.16.1.5
Ipv6IfIndexOrZeroThis textual convention is an extension of the Ipv6IfIndex convention. The latter defines a greater than zero value used to identify an IPv6 interface in the managed system. This extension permits the additional value of zero. The value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d
An index object used to disambiguate conceptual rows in the table, since the connection 4-tuple may not be unique.
If the connection's remote address (ipv6TcpConnRemAddress) is a link-local address and the connection's local address (ipv6TcpConnLocalAddress) is not a link-local address, this object identifies a local interface on the same link as the connection's remote link-local address.
Otherwise, this object identifies the local interface that is associated with the ipv6TcpConnLocalAddress for this TCP connection. If such a local interface cannot be determined, this object should take on the value 0. (A possible example of this would be if the value of ipv6TcpConnLocalAddress is ::0.)
The interface identified by a particular non-0 value of this index is the same interface as identified by the same value of ipv6IfIndex.
The value of this object must remain constant during the life of the TCP connection.
This object is obsoleted by the zone identifier in an InetAddressIPv6z address in either TCP-MIB::tcpConnectionLocalAddress or TCP-MIB::tcpConnectionRemAddress.
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 an error response ('badValue' for SNMPv1, 'wrongValue' for SNMPv2) 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).
This object is obsoleted by TCP-MIB::tcpConnectionState.