OID reference
1.3.6.1.4.1.4935.20.10.1.1.6
Indicates if piggy-backing can be used to send several NCS messages in the same UDP packet. If enabled, piggy-backing can be used. Otherwise, no piggy-backing is used.
Identification
{1 3 6 1 4 1 4935 20 10 1 1 6}
| Value | Name |
|---|---|
| 0 | disable |
| 1 | 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.4935.20.10.1.1.6.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.
ncsPiggyBackingEnable OBJECT-TYPE
SYNTAX INTEGER {
disable(0),
enable(1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Indicates if piggy-backing can be used to send several
NCS messages in the same UDP packet. If enabled,
piggy-backing can be used. Otherwise, no piggy-backing
is used."
DEFVAL { enable }
::= { ncsMIBObjects 6 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Indicates if piggy-backing can be used to send several NCS messages in the same UDP packet. If enabled, piggy-backing can be used. Otherwise, no piggy-backing is used.
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: ncsPiggyBackingEnable
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ncsPiggyBackingEnable",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"disable",
"(",
"0",
")",
",",
"enable",
"(",
"1",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Indicates if piggy-backing can be used to send several NCS messages in the same UDP packet. If enabled, piggy-backing can be used. Otherwise, no piggy-backing is used.\"",
"DEFVAL",
"{",
"enable",
"}",
"::=",
"{",
"ncsMIBObjects",
"6",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"disable",
0
],
[
"enable",
1
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Indicates if piggy-backing can be used to send several NCS messages in the same UDP packet. If enabled, piggy-backing can be used. Otherwise, no piggy-backing is used."
],
null,
null,
null,
[
"DEFVAL",
"enable"
]
]
}Vendor MIB copy from the Observium Community archive.
Module: MX-NCS-MIB
See published definition above
{'MX-TC': ['MxIpHostName', 'MxIpConfigSource', 'MxIpPort', 'MxIpSelectConfigSource', 'MxIpDhcpSiteSpecificCode'], 'MX-SMI': ['ipAddressStatus', 'ipAddressConfig', 'mediatrixIpTelephonySignaling'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Unsigned32'], 'RFC1213-MIB': ['ifIndex'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.4935.20.10.1.1.1 | ncsPort | 0 | 0 | |
| 1.3.6.1.4.1.4935.20.10.1.1.2 | ncsDefaultDigitMap | 0 | 0 | |
| 1.3.6.1.4.1.4935.20.10.1.1.4 | ncsRestartLevel | 0 | 0 | |
| 1.3.6.1.4.1.4935.20.10.1.1.5 | ncsEndpointIdListIncludeNotStarted | 0 | 0 | |
| 1.3.6.1.4.1.4935.20.10.1.1.20 | ncsEndpointId | 1 | 4 | |
| 1.3.6.1.4.1.4935.20.10.1.1.23 | ncsRetransmission | 13 | 13 | |
| 1.3.6.1.4.1.4935.20.10.1.1.30 | ncsLinePackage | 12 | 12 | |
| 1.3.6.1.4.1.4935.20.10.1.1.50 | ncsStats | 3 | 7 |