Status in source: current.
Names: qtechfrExtCircuitMapStatus
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"qtechfrExtCircuitMapStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"2047",
")",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The mapping protocols (internally considered as the 'link type') applied on this circuit. The value ranges from 0 to 2047. For point-to-point DLCI, the value stays zero. Otherwise, the value is a sum. It initially takes the value zero, then, for each type of Protocol, 2 raised to a power is added to the sum. The following table presents respective power and equivalent value for each applicable type: Protocol Power Value -------- ----- ----- IP 0 1 IPX 1 2 Appletalk 2 4 XNS 3 8 VINES 4 16 DECnet 5 32 CLNS 6 64 Bridging 7 128 RSRB 8 256 STUN 9 512 LLC2 10 1024 For example, value 3 means the circuit's mapping protocols include IP and IPX. (3 = 2**1 + 2**0, where 0 corresponds to IP and 1 to IPX.) Value 0 means there is currently no mapping protocol for the circuit. See qtechfrMapTable for more mapping information.\"",
"::=",
"{",
"qtechfrExtCircuitEntry",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
2047
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The mapping protocols (internally considered as the 'link type') applied on this circuit. The value ranges from 0 to 2047. For point-to-point DLCI, the value stays zero. Otherwise, the value is a sum. It initially takes the value zero, then, for each type of Protocol, 2 raised to a power is added to the sum. The following table presents respective power and equivalent value for each applicable type: Protocol Power Value -------- ----- ----- IP 0 1 IPX 1 2 Appletalk 2 4 XNS 3 8 VINES 4 16 DECnet 5 32 CLNS 6 64 Bridging 7 128 RSRB 8 256 STUN 9 512 LLC2 10 1024 For example, value 3 means the circuit's mapping protocols include IP and IPX. (3 = 2**1 + 2**0, where 0 corresponds to IP and 1 to IPX.) Value 0 means there is currently no mapping protocol for the circuit. See qtechfrMapTable for more mapping information."
],
null,
null,
null,
null
]
}
- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
Module: QTECH-FRAME-RELAY-MIB
See published definition above
Module imports
{'IF-MIB': ['InterfaceIndex', 'ifIndex'], 'QTECH-SMI': ['qtechMgmt'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Counter32', 'Integer32', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'FRAME-RELAY-DTE-MIB': ['frDlcmiEntry', 'frCircuitEntry', 'frCircuitIfIndex', 'frCircuitDlci']}
· Download QTECH-FRAME-RELAY-MIB
Related source files and packages: