Reference record for OID 1.3.6.1.2.1.6.20


parent
1.3.6.1.2.1.6 (tcp)
node code
20
node name
tcpListenerTable
dot oid
1.3.6.1.2.1.6.20
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) tcp(6) tcpListenerTable(20)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) tcp(6) tcpListenerTable(20)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) tcp(6) tcpListenerTable(20)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) tcp(6) tcpListenerTable(20)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) tcp(6) tcpListenerTable(20)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) tcp(6) tcpListenerTable(20)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/tcp/tcpListenerTable
  • /iso/identified-organization/dod/internet/mgmt/mib/tcp/tcpListenerTable
  • /iso/org/dod/internet/mgmt/mib-2/tcp/tcpListenerTable
  • /iso/org/dod/internet/mgmt/mib/tcp/tcpListenerTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/tcp/tcpListenerTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/tcp/tcpListenerTable
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/6/20

    Description by circitor

    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)).

    Parsed from file TCP-MIB.mib
    Module: TCP-MIB

    Description by cisco_v1

    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)).

    Description by oid_info

    tcpListenerTable OBJECT-TYPE
    SYNTAX SEQUENCE OF TcpListenerEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
    "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

    View at oid-info.com

    Description by mibdepot

    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)).

    Parsed from file TCP-MIB.mib.txt
    Company: None
    Module: TCP-MIB

    Description by cisco

    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)).

    Information by circitor

    tcpListenerTable OBJECT-TYPE SYNTAX SEQUENCE OF TcpListenerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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))." ::= { tcp 20 }

    Information by cisco_v1

    tcpListenerTable OBJECT-TYPE SYNTAX SEQUENCE OF TcpListenerEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "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))." ::= { tcp 20 }

    Information by oid_info

    Automatically extracted from RFC4022

    Information by mibdepot

    tcpListenerTable OBJECT-TYPE SYNTAX SEQUENCE OF TcpListenerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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))." ::= { tcp 20 }

    Information by cisco

    tcpListenerTable OBJECT-TYPE SYNTAX SEQUENCE OF TcpListenerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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))." ::= { tcp 20 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.6.20.1 tcpListenerEntry 4 4 A conceptual row of the tcpListenerTable containing
    information about a particular TCP listener.

    Brothers (19)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.6.1 tcpRtoAlgorithm 0 0 The algorithm used to determine the timeout value
    used for retransmitting unacknowledged octets.
    1.3.6.1.2.1.6.2 tcpRtoMin 0 0 The minimum value permitted by a TCP implementation for
    the retransmission timeout, measured in milliseconds.
    More refined semant…
    1.3.6.1.2.1.6.3 tcpRtoMax 0 0 The maximum value permitted by a TCP implementation for
    the retransmission timeout, measured in milliseconds.
    More refined semant…
    1.3.6.1.2.1.6.4 tcpMaxConn 0 0 The limit on the total number of TCP connections
    the entity can support. In entities where the
    maximum number of connections is …
    1.3.6.1.2.1.6.5 tcpActiveOpens 0 0 The number of times TCP connections have made a
    direct transition to the SYN-SENT state from the
    CLOSED state.
    1.3.6.1.2.1.6.6 tcpPassiveOpens 0 0 The number of times TCP connections have made a
    direct transition to the SYN-RCVD state from the
    LISTEN state.
    1.3.6.1.2.1.6.7 tcpAttemptFails 0 0 The number of times TCP connections have made a
    direct transition to the CLOSED state from either
    the SYN-SENT state or the SYN-R…
    1.3.6.1.2.1.6.8 tcpEstabResets 0 0 The number of times TCP connections have made a
    direct transition to the CLOSED state from either
    the ESTABLISHED state or the CL…
    1.3.6.1.2.1.6.9 tcpCurrEstab 1 1 The number of TCP connections for which the current state
    is either ESTABLISHED or CLOSE-WAIT.
    1.3.6.1.2.1.6.10 tcpInSegs 0 0 The total number of segments received, including
    those received in error. This count includes
    segments received on currently est…
    1.3.6.1.2.1.6.11 tcpOutSegs 0 0 The total number of segments sent, including
    those on current connections but excluding those
    containing only retransmitted octet…
    1.3.6.1.2.1.6.12 tcpRetransSegs 0 0 The total number of segments retransmitted - that
    is, the number of TCP segments transmitted
    containing one or more previously tr…
    1.3.6.1.2.1.6.13 tcpConnTable 1 6 A table containing TCP connection-specific
    information.
    1.3.6.1.2.1.6.14 tcpInErrs 0 0 The total number of segments received in error
    (e.g., bad TCP checksums).
    1.3.6.1.2.1.6.15 tcpOutRsts 0 0 The number of TCP segments sent containing the
    RST flag.
    1.3.6.1.2.1.6.16 ipv6TcpConnTable 2 8 A table containing TCP connection-specific information,
    for only those connections whose endpoints are IPv6 addresses.
    1.3.6.1.2.1.6.17 tcpHCInSegs 1 1 The total number of segments received, including those
    received in error. This count includes segments received

    on currently est…
    1.3.6.1.2.1.6.18 tcpHCOutSegs 1 1 The total number of segments sent, including those on
    current connections but excluding those containing only
    retransmitted octet…
    1.3.6.1.2.1.6.19 tcpConnectionTable 1 13 A table containing information about existing TCP
    connections. Note that unlike earlier TCP MIBs, there
    is a separate table for …