Home/Catalog/XYLANPNNI-MIB

XYLANPNNI-MIB

AI MIB Summary

The XYLANPNNI-MIB extends the ATM Forum's PNNI MIB to monitor Xylan ATM switch performance metrics, specifically providing visibility into Private Network-to-Network Interface (PNNI) topology states, routing database synchronization, and peer link status for Xylan network elements.

This MIB specifies additional Xylan functionality to the ATM Forum's PNNI MIB.
Main OID:
xylanPnniMIB.1.3.6.1.4.1.800.3.2.1.2
98
Objects
Active
Status
6
Dependencies

Imported Objects

Objects

98 total
Object Name
xylanPnniMIBThis MIB specifies additional Xylan functionality to the ATM Forum's PNNI MIB.
MODULE-IDENTITY
.1.3.6.1.4.1.800.3.2.1.2
SNMPv2-SMIThis MIB specifies additional Xylan functionality to the ATM Forum's PNNI MIB.
Unknown
.1.3.6.1.4.1.800.3.2.1.2
xylanPnniMIBExtens
OBJECT IDENTIFIER
.1.3.6.1.4.1.800.3.2.1.2.1
xylanPnniMIBObjs
OBJECT IDENTIFIER
.1.3.6.1.4.1.800.3.2.1.2.1.1
xPnniAssociativeNameTableThe xPnniAssociativeNameTable contains attributes that bind node names to PNNI Node IDs. There is a single row in this table for each PNNI node in the network. Default names are node1, node2, ... until the administrator specifically configures a different name.
SEQUENCE OF XPnniNameEntry
.1.3.6.1.4.1.800.3.2.1.2.1.1.1
xPnniNameEntryAn entry in the table, containing information about a PNNI node in this network.
XPnniNameEntry
.1.3.6.1.4.1.800.3.2.1.2.1.1.1.1
xPnniNodeIndexThe index into the associative name table. This index also corresponds to entries in the nodal map table.rw
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.1.1.1
xPnniNodeIdThe value of the 22-byte node ID which a switching system uses to represent itself in the peer-group.rw
XPnniNodeId
.1.3.6.1.4.1.800.3.2.1.2.1.1.1.1.2
xPnniNodeNameThe ASCII text string which represents this node. The default node name has the value NODE_n where n is 1..65535.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.800.3.2.1.2.1.1.1.1.3
xPnniAddressFilterTableThe xPnniAddressFilterTable contains attributes that allow an administrator to configure address filters for security. Address filters are specified by the following: the LGN to which the filter applies; their direction (in, out or both); their addresses (src, dest or both specified as an nsap prefix from 2 to 152 bits); their call type (PTOP, PMP, or both); their service class (CBR, ABR or RtVBR); their metric constraints (CBR - metric is PCR threshold, ABR - the metric is Min CR, and RtVBR - the metric threshold is either PCR, SCR, or Max Burst); their metric threshold; their trap threshold; any exceptions (all/no addresses pass except...) and the corresponding exception prefix (from 2-152 bits); and start/stop Time Of Day values: There is a single row in this table for each PNNI filter in this switching system.
SEQUENCE OF XPnniAddressFilterEntry
.1.3.6.1.4.1.800.3.2.1.2.1.1.2
xPnniAddressFilterEntryAn entry in the table, containing information about a filter in this switching system.
XPnniAddressFilterEntry
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1
xPnniFiltIndexThe index into the PNNI Filter Table.rw
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.1
xPnniFiltNodeLevelThe level of the node within this switching system. Note that filters may be defined for any level. If a node at a specific level is disabled, then corresponding filters become inactive until the node is re-enabled.rw
XPnniNodeLevel
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.2
xPnniFiltSrcPrefLenThe length (in bits) of the source prefix.rw
XPnniFilterPrefixLength
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.3
xPnniFiltSrcPrefixThe source prefix to be filtered.rw
XPnniAddrPrefix
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.4
xPnniFiltDestPrefLenThe length (in bits) of the destination prefix.rw
XPnniFilterPrefixLength
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.5
xPnniFiltDestPrefixThe destination prefix to be filtered.rw
XPnniAddrPrefix
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.6
xPnniFiltCallTypeThe call type indicates if the filter is to be applied to point to point calls, point to multi-point calls (add parties), or to both.rw
XPnniFiltCallType
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.7
xPnniFiltCallSrvClsThe service class (if any) which this filter is active for. If the service class is CBR, then the xPnniFiltCallMtrcConstrnt field below must be set to PCR. If the service class is ABR, then the xPnniFiltCallMtrcConstrnt field below must be set to Min-CR. If the service class is RtVbr, then the xPnniFiltCallMtrcConstrnt field below must be set to either PCR, SCR or Max-burst. Any of the three previous values for xPnniFiltCallSrvCls (CBR, ABR and RtVbr) should result in a non-zero xPnniFiltCallMtrcThresh below. Finally, if the service class is set to none-specified, then the fields xPnniFiltCallMtrcConstrnt and xPnniFiltCallMtrcThresh are ignored.rw
XPnniFiltServiceCategory
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.8
xPnniFiltCallMtrcConstrntA metric constraint that is used with xPnniFiltCallSrvCls.rw
XPnniFiltMetricConstraint
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.9
xPnniFiltCallMtrcThreshA metric threshold value that is used with xPnniFiltCallSrvCls. The value 0 is only valid if the xPnniFiltCallSrvCls is none-specified.rw
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.10
xPnniFiltTrapThreshA threshold which when this number of filter hits are encountered, will cause a trap to be sent to all trap-clients. The value of 0 causes traps to be inhibited.rw
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.11
xPnniFiltSrcExceptionCriteriaThe criteria used to cause exceptions to the source address filters. If the value is none-specified, then the fields: xPnniFiltSrcExceptionLen and xPnniFiltSrcException are ignored. If this value is all-addrs-pass-except or no-addrs-pass-except, then the xPnniFiltSrcExceptionLen and xPnniFiltSrcException attributes contain the source prefix len and prefix which are to be exception handled. This value cannot be set to all-addrs-pass-except or no-addrs-pass-except if the xPnniFiltSrcPrefLen (above) is set to 0.rw
XPnniFiltExceptionCriteria
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.12
xPnniFiltSrcExceptionLenThe length (in bits) of the exception address prefix attribute: xPnniFiltSrcException.rw
XPnniFilterPrefixLength
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.13
xPnniFiltSrcExceptionThe ATM Address Prefix of the source address exception.rw
XPnniAddrPrefix
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.14
xPnniFiltDestExceptionCriteriaThe criteria used to cause exceptions to the destination address filters. If the value is none-specified, then the fields: xPnniFiltDestExceptionLen and xPnniFiltDestException are ignored. If this value is all-addrs-pass-except or no-addrs-pass-except, then the xPnniFiltDestExceptionLen and xPnniFiltDestException attributes contain the destination prefix len and prefix which are to be exception handled. This value cannot be set to all-addrs-pass-except or no-addrs-pass-except if the xPnniFiltDestPrefLen (above) is set to 0.rw
XPnniFiltExceptionCriteria
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.15
xPnniFiltDestExceptionLenThe length (in bits) of the exception address prefix attribute: xPnniFiltDestException.rw
XPnniFilterPrefixLength
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.16
xPnniFiltDestExceptionThe ATM Address Prefix of the destination address exception.rw
XPnniAddrPrefix
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.17
xPnniFiltDeniedHitCountA counter specifying how many times this filter was activated. Writing a 0 value to this field will cause this counter to be reset for this filter.rw
Counter
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.18
xPnniFiltExceptionHitCountA counter specifying how many times this filter was activated but an exception was permitted. Writing a 0 value to this field will cause this counter to be reset for this filter.rw
Counter
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.19
xPnniFiltTODStartHrThe hour of the day (using a 24 hour clock) when the filter is to be activated.rw
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.20
xPnniFiltTODStartMinThe minute of the hour when the filter is to be activated.rw
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.21
xPnniFiltTODStartSecThe second of the minute when the filter is to be activated.rw
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.22
xPnniFiltTODStopHrThe hour of the day (using a 24 hour clock) when the filter is to be de-activated.rw
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.23
xPnniFiltTODStopMinThe minute of the hour when the filter is to be de-activated.rw
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.24
xPnniFiltTODStopSecThe second of the minute when the filter is to be de-activated.rw
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.2.1.25
xPnniIAdjMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.800.3.2.1.2.1.1.3
xPnniIAdjGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.800.3.2.1.2.1.1.3.1
xPnniNumIAdjThe 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.2.1.1.3.1.1
xPnniIAdjTableThe xPnniIAdjTable stores records of adjacencies 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 XPnniIAdjEntry
.1.3.6.1.4.1.800.3.2.1.2.1.1.3.1.2
xPnniIAdjEntryAn entry in the table, containing information about a PNNI logical node in this switching system.
XPnniIAdjEntry
.1.3.6.1.4.1.800.3.2.1.2.1.1.3.1.2.1
xPnniIAdjIndexA 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.2.1.1.3.1.2.1.1
xPnniIAdjAtmAddressThis adjacency's ATM End System Address.ro
XPnniAtmAddr
.1.3.6.1.4.1.800.3.2.1.2.1.1.3.1.2.1.2
xPnniIAdjSlotThe slot in which this adjacency is physically connected to this switching system.ro
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.3.1.2.1.3
xPnniIAdjPortThe 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.2.1.1.3.1.2.1.4
xPnniIAdjInstThe 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.2.1.1.3.1.2.1.5
xPnniIAdjCsmPPortThe 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.2.1.1.3.1.2.1.6
xPnniIAdjAdvertisedIndicates 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 xPnniIAdjSummarized is set to True (below).ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.800.3.2.1.2.1.1.3.1.2.1.7
xPnniIAdjSummarizedIndicates 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 xPnniIAdjCsmPPort.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.800.3.2.1.2.1.1.3.1.2.1.8
xPnniIAdjLearnedThis 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.2.1.1.3.1.2.1.9
xPnniTestMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.800.3.2.1.2.1.1.4
xPnniRtstMIBGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.1
xPnniRtstTableThe xPnniRtstTable 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 XPnniRtstEntry
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.1.1
xPnniRtstEntryAn entry in the route test table, containing information about a route lookup request.
XPnniRtstEntry
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.1.1.1
xPnniRtstClassThe class the route request is to use.
Enumeration
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.1.1.1.1
xPnniRtstTypeThis 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.2.1.1.4.1.1.1.2
xPnniRtstDestThe 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.2.1.1.4.1.1.1.3
xPnniRtstErrorIndicates 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.2.1.1.4.1.1.1.4
xPnniRtstFlagsIf 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 xPnniRtstOutboundPort, xPnniRtstHopCount, xPnniRtstDTL, and xPnniRtstCurPointer 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 xPnniRtstOutboundPort 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 xPnniNodeIndex) returned a successful match of myself as the destination. In this case, the xPnniRtstOutboundPort 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 xPnniRtstOutboundPort 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 xPnniRtstVPI and xPnniRtstE164 fields will also be present.ro
Enumeration
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.1.1.1.5
xPnniRtstOutboundPortIf 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 xPnniNodeIndex. 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
XPnniPortId
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.1.1.1.6
xPnniRtstVPIIf error is set to success, and xPnniRtstFlags 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.2.1.1.4.1.1.1.7
xPnniRtstE164If error is set to success, and xPnniRtstFlags 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.2.1.1.4.1.1.1.8
xPnniRtstE164lenIf error is set to success, and xPnniRtstFlags 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.2.1.1.4.1.1.1.9
xPnniRtstHopCountIf error is set to success, and xPnniRtstFlags is set to dtlAdded, then this indicates the number of hops in the xPnniRtstDTL.ro
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.1.1.1.10
xPnniRtstDTLIf error is set to success, and xPnniRtstFlags 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.2.1.1.4.1.1.1.11
xPnniRtstCurPointerIf error is set to success, and xPnniRtstFlags is set to dtlAdded, then this indicates the offset (in bytes) into xPnniRtstDTL of the curPtr.ro
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.1.1.1.12
xPnniTrcMIBGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2
xPnniTrcBufSizA value indicating the size of the trace capture buffer.rw
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.1
xPnniTrcBufTriggerA value indicating action on buffer capacity reached.rw
Enumeration
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.2
xPnniTrcBufControlA value indicating a control action on trace.rw
Enumeration
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.3
xPnniTrcNodeIndexThis variable indicates the node index within this switching system to be traced.rw
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.4
xPnniTrcTableThe xPnniITrcTable stores records of captured frames from both the AAL-SAP as well as signalled RCCs. There is a single row in this table for each adjacency which ILMI has registered.
SEQUENCE OF XPnniTrcEntry
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.5
xPnniTrcEntryAn entry in the analyzer table, containing information about a PNNI received by a node in this switching system.
XPnniTrcEntry
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.5.1
xPnniTrcFrameIndexAn index selecting a particular frame.ro
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.5.1.1
xPnniTrcFrameFragA fragment within a captured frame.ro
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.5.1.2
xPnniTrcDirectionIndicates whether the frame was transmitted or received.ro
Enumeration
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.5.1.3
xPnniTrcSlotIndicates the physical slot where the frame was transmitted or received.ro
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.5.1.4
xPnniTrcPortIndicates the physical port where the frame was transmitted or received.ro
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.5.1.5
xPnniTrcCsmPPortIndicates the advertised PNNI port ID where the frame was transmitted or received. This is used primarily for signaled RCCs.ro
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.5.1.6
xPnniTrcFrTypeIndicates the type of frame as specified in the ATM-Forum PNNI V1.0 Specification, Section 5.14.4, Table 5-21.ro
Enumeration
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.5.1.7
xPnniTrcFrLenIndicates the overall frame length.ro
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.5.1.8
xPnniTrcLearnedIndicates the timestamp of when the frame was either transmitted or received.ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.5.1.9
xPnniTrcFrameContains the raw frame contents.ro
OCTET STRING
.1.3.6.1.4.1.800.3.2.1.2.1.1.4.2.5.1.10
xPnniAliasTableThis table stores address (prefix) bindings for Display purposes.
SEQUENCE OF XPnniAliasEntry
.1.3.6.1.4.1.800.3.2.1.2.1.1.5
xPnniAliasEntryAn entry in the alias table containing information about a binding between PNNI address, nodeId or address prefix and a text string. When referring to a nodeId, this is called a domain name.
XPnniAliasEntry
.1.3.6.1.4.1.800.3.2.1.2.1.1.5.1
xPnniAliasIndexAn index selecting a particular name-binding.rw
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.5.1.1
xPnniAliasNameThe name to be bound to the prefix.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.800.3.2.1.2.1.1.5.1.2
xPnniAliasPrefLenAn length (in bits) of the prefix binding. A Prefix length of 176 bits (22 Octets) implies a node ID. A length of 160 bits implies an ATM Address.rw
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.5.1.3
xPnniAliasPrefixBindingThe prefix binding.rw
OCTET STRING
.1.3.6.1.4.1.800.3.2.1.2.1.1.5.1.4
xPnniTrapMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.800.3.2.1.2.1.1.6
xPnniTrapPnPortIdOn a trap condition, this identifies the port-related variable.ro
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.6.1
xPnniTrapRouteAddrAddressOn a trap condition, this identifies the address prefix-related variable.ro
XPnniAddrPrefix
.1.3.6.1.4.1.800.3.2.1.2.1.1.6.2
xPnniTrapRouteAddrPrefixLengthOn a trap condition, this identifies the address prefix length related variable.ro
XPnniFilterPrefixLength
.1.3.6.1.4.1.800.3.2.1.2.1.1.6.3
xPnniTrapFiltIndexOn a trap condition, this identifies the filter index variable.ro
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.6.4
xPnniTrapNeighborIdOn a Neighbor trap condition, this identifies the neighbor node Id-related variable.ro
XPnniNodeId
.1.3.6.1.4.1.800.3.2.1.2.1.1.6.5
xPnniTrapNodeIdOn a trap condition, this identifies the local node ID variable which specifies the level and LGN or lowest level node.ro
XPnniNodeId
.1.3.6.1.4.1.800.3.2.1.2.1.1.6.6
xPnniTrapNodeDownReasonOn a trap condition, this identifies the reason a node has gone down. A value of LocalUiAdmin specifies that a user on the MPM's Console or Modem Port has caused the action via a UI Shell:phalt command. A value of RemoteTelnet indicates that a user logged in remotely has caused the action via a UI Shell:phalt command. A value of Mgmt indicates that a remote SNMP management entity Has caused the action via a (re)configuration of the PNNI Node Table.ro
Enumeration
.1.3.6.1.4.1.800.3.2.1.2.1.1.6.7
xPnniTrapNodeDownRemoteIPAddrIf the above variable: xPnniTrapNodeDownReason indicates a value of either RemoteTelnet or then this variable indicates the remote IP Address of the entity causing the action.ro
INTEGER
.1.3.6.1.4.1.800.3.2.1.2.1.1.6.8
XYLANPNNI-MIB - SNMP MIB Reference | MIBs Explorer