RMON2-MIB :: protocolDirType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsRMON2-MIBprotocolDirType

protocolDirType

Module: RMON2-MIB

OID (symbolic): RMON2-MIB::protocolDirType

OID (numeric): 1.3.6.1.2.1.16.11.2.1.5

Node type: OBJECT-TYPE

Type: Bits

Access: read-only

Description: This object describes 2 attributes of this protocol directory entry.

The presence or absence of the 'extensible' bit describes whether this protocol directory entry can be extended by the user by creating protocol directory entries that are children of this protocol.

An example of an entry that will often allow extensibility is

'ip.udp'. The probe may automatically populate some children of this node, such as 'ip.udp.snmp' and 'ip.udp.dns'. A probe administrator or user may also populate additional children via remote SNMP requests that create entries in this table. When a child node is added for a protocol for which the probe has no built-in support extending a parent node (for which the probe does have built-in support), that child node is not extendable. This is termed 'limited extensibility'.

When a child node is added through this extensibility mechanism, the values of protocolDirLocalIndex and protocolDirType shall be assigned by the agent.

The other objects in the entry will be assigned by the manager who is creating the new entry.

This object also describes whether this agent can recognize addresses for this protocol, should it be a network-level protocol. That is, while a probe may be able to recognize packets of a particular network-layer protocol and count them, it takes additional logic to be able to recognize the addresses in this protocol and to populate network-layer or application-layer tables with the addresses in this protocol. If this bit is set, the agent will recognize network-layer addresses for this protocol and populate the network- and application-layer host and matrix tables with these protocols.

Note that when an entry is created, the agent will supply values for the bits that match the capabilities of the agent with respect to this protocol. Note that since row creations usually exercise the limited extensibility feature, these bits will usually be set to zero.

What is protocolDirType?

This byte describes whether a protocol entry can be extended with sub-protocols (like IP.UDP under IP). It tells you whether custom or vendor-specific protocols can be added below this protocol layer. A protocol like IP.UDP is usually extensible so administrators can add monitoring for IP.UDP.SNMP.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.16.11.2.1.5
snmpwalk -v2c -c public <target> RMON2-MIB::protocolDirType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.16.11.2.1.5.1
snmpget -v2c -c public <target> RMON2-MIB::protocolDirType.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> protocolDirType.1

Start monitoring RMON-capable network probes, switches, and routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RMON2-MIB::protocolDirType OID value, configure state conditions and alerts, and monitor any RMON-capable network probes, switches, and routers from a single console.

OID Breakdown

Upper-level ancestors (7 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.16rmonLBHUB-BOOM-MIB
Numeric OIDNameModule
1.3.6.1.2.1.16.11protocolDirRMON2-MIB
1.3.6.1.2.1.16.11.2protocolDirTableRMON2-MIB
1.3.6.1.2.1.16.11.2.1protocolDirEntryRMON2-MIB
1.3.6.1.2.1.16.11.2.1.5protocolDirTypeRMON2-MIB