XPNNI-MIB: View SNMP OID List / Download MIB

The highest version of the PNNI protocol that the software in this switching system is capable of executing.

The lowest version of the PNNI Protocol that the software in this switching system is capable of executing.

The total number of DTL stacks that this switching system has originated as the DTLOriginator and placed into signalling messages. This includes the initial DTL stacks computed by this system as well as any alternate route (second, third choice etc.) DTL stacks computed by this switching system in response to crankbacks.

The number of partial DTL stacks that this switching system has added into signalling messages as an entry border node. This includes the initial partial DTL stacks computed by this system as well as any alternate route (second, third choice etc.) partial DTL stacks computed by this switching system in response to crankbacks.

The count of the total number of connection setup messages including DTL stacks originated by this switching system that have cranked back to this switching system at all levels of the hierarchy.

The count of the total number of connection setup messages including DTLs added by this switching system as an entry border node that have cranked back to this switching system at all levels of the hierarchy. This count does not include Crankbacks for which this switching system was not the crankback destination, only those crankbacks that were directed to this switching system are counted here.

The total number of alternate DTL stacks that this switching system has computed and placed into signalling messages as the DTLOriginator.

The total number of alternate partial DTL stacks that this switching system has computed and placed into signalling messages as an entry border node.

The total number of times where the switching system failed to compute a viable DTL stack as the DTLOriginator for some call. It indicates the number of times a call was cleared from this switching system due to originator routing failure.

The total number of times where the switching system failed to compute a viable partial DTL stack as an entry border node for some call. It indicates the number of times a call was either cleared or cranked back from this switching system due to border routing failure.

The total number of times where the switching system failed to compute a viable DTL stack as the DTLOriginator because the destination was unreachable, i.e., those calls that are cleared with cause #2 `specified transit network unreachable' or cause #3 `destination unreachable' in the cause IE.

The total number of times where the switching system failed to compute a viable partial DTL stack as an entry border node because the target of the path calculation was unreachable, i.e., those calls that are cleared or cranked back with cause #2 `specified transit network unreachable' or cause #3 `destination unreachable' in the cause IE.

The pnnixNodeTable collects attributes that affect the operation of a PNNI logical node. There is a single row in this table for each PNNI peer group that the managed system is expected or eligible to become a member of.

An entry in the table, containing information about a PNNI logical node in this switching system.

A value assigned to a node in this switching system that uniquely identifies it in the MIB.

The level of PNNI hierarchy at which this node exists. This attribute is used to determine the default node ID and the default peer group ID for this node. This object may only be written when pnnixNodeAdminStatus has the value down.

The value the switching system is using to represent itself as this node. This object may only be written when pnnixNodeAdminStatus has the value down. If pnnixNodeLowest is true, then the default node ID takes the form defined in Section 5.3.3 for lowest level nodes, with the first octet equal to pnnixNodeLevel, the second octet equal to 160, and the last 20 octets equal to pnnixNodeAtmAddress. If pnnixNodeLowest is false, then the default node ID takes the form defined in Section 5.3.3 for logical group nodes, with the first octet equal to pnnixNodeLevel, the next fourteen octets equal to the value of pnnixNodePeerGroupId for the child node whose election as PGL causes this LGN to be instantiated, the next six octets equal to the ESI of pnnixNodeAtmAddress, and the last octet equal to zero.

Indicates whether this node acts as a lowest level node or whether this node is a logical group node that becomes active when one of the other nodes in this switching system becomes a peer group leader. The value 'false' must not be used with nodes that are not PGL/LGN capable. This object may only be written when pnnixNodeAdminStatus has the value down.

Indicates whether the administrative status of the node is up (the node is allowed to become active) or down (the node is forced to be inactive). When pnnixNodeAdminStatus is down, then pnnixNodeOperStatus must also be down. Enumeration: 'down': 2, 'up': 1.

Indicates whether the node is active or whether the node has yet to become operational. When the value is down, all state has been cleared from the node and the node is not communicating with any of its neighbor nodes. Enumeration: 'down': 2, 'up': 1.

The name of the PNNI routing domain in which this node participates. All lowest-level PNNI nodes with the same pnnixNodeDomainName are presumed to be connected.

This node's ATM End System Address. Remote systems wishing to exchange PNNI protocol packets with this node should direct packets or calls to this address. This attribute may only be written when pnnixNodeAdminStatus has the value down.

The Peer Group Identifier of the peer group that the given node is to become a member of. The default value of this attribute has the first octet equal to pnnixNodeLevel, the next pnnixNodeLevel bits equal to the pnnixNodeLevel bits starting from the third octet of pnnixNodeId, and the remainder padded with zeros. This object may only be written when pnnixNodeAdminStatus has the value down.

Specifies whether the node is restricted to not allowing support of SVCs transiting this node. This attribute determines the setting of the restricted transit bit in the nodal information group originated by this node.

Specifies whether this node uses the complex node representation. A value of `true' indicates that the complex node representation is used, whereas a value of `false' indicates that the simple node representation is used. This attribute determines the setting of the nodal representation bit in the nodal information group originated by this node.

Indicates whether the node is able to support additional point-to-multipoint branches. A value of 'false' indicates that additional branches can be supported, and a value of 'true' indicates that additional branches cannot be supported. This attribute reflects the setting of the restricted branching bit in the nodal information group originated by this node.

Specifies whether the node is currently operating in topology database overload state. This attribute has the same value as the Non-transit for PGL Election bit in the nodal information group originated by this node.

Gauges the total number of PTSEs currently in this node's topology database(s).

To create, delete, activate and de-activate a Node. Enumeration: 'active': 4, 'notActive': 5, 'create': 1, 'modify': 2, 'delete': 3.

Peer group leader election information for a PNNI node in this switching system.

An entry in the table, containing PGL election information of a PNNI logical node in this switching system.

The Leadership priority value this node should advertise in its nodal information group for the given peer group. Only the value zero can be used with nodes that are not PGL/LGN capable. If there is no configured parent node index or no corresponding entry in the pnnixNodeTable, then the advertised leadership priority is zero regardless of this value.

