IPV6-TCP-MIB

All MIBs › IPV6-TCP-MIB

Organization: IETF IPv6 MIB Working Group

Last Updated: 2017-02-22

Category: IP and Core Protocols

Description: Defines managed objects for entities implementing TCP over IPv6, providing TCP connection and listener information for IPv6 networks.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring IPV6-TCP-MIB with a free 30-day trial of IPNetwork Monitor.

What Is IPV6-TCP-MIB?

IPV6-TCP-MIB is a vendor-neutral IETF module that extends standard TCP management to connections whose endpoints use IPv6 addresses, complementing the classic TCP-MIB which was IPv4-only. It exposes a connection table listing each active TCP connection's local and remote IPv6 address and port, the associated interface index, and the connection's TCP state (e.g. established, listen, time-wait). Its practical use is monitoring software/network-stack status on a host or network device: confirming that expected IPv6 services are listening, that client connections are progressing through normal TCP states rather than piling up in problem states, and correlating connections to specific interfaces. It is closely tied to and structured in parallel with the base TCP-MIB and the IPv6 addressing conventions in IP-MIB/IPV6-MIB. It is typically deployed on any dual-stack or IPv6-only host, server, or router whose management station needs visibility into IPv6 TCP session activity, as defined in the IPV6-TCP-MIB RFC that extends TCP-MIB semantics to IPv6 endpoints.

IPNetwork Monitor allows you to monitor SNMP objects defined in IPV6-TCP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

vendor-neutral, standards-based MIB, not tied to a specific manufacturer
any IPv6-capable host, server, or network device

Monitoring Examples

An administrator walks ipv6TcpConnTable (ipv6TcpConnEntry) to see all IPv6 TCP sessions, using ipv6TcpConnLocalAddress/ipv6TcpConnLocalPort to confirm a service is bound and listening, and ipv6TcpConnRemAddress/ipv6TcpConnRemPort to identify remote peers. A large number of entries stuck in a non-established ipv6TcpConnState (e.g. SYN-received) would reveal a half-open connection flood or a firewall/NAT issue affecting only IPv6 clients. ipv6TcpConnIfIndex ties a given session back to the specific network interface it traversed, useful for isolating problems to one link.

What Can Be Monitored

active IPv6 TCP connections
local and remote address/port pairs
TCP connection state
associated interface index

Imported Objects

From IPV6-TC

Ipv6Address
Ipv6IfIndexOrZero

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
experimental
mib-2

OIDs

OID symbolic	OID numeric	Type	Access	Description
tcp	1.3.6.1.2.1.6
ipv6TcpConnTable	1.3.6.1.2.1.6.16		not-accessible	A table containing TCP connection-specific information, for only those connections whose endpoints are IPv6 addresses. This table is obsoleted by TCP-MIB::tcpConnectionTable.
ipv6TcpConnEntry	1.3.6.1.2.1.6.16.1		not-accessible	A conceptual row of the ipv6TcpConnTable 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. Note that conceptual rows in this table require an additional index object compared to tcpConnTable, since IPv6 addresses are not guaranteed to be unique on the managed node. This entry is obsoleted by TCP-MIB::tcpConnectionEntry.
ADR ipv6TcpConnLocalAddress	1.3.6.1.2.1.6.16.1.1	Ipv6Address	not-accessible	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.
INT ipv6TcpConnLocalPort	1.3.6.1.2.1.6.16.1.2	INTEGER	not-accessible	The local port number for this TCP connection. This object is obsoleted by TCP-MIB::tcpConnectionLocalPort.
ADR ipv6TcpConnRemAddress	1.3.6.1.2.1.6.16.1.3	Ipv6Address	not-accessible	The remote IPv6 address for this TCP connection. This object is obsoleted by TCP-MIB::tcpConnectionRemAddress.
INT ipv6TcpConnRemPort	1.3.6.1.2.1.6.16.1.4	INTEGER	not-accessible	The remote port number for this TCP connection. This object is obsoleted by TCP-MIB::tcpConnectionRemPort.
IPV ipv6TcpConnIfIndex	1.3.6.1.2.1.6.16.1.5	Ipv6IfIndexOrZero	not-accessible	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.
INT ipv6TcpConnState	1.3.6.1.2.1.6.16.1.6	INTEGER	read-write	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.
ipv6TcpMIB	1.3.6.1.3.86			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).
ipv6TcpConformance	1.3.6.1.3.86.2
ipv6TcpCompliances	1.3.6.1.3.86.2.1
ipv6TcpCompliance	1.3.6.1.3.86.2.1.1			The compliance statement for SNMPv2 entities which implement TCP over IPv6. This compliance statement is obsoleted by TCP-MIB::tcpMIBCompliance2.
ipv6TcpGroups	1.3.6.1.3.86.2.2
ipv6TcpGroup	1.3.6.1.3.86.2.2.1			The group of objects providing management of TCP over IPv6. This group is obsoleted by several groups in TCP-MIB.

RFC description

Obsolete IPv6 TCP connection tracking MIB replaced by TCP-MIB; provides IPv6 endpoint connection statistics.

Start monitoring IPv6-capable hosts and network devices with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download IPV6-TCP-MIB

What Is IPV6-TCP-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description