OID reference
1.3.6.1.3.37.1.6.1.1.5
The type of the neighboring system.
Identification
{1 3 6 1 3 37 1 6 1 1 5}
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 | l1IntermediateSystem | 1 |
| 1 | none | 2 |
| 2 | explicit | 2 |
| 2 | l2IntermediateSystem | 1 |
| 3 | extractIDI | 2 |
| 3 | l1L2IntermediateSystem | 1 |
| 4 | extractDSP | 2 |
| 4 | unknown | 1 |
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.
In ISIS-MIB, the row index consists of these components in order:
isisSysInstance (Integer32): one numeric subidentifier for the non-negative value.isisCircIndex (Integer32): one numeric subidentifier for the non-negative value.isisISAdjIndex (Integer32): one numeric subidentifier for the non-negative value.An instance has the form .1.3.6.1.3.37.1.6.1.1.5.<isisSysInstance>.<isisCircIndex>.<isisISAdjIndex>. Use values present on the device and permitted by its MIB. Other definitions can differ.
Published row index variants: isisCircIndex, isisISAdjIndex; isisSysInstance, isisCircIndex, isisISAdjIndex; isisSysInstance, isisCircIndex, isisRAIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.3.37.1.6.1.1.5
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.
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 2 distinct definitions; some records may not include a definition.
isisISAdjNeighSysType OBJECT-TYPE
SYNTAX INTEGER
{
l1IntermediateSystem(1),
l2IntermediateSystem(2),
l1L2IntermediateSystem(3),
unknown(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of the neighboring system."
REFERENCE "{ISIS.aoi neighbourSystemType (80)}"
::= { isisISAdjEntry 5 }isisRAMapType OBJECT-TYPE
SYNTAX INTEGER {
none (1),
explicit (2),
extractIDI (3),
extractDSP (4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of mapping to be employed to ascertain the SNPA
Address which should be used in forwarding PDUs for this
Reachable Address prefix. This object follows the
manualOrAutomatic behaviour. The following values of
mapping type are defined:
none: The mapping is null because the neighbor SNPA is
implicit by nature of the subnetwork (e.g. a
point-to-point linkage).
explicit: The subnetwork addresses in the object
isisRASNPAAddress is to be used.
extractIDI: The SNPA is embedded in the IDI of the
destination NSAP Address. The mapping algorithm
extracts the SNPA to be used according to the format
and encoding rules of ISO8473/Add2. This SNPA
extraction algorithm can be used in conjunction with
Reachable Address prefixes from the X.121, F.69, E.163
and E.164 addressing subdomains.
extractDSP: All, or a suffix, of the SNPA is embedded
in the DSP of the destination address. This SNPA
extraction algorithm extracts the embedded subnetwork
addressing information by performing a logical AND of
the isisRASNPAMask object value with the destination
address. The part of the SNPA extracted from the
destination NSAP is appended to the isisRASNPAPrefix
object value to form the next hop subnetwork
addressing information."
REFERENCE "ISO10589-ISIS.aoi mappingType (107)"
::= { isisRAEntry 5 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
The type of the neighboring system.
D-Link official switch MIBsFS.COM official Documentation Hub native MIB packagesHuawei MIB copies (LibreNMS/Observium Community)Huawei official enterprise MIB Query and object descriptionsMIBdepotCommon and standard MIB copies (LibreNMS/Observium Community)
Description 2
The type of the neighboring system. 1 indicates Level-1. 2 indicates Level-2. 3 indicates Level-1-2. 4 indicates unknown.
Huawei official enterprise MIB Query and object descriptions
Description 3
The type of mapping to be employed to ascertain the SNPA Address which should be used in forwarding PDUs for this Reachable Address prefix. This object follows the manualOrAutomatic behaviour. The following values of mapping type are defined: none: The mapping is null because the neighbor SNPA is implicit by nature of the subnetwork (e.g. a point-to-point linkage). explicit: The subnetwork addresses in the object isisRASNPAAddress is to be used. extractIDI: The SNPA is embedded in the IDI of the destination NSAP Address. The mapping algorithm extracts the SNPA to be used according to the format and encoding rules of ISO8473/Add2. This SNPA extraction algorithm can be used in conjunction with Reachable Address prefixes from the X.121, F.69, E.163 and E.164 addressing subdomains. extractDSP: All, or a suffix, of the SNPA is embedded in the DSP of the destination address. This SNPA extraction algorithm extracts the embedded subnetwork addressing information by performing a logical AND of the isisRASNPAMask object value with the destination address. The part of the SNPA extracted from the destination NSAP is appended to the isisRASNPAPrefix object value to form the next hop subnetwork addressing information.
Nokia networking MIB copies (LibreNMS/Observium Community)
Description 4
The type of the neighboring system. 1: Level-1 2: Level-2 3: Level-1-2 4: unknown
Huawei official enterprise MIB Query and object descriptions
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: unspecified.
Names: isisISAdjNeighSysType
{
"syntax": "INTEGER{(l1IntermediateSystem,1),(l2IntermediateSystem,2),(l1L2IntermediateSystem,3),(unknown,4)}",
"max_access": "read-only",
"object_class": "table column"
}Module: ISIS-MIB
· Download Huawei MIB Query — ISIS-MIB (derived data index)Related source files and packages:
Status in source: current.
Names: isisISAdjNeighSysType
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"isisISAdjNeighSysType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"l1IntermediateSystem",
"(",
"1",
")",
",",
"l2IntermediateSystem",
"(",
"2",
")",
",",
"l1L2IntermediateSystem",
"(",
"3",
")",
",",
"unknown",
"(",
"4",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The type of the neighboring system.\"",
"REFERENCE",
"\"{ISIS.aoi neighbourSystemType (80)}\"",
"::=",
"{",
"isisISAdjEntry",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"l1IntermediateSystem",
1
],
[
"l2IntermediateSystem",
2
],
[
"l1L2IntermediateSystem",
3
],
[
"unknown",
4
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The type of the neighboring system."
],
[
"REFERENCE",
"{ISIS.aoi neighbourSystemType (80)}"
],
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
Same published definition (formatting differs; exact original is in the source file)
{'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
Same published definition (formatting differs; exact original is in the source file)
{'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
Same published definition (formatting differs; exact original is in the source file)
{'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.
Vendor MIB copy from the LibreNMS archive.
Module: ISIS-MIB-LEGACY
{'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:
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.
Related source files and packages:
Browse all related files for Huawei MIB Query — ISIS-MIB (derived data index)
Status in source: unspecified.
Names: isisISAdjNeighSysType
{
"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: current.
Names: isisRAMapType
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"isisRAMapType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"none",
"(",
"1",
")",
",",
"explicit",
"(",
"2",
")",
",",
"extractIDI",
"(",
"3",
")",
",",
"extractDSP",
"(",
"4",
")",
"}",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"The type of mapping to be employed to ascertain the SNPA Address which should be used in forwarding PDUs for this Reachable Address prefix. This object follows the manualOrAutomatic behaviour. The following values of mapping type are defined: none: The mapping is null because the neighbor SNPA is implicit by nature of the subnetwork (e.g. a point-to-point linkage). explicit: The subnetwork addresses in the object isisRASNPAAddress is to be used. extractIDI: The SNPA is embedded in the IDI of the destination NSAP Address. The mapping algorithm extracts the SNPA to be used according to the format and encoding rules of ISO8473/Add2. This SNPA extraction algorithm can be used in conjunction with Reachable Address prefixes from the X.121, F.69, E.163 and E.164 addressing subdomains. extractDSP: All, or a suffix, of the SNPA is embedded in the DSP of the destination address. This SNPA extraction algorithm extracts the embedded subnetwork addressing information by performing a logical AND of the isisRASNPAMask object value with the destination address. The part of the SNPA extracted from the destination NSAP is appended to the isisRASNPAPrefix object value to form the next hop subnetwork addressing information.\"",
"REFERENCE",
"\"ISO10589-ISIS.aoi mappingType (107)\"",
"::=",
"{",
"isisRAEntry",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"none",
1
],
[
"explicit",
2
],
[
"extractIDI",
3
],
[
"extractDSP",
4
]
]
]
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The type of mapping to be employed to ascertain the SNPA Address which should be used in forwarding PDUs for this Reachable Address prefix. This object follows the manualOrAutomatic behaviour. The following values of mapping type are defined: none: The mapping is null because the neighbor SNPA is implicit by nature of the subnetwork (e.g. a point-to-point linkage). explicit: The subnetwork addresses in the object isisRASNPAAddress is to be used. extractIDI: The SNPA is embedded in the IDI of the destination NSAP Address. The mapping algorithm extracts the SNPA to be used according to the format and encoding rules of ISO8473/Add2. This SNPA extraction algorithm can be used in conjunction with Reachable Address prefixes from the X.121, F.69, E.163 and E.164 addressing subdomains. extractDSP: All, or a suffix, of the SNPA is embedded in the DSP of the destination address. This SNPA extraction algorithm extracts the embedded subnetwork addressing information by performing a logical AND of the isisRASNPAMask object value with the destination address. The part of the SNPA extracted from the destination NSAP is appended to the isisRASNPAPrefix object value to form the next hop subnetwork addressing information."
],
[
"REFERENCE",
"ISO10589-ISIS.aoi mappingType (107)"
],
null,
null,
null
]
}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']}Status in source: unspecified.
Names: isisISAdjNeighSysType
{
"syntax": "INTEGER",
"max_access": "read-only",
"object_class": "table column"
}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.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.8 | isisISAdjUsage, isisRASNPAAddress | 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 |