The local node index used to identify the node that will represent this peer group at the next higher level of hierarchy, if this node becomes peer group leader. The value 0 indicates that there is no parent node.

The amount of time in seconds this node will delay advertising its choice of preferred PGL after having initialized operation and reached the full state with at least one neighbor in the peer group.

The amount of time in seconds a node will wait for itself to be declared the preferred PGL by unanimous agreement among its peers. In the absence of unanimous agreement this will be the amount of time that will pass before this node considers a two thirds majority as sufficient agreement to declare itself peer group leader, abandoning the attempt to get unanimous agreement.

The amount of time in seconds after losing connectivity to the current peer group leader, that this node will wait before re-starting the process of electing a new peer group leader.

Indicates the state that this node is in with respect to the Peer Group Leader election that takes place in the node's peer group. The values are enumerated in the Peer Group Leader State Machine. Enumeration: 'hungElection': 9, 'calculating': 5, 'awaitReElection': 10, 'awaitingFull': 3, 'initialDelay': 4, 'operPgl': 7, 'operNotPgl': 8, 'awaiting': 2, 'starting': 1, 'awaitUnanimity': 6.

The Node ID of the node which the local node believes should be or become the peer group leader. This is also the value the local node is currently advertising in the `Preferred Peer Group Leader Node ID' field of its nodal information group within the given peer group. If a Preferred PGL has not been chosen, this attribute's value is set to (all) zero(s).

The Node Identifier of the node which is currently operating as peer group leader of the peer group this node belongs to. If a PGL has not been elected, this attribute's value is set to (all) zero(s).

The time at which the current Peer Group Leader established itself.

The Node Identifier value being used by the Peer Group Leader to represent this peer group at the next higher level of the hierarchy. If this node is at the highest level of the hierarchy or if no PGL has yet been elected the PNNI Protocol Entity sets the value of this attribute to (all) zero(s).

A table of initial PNNI timer values and significant change thresholds.

An entry in the table, containing initial PNNI timer values and significant change thresholds of a PNNI logical node in this switching system.

The initial value for the PTSE hold down timer that will be used by the given node to limit the rate at which it can re-originate PTSEs. It must be a positive non-zero number.

The initial value for the Hello hold down timer that will be used by the given node to limit the rate at which it sends Hellos. It must be a positive non-zero number.

The initial value for the Hello Timer. In the absence of triggered Hellos, this node will send one Hello packet on each of its ports on this interval.

The value for the Hello Inactivity factor that this node will use to determine when a neighbor has gone down.

The amount of time a node will continue to advertise a horizontal (logical) link for which it has not received and processed a LGN Horizontal Link information group.

The initial value for the Refresh timer that this node will use to drive (re-)origination of PTSEs in the absence of triggered updates.

The value for the lifetime multiplier, expressed as a percentage. The result of multiplying the pnnixNodePtseRefreshInterval attribute value by this attribute value is used as the initial lifetime that this node places into self-originated PTSEs.

The period between retransmissions of unacknowledged Database Summary packets, PTSE Request packets, and PTSPs.

The minimum amount of time between transmissions of delayed PTSE acknowledgement packets.

The proportional multiplier used in the algorithms that determine significant change for AvCR parameters, expressed as a percentage.

The minimum threshold used in the algorithms that determine significant change for AvCR parameters, expressed as a percentage.

The proportional multiplier used in the algorithms that determine significant change for CDV metrics, expressed as a percentage.

The proportional multiplier used in the algorithms that determine significant change for CTD metrics, expressed as a percentage.

A table of variables related to SVCC-based routing control channels..

An entry in the table, containing SVCC-based RCC variables of a PNNI logical node in this switching system.

The amount of time this node will delay initiating establishment of an SVCC to a neighbor with a numerically lower ATM address, after determining that such an SVCC should be established.

The amount of time this node will delay after an apparently still necessary and viable SVCC-based RCC is unexpectedly torn down, before attempting to re-establish it.

The amount of time this node will wait for an SVCC, which it has initiated establishment of as the calling party, to become fully established before giving up and tearing it down.

The amount of time this node will wait for an SVCC, which it has decided to accept as the called party, to become fully established before giving up and tearing it down.

An index into the atmTrafficDescrParamTable defined in RFC 1695. This traffic descriptor is used when establishing switched virtual channels for use as SVCC-based RCCs to/from PNNI logical group nodes.

The pnnixScopeTable contains the mappings of membership and connection scope from organizational scope values (used at UNI interfaces) to PNNI scope (i.e. in terms of PNNI routing level indicators).

An entry in the table, containing scope mapping information for a PNNI logical node in this switching system.

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value localNetwork(1).

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value localNetworkPlusOne(2).

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value localNetworkPlusTwo(3).

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value siteMinusOne(4).

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value intraSite(5).

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value sitePlusOne(6).

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value organizationMinusOne(7).

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value intraOrganization(8).

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value organizationPlusOne(9).

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value communityMinusOne(10).

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value intraCommunity(11).

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value communityPlusOne(12).

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value regional(13).

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value interRegional(14).

The highest level of PNNI hierarchy (i.e. smallest PNNI routing level) that lies within the organizational scope value global(15).

A list of the summary address prefixes that may be advertised by the specified logical PNNI entity.

An entry in the table, containing summary address prefix information in this switching system.

The ATM End System Address prefix for the summary.

The prefix length for the summary.

The type (e.g. internal or exterior) of summary being described. Enumeration: 'internal': 1, 'exterior': 2.

Determines what is done with addresses that are being summarized by the instance. The default value (e.g. false) will indicate that the summary should propagate into the peer group. Network Management will be able to set the value of this attribute to `suppress' (e.g. true), which suppresses the summary and any reachable addresses it summarizes from being advertised into the peer group.

Indicates whether the summary is currently being advertised by the node within the local switching system into its peer group. Enumeration: 'inactive': 3, 'suppressing': 2, 'advertising': 1.

To create, delete, activate and de-activate a summary. Enumeration: 'active': 4, 'notActive': 5, 'create': 1, 'modify': 2, 'delete': 3.

