PNNI-MIB Table View

The pnniNodeTable 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.

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

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

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

The pnniScopeTable 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).

The pnniIfTable 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).

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 pnniLink object is read-only, reflecting the
fact that this information is discovered dynamically by the
PNNI protocol rather than configured.

The pnniNbrPeer 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 pnniNbrPeer object is read-only, reflecting the
fact that neighboring peers are discovered dynamically by
the PNNI protocol rather than configured.

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.

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.

The pnniPtse 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.

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.

A list of nodes as seen from the perspective of a local
node.  The pnniMapNodeTable 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.

The pnniMapAddr 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.

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.

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.

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

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

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.

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.

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