OID reference
1.3.6.1.3.37.1.6.1.1.8
How is the adjacency used? On a point-to-point link, this might be level1and2, but on a LAN, the usage will be level1 on the adjacency between peers at level 1, and level2 for the adjacency between peers at level 2.
Identification
{1 3 6 1 3 37 1 6 1 1 8}
Definitions may combine these properties differently.
Numbers refer to source variants above. Each value is shown only for variants that define it.
| Value | Name | Source variants |
|---|---|---|
| 1 | level1 | 1 |
| 2 | level2 | 1 |
| 3 | level1and2 | 1 |
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Product context
The FS.COM catalogue lists MIB packages containing this definition for these models:
N5860-48SC, N8560-32C, N8560-48BC, N8560-64C, NC8200-16Q, NC8200-24BC, NC8200-4TD, NC8200-8C, NC8400-16CD, NC8400-32C, NC8400-4TH, S3100-16TF.
S3410-24TS-P, S3910-24TS, S3910-48TS, S5810-28FS, S5810-28TS, S5810-48FS, S5810-48TS, S5810-48TS-P, S5860-20SQ, S5860-24XB-U, S5860-48SC.
A definition in a model's MIB package does not establish that the device implements it or permits access.
Available source records contain 4 distinct definitions; some records may not include a definition.
isisISAdjUsage OBJECT-TYPE
SYNTAX INTEGER
{
level1(1),
level2(2),
level1and2(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"How is the adjacency used? On a point-to-point link,
this might be level1and2, but on a LAN, the usage will
be level1 on the adjacency between peers at level 1,
and level2 for the adjacency between peers at level 2."
REFERENCE "{ISIS.aoi adjacencyUsage (82)}"
::= { isisISAdjEntry 8 }isisISAdjUsage OBJECT-TYPE
SYNTAX INTEGER
{
level1(1),
level2(2),
level1and2(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"How is the adjacency used? On a point-to-point link,
this might be level1and2, but on a LAN, the usage will
be level1 on the adjacency between peers at level 1,
and level2 for the adjacency between peers at level 2."
REFERENCE "{ISIS.aoi adjacencyUsage (82)}"
::= { isisISAdjEntry 8 }isisISAdjUsage OBJECT-TYPE
SYNTAX IsisLevel
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"How is the adjacency used? On a point-to-point link,
this might be level1and2, but on a LAN, the usage will
be level1 on the adjacency between peers at L1,
and level2 for the adjacency between peers at L2."
REFERENCE "{ISIS.aoi adjacencyUsage (82)}"
::= { isisISAdjEntry 8 }isisRASNPAAddress OBJECT-TYPE
SYNTAX SNPAAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The SNPA Address to which a PDU may be forwarded in
order to reach a destination which matches the address
prefix of the Reachable Address. This object follows the
manualOrAutomatic behaviour."
REFERENCE "ISIS.aoi sNPAAddresses (109)"
-- note only one address may be specified per Reachable Address
-- in the MIB
DEFVAL { ''H }
::= { isisRAEntry 8 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
How is the adjacency used? On a point-to-point link, this might be level1and2, but on a LAN, the usage will be level1 on the adjacency between peers at level 1, and level2 for the adjacency between peers at level 2.
D-Link official switch MIBsFS.COM official Documentation Hub native MIB packagesHuawei MIB copies (LibreNMS/Observium Community)Huawei official enterprise MIB Query and object descriptionsMIBdepot
Description 2
How is the adjacency used? On a point-to-point link, this might be level1and2, but on a LAN, the usage will be level1 on the adjacency between peers at L1, and level2 for the adjacency between peers at L2.
Common and standard MIB copies (LibreNMS/Observium Community)
Description 3
How is the adjacency used? On a point-to-point link, this might be level1and2, but on a LAN, the usage will be level1 on the adjacency between peers at level 1, and level2 for the adjacency between peers at level 2. 1: indicates Level-1. 2: indicates Level-2. 3: indicates Level-1-2.
Huawei official enterprise MIB Query and object descriptions
Description 4
How is the adjacency used? On a point-to-point link, this might be level1and2, but on a LAN, the usage will be level1 on the adjacency between peers at L1, and level2 for the adjacency between peers at L2 1: Level-1 2: Level-2 3: Level-1-2
Huawei official enterprise MIB Query and object descriptions
Description 5
The SNPA Address to which a PDU may be forwarded in order to reach a destination which matches the address prefix of the Reachable Address. This object follows the manualOrAutomatic behaviour.
Nokia networking MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: isisISAdjUsage
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"isisISAdjUsage",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"level1",
"(",
"1",
")",
",",
"level2",
"(",
"2",
")",
",",
"level1and2",
"(",
"3",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"How is the adjacency used? On a point-to-point link, this might be level1and2, but on a LAN, the usage will be level1 on the adjacency between peers at level 1, and level2 for the adjacency between peers at level 2.\"",
"REFERENCE",
"\"{ISIS.aoi adjacencyUsage (82)}\"",
"::=",
"{",
"isisISAdjEntry",
"8",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"level1",
1
],
[
"level2",
2
],
[
"level1and2",
3
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"How is the adjacency used? On a point-to-point link, this might be level1and2, but on a LAN, the usage will be level1 on the adjacency between peers at level 1, and level2 for the adjacency between peers at level 2."
],
[
"REFERENCE",
"{ISIS.aoi adjacencyUsage (82)}"
],
null,
null,
null
]
}Module: ISIS-MIB
See published definition above
{'IF-MIB': ['ifName'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'RowStatus', 'TruthValue', 'TestAndIncr'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'NOTIFICATION-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'experimental', 'TimeTicks'], 'RFC1213-MIB': ['ifEntry', 'ifIndex'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength'], 'HUAWEI-ISIS-CONF-MIB': ['hwIsisAdjChangeReason']}Module: ISIS-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'RowStatus', 'TruthValue', 'TestAndIncr'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'NOTIFICATION-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'experimental', 'TimeTicks'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength']}Module: ISIS-MIB
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'RowStatus', 'TruthValue', 'TestAndIncr'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'NOTIFICATION-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'experimental', 'TimeTicks'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength']}Related source files and packages:
Same file in 3610.zip.
Same file in 3610.zip.
Same file in 3610.zip.
Same file in 3610-MIB.rar.
Vendor MIB copy from the Observium Community archive. Huawei support.
Module: ISIS-MIB
{'IF-MIB': ['ifName'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'RowStatus', 'TruthValue', 'TestAndIncr'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'NOTIFICATION-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'experimental', 'TimeTicks'], 'RFC1213-MIB': ['ifEntry', 'ifIndex'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength']}Related source files and packages:
Module: ISIS-MIB
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'RowStatus', 'TruthValue', 'TestAndIncr'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'NOTIFICATION-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'experimental', 'TimeTicks'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength']}Related source files and packages:
Same file in s3100-16tf-switch-snmp-mib-files.zip.
Same file in s5860-series-swithes-snmp-mib-files.zip.
Same file in s3910-series-swithes-snmp-mib-files.zip.
Same file in s3410-series-swithes-snmp-mib-files.zip.
Module: ISIS-MIB
{'IF-MIB': ['ifName'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'RowStatus', 'TruthValue', 'TestAndIncr'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'NOTIFICATION-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'experimental', 'TimeTicks'], 'RFC1213-MIB': ['ifEntry', 'ifIndex'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength']}Source data warning: Huawei MIB Query supplies the identical numeric OID, name, purpose, syntax and access. The complete technical declaration is supplied by the independently cited native MIB original (huawei-mibs: observium/huawei/ISIS-MIB); it is not inferred from the documentation table.
· Download Huawei MIB Query — ISIS-MIB (derived data index)Related source files and packages:
Browse all related files for Huawei MIB Query — ISIS-MIB (derived data index)
Status in source: unspecified.
Names: isisISAdjUsage
{
"syntax": "INTEGER{(level1,1),(level2,2),(level1and2,3)}",
"max_access": "read-only",
"object_class": "table column"
}Module: ISIS-MIB
Related source files and packages:
Status in source: current.
Names: isisISAdjUsage
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"isisISAdjUsage",
"OBJECT-TYPE",
"SYNTAX",
"IsisLevel",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"How is the adjacency used? On a point-to-point link, this might be level1and2, but on a LAN, the usage will be level1 on the adjacency between peers at L1, and level2 for the adjacency between peers at L2.\"",
"REFERENCE",
"\"{ISIS.aoi adjacencyUsage (82)}\"",
"::=",
"{",
"isisISAdjEntry",
"8",
"}"
],
"syntax_tree": [
[
"row",
"IsisLevel"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"How is the adjacency used? On a point-to-point link, this might be level1and2, but on a LAN, the usage will be level1 on the adjacency between peers at L1, and level2 for the adjacency between peers at L2."
],
[
"REFERENCE",
"{ISIS.aoi adjacencyUsage (82)}"
],
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: ISIS-MIB-LEGACY
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'TruthValue', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Counter32', 'mib-2', 'experimental'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'DIFFSERV-MIB': ['IndexInteger', 'IndexIntegerNextFree'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}Related source files and packages:
Status in source: unspecified.
Names: isisISAdjUsage
{
"syntax": "Integer",
"max_access": "read-only",
"object_class": "table column"
}Module: ISIS-MIB
Related source files and packages:
Browse all related files for Huawei MIB Query — ISIS-MIB (derived data index)
Status in source: unspecified.
Names: isisISAdjUsage
{
"syntax": "INTEGER",
"max_access": "read-only",
"object_class": "table column"
}Status in source: current.
Names: isisRASNPAAddress
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"isisRASNPAAddress",
"OBJECT-TYPE",
"SYNTAX",
"SNPAAddress",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"The SNPA Address to which a PDU may be forwarded in order to reach a destination which matches the address prefix of the Reachable Address. This object follows the manualOrAutomatic behaviour.\"",
"REFERENCE",
"\"ISIS.aoi sNPAAddresses (109)\"",
"DEFVAL",
"{",
"'",
"'",
"H",
"}",
"::=",
"{",
"isisRAEntry",
"8",
"}"
],
"syntax_tree": [
[
"row",
"SNPAAddress"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The SNPA Address to which a PDU may be forwarded in order to reach a destination which matches the address prefix of the Reachable Address. This object follows the manualOrAutomatic behaviour."
],
[
"REFERENCE",
"ISIS.aoi sNPAAddresses (109)"
],
null,
null,
[
"DEFVAL",
"''H"
]
]
}Vendor MIB copy from the Observium Community archive. Nokia support.
Module: ISIS-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'RowStatus', 'TruthValue', 'TestAndIncr'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'Integer32', 'Counter32', 'experimental'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength']}Historical records
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.3.37.1.6.1.1.1 | isisISAdjIndex, isisRAIndex | 0 | 0 | |
| 1.3.6.1.3.37.1.6.1.1.2 | isisISAdjState, isisRAExistState | 0 | 0 | |
| 1.3.6.1.3.37.1.6.1.1.3 | isisISAdj3WayState, isisRAAdminState | 0 | 0 | |
| 1.3.6.1.3.37.1.6.1.1.4 | isisISAdjNeighSNPAAddress, isisRAAddrPrefix | 0 | 0 | |
| 1.3.6.1.3.37.1.6.1.1.5 | isisISAdjNeighSysType, isisRAMapType | 0 | 0 | |
| 1.3.6.1.3.37.1.6.1.1.6 | isisISAdjExtendedCircID, isisISAdjNeighSysID, isisRADefMetric | 0 | 0 | |
| 1.3.6.1.3.37.1.6.1.1.7 | isisISAdjNeighSysID, isisISAdjNbrExtendedCircID, isisRADefMetricType | 0 | 0 | |
| 1.3.6.1.3.37.1.6.1.1.9 | isisISAdjHoldTimer, isisRASNPAMask | 0 | 0 | |
| 1.3.6.1.3.37.1.6.1.1.10 | isisISAdjNeighPriority, isisRASNPAPrefix | 0 | 0 | |
| 1.3.6.1.3.37.1.6.1.1.11 | isisISAdjLastUpTime, isisRAType | 0 | 0 |