XPNNI-MIB
Detailed view of the defined objects, syntax rules, and hierarchical paths.
365
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
365 total| Object Name |
|---|
pnnixMIB OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1 |
RFC1213-MIB Unknown .1.3.6.1.4.1.800.3.2.1.1 |
pnnixMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.1 |
pnnixBaseGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.1.1 |
pnnixHighestVersionThe highest version of the PNNI protocol that the
software in this switching system is capable of executing.ro PnnixVersion .1.3.6.1.4.1.800.3.2.1.1.1.1.1 |
pnnixLowestVersionThe lowest version of the PNNI Protocol that the
software in this switching system is capable of executing.ro PnnixVersion .1.3.6.1.4.1.800.3.2.1.1.1.1.2 |
pnnixDtlCountOriginatorThe 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.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.1.3 |
pnnixDtlCountBorderThe 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.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.1.4 |
pnnixCrankbackCountOriginatorThe 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.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.1.5 |
pnnixCrankbackCountBorderThe 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.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.1.6 |
pnnixAltRouteCountOriginatorThe total number of alternate DTL stacks that this
switching system has computed and placed into
signalling messages as the DTLOriginator.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.1.7 |
pnnixAltRouteCountBorderThe total number of alternate partial DTL stacks that this
switching system has computed and placed into signalling
messages as an entry border node.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.1.8 |
pnnixRouteFailCountOriginatorThe 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.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.1.9 |
pnnixRouteFailCountBorderThe 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.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.1.10 |
pnnixRouteFailUnreachableOriginatorThe 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.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.1.11 |
pnnixRouteFailUnreachableBorderThe 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.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.1.12 |
pnnixNodeTableThe 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. SEQUENCE OF PnnixNodeEntry .1.3.6.1.4.1.800.3.2.1.1.1.2 |
pnnixNodeEntryAn entry in the table, containing information about a PNNI
logical node in this switching system. PnnixNodeEntry .1.3.6.1.4.1.800.3.2.1.1.1.2.1 |
pnnixNodeIndexA value assigned to a node in this switching system that
uniquely identifies it in the MIB. PnnixNodeIndex .1.3.6.1.4.1.800.3.2.1.1.1.2.1.1 |
pnnixNodeLevelThe 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.rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.2.1.2 |
pnnixNodeIdThe 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.rw PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.2.1.3 |
pnnixNodeLowestIndicates 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.2.1.4 |
pnnixNodeAdminStatusIndicates 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.rw Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.2.1.5 |
pnnixNodeOperStatusIndicates 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.ro Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.2.1.6 |
pnnixNodeDomainNameThe 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.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.2.1.7 |
pnnixNodeAtmAddressThis 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.rw PnnixAtmAddr .1.3.6.1.4.1.800.3.2.1.1.1.2.1.8 |
pnnixNodePeerGroupIdThe 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.rw PnnixPeerGroupId .1.3.6.1.4.1.800.3.2.1.1.1.2.1.9 |
pnnixNodeRestrictedTransitSpecifies 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.2.1.10 |
pnnixNodeComplexRepSpecifies 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.2.1.11 |
pnnixNodeRestrictedBranchingIndicates 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.2.1.12 |
pnnixNodeDatabaseOverloadSpecifies 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.2.1.13 |
pnnixNodePtsesGauges the total number of PTSEs currently in this
node's topology database(s).ro Gauge .1.3.6.1.4.1.800.3.2.1.1.1.2.1.14 |
pnnixNodeRowStatusTo create, delete, activate and de-activate a Node.rw Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.2.1.15 |
pnnixNodePglTablePeer group leader election information for a PNNI node in
this switching system. SEQUENCE OF PnnixNodePglEntry .1.3.6.1.4.1.800.3.2.1.1.1.3 |
pnnixNodePglEntryAn entry in the table, containing PGL election information
of a PNNI logical node in this switching system. PnnixNodePglEntry .1.3.6.1.4.1.800.3.2.1.1.1.3.1 |
pnnixNodePglLeadershipPriorityThe 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.rw INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.3.1.1 |
pnnixNodeCfgParentNodeIndexThe 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.rw PnnixNodeIndex .1.3.6.1.4.1.800.3.2.1.1.1.3.1.2 |
pnnixNodePglInitTimeThe 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.rw INTEGER -- UNITS "seconds" .1.3.6.1.4.1.800.3.2.1.1.1.3.1.3 |
pnnixNodePglOverrideDelayThe 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.rw INTEGER -- UNITS "seconds" .1.3.6.1.4.1.800.3.2.1.1.1.3.1.4 |
pnnixNodePglReelectTimeThe 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.rw INTEGER -- UNITS "seconds" .1.3.6.1.4.1.800.3.2.1.1.1.3.1.5 |
pnnixNodePglStateIndicates 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.ro Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.3.1.6 |
pnnixNodePreferredPglThe 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).ro PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.3.1.7 |
pnnixNodePeerGroupLeaderThe 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).ro PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.3.1.8 |
pnnixNodePglTimeStampThe time at which the current Peer Group Leader established
itself.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.3.1.9 |
pnnixNodeActiveParentNodeIdThe 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).ro PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.3.1.10 |
pnnixNodeTimerTableA table of initial PNNI timer values and significant
change thresholds. SEQUENCE OF PnnixNodeTimerEntry .1.3.6.1.4.1.800.3.2.1.1.1.4 |
pnnixNodeTimerEntryAn entry in the table, containing initial PNNI timer values
and significant change thresholds of a PNNI logical node in
this switching system. PnnixNodeTimerEntry .1.3.6.1.4.1.800.3.2.1.1.1.4.1 |
pnnixNodePtseHolddownThe 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.rw INTEGER -- UNITS "100 milliseconds" .1.3.6.1.4.1.800.3.2.1.1.1.4.1.1 |
pnnixNodeHelloHolddownThe 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.rw INTEGER -- UNITS "100 milliseconds" .1.3.6.1.4.1.800.3.2.1.1.1.4.1.2 |
pnnixNodeHelloIntervalThe 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.rw INTEGER -- UNITS "seconds" .1.3.6.1.4.1.800.3.2.1.1.1.4.1.3 |
pnnixNodeHelloInactivityFactorThe value for the Hello Inactivity factor that this
node will use to determine when a neighbor has gone down.rw INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.4.1.4 |
pnnixNodeHlinkInactThe 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.rw INTEGER -- UNITS "seconds" .1.3.6.1.4.1.800.3.2.1.1.1.4.1.5 |
pnnixNodePtseRefreshIntervalThe initial value for the Refresh timer that this node will
use to drive (re-)origination of PTSEs in the absence of
triggered updates.rw INTEGER -- UNITS "seconds" .1.3.6.1.4.1.800.3.2.1.1.1.4.1.6 |
pnnixNodePtseLifetimeFactorThe 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.rw INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.4.1.7 |
pnnixNodeRxmtIntervalThe period between retransmissions of unacknowledged
Database Summary packets, PTSE Request packets, and PTSPs.rw INTEGER -- UNITS "seconds" .1.3.6.1.4.1.800.3.2.1.1.1.4.1.8 |
pnnixNodePeerDelayedAckIntervalThe minimum amount of time between transmissions of
delayed PTSE acknowledgement packets.rw INTEGER -- UNITS "100 milliseconds" .1.3.6.1.4.1.800.3.2.1.1.1.4.1.9 |
pnnixNodeAvcrPmThe proportional multiplier used in the algorithms that
determine significant change for AvCR parameters, expressed
as a percentage.rw INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.4.1.10 |
pnnixNodeAvcrMtThe minimum threshold used in the algorithms that determine
significant change for AvCR parameters, expressed as a
percentage.rw INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.4.1.11 |
pnnixNodeCdvPmThe proportional multiplier used in the algorithms that
determine significant change for CDV metrics, expressed as
a percentage.rw INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.4.1.12 |
pnnixNodeCtdPmThe proportional multiplier used in the algorithms that
determine significant change for CTD metrics, expressed as
a percentage.rw INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.4.1.13 |
pnnixNodeSvccTableA table of variables related to SVCC-based routing control
channels.. SEQUENCE OF PnnixNodeSvccEntry .1.3.6.1.4.1.800.3.2.1.1.1.5 |
pnnixNodeSvccEntryAn entry in the table, containing SVCC-based RCC variables
of a PNNI logical node in this switching system. PnnixNodeSvccEntry .1.3.6.1.4.1.800.3.2.1.1.1.5.1 |
pnnixNodeSvccInitTimeThe 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.rw INTEGER -- UNITS "seconds" .1.3.6.1.4.1.800.3.2.1.1.1.5.1.1 |
pnnixNodeSvccRetryTimeThe 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.rw INTEGER -- UNITS "seconds" .1.3.6.1.4.1.800.3.2.1.1.1.5.1.2 |
pnnixNodeSvccCallingIntegrityTimeThe 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.rw INTEGER -- UNITS "seconds" .1.3.6.1.4.1.800.3.2.1.1.1.5.1.3 |
pnnixNodeSvccCalledIntegrityTimeThe 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.rw INTEGER -- UNITS "seconds" .1.3.6.1.4.1.800.3.2.1.1.1.5.1.4 |
pnnixNodeSvccTrafficDescriptorIndexAn 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.rw AtmpTrafficDescrParamIndex .1.3.6.1.4.1.800.3.2.1.1.1.5.1.5 |
pnnixScopeMappingTableThe 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). SEQUENCE OF PnnixScopeMappingEntry .1.3.6.1.4.1.800.3.2.1.1.1.6 |
pnnixScopeMappingEntryAn entry in the table, containing scope mapping information
for a PNNI logical node in this switching system. PnnixScopeMappingEntry .1.3.6.1.4.1.800.3.2.1.1.1.6.1 |
pnnixScopeLocalNetworkThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value localNetwork(1).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.1 |
pnnixScopeLocalNetworkPlusOneThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value localNetworkPlusOne(2).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.2 |
pnnixScopeLocalNetworkPlusTwoThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value localNetworkPlusTwo(3).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.3 |
pnnixScopeSiteMinusOneThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value siteMinusOne(4).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.4 |
pnnixScopeIntraSiteThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value intraSite(5).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.5 |
pnnixScopeSitePlusOneThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value sitePlusOne(6).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.6 |
pnnixScopeOrganizationMinusOneThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value organizationMinusOne(7).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.7 |
pnnixScopeIntraOrganizationThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value intraOrganization(8).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.8 |
pnnixScopeOrganizationPlusOneThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value organizationPlusOne(9).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.9 |
pnnixScopeCommunityMinusOneThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value communityMinusOne(10).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.10 |
pnnixScopeIntraCommunityThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value intraCommunity(11).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.11 |
pnnixScopeCommunityPlusOneThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value communityPlusOne(12).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.12 |
pnnixScopeRegionalThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value regional(13).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.13 |
pnnixScopeInterRegionalThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value interRegional(14).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.14 |
pnnixScopeGlobalThe highest level of PNNI hierarchy (i.e. smallest PNNI
routing level) that lies within the organizational scope
value global(15).rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.6.1.15 |
pnnixSummaryTableA list of the summary address prefixes that may be
advertised by the specified logical PNNI entity. SEQUENCE OF PnnixSummaryEntry .1.3.6.1.4.1.800.3.2.1.1.1.7 |
pnnixSummaryEntryAn entry in the table, containing summary address prefix
information in this switching system. PnnixSummaryEntry .1.3.6.1.4.1.800.3.2.1.1.1.7.1 |
pnnixSummaryAddressThe ATM End System Address prefix for the summary. AtmAddrPrefix .1.3.6.1.4.1.800.3.2.1.1.1.7.1.1 |
pnnixSummaryPrefixLengthThe prefix length for the summary. PnnixPrefixLength .1.3.6.1.4.1.800.3.2.1.1.1.7.1.2 |
pnnixSummaryTypeThe type (e.g. internal or exterior) of summary being
described.rw Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.7.1.3 |
pnnixSummarySuppressDetermines 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.7.1.4 |
pnnixSummaryStateIndicates whether the summary is currently being advertised
by the node within the local switching system into its peer
group.ro Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.7.1.5 |
pnnixSummaryRowStatusTo create, delete, activate and de-activate a summary.rw Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.7.1.6 |
pnnixIfTableThe 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). SEQUENCE OF PnnixIfEntry .1.3.6.1.4.1.800.3.2.1.1.1.8 |
pnnixIfEntryAn entry in the table, containing PNNI specific interface
information in this switching system. PnnixIfEntry .1.3.6.1.4.1.800.3.2.1.1.1.8.1 |
pnnixIfNodeIndexIdentifies the node within the switching system that the
interface is directly attached to.rw PnnixNodeIndex .1.3.6.1.4.1.800.3.2.1.1.1.8.1.1 |
pnnixIfPortIdThe 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.ro PnnixPortId .1.3.6.1.4.1.800.3.2.1.1.1.8.1.2 |
pnnixIfAggrTokenThe configured aggregation token for this interface. The
aggregation token controls what other links the link
associated with this interface will be aggregated together
with.rw PnnixAggrToken .1.3.6.1.4.1.800.3.2.1.1.1.8.1.3 |
pnnixIfVPCapabilityIndicates 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).rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.8.1.4 |
pnnixIfAdmWeightCbrThe administrative weight of this interface for the
constant bit rate service category.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.8.1.5 |
pnnixIfAdmWeightRtVbrThe administrative weight of this interface for the
real-time variable bit rate service category.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.8.1.6 |
pnnixIfAdmWeightNrtVbrThe administrative weight of this interface for the
non-real-time variable bit rate service category.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.8.1.7 |
pnnixIfAdmWeightAbrThe administrative weight of this interface for the
available bit rate service category.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.8.1.8 |
pnnixIfAdmWeightUbrThe administrative weight of this interface for the
unspecified bit rate service category.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.8.1.9 |
pnnixIfRccServiceCategoryThe service category used for the PNNI routing control
channel (VCI=18) on this interface.rw ServiceCategory .1.3.6.1.4.1.800.3.2.1.1.1.8.1.10 |
pnnixIfRccTrafficDescrIndexThe 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.rw AtmpTrafficDescrParamIndex .1.3.6.1.4.1.800.3.2.1.1.1.8.1.11 |
pnnixLinkTableThis 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. SEQUENCE OF PnnixLinkEntry .1.3.6.1.4.1.800.3.2.1.1.1.9 |
pnnixLinkEntryAn entry in the table, containing information about a link
attached to a PNNI logical node in this switching system. PnnixLinkEntry .1.3.6.1.4.1.800.3.2.1.1.1.9.1 |
pnnixLinkPortIdThe 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. INTEGER -- SYNTAX PnnixPortId .1.3.6.1.4.1.800.3.2.1.1.1.9.1.1 |
pnnixLinkTypeIndicates the type of link being described.ro Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.9.1.2 |
pnnixLinkVersionFor 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'.ro PnnixVersion .1.3.6.1.4.1.800.3.2.1.1.1.9.1.3 |
pnnixLinkHelloStateFor 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.ro PnnixHelloState .1.3.6.1.4.1.800.3.2.1.1.1.9.1.4 |
pnnixLinkRemoteNodeIdIndicates 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.ro PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.9.1.5 |
pnnixLinkRemotePortIdIndicates 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.ro PnnixPortId .1.3.6.1.4.1.800.3.2.1.1.1.9.1.6 |
pnnixLinkDerivedAggrTokenIndicates 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.ro PnnixAggrToken .1.3.6.1.4.1.800.3.2.1.1.1.9.1.7 |
pnnixLinkUpnodeIdFor 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.ro PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.9.1.8 |
pnnixLinkUpnodeAtmAddressFor 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.ro PnnixAtmAddr .1.3.6.1.4.1.800.3.2.1.1.1.9.1.9 |
pnnixLinkCommonPeerGroupIdFor 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.ro PnnixPeerGroupId .1.3.6.1.4.1.800.3.2.1.1.1.9.1.10 |
pnnixLinkIfIndexFor 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.ro InterfaceIndex .1.3.6.1.4.1.800.3.2.1.1.1.9.1.11 |
pnnixLinkSvccRccIndexFor 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.ro PnnixSvccRccIndex .1.3.6.1.4.1.800.3.2.1.1.1.9.1.12 |
pnnixLinkRcvHellosFor 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.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.9.1.13 |
pnnixLinkXmtHellosFor 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.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.9.1.14 |
pnnixNbrPeerTableThe 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. SEQUENCE OF PnnixNbrPeerEntry .1.3.6.1.4.1.800.3.2.1.1.1.10 |
pnnixNbrPeerEntryAn entry in the table, containing information about this
node's relationship with a neighboring peer node. PnnixNbrPeerEntry .1.3.6.1.4.1.800.3.2.1.1.1.10.1 |
pnnixNbrPeerRemoteNodeIdThe Node Identifier of the neighboring peer node. PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.10.1.1 |
pnnixNbrPeerStateIndicates the state of this node's Neighboring Peer State
Machine associated with pnnixNbrPeerRemoteNodeId.ro Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.10.1.2 |
pnnixNbrPeerSvccRccIndexIdentifies 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.ro PnnixSvccRccIndex .1.3.6.1.4.1.800.3.2.1.1.1.10.1.3 |
pnnixNbrPeerPortCountA 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.ro Gauge .1.3.6.1.4.1.800.3.2.1.1.1.10.1.4 |
pnnixNbrPeerRcvDbSumsA count of the number of Database Summary Packets received
from the neighboring peer.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.10.1.5 |
pnnixNbrPeerXmtDbSumsA count of the number of Database Summary Packets
transmitted to the neighboring peer.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.10.1.6 |
pnnixNbrPeerRcvPtspsA count of the number of PTSPs received from the
neighboring peer.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.10.1.7 |
pnnixNbrPeerXmtPtspsA count of the number of PTSPs (re)transmitted to the
neighboring peer.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.10.1.8 |
pnnixNbrPeerRcvPtseReqsA count of the number of PTSE Request packets received from
the neighboring peer.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.10.1.9 |
pnnixNbrPeerXmtPtseReqsA count of the number of PTSE Request packets transmitted
to the neighboring peer.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.10.1.10 |
pnnixNbrPeerRcvPtseAcksA count of the number of PTSE Ack packets received from the
neighboring peer.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.10.1.11 |
pnnixNbrPeerXmtPtseAcksA count of the number of PTSE Ack packets transmitted to
the neighboring peer.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.10.1.12 |
pnnixNbrPeerPortTableA 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. SEQUENCE OF PnnixNbrPeerPortEntry .1.3.6.1.4.1.800.3.2.1.1.1.11 |
pnnixNbrPeerPortEntryAn 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. PnnixNbrPeerPortEntry .1.3.6.1.4.1.800.3.2.1.1.1.11.1 |
pnnixNbrPeerPortIdThe port ID of a port to the neighboring peer that is in
the Hello state 2-Way Inside. PnnixPortId SYNTAX INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.11.1.1 |
pnnixNbrPeerPortFloodStatusIndicates whether the port is being used for transmission
of flooding and database synchronization information to the
neighboring peer.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.11.1.2 |
pnnixSvccRccTableA 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. SEQUENCE OF PnnixSvccRccEntry .1.3.6.1.4.1.800.3.2.1.1.1.12 |
pnnixSvccRccEntryAn entry in the table, containing information about an
SVCC-based RCC from a PNNI logical node in this switching
system. PnnixSvccRccEntry .1.3.6.1.4.1.800.3.2.1.1.1.12.1 |
pnnixSvccRccIndexAn index into the node's tables of SVCC-based RCCs. PnnixSvccRccIndex .1.3.6.1.4.1.800.3.2.1.1.1.12.1.1 |
pnnixSvccRccVersionThe version of the PNNI routing protocol used to exchange
information with the neighbor node.ro PnnixVersion .1.3.6.1.4.1.800.3.2.1.1.1.12.1.2 |
pnnixSvccRccHelloStateThe state of the Hello protocol exchange over the
SVCC-based RCC.
Note: the Down state indicates that the SVCC
establishment is in progress.ro PnnixHelloState .1.3.6.1.4.1.800.3.2.1.1.1.12.1.3 |
pnnixSvccRccRemoteNodeIdThe remote node at which the SVCC-based RCC terminates.ro PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.12.1.4 |
pnnixSvccRccRemoteAtmAddressThe ATM End System Address to which SVCC establishment is
attempted.ro PnnixAtmAddr .1.3.6.1.4.1.800.3.2.1.1.1.12.1.5 |
pnnixSvccRccRcvHellosA count of the number of Hello Packets received over this
SVCC-based RCC.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.12.1.6 |
pnnixSvccRccXmtHellosA count of the number of Hello Packets transmitted over
this SVCC-based RCC.ro Counter .1.3.6.1.4.1.800.3.2.1.1.1.12.1.7 |
pnnixSvccRccIfIndexThe 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.ro InterfaceIndex .1.3.6.1.4.1.800.3.2.1.1.1.12.1.8 |
pnnixSvccRccVpiThe 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 zeroro INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.12.1.9 |
pnnixSvccRccVciThe 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 zeroro INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.12.1.10 |
pnnixPtseTableThe 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. SEQUENCE OF PnnixPtseEntry .1.3.6.1.4.1.800.3.2.1.1.1.13 |
pnnixPtseEntryAn entry in the table, containing information about a PTSE
in the topology database of a PNNI logical node in this
switching system. PnnixPtseEntry .1.3.6.1.4.1.800.3.2.1.1.1.13.1 |
pnnixPtseOriginatingNodeIdThe Node Identifier of the node that originated the PTSE. PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.13.1.1 |
pnnixPtseIdThe value of the PTSE Identifier assigned to the PTSE by
its originator. Gauge SYNTAX INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.13.1.2 |
pnnixPtseTypeThe type of information contained in the PTSE.ro Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.13.1.3 |
pnnixPtseSequenceNumThe sequence number of the instance of the PTSE as it
appears in the local topology database.ro Gauge .1.3.6.1.4.1.800.3.2.1.1.1.13.1.4 |
pnnixPtseChecksumThe value of the PTSE checksum as it appears in the local
topology database.ro Gauge .1.3.6.1.4.1.800.3.2.1.1.1.13.1.5 |
pnnixPtseLifeTimeThe value of the remaining lifetime for the given PTSE as
it appears in the local topology database.ro Gauge -- UNITS "seconds" .1.3.6.1.4.1.800.3.2.1.1.1.13.1.6 |
pnnixPtseInfoAn 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.ro OCTET STRING .1.3.6.1.4.1.800.3.2.1.1.1.13.1.7 |
pnnixMapTableA 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. SEQUENCE OF PnnixMapEntry .1.3.6.1.4.1.800.3.2.1.1.1.14 |
pnnixMapEntryAn 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. PnnixMapEntry .1.3.6.1.4.1.800.3.2.1.1.1.14.1 |
pnnixMapOriginatingNodeIdThe node identifier of the node whose connectivity within
itself or to other nodes is being described. PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.14.1.1 |
pnnixMapOriginatingPortIdThe port identifier of the port as assigned by the
originating node, to which the port is attached. INTEGER -- SYNTAX PnnixPortId .1.3.6.1.4.1.800.3.2.1.1.1.14.1.2 |
pnnixMapIndexAn 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. INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.14.1.3 |
pnnixMapTypeThe type of PNNI entity being described by this entry in
the table.ro Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.14.1.4 |
pnnixMapPeerGroupIdIdentifies the peer group of the originating node.ro PnnixPeerGroupId .1.3.6.1.4.1.800.3.2.1.1.1.14.1.5 |
pnnixMapAggrTokenFor 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.ro PnnixAggrToken .1.3.6.1.4.1.800.3.2.1.1.1.14.1.6 |
pnnixMapRemoteNodeIdFor 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).ro PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.14.1.7 |
pnnixMapRemotePortIdFor 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.ro PnnixPortId .1.3.6.1.4.1.800.3.2.1.1.1.14.1.8 |
pnnixMapVPCapabilityIndicates whether VPCs
can be established across the PNNI entity being described
by this entry in the pnnixMapTable.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.14.1.9 |
pnnixMapPtseIdThe value of the PTSE Identifier for the PTSE being
originated by the originating node which contains the
information group(s) describing the PNNI entity.ro Gauge .1.3.6.1.4.1.800.3.2.1.1.1.14.1.10 |
pnnixMapMetricsTagAn 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.ro PnnixMetricsTag .1.3.6.1.4.1.800.3.2.1.1.1.14.1.11 |
pnnixMapNodeTableA 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. SEQUENCE OF PnnixMapNodeEntry .1.3.6.1.4.1.800.3.2.1.1.1.15 |
pnnixMapNodeEntryAn 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. PnnixMapNodeEntry .1.3.6.1.4.1.800.3.2.1.1.1.15.1 |
pnnixMapNodeIdIdentifies the node whose nodal information is being
described. PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.15.1.1 |
pnnixMapNodePeerGroupIdIdentifies the peer group of the originating node.ro PnnixPeerGroupId .1.3.6.1.4.1.800.3.2.1.1.1.15.1.2 |
pnnixMapNodeAtmAddressThe ATM End System Address of the originating node.ro PnnixAtmAddr .1.3.6.1.4.1.800.3.2.1.1.1.15.1.3 |
pnnixMapNodeRestrictedTransitIndicates 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.15.1.4 |
pnnixMapNodeComplexRepIndicates 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.15.1.5 |
pnnixMapNodeRestrictedBranchingIndicates 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.15.1.6 |
pnnixMapNodeDatabaseOverloadIndicates 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.15.1.7 |
pnnixMapNodeIAmLeaderIndicates 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.15.1.8 |
pnnixMapNodeLeadershipPriorityThe Leadership priority value advertised by the originating
node.ro INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.15.1.9 |
pnnixMapNodePreferredPglIdentifies 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).ro PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.15.1.10 |
pnnixMapNodeParentNodeIdWhen 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).ro PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.15.1.11 |
pnnixMapNodeParentAtmAddressWhen 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).ro PnnixAtmAddr .1.3.6.1.4.1.800.3.2.1.1.1.15.1.12 |
pnnixMapNodeParentPeerGroupIdWhen 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).ro PnnixPeerGroupId .1.3.6.1.4.1.800.3.2.1.1.1.15.1.13 |
pnnixMapNodeParentPglNodeIdWhen 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).ro PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.15.1.14 |
pnnixMapAddrTableThe 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. SEQUENCE OF PnnixMapAddrEntry .1.3.6.1.4.1.800.3.2.1.1.1.16 |
pnnixMapAddrEntryAn 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. PnnixMapAddrEntry .1.3.6.1.4.1.800.3.2.1.1.1.16.1 |
pnnixMapAddrAdvertisingNodeIdThe node ID of a node advertising reachability to the
address prefix. PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.16.1.1 |
pnnixMapAddrAdvertisedPortIdThe port identifier used from the advertising node to reach
the given address prefix. PnnixPortId SYNTAX INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.16.1.2 |
pnnixMapAddrIndexAn arbitrary index that is used to enumerate all of the
addresses advertised by the specified node. INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.16.1.3 |
pnnixMapAddrAddressThe value of the ATM End System Address prefix.ro AtmAddrPrefix .1.3.6.1.4.1.800.3.2.1.1.1.16.1.4 |
pnnixMapAddrPrefixLengthThe Prefix length to be applied to the ATM End System
Address prefix.ro PnnixPrefixLength .1.3.6.1.4.1.800.3.2.1.1.1.16.1.5 |
pnnixMapTnsTableA 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.. SEQUENCE OF PnnixMapTnsEntry .1.3.6.1.4.1.800.3.2.1.1.1.17 |
pnnixMapTnsEntryAn 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. PnnixMapTnsEntry .1.3.6.1.4.1.800.3.2.1.1.1.17.1 |
pnnixMapTnsAdvertisingNodeIdThe node ID of a node advertising reachability to the
transit network. PnnixNodeId SYNTAX INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.17.1.1 |
pnnixMapTnsAdvertisedPortIdThe port identifier used from the advertising node to reach
the given transit network. INTEGER -- SYNTAX PnnixPortId .1.3.6.1.4.1.800.3.2.1.1.1.17.1.2 |
pnnixMapTnsTypeThe type of network identification used for this transit
network. TnsType .1.3.6.1.4.1.800.3.2.1.1.1.17.1.3 |
pnnixMapTnsPlanThe network identification plan according to which network
identification has been assigned. TnsPlan .1.3.6.1.4.1.800.3.2.1.1.1.17.1.4 |
pnnixMapTnsIdThe value of the transit network identifier.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.17.1.5 |
pnnixMetricsTableThis 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. SEQUENCE OF PnnixMetricsEntry .1.3.6.1.4.1.800.3.2.1.1.1.18 |
pnnixMetricsEntryA 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. PnnixMetricsEntry .1.3.6.1.4.1.800.3.2.1.1.1.18.1 |
pnnixMetricsTagAn 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. PnnixMetricsTag .1.3.6.1.4.1.800.3.2.1.1.1.18.1.1 |
pnnixMetricsDirectionThe direction, with respect to the advertising node, in
which the parameters in this entry apply. Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.18.1.2 |
pnnixMetricsIndexAn index into the set of parameters associated with the
given tag and direction. INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.18.1.3 |
pnnixMetricsClassesThe 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.rw INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.18.1.4 |
pnnixMetricsGcacClpIndicates whether the advertised GCAC parameters apply for
CLP=0 traffic or for CLP=0+1 traffic.rw ClpType .1.3.6.1.4.1.800.3.2.1.1.1.18.1.5 |
pnnixMetricsAdminWeightThe 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.18.1.6 |
pnnixMetrics1An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.18.1.7 |
pnnixMetrics2An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.18.1.8 |
pnnixMetrics3An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.18.1.9 |
pnnixMetrics4An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.18.1.10 |
pnnixMetrics5An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.18.1.11 |
pnnixMetrics6An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.18.1.12 |
pnnixMetrics7An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.18.1.13 |
pnnixMetrics8An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.18.1.14 |
pnnixMetricsRowStatusTo create, delete, activate and de-activate a set of
metrics.rw Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.18.1.15 |
pnnixRoutingGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.1.19 |
pnnixRouteBaseGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.1.19.1 |
pnnixRouteNodeNumberThe number of current precalculated PNNI routes to PNNI
nodes that are not invalid.ro Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.1.1 |
pnnixRouteAddrNumberThe number of current PNNI routes from nodes in the PNNI
routing domain to addresses and transit networks that are
not invalid.ro Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.1.2 |
pnnixRouteNodeTableThis entity's PNNI Routing table (of routes to other
nodes). SEQUENCE OF PnnixRouteNodeEntry .1.3.6.1.4.1.800.3.2.1.1.1.19.2 |
pnnixRouteNodeEntryA particular route to a particular destination node, under
a particular policy. PnnixRouteNodeEntry .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1 |
pnnixRouteNodeClassIndicates the service category with which this forwarding
table entry is associated. ServiceCategory .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.1 |
pnnixRouteNodeDestNodeIdThe node ID of the destination node to which this route
proceeds, and at which the DTL stack for this route
terminates. PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.2 |
pnnixRouteNodeDTLThe index into the owning PNNI node's DTL table of the DTL
stack that goes with this route. INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.3 |
pnnixRouteNodeDestPortIdThe 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.rw PnnixPortId .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.4 |
pnnixRouteNodeProtoThe routing mechanism via which this route was learned.ro Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.5 |
pnnixRouteNodeTimeStampThe 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.6 |
pnnixRouteNodeInfoA 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 }.rw OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.7 |
pnnixRouteNodeGcacClpFor PNNI, indicates whether any advertised GCAC parameters
apply for CLP=0 traffic or for CLP=0+1 traffic.rw ClpType .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.8 |
pnnixRouteNodeFwdMetricAWThe cumulative administrative weight calculated for the
forward direction of this route. If this metric is not
used, its value should be set to 0xFFFFFFFF.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.9 |
pnnixRouteNodeFwdMetric1An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.10 |
pnnixRouteNodeFwdMetric2An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.11 |
pnnixRouteNodeFwdMetric3An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.12 |
pnnixRouteNodeFwdMetric4An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.13 |
pnnixRouteNodeFwdMetric5An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.14 |
pnnixRouteNodeFwdMetric6An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.15 |
pnnixRouteNodeFwdMetric7An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.16 |
pnnixRouteNodeFwdMetric8An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.17 |
pnnixRouteNodeBwdMetricAWThe administrative weight calculated for the backward
direction of this route. If this metric is not used, its
value should be set to 0xFFFFFFFF.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.18 |
pnnixRouteNodeBwdMetric1An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.19 |
pnnixRouteNodeBwdMetric2An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.20 |
pnnixRouteNodeBwdMetric3An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.21 |
pnnixRouteNodeBwdMetric4An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.22 |
pnnixRouteNodeBwdMetric5An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.23 |
pnnixRouteNodeBwdMetric6An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.24 |
pnnixRouteNodeBwdMetric7An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.25 |
pnnixRouteNodeBwdMetric8An 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.rw Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.26 |
pnnixRouteNodeVPCapabilityThis attribute indicates whether a VPC setup on this route
is possible.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.27 |
pnnixRouteNodeStatusThe row status variable, used according to row installation
and removal conventions.rw Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.19.2.1.28 |
pnnixDTLTableThe set of all DTL stacks used for the pre-computed routes
maintained by this managed entity. SEQUENCE OF PnnixDTLEntry .1.3.6.1.4.1.800.3.2.1.1.1.19.3 |
pnnixDTLEntryA 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. PnnixDTLEntry .1.3.6.1.4.1.800.3.2.1.1.1.19.3.1 |
pnnixDTLIndexThe index in the node's DTL table of this DTL stack. INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.19.3.1.1 |
pnnixDTLEntryIndexThe index in the current DTL stack of this entry. INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.19.3.1.2 |
pnnixDTLNodeIdThe node which is this hop in the DTL stack.rw PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.19.3.1.3 |
pnnixDTLPortIdThe port from the pnnixDTLNodeId to use as the exit. If the
DTL stack does not care, this is coded as zero.rw PnnixPortId .1.3.6.1.4.1.800.3.2.1.1.1.19.3.1.4 |
pnnixDTLLinkTypeThe type of link out from this node (pnnixDTLNodeId). This
is well defined even if the specific port is not
specified.rw Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.19.3.1.5 |
pnnixDTLStatusThe row status variable, used according to row installation
and removal conventions.rw Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.19.3.1.6 |
pnnixRouteAddrTableA 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.. SEQUENCE OF PnnixRouteAddrEntry .1.3.6.1.4.1.800.3.2.1.1.1.19.4 |
pnnixRouteAddrEntryAn entry in the table, containing information about a
reachable address prefix. PnnixRouteAddrEntry .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1 |
pnnixRouteAddrAddressThe value of the ATM End System Address prefix. AtmAddrPrefix .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.1 |
pnnixRouteAddrPrefixLengthThe prefix length to be applied to the ATM End System
Address prefix. PnnixPrefixLength .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.2 |
pnnixRouteAddrIndexAn 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. INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.3 |
pnnixRouteAddrIfIndexThe 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.rw InterfaceIndex .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.4 |
pnnixRouteAddrAdvertisingNodeIdThe 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.rw PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.5 |
pnnixRouteAddrAdvertisedPortIdThe port identifier used from the advertising node to reach
the given address prefix.rw PnnixPortId .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.6 |
pnnixRouteAddrTypeThe 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.rw Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.7 |
pnnixRouteAddrProtoThe routing mechanism via which the connectivity from the
advertising node to the reachable address prefix was
learned.ro Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.8 |
pnnixRouteAddrPnniScopeThe PNNIX scope of advertisement (i.e. level of PNNI
hierarchy) of the reachability from the advertising node to
the address prefix.rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.9 |
pnnixRouteAddrVPCapabilityIndicates whether VPCs can be established from the
advertising node to the reachable address prefix.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.10 |
pnnixRouteAddrMetricsTagThe 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.rw PnnixMetricsTag .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.11 |
pnnixRouteAddrPtseIdFor 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.ro Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.12 |
pnnixRouteAddrOriginateAdvertisementWhether 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'.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.13 |
pnnixRouteAddrInfoA 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 }.rw OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.14 |
pnnixRouteAddrOperStatusIndicates whether the reachable address prefix is
operationally valid and whether it is being advertised by
this node.ro Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.15 |
pnnixRouteAddrTimeStampIndicates when the connectivity from the advertising node
to the reachable address prefix became known to the local
node.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.16 |
pnnixRouteAddrRowStatusTo create, delete, activate and de-activate a reachable
address prefix.rw Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.19.4.1.17 |
pnnixRouteTnsTableA 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. SEQUENCE OF PnnixRouteTnsEntry .1.3.6.1.4.1.800.3.2.1.1.1.19.5 |
pnnixRouteTnsEntryAn entry in the table, containing information about a
reachable transit network. PnnixRouteTnsEntry .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1 |
pnnixRouteTnsTypeThe type of network identification used for this transit
network. TnsType .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.1 |
pnnixRouteTnsPlanThe network identification plan according to which network
identification has been assigned. TnsPlan .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.2 |
pnnixRouteTnsIdThe value of the transit network identifier. DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.3 |
pnnixRouteTnsIndexAn 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. INTEGER .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.4 |
pnnixRouteTnsIfIndexThe 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.rw InterfaceIndex .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.5 |
pnnixRouteTnsAdvertisingNodeIdThe 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.rw PnnixNodeId .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.6 |
pnnixRouteTnsAdvertisedPortIdThe port identifier used from the advertising node to
reach the given transit network.rw PnnixPortId .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.7 |
pnnixRouteTnsRouteTypeThe type (e.g. exterior or other) of reachability from the
advertising node to the transit network.rw Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.8 |
pnnixRouteTnsProtoThe routing mechanism via which the connectivity from the
advertising node to the transit network was learned.ro Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.9 |
pnnixRouteTnsPnniScopeThe PNNI scope of advertisement (i.e. level of PNNI
hierarchy) of the reachability from the advertising node to
the transit network.rw PnnixLevel .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.10 |
pnnixRouteTnsVPCapabilityIndicates whether VPCs can be established from the
advertising node to the reachable transit network.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.11 |
pnnixRouteTnsMetricsTagThe 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.rw PnnixMetricsTag .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.12 |
pnnixRouteTnsPtseIdFor 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.ro Gauge .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.13 |
pnnixRouteTnsOriginateAdvertisementWhether 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'.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.14 |
pnnixRouteTnsInfoA 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 }.rw OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.15 |
pnnixRouteTnsOperStatusIndicates whether the reachable transit network is
operationally valid and whether it is being advertised by
this node.ro Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.16 |
pnnixRouteTnsTimeStampIndicates how long the connectivity from the advertising
node to the reachable transit network has been known to the
local node.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.17 |
pnnixRouteTnsRowStatusTo create, delete, activate and de-activate a reachable
transit network.rw Enumeration .1.3.6.1.4.1.800.3.2.1.1.1.19.5.1.18 |
pnnixMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2 |
pnnixMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.1 |
pnnixMIBCompliance OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.1.1 |
pnnixMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2 |
pnnixGeneralMinGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.1 |
pnnixGeneralBorderGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.2 |
pnnixNodeMinGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.3 |
pnnixNodePglMinGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.4 |
pnnixNodePglLgnGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.5 |
pnnixNodeTimerMinGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.6 |
pnnixNodeTimerLgnGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.7 |
pnnixNodeSvccLgnGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.8 |
pnnixScopeMinGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.9 |
pnnixSummaryLgnGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.10 |
pnnixIfMinGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.11 |
pnnixIfBorderGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.12 |
pnnixLinkMinGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.13 |
pnnixLinkBorderOrLgnGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.14 |
pnnixLinkLgnGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.15 |
pnnixNbrPeerMinGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.16 |
pnnixNbrPeerLgnGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.17 |
pnnixNbrPeerPortMinGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.18 |
pnnixSvccRccLgnGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.19 |
pnnixPtseOptionalGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.20 |
pnnixMapOptionalGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.21 |
pnnixMapNodeOptionalGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.22 |
pnnixMapAddrOptionalGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.23 |
pnnixMapTnsOptionalGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.24 |
pnnixMetricsOptionalGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.25 |
pnnixRouteGeneralOptionalGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.26 |
pnnixRouteNodeOptionalGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.27 |
pnnixDTLOptionalGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.28 |
pnnixRouteAddrOptionalGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.29 |
pnnixRouteTnsOptionalGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.2.2.30 |
pnniIAdjMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.3 |
pnnixIAdjGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.3.1 |
pnnixNumIAdjThe number of adjacencies registered via ILMI in PNNIs
lowest nodes adjacency table in this switching system.ro Counter .1.3.6.1.4.1.800.3.2.1.1.3.1.1 |
pnnixIAdjTableThe 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. SEQUENCE OF PnnixIAdjEntry .1.3.6.1.4.1.800.3.2.1.1.3.1.2 |
pnnixIAdjEntryAn entry in the table, containing information about a PNNI
logical node in this switching system. PnnixIAdjEntry .1.3.6.1.4.1.800.3.2.1.1.3.1.2.1 |
pnnixIadjIndexA value assigned to an ILMI client registered via ILMI in this
switching system that uniquely identifies it in the PNNI ILMI
adjacency table. INTEGER .1.3.6.1.4.1.800.3.2.1.1.3.1.2.1.1 |
pnnixIAdjAtmAddressThis adjacency's ATM End System Address.ro PnnixAtmAddr .1.3.6.1.4.1.800.3.2.1.1.3.1.2.1.2 |
pnnixIAdjSlotThe slot in which this adjacency is physically connected to this
switching system.ro INTEGER .1.3.6.1.4.1.800.3.2.1.1.3.1.2.1.3 |
pnnixIAdjPortThe port in the slot which this adjacency is physically
connected to this switching system.ro INTEGER .1.3.6.1.4.1.800.3.2.1.1.3.1.2.1.4 |
pnnixIAdjInstThe 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.ro INTEGER .1.3.6.1.4.1.800.3.2.1.1.3.1.2.1.5 |
pnnixIAdjCsmPPortThe unique port id which PNNI has bound to this physical slot,
port, and instance tuple.ro INTEGER .1.3.6.1.4.1.800.3.2.1.1.3.1.2.1.6 |
pnnixIAdjAdvertisedIndicates 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).ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.3.1.2.1.7 |
pnnixIAdjSummarizedIndicates 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.3.1.2.1.8 |
pnnixIAdjLearnedThis field contains a timestamp of when ILMI registered this
adjacency with PNNI.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.800.3.2.1.1.3.1.2.1.9 |
pnniTestMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.4 |
pnniRtstMIBGroup OBJECT IDENTIFIER .1.3.6.1.4.1.800.3.2.1.1.4.1 |
pnnixRtstTableThe 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. SEQUENCE OF PnnixRtstEntry .1.3.6.1.4.1.800.3.2.1.1.4.1.1 |
pnnixRtstEntryAn entry in the route test table, containing information
about a route lookup request. PnnixRtstEntry .1.3.6.1.4.1.800.3.2.1.1.4.1.1.1 |
pnnixRtstClassThe class the route request is to use. Enumeration .1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.1 |
pnnixRtstTypeThis index specifies the type of call which may be either point
to point or point to multi-point. Enumeration .1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.2 |
pnnixRtstDestThe destination address. This may be specified by the user
as an address prefix, but the snmp manager must pad this
out to 20 octets. OCTET STRING .1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.3 |
pnnixRtstErrorIndicates 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.ro Enumeration .1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.4 |
pnnixRtstFlagsIf 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.ro Enumeration .1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.5 |
pnnixRtstOutboundPortIf 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.ro PnnixPortId .1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.6 |
pnnixRtstVPIIf 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.ro INTEGER .1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.7 |
pnnixRtstE164If 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.ro OCTET STRING .1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.8 |
pnnixRtstE164lenIf 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.ro INTEGER .1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.9 |
pnnixRtstHopCountIf error is set to success, and pnnixRtstFlags is set to
dtlAdded, then this indicates the number of hops in the
pnnixRtstDTL.ro INTEGER .1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.10 |
pnnixRtstDTLIf 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.ro OCTET STRING .1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.11 |
pnnixRtstCurPointerIf error is set to success, and pnnixRtstFlags is set to
dtlAdded, then this indicates the offset (in bytes) into
pnnixRtstDTL of the curPtr.ro INTEGER .1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.12 |