OID reference
1.3.6.1.4.1.4935.99.5.1.60.20
PCM capture endpoint number. This variable's semantics are different depending on protocol and/or hardware platforms. Please refer to the documentation shipped with your device for more details.
Identification
{1 3 6 1 4 1 4935 99 5 1 60 20}
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.4935.99.5.1.60.20.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.
mxDebugPcmCaptureEndpointNumber OBJECT-TYPE
SYNTAX Unsigned32(1..65535)
MAX-ACCESS read-write
STATUS current
DESCRIPTION "PCM capture endpoint number.
This variable's semantics are different depending on
protocol and/or hardware platforms.
Please refer to the documentation shipped with your
device for more details."
DEFVAL { 1 }
::= { mxDebugPcmCapture 20 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
PCM capture endpoint number. This variable's semantics are different depending on protocol and/or hardware platforms. Please refer to the documentation shipped with your device for more details.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: mxDebugPcmCaptureEndpointNumber
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mxDebugPcmCaptureEndpointNumber",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"(",
"1",
".",
".",
"65535",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"PCM capture endpoint number. This variable's semantics are different depending on protocol and/or hardware platforms. Please refer to the documentation shipped with your device for more details.\"",
"DEFVAL",
"{",
"1",
"}",
"::=",
"{",
"mxDebugPcmCapture",
"20",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32",
[
"integerSubType",
[
[
1,
65535
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"PCM capture endpoint number. This variable's semantics are different depending on protocol and/or hardware platforms. Please refer to the documentation shipped with your device for more details."
],
null,
null,
null,
[
"DEFVAL",
1
]
]
}Vendor MIB copy from the Observium Community archive.
Module: MX-DEBUG-MIB
See published definition above
{'MX-TC': ['MxIpHostName', 'MxIpPort'], 'MX-SMI': ['mediatrixExperimental'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.4935.99.5.1.60.5 | mxDebugPcmCaptureEnable | 0 | 0 | |
| 1.3.6.1.4.1.4935.99.5.1.60.10 | mxDebugPcmCaptureIpAddress | 0 | 0 |