Indicates the loop mode(360 or 380 or 380H or 380hn or 380a or 380ax not support this node): 0:no loop 1:in loop 3:masterinloop 4:slaveinloop
Sources for this description
Huawei MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.2011.2.25.4.40.4.10.17.1.4
Indicates the loop mode(360 or 380 or 380H or 380hn or 380a or 380ax not support this node): 0:no loop 1:in loop 3:masterinloop 4:slaveinloop
Identification
{1 3 6 1 4 1 2011 2 25 4 40 4 10 17 1 4}
| Value | Name |
|---|---|
| 0 | noloop |
| 1 | inloop |
| 3 | masterinloop |
| 4 | slaveinloop |
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: optixRtnOduIndex1, optixRtnOduIndex2.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2011.2.25.4.40.4.10.17.1.4
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.
optixRtnOduLoopModeExt OBJECT-TYPE
SYNTAX INTEGER
{
noloop(0),
inloop(1),
masterinloop(3),
slaveinloop(4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates the loop mode(360 or 380 or 380H or 380hn or 380a or 380ax not support this node):
0:no loop
1:in loop
3:masterinloop
4:slaveinloop"
::= { optixRtnOduGeneralAttrExtEntry 4 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Indicates the loop mode(360 or 380 or 380H or 380hn or 380a or 380ax not support this node): 0:no loop 1:in loop 3:masterinloop 4:slaveinloop
Huawei MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: optixRtnOduLoopModeExt
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"optixRtnOduLoopModeExt",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"noloop",
"(",
"0",
")",
",",
"inloop",
"(",
"1",
")",
",",
"masterinloop",
"(",
"3",
")",
",",
"slaveinloop",
"(",
"4",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Indicates the loop mode(360 or 380 or 380H or 380hn or 380a or 380ax not support this node): 0:no loop 1:in loop 3:masterinloop 4:slaveinloop\"",
"::=",
"{",
"optixRtnOduGeneralAttrExtEntry",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"noloop",
0
],
[
"inloop",
1
],
[
"masterinloop",
3
],
[
"slaveinloop",
4
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Indicates the loop mode(360 or 380 or 380H or 380hn or 380a or 380ax not support this node): 0:no loop 1:in loop 3:masterinloop 4:slaveinloop"
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive. Huawei support.
Module: OPTIX-RTN-ODU-MGR-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['Unsigned32', 'Integer32', 'OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE'], 'OPTIX-OID-MIB': ['optixProvisionRtn'], 'OPTIX-RTN-GENNERAL-MIB': ['optixRtnIFPortlist']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2011.2.25.4.40.4.10.17.1.1 | optixRtnOduFademarginAlmThExt | 0 | 0 | |
| 1.3.6.1.4.1.2011.2.25.4.40.4.10.17.1.2 | optixRtnOduCurrentFilterExt | 0 | 0 | |
| 1.3.6.1.4.1.2011.2.25.4.40.4.10.17.1.3 | optixRtnOduAllFilterListInfoExt | 0 | 0 |