All MIBs › RMON2-MIB › alMatrixTopNAppProtocolDirLocalIndex
alMatrixTopNAppProtocolDirLocalIndex
Module: RMON2-MIB
OID (symbolic): RMON2-MIB::alMatrixTopNAppProtocolDirLocalIndex
OID (numeric): 1.3.6.1.2.1.16.17.4.1.5
Node type: OBJECT-TYPE
Type: Integer32
Access: read-only
Description:
The type of the protocol counted by this matrix entry.
What is alMatrixTopNAppProtocolDirLocalIndex?
This number identifies the application or transport protocol (like TCP, UDP, or specific applications) being used in this conversation. Engineers use this to narrow down root causes of congestion by seeing whether heavy traffic is HTTP, FTP, database replication, or other protocol types. For instance, a value of "6" might mean TCP, showing that the high-traffic conversation uses connection-oriented reliable delivery rather than UDP's fire-and-forget model.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.16.17.4.1.5 snmpwalk -v2c -c public <target> RMON2-MIB::alMatrixTopNAppProtocolDirLocalIndex
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.16.17.4.1.5.1 snmpget -v2c -c public <target> RMON2-MIB::alMatrixTopNAppProtocolDirLocalIndex.1
OID Breakdown
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | BIANCA-BRICK-PPP-MIB |
| 1.3.6 | dod | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1 | internet | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.2 | mgmt | BKTEL-HFC862-BASE-MIB |
| 1.3.6.1.2.1 | mib_2 | CHECKPOINT-MIB-2 |
| 1.3.6.1.2.1.16 | rmon | LBHUB-BOOM-MIB |
| 1.3.6.1.2.1.16.17 | alMatrix | RMON2-MIB |
| 1.3.6.1.2.1.16.17.4 | alMatrixTopNTable | RMON2-MIB |
| 1.3.6.1.2.1.16.17.4.1 | alMatrixTopNEntry | RMON2-MIB |
| 1.3.6.1.2.1.16.17.4.1.5 | alMatrixTopNAppProtocolDirLocalIndex | RMON2-MIB |