OID reference
1.3.6.1.4.1.21296.2.2.2.2.2.1.1.8
If enabled(2), span loss reporting will proceed based on the provided expectedSpanLoss and maxEngineeredSpanLoss attributes. If set to disabled(1), the spanLossExceededLimit alarms/TCC is suppressed.
Identification
{1 3 6 1 4 1 21296 2 2 2 2 2 1 1 8}
| Value | Name |
|---|---|
| 1 | disabled |
| 2 | enabled |
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.
Published row index: ifIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.21296.2.2.2.2.2.1.1.8
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.
bandCtpSpanLossReporting OBJECT-TYPE
SYNTAX INTEGER {
disabled(1),
enabled(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If enabled(2), span loss reporting will proceed based on the provided expectedSpanLoss and
maxEngineeredSpanLoss attributes. If set to disabled(1), the spanLossExceededLimit alarms/TCC
is suppressed."
DEFVAL { disabled }
::= { bandCtpEntry 8 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
If enabled(2), span loss reporting will proceed based on the provided expectedSpanLoss and maxEngineeredSpanLoss attributes. If set to disabled(1), the spanLossExceededLimit alarms/TCC is suppressed.
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: bandCtpSpanLossReporting
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"bandCtpSpanLossReporting",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"disabled",
"(",
"1",
")",
",",
"enabled",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"If enabled(2), span loss reporting will proceed based on the provided expectedSpanLoss and maxEngineeredSpanLoss attributes. If set to disabled(1), the spanLossExceededLimit alarms/TCC is suppressed.\"",
"DEFVAL",
"{",
"disabled",
"}",
"::=",
"{",
"bandCtpEntry",
"8",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"disabled",
1
],
[
"enabled",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"If enabled(2), span loss reporting will proceed based on the provided expectedSpanLoss and maxEngineeredSpanLoss attributes. If set to disabled(1), the spanLossExceededLimit alarms/TCC is suppressed."
],
null,
null,
null,
[
"DEFVAL",
"disabled"
]
]
}Vendor MIB copy from the Observium Community archive.
Module: INFINERA-TP-BANDCTP-MIB
See published definition above
{'IF-MIB': ['ifIndex'], 'SNMPv2-TC': ['DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'INFINERA-TC-MIB': ['InfnReporting', 'InfnALSDisableMode', 'InfnSlotOperatingMode', 'InfnRxEDFAGainMode', 'FloatTenths', 'FloatArbitraryPrecision'], 'INFINERA-REG-MIB': ['terminationPoint']}Related source files and packages:
Registration