The pnnixIfTable contains the attributes necessary to configure a physical interface on a switching system which is capable of being used for PNNI routing. Interfaces may represent physical connection points (i.e. copper/fiber connection points) or VPCs which have been configured for PNNI's use. Each interface is attached to a specific lowest-level node within the switching system. An ifIndex is used as the instance ID to uniquely identify the interface on the local switching system. This index has the same value as the ifIndex object defined in RFC 1573 for the same interface, since this table correlates with the ifTable in RFC 1573. One row in this table is created by the managed system for each row in the ifTable that has an ifType of atm(37) or atmLogical(80).

An entry in the table, containing PNNI specific interface information in this switching system.

Identifies the node within the switching system that the interface is directly attached to.

The Port Identifier of the port as selected by the PNNI protocol entity for the given interface. This value has meaning only within the context of the node to which the port is attached.

The configured aggregation token for this interface. The aggregation token controls what other links the link associated with this interface will be aggregated together with.

Indicates whether the interface is capable of having VPCs established within it or not. This object may only have the value `true' for physical ATM interfaces, i.e. those with an ifType of atm(37).

The administrative weight of this interface for the constant bit rate service category.

The administrative weight of this interface for the real-time variable bit rate service category.

The administrative weight of this interface for the non-real-time variable bit rate service category.

The administrative weight of this interface for the available bit rate service category.

The administrative weight of this interface for the unspecified bit rate service category.

The service category used for the PNNI routing control channel (VCI=18) on this interface.

The traffic descriptor index referring to the entry in the atmTrafficDescrParamTable defined in RFC 1695 that specifies the traffic allocation for the PNNI routing control channel (VCI=18) on this interface.

This table contains the attributes necessary to describe the operation of logical links attached to the local switching system and the relationship with the neighbor nodes on the other end of the links. Links are attached to a specific node within the switching system. A concatenation of the Node Index of the node within the local switching system and the port ID are used as the instance ID to uniquely identify the link. Links may represent horizontal links between lowest level neighboring peers, outside links, uplinks, or horizontal links to/from LGNs. The entire pnnixLink object is read-only, reflecting the fact that this information is discovered dynamically by the PNNI protocol rather than configured.

An entry in the table, containing information about a link attached to a PNNI logical node in this switching system.

The Port Identifier of the link as selected by the local node. This value has meaning only within the context of the node to which the port is attached.

Indicates the type of link being described. Enumeration: 'lowestLevelOutsideLink': 4, 'unknown': 1, 'outsideLinkAndUplink': 6, 'lowestLevelHorizontalLink': 2, 'horizontalLinkToFromLgn': 3, 'uplink': 5.

For horizontal and outside links between lowest-level nodes and for links of unknown type, this attribute indicates the version of PNNI routing protocol used to exchange information over this link. If communication with the neighbor node has not yet been established, then the Version is set to `unknown'. For uplinks (where the port ID is not also used for the underlying outside link) or links to/from LGNs, the Version is set to `unknown'.

For horizontal and outside links between lowest-level nodes and for links of unknown type, this attribute indicates the state of the Hello protocol exchange over this link. For links to/from LGNs, this attribute indicates the state of the corresponding LGN Horizontal Link Hello State Machine. For uplinks (where the port ID is not also used for the underlying outside link), this attribute is set to notApplicable.

Indicates the node identifier of the remote (neighboring) node on the other end of the link. If the pnnixLinkType is `outside link and uplink', this is the node identifier of the lowest-level neighbor node on the other end of the outside link. If the remote node ID is unknown or if the pnnixLinkType is `uplink', this attribute is set to all zeros.

Indicates the port identifier of the port at the remote end of the link as assigned by the remote node. If the pnnixLinkType is `outside link and uplink', this is the port identifier assigned by the lowest-level neighbor node to identify the outside link. If the remote port ID is unknown or if the pnnixLinkType is `uplink', this attribute is set to zero.

Indicates the derived aggregation token value used on this link. For horizontal links between lowest-level nodes and when the link type is not yet known, this attribute takes the value of zero.

