Reference record for OID 1.3.6.1.2.1.16.11.2


parent
1.3.6.1.2.1.16.11 (protocolDir)
node code
2
node name
protocolDirTable
dot oid
1.3.6.1.2.1.16.11.2
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) rmon(16) protocolDir(11) protocolDirTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) rmon(16) protocolDir(11) protocolDirTable(2)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) rmon(16) protocolDir(11) protocolDirTable(2)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) rmon(16) protocolDir(11) protocolDirTable(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) rmon(16) protocolDir(11) protocolDirTable(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) rmon(16) protocolDir(11) protocolDirTable(2)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/rmon/protocolDir/protocolDirTable
  • /iso/identified-organization/dod/internet/mgmt/mib/rmon/protocolDir/protocolDirTable
  • /iso/org/dod/internet/mgmt/mib-2/rmon/protocolDir/protocolDirTable
  • /iso/org/dod/internet/mgmt/mib/rmon/protocolDir/protocolDirTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/rmon/protocolDir/protocolDirTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/rmon/protocolDir/protocolDirTable
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/16/11/2

    Description by circitor

    This table lists the protocols that this agent has the
    capability to decode and count. There is one entry in this
    table for each such protocol. These protocols represent
    different network layer, transport layer, and higher-layer
    protocols. The agent should boot up with this table
    preconfigured with those protocols that it knows about and
    wishes to monitor. Implementations are strongly encouraged to
    support protocols higher than the network layer (at least for
    the protocol distribution group), even for implementations
    that don't support the application layer groups.

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

    Description by cisco_v1

    This table lists the protocols that this agent has the
    capability to decode and count. There is one entry in this
    table for each such protocol. These protocols represent
    different network layer, transport layer, and higher-layer
    protocols. The agent should boot up with this table
    preconfigured with those protocols that it knows about and
    wishes to monitor. Implementations are strongly encouraged to
    support protocols higher than the network layer (at least for
    the protocol distribution group), even for implementations
    that don't support the application layer groups.

    Description by oid_info

    protocolDirTable OBJECT-TYPE
    SYNTAX SEQUENCE OF ProtocolDirEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
    "This table lists the protocols that this agent has the
    capability to decode and count. There is one entry in this
    table for each such protocol. These protocols represent
    different network layer, transport layer, and higher-layer
    protocols. The agent should boot up with this table
    preconfigured with those protocols that it knows about and
    wishes to monitor. Implementations are strongly encouraged to
    support protocols higher than the network layer (at least for
    the protocol distribution group), even for implementations
    that don support the application layer groups."

    View at oid-info.com

    Description by mibdepot

    This table lists the protocols that this agent has the
    capability to decode and count. There is one entry in this
    table for each such protocol. These protocols represent
    different network-layer, transport-layer, and higher-layer



    protocols. The agent should boot up with this table
    preconfigured with those protocols that it knows about and
    wishes to monitor. Implementations are strongly encouraged to
    support protocols higher than the network layer (at least for
    the protocol distribution group), even for implementations
    that don't support the application-layer groups.

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

    Description by cisco

    This table lists the protocols that this agent has the
    capability to decode and count. There is one entry in this
    table for each such protocol. These protocols represent
    different network layer, transport layer, and higher-layer
    protocols. The agent should boot up with this table
    preconfigured with those protocols that it knows about and
    wishes to monitor. Implementations are strongly encouraged to
    support protocols higher than the network layer (at least for
    the protocol distribution group), even for implementations
    that don't support the application layer groups.

    Information by circitor

    protocolDirTable OBJECT-TYPE SYNTAX SEQUENCE OF ProtocolDirEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table lists the protocols that this agent has the capability to decode and count. There is one entry in this table for each such protocol. These protocols represent different network layer, transport layer, and higher-layer protocols. The agent should boot up with this table preconfigured with those protocols that it knows about and wishes to monitor. Implementations are strongly encouraged to support protocols higher than the network layer (at least for the protocol distribution group), even for implementations that don't support the application layer groups." ::= { protocolDir 2 }

    Information by cisco_v1

    protocolDirTable OBJECT-TYPE SYNTAX SEQUENCE OF ProtocolDirEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table lists the protocols that this agent has the capability to decode and count. There is one entry in this table for each such protocol. These protocols represent different network layer, transport layer, and higher-layer protocols. The agent should boot up with this table preconfigured with those protocols that it knows about and wishes to monitor. Implementations are strongly encouraged to support protocols higher than the network layer (at least for the protocol distribution group), even for implementations that don't support the application layer groups." ::= { protocolDir 2 }

    Information by oid_info

    Automatically extracted from RFC2021

    Information by mibdepot

    protocolDirTable OBJECT-TYPE SYNTAX SEQUENCE OF ProtocolDirEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table lists the protocols that this agent has the capability to decode and count. There is one entry in this table for each such protocol. These protocols represent different network-layer, transport-layer, and higher-layer protocols. The agent should boot up with this table preconfigured with those protocols that it knows about and wishes to monitor. Implementations are strongly encouraged to support protocols higher than the network layer (at least for the protocol distribution group), even for implementations that don't support the application-layer groups." ::= { protocolDir 2 }

    Information by cisco

    protocolDirTable OBJECT-TYPE SYNTAX SEQUENCE OF ProtocolDirEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table lists the protocols that this agent has the capability to decode and count. There is one entry in this table for each such protocol. These protocols represent different network layer, transport layer, and higher-layer protocols. The agent should boot up with this table preconfigured with those protocols that it knows about and wishes to monitor. Implementations are strongly encouraged to support protocols higher than the network layer (at least for the protocol distribution group), even for implementations that don't support the application layer groups." ::= { protocolDir 2 }

    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.16.11.2.1 protocolDirEntry 10 10 A conceptual row in the protocolDirTable.

    An example of the indexing of this entry is
    protocolDirLocalIndex.8.0.0.0.1.0.0.8.0.2.0…

    Brothers (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.16.11.1 protocolDirLastChange 1 1 The value of sysUpTime at the time the protocol directory
    was last modified, either through insertions or deletions,
    or through m…