CISCO-IETF-ISIS-MIB :: ciiRAMapType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-IETF-ISIS-MIBciiRAMapType

ciiRAMapType

Module: CISCO-IETF-ISIS-MIB

OID (symbolic): CISCO-IETF-ISIS-MIB::ciiRAMapType

OID (numeric): 1.3.6.1.4.1.9.10.118.1.7.1.1.5

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-create

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 behavior. 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 ciiRASNPAAddress 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 ciiRASNPAMask object value with the destination address. The part of the SNPA extracted from the destination NSAP is appended to the ciiRASNPAPrefix object value to form the next hop subnetwork addressing information.

What is ciiRAMapType?

This is the type of mapping employed to ascertain the SNPA Address used in forwarding PDUs for this Reachable Address prefix, following the ManualOrAutomatic behavior, where none means the mapping is null because the neighbor SNPA is implicit, such as on a point-to-point link. It determines how the router derives the actual next-hop SNPA address for a reachable prefix, so picking the wrong mapping type on a broadcast circuit, where the SNPA must be computed or explicitly configured, could leave the router unable to actually resolve where to send traffic even with a correct prefix. For example, on a point-to-point circuit this would correctly be set to none since there is only one possible next hop, but the same setting used mistakenly on a broadcast LAN circuit would leave the router with no way to determine which of several neighbors to forward toward.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.10ciscoExperimentCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.10.118ciscoIetfIsisMIBCISCO-IETF-ISIS-MIB
1.3.6.1.4.1.9.10.118.1ciscoIetfIsisMIBObjectsCISCO-IETF-ISIS-MIB
1.3.6.1.4.1.9.10.118.1.7ciiReachAddrCISCO-IETF-ISIS-MIB
1.3.6.1.4.1.9.10.118.1.7.1ciiRATableCISCO-IETF-ISIS-MIB
1.3.6.1.4.1.9.10.118.1.7.1.1ciiRAEntryCISCO-IETF-ISIS-MIB
1.3.6.1.4.1.9.10.118.1.7.1.1.5ciiRAMapTypeCISCO-IETF-ISIS-MIB