For outside links and uplinks, this attribute contains the Node Identifier of the upnode (the neighbor node's identity at the level of the common peer group). When the upnode has not yet been identified, this attribute is set to zero. For horizontal links or when the link type is not yet known, this attribute is set to zero.

For outside links and uplinks, this attribute contains the ATM End System Address used to establish connections to the upnode. When the upnode has not yet been identified, this attribute is set to zero. For horizontal links or when the link type is not yet known, this attribute is set to zero.

For outside links and uplinks, this attribute contains the peer group identifier of the lowest level common Peer Group in the ancestry of the neighboring node and the node within the local switching system. The value of this attribute takes on a value determined by the Hello exchange of hierarchical information that occurs between the two lowest-level border nodes. When the common peer group has not yet been identified, this attribute is set to zero. For horizontal links or when the link type is not yet known, this attribute is set to all zeros.

For horizontal and outside links between lowest-level nodes and for links of unknown type, this attribute identifies the interface to which the logical link corresponds. For all other cases, the value of this object is zero.

For horizontal links to/from LGNs, this attribute identifies the SVCC-based RCC used to exchange information with the neighboring peer logical group node. If the pnnixLinkType is not `horizontal link to/from LGN', this attribute shall take the value of zero.

For horizontal and outside links between lowest-level nodes and for links of unknown type, this attribute contains a count of the number of Hello Packets received over this link. If the pnnixLinkType is `horizontal link to/from LGN' or `uplink', this attribute is set to zero.

For horizontal and outside links between lowest-level nodes and for links of unknown type, this attribute contains a count of the number of Hello Packets transmitted over this link. If the pnnixLinkType is `horizontal link to/from LGN' or `uplink', this attribute is set to zero.

The pnnixNbrPeer Object contains all the attributes necessary to describe the relationship a node in this switching system has with a neighboring node within the same peer group. A concatenation of the Node Identifier of the node within the local switching system and the neighboring peer's Node Identifier is used to form the instance ID for this object. The entire pnnixNbrPeer object is read-only, reflecting the fact that neighboring peers are discovered dynamically by the PNNI protocol rather than configured.

An entry in the table, containing information about this node's relationship with a neighboring peer node.

The Node Identifier of the neighboring peer node.

Indicates the state of this node's Neighboring Peer State Machine associated with pnnixNbrPeerRemoteNodeId. Enumeration: 'exchanging': 3, 'loading': 4, 'npdown': 1, 'full': 5, 'negotiating': 2.

Identifies the SVCC-based RCC being used to communicate with the neighboring peer if one exists. If both the local node and the neighboring peer node are lowest-level nodes, this attribute is set to zero.

A count of the total number of ports that connect to the neighboring peer. If the neighboring peer only communicates via an SVCC-based RCC, the value of this attribute is set to zero. Otherwise it is set to the total number of ports to the neighboring peer in the Hello state 2-WayInside.

A count of the number of Database Summary Packets received from the neighboring peer.

A count of the number of Database Summary Packets transmitted to the neighboring peer.

A count of the number of PTSPs received from the neighboring peer.

A count of the number of PTSPs (re)transmitted to the neighboring peer.

A count of the number of PTSE Request packets received from the neighboring peer.

A count of the number of PTSE Request packets transmitted to the neighboring peer.

A count of the number of PTSE Ack packets received from the neighboring peer.

A count of the number of PTSE Ack packets transmitted to the neighboring peer.

A table of all ports in Hello state 2-Way Inside to a given neighboring peer node. A concatenation of the Node Index of the node within the local switching system, the neighbor's Node Identifier and the Interface Index of the port being described forms the instance ID for this object. This object is only used for lowest-level nodes.

An entry in the table, containing information about a port in the Hello state 2-Way Inside from a PNNI logical node in this switching system to a neighboring peer node.

The port ID of a port to the neighboring peer that is in the Hello state 2-Way Inside.

Indicates whether the port is being used for transmission of flooding and database synchronization information to the neighboring peer.

A table containing the attributes necessary to analyze the operation of the PNNI protocol on SVCC-based Routing Control Channels. This entire object is read-only, reflecting the fact that SVCC-based RCCs are established dynamically during operation of the PNNI protocol rather than configured.

An entry in the table, containing information about an SVCC-based RCC from a PNNI logical node in this switching system.

An index into the node's tables of SVCC-based RCCs.

The version of the PNNI routing protocol used to exchange information with the neighbor node.

The state of the Hello protocol exchange over the SVCC-based RCC. Note: the Down state indicates that the SVCC establishment is in progress.

The remote node at which the SVCC-based RCC terminates.

The ATM End System Address to which SVCC establishment is attempted.

A count of the number of Hello Packets received over this SVCC-based RCC.

A count of the number of Hello Packets transmitted over this SVCC-based RCC.

The interface from which the SVCC-based RCC leaves the switching system. If the SVCC-based RCC has not yet been established, then this attribute takes the value of zero.

The VPI used at the interface from which the SVCC-based RCC leaves the switching system. If the SVCC-based RCC has not yet been established, then this attribute takes the value of zero

The VCI used at the interface from which the SVCC-based RCC leaves the switching system. If the SVCC-based RCC has not yet been established, then this attribute takes the value of zero

The pnnixPtse object contains the attributes that describe the most recent instances of PTSEs in a node's topology database. A concatenation of the Node Identifier of the local node that received the PTSE, the originating Node's Node Identifier and the PTSE Identifier are used to form the instance ID for an instance of this object.

An entry in the table, containing information about a PTSE in the topology database of a PNNI logical node in this switching system.

The Node Identifier of the node that originated the PTSE.

The value of the PTSE Identifier assigned to the PTSE by its originator.

The type of information contained in the PTSE. Enumeration: 'uplinks': 289, 'nodalInformation': 97, 'nodalStateParameters': 96, 'internalReachableAddresses': 224, 'other': 1, 'exteriorReachableAddresses': 256, 'horizontalLinks': 288.

The sequence number of the instance of the PTSE as it appears in the local topology database.

The value of the PTSE checksum as it appears in the local topology database.

The value of the remaining lifetime for the given PTSE as it appears in the local topology database.

An unformatted hexadecimal dump of the PTSE contents in full. Note: If the size of the PTSE contents is larger than the maximum size of SNMP packets then this is truncated.

A table containing attributes necessary to find and analyze the operation of all links and nodes within the PNNI hierarchy, as seen from the perspective of a local node. An instance of a pnniMap Object describes a link in terms of a node at one end of the link. Normally there will be two instances of the pnniMap object in the MIB for each horizontal link. The two instances provide information for Network management to map port identifiers from the nodes at both ends to the link between them. A concatenation of the Local Node Index, Originating Node Identifier and Originating Port Identifier are used to form the instance ID for this object. This entire object is read-only, reflecting the fact that the map is discovered dynamically during operation of the PNNI protocol rather than configured.

An entry in the table, containing connectivity information about a node or link in the PNNI routing domain, as seen from the perspective of a PNNI logical node in this switching system.

The node identifier of the node whose connectivity within itself or to other nodes is being described.

The port identifier of the port as assigned by the originating node, to which the port is attached.

An index into the set of link and nodal connectivity associated with the originating node and port. This index is needed since there may be multiple entries for nodal connectivity from a specific node and port pair, in addition to any entry for a horizontal link or uplink.

The type of PNNI entity being described by this entry in the table. Enumeration: 'node': 3, 'uplink': 2, 'horizontalLink': 1.

Identifies the peer group of the originating node.

For horizontal links to/from LGNs and for uplinks, this attribute contains the derived aggregation token value for this link. For nodes and for horizontal links between lowest-level nodes, this attribute is set to zero.

For horizontal links and uplinks, this attribute contains the node identifier of the node at the other end of the link from the originating node. If unknown, the PNNI protocol entity sets this attribute's value to (all) zero(s). For nodes, this attribute's value is set to (all) zero(s).

For horizontal links and uplinks, this attribute contains the port identifier of the port at the remote end of the link as assigned by the remote node. If unknown, the PNNI protocol entity sets this attribute's value to zero. For nodes, this attribute contains the port identifier of the port at the other end of the spoke or bypass from the originating port. When the originating port ID is zero, a value of zero indicates the default radius. When the originating port ID is non-zero, a value of zero indicates the nodal nucleus.

Indicates whether VPCs can be established across the PNNI entity being described by this entry in the pnnixMapTable.

The value of the PTSE Identifier for the PTSE being originated by the originating node which contains the information group(s) describing the PNNI entity.

An arbitrary integer that is used to associate a set of traffic parameters that are always advertised together. Within this set, the parameters are distinguished by the service categories and direction to which a set of parameters apply.

A list of nodes as seen from the perspective of a local node. The pnnixMapNodeTable contains all information learned by the local node from nodal information PTSEs. This entire object is read-only, reflecting the fact that the map is discovered dynamically during operation of the PNNI protocol rather than configured.

An entry in the table, containing information about a node in the PNNI routing domain, as seen from the perspective of a logical node in this switching system.

Identifies the node whose nodal information is being described.

Identifies the peer group of the originating node.

The ATM End System Address of the originating node.

Indicates whether the originating node is restricted to only allow support of SVCs originating or terminating at this node. A value of `true' indicates that the transit capabilities are restricted, i.e., transit connections are not allowed, whereas a value of `false' indicates that transit connections are allowed. This attribute reflects the setting of the restricted transit bit received in the nodal information PTSE of the originating node.

Indicates whether the originating node uses the complex node representation. If the value is `true', the spokes and bypasses that make up the complex node representation should be found in the pnnixMapTable. This attribute reflects the setting of the nodal representation bit received in the nodal information PTSE of the originating node.

Indicates whether the originating node is able to support additional branches. If the value is 'false', then it can support additional branches. This attribute reflects the setting of the restricted branching bit received in the nodal information PTSE of the originating node.

Indicates whether the originating node is currently operating in topology database overload state. This attribute has the same value as the Non-transit for PGL Election bit in the nodal information group originated by this node.

Indicates whether the originating node claims to be peer group leader of its peer group. This attribute reflects the setting of the 'I am Leader' bit received in the nodal information PTSE of the originating node.

The Leadership priority value advertised by the originating node.

Identifies the node which the originating node believes should be or is peer group leader of its peer group. If the originating node has not chosen a Preferred PGL, this attribute's value is set to (all) zero(s).

When the originating node is a peer group leader, indicates the node ID of the parent LGN. If the originating node is not peer group leader of its peer group, this attribute's value is set to (all) zero(s).

When the originating node is a peer group leader, indicates the ATM address of the parent LGN. If the originating node is not peer group leader of its peer group, this attribute's value is set to (all) zero(s).

When the originating node is a peer group leader, indicates the node's parent peer group ID. If the originating node is not peer group leader of its peer group, this attribute's value is set to (all) zero(s).

When the originating node is a peer group leader, identifies the node elected as peer group leader of the parent peer group. If the originating node is not peer group leader of its peer group, this attribute's value is set to (all) zero(s).

The pnnixMapAddr MIB Object contains a list of all reachable addresses from each node visible to the local node. The Local Node Index, Advertising Node ID, Advertised Port ID, Reachable Address, and Address prefix length are combined to form an instance ID for this object. The entire object is read-only, reflecting the fact that reachable addresses are discovered during dynamic operation of the PNNI protocol rather than configured.

An entry in the table, containing information about an address prefix reachable from a node in the PNNI routing domain, as seen from the perspective of a PNNIX logical node in this switching system.

The node ID of a node advertising reachability to the address prefix.

The port identifier used from the advertising node to reach the given address prefix.

An arbitrary index that is used to enumerate all of the addresses advertised by the specified node.

The value of the ATM End System Address prefix.

The Prefix length to be applied to the ATM End System Address prefix.

A list of all reachable transit networks from each node visible to the local node. The Local Node Index, Advertising Node ID, Advertised Port ID, Transit Network Type, Transit Network Plan, and Transit Network ID are combined to form an instance ID for this object. The entire object is read-only, reflecting the fact that reachable transit networks are discovered during dynamic operation of the PNNI protocol rather than configured..

An entry in the table, containing information about a transit network reachable from a node in the PNNI routing domain, as seen from the perspective of a PNNI logical node in this switching system.

The node ID of a node advertising reachability to the transit network.

The port identifier used from the advertising node to reach the given transit network.

The type of network identification used for this transit network.

The network identification plan according to which network identification has been assigned.

The value of the transit network identifier.

This entity's table of PNNI parameters either associated with a PNNI entity or for the connectivity between a PNNI node and a reachable address or transit network.

A set of parameters that applies to the connectivity from a certain node and port to another node or port or to one or more reachable address prefixes and/or transit networks, for one (or more) particular service category(s). Note that there can be multiple sets of parameters with the same tag, in which case all sets apply to the specified connectivity.

An arbitrary integer that is used to associate a set of traffic parameters that are always advertised together. Within this set, the parameters are distinguished by the service categories and direction to which a set of parameters apply.

The direction, with respect to the advertising node, in which the parameters in this entry apply. Enumeration: 'outgoing': 2, 'incoming': 1.

An index into the set of parameters associated with the given tag and direction.

The service categories to which this set of parameters applies. This is an integer used as a bit mask with each bit that is set representing a single service category for which the resources indicated are available. Bit 5 represents CBR, bit 4 represents real-time VBR, bit 3 represents non-real-time VBR, bit 2 represents ABR, and bit 1 (LSB) represents UBR.

Indicates whether the advertised GCAC parameters apply for CLP=0 traffic or for CLP=0+1 traffic.

The administrative weight from the advertising node to the remote end of the PNNI entity or to the reachable address or transit network, for the specified service categories. If this metric is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter from the advertising node to the remote end of the PNNI entity or to the reachable address or transit network, for the specified service categories. For information learned from PNNI nodes, this is the maximum cell rate in cells per second for the specified service categories. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter from the advertising node to the remote end of the PNNI entity or to the reachable address or transit network, for the specified service categories. For information learned from PNNI nodes, this is the available cell rate in cells per second for the specified service categories. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter from the advertising node to the remote end of the PNNI entity or to the reachable address or transit network, for the specified service categories. For information learned from PNNI nodes, this is the maximum cell transfer delay in microseconds for the specified service categories. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter from the advertising node to the remote end of the PNNI entity or to the reachable address or transit network, for the specified service categories. For information learned from PNNI nodes, this is the cell delay variation in microseconds for the specified service categories. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter from the advertising node to the remote end of the PNNI entity or to the reachable address or transit network, for the specified service categories. For PNNI, this is the cell loss ratio for CLP=0 traffic for the specified service categories. The cell loss ratio value is computed as 10**(-n) where 'n' is the value returned in this variable. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter from the advertising node to the remote end of the PNNI entity or to the reachable address or transit network, for the specified service categories. For PNNI, this is the cell loss ratio for CLP=0+1 traffic for the specified service categories. The cell loss ratio value is computed as 10**(-n) where 'n' is the value returned in this variable. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter from the advertising node to the remote end of the PNNI entity or to the reachable address or transit network, for the specified service categories. For information learned from PNNI nodes, this is the cell rate margin in cells per second for the specified service categories. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter from the advertising node to the remote end of the PNNI entity or to the reachable address or transit network, for the specified service categories. For information learned from PNNI nodes, this is the variance factor in units of 2**(-8) for the specified service categories. If this parameter is not used, its value should be set to 0xFFFFFFFF.

To create, delete, activate and de-activate a set of metrics. Enumeration: 'active': 4, 'notActive': 5, 'create': 1, 'modify': 2, 'delete': 3.

The number of current precalculated PNNI routes to PNNI nodes that are not invalid.

The number of current PNNI routes from nodes in the PNNI routing domain to addresses and transit networks that are not invalid.

This entity's PNNI Routing table (of routes to other nodes).

A particular route to a particular destination node, under a particular policy.

Indicates the service category with which this forwarding table entry is associated.

The node ID of the destination node to which this route proceeds, and at which the DTL stack for this route terminates.

The index into the owning PNNI node's DTL table of the DTL stack that goes with this route.

The port ID of the destination node at which the route terminates. A port ID of zero indicates the node nucleus. When the destination node is represented by the simple node representation, this value should be set to zero.

The routing mechanism via which this route was learned. Enumeration: 'pnni': 4, 'other': 1, 'local': 2, 'mgmt': 3.

The time at which this route was last updated or otherwise determined to be correct. Note that no semantics of `too old' can be implied except through knowledge of the routing protocol by which the route was learned.

A reference to MIB definitions specific to the particular routing protocol which is responsible for this route, as determined by the value specified in the route's pnnixRouteNodeProto value. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }.

For PNNI, indicates whether any advertised GCAC parameters apply for CLP=0 traffic or for CLP=0+1 traffic.

The cumulative administrative weight calculated for the forward direction of this route. If this metric is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the forward direction of this route. For information learned from PNNI nodes, this is the maximum possible cell rate (in cells per second) for the forward direction of the route. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the forward direction of this route. For information learned from PNNI nodes, this is the Available cell rate (in cells per second) for the forward direction of the route. Further information on available bandwidth may be obtainable by reference to the nodal advertisements of the nodes in the path. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the forward direction of this route. For information learned from PNNI nodes, this is the cumulative Maximum Cell Transfer Delay (in microseconds) for the forward direction of the route. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the forward direction of this route. For information learned from PNNI nodes, this is the cumulative Cell Delay Variation (in microseconds) for the forward direction of the route. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the forward direction of this route. For information learned from PNNI nodes, this is the cumulative Cell Loss Ratio for CLP=0 traffic for the forward direction of the route. The cell loss ratio value is computed as 10**(-n) where 'n' is the value returned in this variable. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the forward direction of this route. For information learned from PNNI nodes, this is the cumulative Cell Loss Ratio for CLP=0+1 traffic for the forward direction of the route. The cell loss ratio value is computed as 10**(-n) where 'n' is the value returned in this variable. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the forward direction of this route. For information learned from PNNI nodes, this is the Cell Rate Margin (in cells per second) for the forward direction of the route. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the forward direction of this route. For information learned from PNNI nodes, this is the Variance Factor (in units of 2**(-8)) for the forward direction of the route. If this parameter is not used, its value should be set to 0xFFFFFFFF.

The administrative weight calculated for the backward direction of this route. If this metric is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the backward direction of this route. For information learned from PNNI nodes, this is the maximum possible cell rate (in cells per second) for the backward direction of the route. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the backward direction of this route. For information learned from PNNI nodes, this is the Available cell rate (in cells per second) for the backward direction of the route. Further information on available bandwidth may be obtainable by reference to the nodal advertisements of the nodes in the path. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the backward direction of this route. For information learned from PNNI nodes, this is the cumulative Maximum Cell Transfer Delay (in microseconds) for the backward direction of the route. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the backward direction of this route. For information learned from PNNI nodes, this is the cumulative Cell Delay Variation (in microseconds) for the backward direction of the route. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the backward direction of this route. For information learned from PNNI nodes, this is the cumulative Cell Loss Ratio for CLP=0 traffic for the backward direction of the route. The cell loss ratio value is computed as 10**(-n) where 'n' is the value returned in this variable. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the backward direction of this route. For information learned from PNNI nodes, this is the cumulative Cell Loss Ratio for CLP=0+1 traffic for the backward direction of the route. The cell loss ratio value is computed as 10**(-n) where 'n' is the value returned in this variable. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the backward direction of this route. For information learned from PNNI nodes, this is the Cell Rate Margin (in cells per second) for the backward direction of the route. If this parameter is not used, its value should be set to 0xFFFFFFFF.

An alternate routing parameter for the backward direction of this route. For information learned from PNNI nodes, this is the Variance Factor (in units of 2**(-8)) for the backward direction of the route. If this parameter is not used, its value should be set to 0xFFFFFFFF.

This attribute indicates whether a VPC setup on this route is possible.

The row status variable, used according to row installation and removal conventions. Enumeration: 'active': 4, 'notActive': 5, 'create': 1, 'modify': 2, 'delete': 3.

The set of all DTL stacks used for the pre-computed routes maintained by this managed entity.

A segment of a DTL stack. The complete DTL stack is formed by traversing the rows of the table for which the pnniDTLIndex is the same. Level transitions are indicated using the pnnixDLTLinkType column.

The index in the node's DTL table of this DTL stack.

The index in the current DTL stack of this entry.

The node which is this hop in the DTL stack.

The port from the pnnixDTLNodeId to use as the exit. If the DTL stack does not care, this is coded as zero.

The type of link out from this node (pnnixDTLNodeId). This is well defined even if the specific port is not specified. Enumeration: 'horizontal': 2, 'last': 4, 'uplink': 3, 'invalid': 1.

The row status variable, used according to row installation and removal conventions. Enumeration: 'active': 4, 'notActive': 5, 'create': 1, 'modify': 2, 'delete': 3.

A table containing all the attributes necessary to determine what the PNNI entity believes is reachable in terms of ATM End System Addresses and to determine which nodes are advertising this reachability. This table is also used to configure static routes to reachable address prefixes. The local node index that received the reachability information, reachable address, address prefix length, and an index that distinguishes between multiple listings of connectivity to a given address prefix from a given local node are combined to form an instance ID for this object..

An entry in the table, containing information about a reachable address prefix.

The value of the ATM End System Address prefix.

The prefix length to be applied to the ATM End System Address prefix.

An index into the set of listings of connectivity to a given address prefix from a given local node. In our implementation we allow the range of 1-5 for each type of QOS class.

The local interface over which the reachable address can be reached. The value zero indicates an unknown interface or reachability through a remote node. This object may only have a non-zero value if the value of the corresponding instance of pnniRouteAddrProto is other than 'pnni', pnnixRouteAddrType is other than 'reject', and the node identified by pnnixRouteAddrAdvertisingNodeId is instantiated within this switching system.

The node ID of a node advertising reachability to the address prefix. If the local node index is zero, then the advertising node ID must be set to all zeros.

The port identifier used from the advertising node to reach the given address prefix.

The type (e.g. internal or exterior) of reachability from the advertising node to the address prefix. Reject(2) refers to an address prefix which, if matched, indicates that the message should be discarded as unreachable. This is used in some protocols as a means of correctly aggregating routes. Enumeration: 'other': 1, 'internal': 3, 'exterior': 4, 'reject': 2.

The routing mechanism via which the connectivity from the advertising node to the reachable address prefix was learned. Enumeration: 'pnni': 4, 'other': 1, 'local': 2, 'mgmt': 3.

The PNNIX scope of advertisement (i.e. level of PNNI hierarchy) of the reachability from the advertising node to the address prefix.

Indicates whether VPCs can be established from the advertising node to the reachable address prefix.

The index into the pnnixMetricsTable for the traffic parameter values that apply for the connectivity from the advertising node to the reachable address prefix. There will be one or more entries in the pnnixMetricsTable whose first instance identifier matches the value of this variable. If there are no parameters associated with this reachable address prefix then the distinguished value zero is used.

For reachable addresses learned via PNNI, this attribute contains the value of the PTSE Identifier for the PTSE being originated by the originating node which contains the information group(s) describing the reachable address. For reachable addresses learned by means other than PNNI, this attribute is set to zero.

Whether or not the reachable address specified by this entry is to be advertised by the local node into its PNNI routing domain. This object may only take on the value 'true' when the value of the corresponding instance of pnnixRouteAddrProto is other than 'pnni'.

A reference to MIB definitions specific to the particular routing protocol which is responsible for this reachable address prefix, as determined by the value specified in the route's pnnixRouteAddrProto value. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }.

Indicates whether the reachable address prefix is operationally valid and whether it is being advertised by this node. Enumeration: 'active': 2, 'inactive': 1, 'advertised': 3.

Indicates when the connectivity from the advertising node to the reachable address prefix became known to the local node.

To create, delete, activate and de-activate a reachable address prefix. Enumeration: 'active': 4, 'notActive': 5, 'create': 1, 'modify': 2, 'delete': 3.

A table containing all the attributes necessary to determine what transit networks the PNNI entity believes are reachable and to determine which nodes are advertising this reachability. This table is also used to add static routes to reachable transit networks. The local node index which received the reachability information, type of network identification, network identification plan, transit network identifier, and an index that distinguishes between multiple listings of connectivity to a given transit network from a given local node are combined to form an instance ID for this object.

An entry in the table, containing information about a reachable transit network.

The type of network identification used for this transit network.

The network identification plan according to which network identification has been assigned.

The value of the transit network identifier.

An index into the set of listings of connectivity to a given transit network from a given local node. In our implementation we allow the range of 1-5 for each type of QOS class.

The local interface over which the transit network can be reached. The value zero indicates an unknown interface or reachability through a remote node. This object may only have a non-zero value if the value of the corresponding instance of pnnixRouteTnsProto is other than 'pnni' and the node identified by pnnixRouteTnsAdvertisingNodeId is instantiated within this switching system.

The node ID of a node advertising reachability to the transit network. If the local node index is zero, then the advertising node ID must also be set to zero.

The port identifier used from the advertising node to reach the given transit network.

The type (e.g. exterior or other) of reachability from the advertising node to the transit network. Enumeration: 'other': 1, 'exterior': 4.

The routing mechanism via which the connectivity from the advertising node to the transit network was learned. Enumeration: 'pnni': 4, 'other': 1, 'local': 2, 'mgmt': 3.

The PNNI scope of advertisement (i.e. level of PNNI hierarchy) of the reachability from the advertising node to the transit network.

Indicates whether VPCs can be established from the advertising node to the reachable transit network.

The index into the pnnixMetricsTable for the traffic parameter values that apply for the connectivity from the advertising node to the transit network. There will be one or more entries in the pnnixMetricsTable whose first instance identifier matches the value of this variable. If there are no parameters associated with this transit network then the distinguished value zero is used.

For reachable transit networks learned via PNNI, this attribute contains the value of the PTSE Identifier for the PTSE being originated by the originating node which contains the information group(s) describing the transit network. For reachable transit networks learned by means other than PNNI, this attribute is set to zero.

Whether or not the transit network specified by this entry is to be advertised by the local node into its PNNI routing domain. This object may only take on the value 'true' when the value of the corresponding instance of pnniRouteNodeProto is other than 'pnni'.

A reference to MIB definitions specific to the particular routing protocol which is responsible for this transit network, as determined by the value specified in the route's pnnixRouteTnsProto value. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }.

Indicates whether the reachable transit network is operationally valid and whether it is being advertised by this node. Enumeration: 'active': 2, 'inactive': 1, 'advertised': 3.

Indicates how long the connectivity from the advertising node to the reachable transit network has been known to the local node.

To create, delete, activate and de-activate a reachable transit network. Enumeration: 'active': 4, 'notActive': 5, 'create': 1, 'modify': 2, 'delete': 3.

The number of adjacencies registered via ILMI in PNNIs lowest nodes adjacency table in this switching system.

The pnnixIAdjTable stores records of adjacncies which ILMI has registered with the lowest level PNNI node in this network. There is a single row in this table for each adjacency which ILMI has registered.

An entry in the table, containing information about a PNNI logical node in this switching system.

A value assigned to an ILMI client registered via ILMI in this switching system that uniquely identifies it in the PNNI ILMI adjacency table.

This adjacency's ATM End System Address.

The slot in which this adjacency is physically connected to this switching system.

The port in the slot which this adjacency is physically connected to this switching system.

The instance identifier on the slot port pair which this adjacency is physically connected to this switching system. In the event that this is not a tunnel, this value will be zero.

The unique port id which PNNI has bound to this physical slot, port, and instance tuple.

Indicates if this ILMI client is advertised by this switching system. Note that if this value is False, the summary address may be used by remote nodes to still reach this ILMI client if pnnixIAdjSummarized is set to True (below).

Indicates if this ILMI client is summarized by this switching system. Note that if this value is True, other nodes in the peer group will route to this node's advertised port of 1. Calls terminating at end-systems attached to this node will then be vectored out the pnnixIAdjCsmPPort.

This field contains a timestamp of when ILMI registered this adjacency with PNNI.

The pnnixRtstTable is a single-row table which returns the results of a route test requested by a remote mgmt station. The route test parameters are specified in the INDEX.

An entry in the route test table, containing information about a route lookup request.

The class the route request is to use. Enumeration: 'cbr': 2, 'abr': 5, 'vbrNrt': 4, 'vbrRt': 3, 'ubr': 1.

This index specifies the type of call which may be either point to point or point to multi-point. Enumeration: 'pmp': 2, 'ptpt': 1.

The destination address. This may be specified by the user as an address prefix, but the snmp manager must pad this out to 20 octets.

Indicates if an error has occurred and if so, the nature of the error. If this is set to success, then no error occurred and the rest of the row contains useful information. Enumeration: 'noRouteToDest': 2, 'other': 4, 'dtlExhaustion': 3, 'success': 1.

If error is set to success, this flag indicates the nature of the route lookup confirmation. If this flag is set to dtlAdded, then the route request resulted in a DTL being allocated for this request. In this case, the pnnixRtstOutboundPort, pnnixRtstHopCount, pnnixRtstDTL, and pnnixRtstCurPointer contain useful information. (Also, after this information is conveyed back to the manager, the DTL entry is freed.) If this flag is set to direct, then the route request is informing the caller to proceed out a directly attached port. In this case, the pnnixRtstOutboundPort is valid and is either 1 (to indicate a match on this node's summary address) or is a reference to the pnni advertised outbound port. If this flag is set to myself, then the route request is informing the caller that the test call to the node in this switching system (identified by pnnixNodeIndex) returned a successful match of myself as the destination. In this case, the pnnixRtstOutboundPort is valid and is set to 0 (which indicates a match on this node's own address). If this flag is set to directEreach, then the route request is informing the caller that the test call to the destination resulted in a direct indication. In this case, the pnnixRtstOutboundPort is valid and is set to the static route's pnni advertised port ID. If the user also specified a VPI and E.164 address, then the pnnixRtstVPI and pnnixRtstE164 fields will also be present. Enumeration: 'myself': 3, 'directEreach': 4, 'dtlAdded': 1, 'direct': 2.

If error is set to success, this indicates the outbound port of the route lookup confirmation. If this is set to 0, then this indicates the call was placed to this switching system's pnnixNodeIndex. If this is set to 1, then this indicates the call was placed to a reachability which matched this node's summary address. In this event, the IAdj table would be consulted to determine the actual port (if any) where the destination resided. If set to any other value, it indicates the pnni advertised port of the static route which caused this port to be returned.

If error is set to success, and pnnixRtstFlags is set to directEreach, then this indicates the vpi (if set by the user) used to route the call.

If error is set to success, and pnnixRtstFlags is set to directEreach, then this indicates the E.164 address (if set by the user) used to route the call.

If error is set to success, and pnnixRtstFlags is set to directEreach, then this indicates the number of significant octets used in the above E.164 address.

If error is set to success, and pnnixRtstFlags is set to dtlAdded, then this indicates the number of hops in the pnnixRtstDTL.

If error is set to success, and pnnixRtstFlags is set to dtlAdded, then this indicates the DTL generated by the route lookup function in the switching system. Note that this is a complete DTL meaning that the DTL IE header is also present. It has enough room for 50 entries (50 hops). Each entry has a 22-octet node-ID followed by a 4-octet PnniPortId. Entries therefore are 26 octets each and each entry is contiguous with its predecessor and successor. This DTL will not appear in the DTL table since it's freed after generating the reply to the management station.

If error is set to success, and pnnixRtstFlags is set to dtlAdded, then this indicates the offset (in bytes) into pnnixRtstDTL of the curPtr.