Dpi status
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Cisco MIB copies (LibreNMS/Observium Community)Cisco product and release MIB packages
OID reference
1.3.6.1.4.1.41916.12.6.2.4.1
Dpi status
Identification
{1 3 6 1 4 1 41916 12 6 2 4 1}
| Value | Name |
|---|---|
| 1 | disable |
| 2 | enable |
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.41916.12.6.2.4.1.0
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
appDpiSummaryStatus OBJECT-TYPE
SYNTAX INTEGER {disable(1),enable(2)}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Dpi status"
::= { appDpiSummary 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Dpi status
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Cisco MIB copies (LibreNMS/Observium Community)Cisco product and release MIB packages
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: appDpiSummaryStatus
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"appDpiSummaryStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"disable",
"(",
"1",
")",
",",
"enable",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"Dpi status\"",
"::=",
"{",
"appDpiSummary",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"disable",
1
],
[
"enable",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Dpi status"
],
null,
null,
null,
null
]
}Module: VIPTELA-OPER-VPN
See published definition above
{'IPV6-TC': ['Ipv6Address'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'DateAndTime', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'Counter64', 'Gauge32', 'IpAddress'], 'VIPTELA-GLOBAL': ['viptela', 'VpnIndex']}Related source files and packages:
Module: VIPTELA-OPER-VPN
{'IPV6-TC': ['Ipv6Address'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'DateAndTime', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'Counter64', 'Gauge32', 'IpAddress'], 'VIPTELA-GLOBAL': ['viptela', 'VpnIndex']}Vendor MIB copy from the LibreNMS archive.
Module: VIPTELA-OPER-VPN
{'IPV6-TC': ['Ipv6Address'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'DateAndTime', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'Counter64', 'Gauge32', 'IpAddress'], 'VIPTELA-GLOBAL': ['viptela']}Related source files and packages:
Vendor MIB copy from the Observium Community archive. Cisco support.
Module: VIPTELA-OPER-VPN
{'IPV6-TC': ['Ipv6Address'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'DateAndTime', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'Counter64', 'Gauge32', 'IpAddress'], 'VIPTELA-GLOBAL': ['viptela', 'VpnIndex']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.41916.12.6.2.4.2 | appDpiSummaryFlowsCreated | 0 | 0 | |
| 1.3.6.1.4.1.41916.12.6.2.4.3 | appDpiSummaryFlowsExpired | 0 | 0 | |
| 1.3.6.1.4.1.41916.12.6.2.4.4 | appDpiSummaryCurrentFlows | 0 | 0 | |
| 1.3.6.1.4.1.41916.12.6.2.4.5 | appDpiSummaryPeakFlows | 0 | 0 | |
| 1.3.6.1.4.1.41916.12.6.2.4.6 | appDpiSummaryCurrentRate | 0 | 0 | |
| 1.3.6.1.4.1.41916.12.6.2.4.7 | appDpiSummaryPeakRate | 0 | 0 |