Description 1
Sources for this description
MIBdepot
Parsed from zebos_ISIS_MIB.mib.txt · ruijie · ISIS-MIB
Source file: Download isis_draft_03.mib.txt
Source file: Download isis.mib.txt
OID reference
1.3.6.1.3.37.6.1.1.5
The internal path metric value for this destination.
Identification
{1 3 6 1 3 37 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 | none | 1 |
| 2 | explicit | 1 |
| 3 | extractIDI | 1 |
| 4 | extractDSP | 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.isisRAIndex (Integer32): one numeric subidentifier for the non-negative value.An instance has the form .1.3.6.1.3.37.6.1.1.5.<isisSysInstance>.<isisCircIndex>.<isisRAIndex>. Use values present on the device and permitted by its MIB. Other definitions can differ.
Published row index variants: isisIPRouteMetTOS, isisIPRouteDest, isisIPRouteMask, isisIPRouteForw; isisSysInstance, isisCircIndex, isisRAIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.3.37.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.
Available source records contain 2 distinct definitions; some records may not include a 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 }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
Parsed from zebos_ISIS_MIB.mib.txt · ruijie · ISIS-MIB
Source file: Download isis_draft_03.mib.txt
Source file: Download isis.mib.txt
Description 2
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.
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
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
]
}Module: ISIS-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'RowStatus', 'TruthValue', 'TestAndIncr', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'Integer32', 'Counter32', 'experimental']}Module: ISIS-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'RowStatus', 'TruthValue', 'TestAndIncr', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'Integer32', 'Counter32', 'experimental']}Historical records
isisIPRouteIntMetric OBJECT-TYPE
SYNTAX PathCost
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The internal path metric value for this destination."
::= { isisIPDestEntry 5 }
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.3.37.6.1.1.1 | isisIPRouteDest, isisRAIndex | 0 | 0 | The destination IP Address. |
| 1.3.6.1.3.37.6.1.1.2 | isisIPRouteMask, isisRAExistState | 0 | 0 | The mask for the isisIPRouteDest value. |
| 1.3.6.1.3.37.6.1.1.3 | isisIPRouteMetTOS, isisRAAdminState | 0 | 0 | The TOS of the metric for this destination. |
| 1.3.6.1.3.37.6.1.1.4 | isisIPRouteMetType, isisRAAddrPrefix | 0 | 0 | Indicates whether the metric includes an external component or not. |
| 1.3.6.1.3.37.6.1.1.6 | isisIPRouteExtMetric, isisRADefMetric | 0 | 0 | The external metric value for this destination. If the metric type is internal then this value is zero. |
| 1.3.6.1.3.37.6.1.1.7 | isisIPRouteForw, isisRADefMetricType | 0 | 0 | The OBJECT IDENTIFIER for the first object in the table entry which corresponds to the entry used for forwarding packets to this … |
| 1.3.6.1.3.37.6.1.1.8 | isisIPRouteSource, isisRASNPAAddress | 0 | 0 | The source of the destination. Manual is used if the source is manually configured information on the system. Level1 is used if t… |
| 1.3.6.1.3.37.6.1.1.9 | isisIPRouteSysInstance, isisRASNPAMask | 0 | 0 | The identifier of the Integrated IS-IS instance from which this reachability information was learned. |
| 1.3.6.1.3.37.6.1.1.10 | isisRASNPAPrefix | 0 | 0 | |
| 1.3.6.1.3.37.6.1.1.11 | isisRAType | 0 | 0 |