MPC-MIB
AI MIB Summary
The MPC-MIB facilitates the monitoring and management of Multiprotocol Over ATM (MPOA) clients and servers, specifically tracking Multiprotocol Switching (MPS) entities and their associated MAC address mappings via the `mpcMpsMultipleMacAddressTable`. This module enables the observation of MPOA session states and forwarding information for legacy ATM-based multiprotocol networks.
This module defines a portion of the management information base (MIB) for managing Multiprotocol Over ATM clients and servers which was revised based on MPOA Errata contained in MPOA v1.1.
The difference between af-mpoa-0092.000 and this version is the mpcMpsMacAddressTable has been obsoleted. The mpcMpsMultipleMacAddressTable has been added. The mpcMpsMultipleMacAddressTable replaces the mpcMpsMacAddressTable.
Main OID:
mpoaMIB.1.3.6.1.4.1.353.5.8.1
102
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
102 total| Object Name |
|---|
atmForum OBJECT IDENTIFIER .1.3.6.1.4.1.353 |
atmForumNetworkManagement OBJECT IDENTIFIER .1.3.6.1.4.1.353.5 |
atmfMpoa OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8 |
mpoaMIBThis module defines a portion of the management
information base (MIB) for managing Multiprotocol Over
ATM clients and servers which was revised based
on MPOA Errata contained in MPOA v1.1.
The difference between af-mpoa-0092.000 and this
version is the mpcMpsMacAddressTable has been
obsoleted. The mpcMpsMultipleMacAddressTable
has been added. The mpcMpsMultipleMacAddressTable
replaces the mpcMpsMacAddressTable. MODULE-IDENTITY .1.3.6.1.4.1.353.5.8.1 |
mpoaMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.1 |
mpoaCommonObjects OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.1.1 |
mpcObjects OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.1.2 |
mpcNextIndexThis object contains an appropriate value to
be used for mpcIndex when creating entries in
the mpcConfigTable. The value 0 indicates that
no new rows can be created. Otherwise, it is
recommended that values are assigned contiguously,
starting from 1.
MPC creation by a Manager: To obtain the mpcIndex value
for a new entry, the manager issues a management protocol
retrieval operation to obtain the current value of this
object. If the value retrieved is 0 (zero), the manager
cannot create a row.
After each retrieval of a non-zero value, the manager
should issue a management protocol SET operation using
the value just retrieved. If the SET is successful,
the agent should update the value to the next unassigned
index, or zero if appropriate.
NOTE: the manager may also issue a set on this object
with a value of its own choosing. If the set is successful,
the manager may use this value for the mpcIndex. In this
case, the agent would update the value to the next
unassigned index, or zero if appropriate.
The definition of `next unassigned index' is any
mpcNextIndex value that has not yet been set by a manager,
or reserved by the agent (see next paragraph), since this
agent was last re-initialized.
MPC creation by an Agent: When a row in the
mpcConfigTable is created by an agent, the agent should
reserve the value of the index by updating the value of
this object to the next unassigned index
or zero if appropriate. Thus, a manager will not
be able to set an index reserved by an agent.
In the situation of an agent re-initialization, all currently
used mpcIndexes must be preserved.
In other words, the Agent should store in non-volatile memory
all of the currently used mpcIndexes (along with all necessary
configuration information from the mpcConfigTable). When the
agent is re-initialized, the mpcNextIndex value is
any valid Integer32 value which is not being used
as an mpcIndex, except 0 which maintains its original
definition of indicating that a row cannot be created.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.1 |
mpcConfigTableThe MPOA Client Configuration Table.
This table contains configuration information
for all MPOA Clients which this agent manages. SEQUENCE OF MpcConfigEntry .1.3.6.1.4.1.353.5.8.1.1.2.2 |
mpcConfigEntryMPOA Client Configuration Entry.
Each entry contains configuration information
for one MPOA Client. The configuration information, including
the mpcIndex, must be restored after a re-initialization of an
MPC or a re-initialization of the SNMP agent. MpcConfigEntry .1.3.6.1.4.1.353.5.8.1.1.2.2.1 |
mpcIndexA value which uniquely identifies this conceptual
row in the mpcConfigTable. The `mpcNextIndex' object
needs to be used to determine the value of this object.
A row cannot be added, unless the mpcCtrlAtmAddress is unique.
In the event of either an MPC re-initialization or an agent
re-initialization, the value of this mpcIndex must remain the
same. In other words, the row needs to be saved and restored
in the event of an MPC or SNMP Agent re-initialization. MpcIndex .1.3.6.1.4.1.353.5.8.1.1.2.2.1.1 |
mpcRowStatusThis object allows creation and deletion of
MPOA Clients.
Within each conceptual mpcConfigTable row, writable objects
may be modified, regardless of the value of mpcRowStatus.
It is not necessary to set a row's status to `notInService'
first.
A row cannot be created, unless the mpcAtmCtrlAddress
in this table is unique.
When an MPOA Client is created via this object,
it will initially have
`mpcActualState' = `initialState'rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.2.1.2 |
mpcConfigModeIndicates whether this MPC should auto-configure
the next time it is (re-)initialized.
During the (re-)initialization of this MPC, if
the mode is automatic(1), the LECS is contacted and
requests are made for all MPC-p* parameters.
Otherwise, if the mode is manual(2), the values of the
configuration parameters are obtained from the
mpcConfigTableand the mpcProtocolTable. In other words, when
the MPC is first initialized, it can use the default or
configured values from the mpcConfigTable and
mpcProtocolTable. If the mode is manual (2), no further
action is required. If the mode is automatic (1), then
the LECS should be contacted and all available MPC-p1
to MPC-p6 parameters would be retrieved.
These parameters would then overwrite the existing MPC-p1 to
MPC-p6 parameters. The actual values are reflected in the
mpcActualTable.rw Enumeration .1.3.6.1.4.1.353.5.8.1.1.2.2.1.3 |
mpcCtrlAtmAddrThe MPC's Control ATM Address. There exists one
Control ATM Address per MPC, therefore, the value
of this entry is unique within the table. The control ATM
Address is the address which is used by the MPC in its requests
to the MPS. The value of this object should not change, once
created.rw AtmConfigAddr .1.3.6.1.4.1.353.5.8.1.1.2.2.1.4 |
mpcSCSetupFrameCountThis represents the MPC-p1 Short-cut setup frame count
parameter.
The MPC-p1 value is frames measured over mpcSCFrameTime seconds.
Flow detection is protocol independent. i.e. all network layers
mpcProtocolEntries for this MPC share the flow rate
specification.
A value of 1 causes all flows to initiate resolution/shortcut
process.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.2.1.5 |
mpcSCSetupFrameTimeMPC-p2 Short-cut setup frame time, in seconds.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.2.1.6 |
mpcInitialRetryTimeMPC-p4 is the initial value for the retry time out
period used for timing out MPOA Resolution Requests
in seconds. Retry time consists of this initial
time-out (MPC-p4) and a retry multiplier (MPC-c1).
If a response is not received, then another request
is sent with a timeout of `retry time' * MPC-c1
seconds, or until mpcRetryTimeMaximum.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.2.1.7 |
mpcRetryTimeMaximumMPC-p5 cumulative max value for Retry Time (MPC-p4).
Retries are attempted at intervals determined by the
algorithm described in the definition of mpcIntialRetryTime.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.2.1.8 |
mpcHoldDownTimeMPC-p6 Hold Down Time
Minimum time to wait before reinitiating
a failed resolution attempt. Default is
mpcRetryTimeMaximum * 4.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.2.1.9 |
mpcActualTableMPOA Client Actual Table.
A read-only table which contains state
information and reflects the actual values which
these MPOA Clients are using. The actual
values may differ from the configured values.
For example, the mpcConfigMode takes affect
only during (re-)initialization of the MPC.
The MPC-p1 to MPC-p6 parameters may differ
from the configured values because, if the
MPC was (re-)initialized and the mpcConfigMode
was set to automatic (1) then some, perhaps all,
of the MPC-p1 to MPC-p6 parameters were retrieved
from the LECS and the values from the LECS may
differ from the configured/default values of the
mpcConfigTable. NOTE: after re-initialization
a set to an object in the mpcConfigTable which
changes the value of the object will be reflect
in this Table, except for a set to the
mpcConfigMode which takes effect only during
re-initialization. SEQUENCE OF MpcActualEntry .1.3.6.1.4.1.353.5.8.1.1.2.3 |
mpcActualEntryAn entry in the MPC Actual Table.
An entry represents a specific MPOA Client's
state information and the actual values
which are being used by the MPOA Client.
For example, the corresponding mpcConfigEntry contains
default and/or configured parameters, if mpcConfigMode was
set to manual, then these are the objects values' which are
reflected for the mpcActualEntry. However, if the
mpcConfigMode is automatic, then the mpcActualEntry
will be all the corresponding mpcConfigEntry's object,
excluding any objects which were retrieved from the LECS.
In other words, the objects retrieved from the LECS during
the (re-)initialization of the MPC overwrite any of the default
and/or configured values.
NOTE: any subsequent `set' to the configured values, e.g. an
SNMP
set operation, which is successful could result in a change to an
mpcConfigTable value, and will be reflected in this table as
well. MpcActualEntry .1.3.6.1.4.1.353.5.8.1.1.2.3.1 |
mpcActualStateThis object indicates the actual state
of the MPOA Client.ro Enumeration .1.3.6.1.4.1.353.5.8.1.1.2.3.1.1 |
mpcDiscontinuityTimeThe value of sysUpTime on the most recent occasion at
which any one or more of this MPC's counters
experienced a discontinuity. The relevant counters
are the specific instances associated with this
MPC. If discontinuities have not occurred since the
last re-initialization of the local management subsystem,
then this object contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.3.1.2 |
mpcActualConfigModeIndicates whether this MPC auto-configured
when it was last (re-)initialized.ro Enumeration .1.3.6.1.4.1.353.5.8.1.1.2.3.1.3 |
mpcActualSCSetupFrameCountMPC-p1 Short-cut setup frame count.
In frames measured over mpcShortcutFrameTime seconds.
Flow detection is protocol independent. i.e. all
network layers mpcProtocolEntry share the flow rate
specification.
A value of 1 implies that resolutions for short-cuts
are attempted for all flows.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.3.1.4 |
mpcActualSCSetupFrameTimeActual MPC-p2 Short-cut setup frame time, in seconds.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.3.1.5 |
mpcActualInitialRetryTimeActual MPC-p4 is initial value for the
retry time out.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.3.1.6 |
mpcActualRetryTimeMaximumMPC-p5 cumulative maximum value for Retry Time (MPC-p4).
Retries are attempted at intervals determined by the
algorithm described in the definition of
mpcActualInitialRetryTime.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.3.1.7 |
mpcActualHoldDownTimeMPC-p6 Hold Down Time
Minimum time to wait before reinitiating a failed
resolution attempt. The default value is
mpcRetryTimeMaximum * 4.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.3.1.8 |
mpcStatisticsTableA read-only table which contains statistical
information for all MPOA Clients that
this agent manages. SEQUENCE OF MpcStatisticsEntry .1.3.6.1.4.1.353.5.8.1.1.2.5 |
mpcStatisticsEntryEach row in this table contains statistics
for one MPOA Client. MpcStatisticsEntry .1.3.6.1.4.1.353.5.8.1.1.2.5.1 |
mpcStatTxMpoaResolveRequestsThe number of MPOA Resolve Requests transmitted
by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.1 |
mpcStatRxMpoaResolveReplyAcksThe number of positively acknowledged MPC
Resolved Replies received by this MPC with an MPOA
CIE Code of 0x00 (Success).
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and/or re-
initialization
of the MPC, and at other times, as indicated by the value of
mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.2 |
mpcStatRxMpoaResolveReplyInsufECResourcesThe number of MPOA Resolution Replies received with
an MPOA CIE Code of 0x81, `Insufficient resources to
accept egress cache entry'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.3 |
mpcStatRxMpoaResolveReplyInsufSCResourcesThe number of MPOA Resolution Replies received with
an MPOA CIE Code of 0x82, `Insufficient resources to
accept the shortcut'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.4 |
mpcStatRxMpoaResolveReplyInsufEitherResourcesThe number of MPOA Resolution Replies received with
an MPOA CIE Code of 0x83, `Insufficient resources to
accept either shortcut or egress cache entry'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.5 |
mpcStatRxMpoaResolveReplyUnsupportedInetProtThe number of MPOA Resolution Replies received with
an MPOA CIE Code of 0x84, `Unsupported Internework
Layer protocol'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.6 |
mpcStatRxMpoaResolveReplyUnsupportedMacEncapsThe number of MPOA Resolution Replies received with
an MPOA CIE Code of 0x85, `Unsupported MAC layer encapsulation'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.7 |
mpcStatRxMpoaResolveReplyUnspecifiedOtherThe number of MPOA Resolution Replies received with
an MPOA CIE Code of 0x88, `Unspecified/Other'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.8 |
mpcStatRxMpoaImpRequestsThe number of MPOA Cache Imposition Requests received
by this MPC.
Discontinuities in the value of this counter can occur at re-
initialization
of the management system, and/or re-initialization of the MPC,
and at
other times, as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.9 |
mpcStatTxMpoaImpReplyAcksThe number of successful MPOA Cache Imposition replies
transmitted by this MPC with an MPOA CIE Code of 0x00
`Success'.
Discontinuities in the value of this counter can occur at re-
initialization
of the management system, and/or re-initialization of the MPC,
and at
other times, as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.10 |
mpcStatTxMpoaImpReplyInsufECResourcesThe number of MPOA Cache Imposition Replies transmitted with
an MPOA CIE Code of 0x81, `Insufficient resources to
accept egress cache entry'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.11 |
mpcStatTxMpoaImpReplyInsufSCResourcesThe number of MPOA Imposition Replies transmitted with
an MPOA CIE Code of 0x82, `Insufficient resources to
accept shortcut'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.12 |
mpcStatTxMpoaImpReplyInsufEitherResourcesThe number of MPOA Imposition Replies transmitted with
an MPOA CIE Code of 0x83, `Insufficient resources to
accept either shortcut or egress cache entry'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.13 |
mpcStatTxMpoaImpReplyUnsupportedInetProtThe number of MPOA Imposition Replies transmitted with
an MPOA CIE Code of 0x84, `Unsupported Internetwork Layer
protocol'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.14 |
mpcStatTxMpoaImpReplyUnsupportedMacEncapsThe number of MPOA Imposition Replies transmitted with
an MPOA CIE Code of 0x85, `Unsupported MAC Layer
encapsulation'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.15 |
mpcStatTxMpoaImpReplyUnspecifiedOtherThe number of MPOA Imposition Replies transmitted with
an MPOA CIE Code of 0x88, `Unspecified/Other'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.16 |
mpcStatTxMpoaEgressCachePurgeRequestsThe number of MPOA Egress Cache Purge Requests transmitted
by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.17 |
mpcStatRxMpoaEgressCachePurgeRepliesThe number of MPOA Egress Cache Purge Replies received by
this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.18 |
mpcStatRxMpoaKeepAlivesThe number of MPOA Keep Alive messages received by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.19 |
mpcStatRxMpoaTriggersThe number of MPOA Trigger messages received by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.20 |
mpcStatRxMpoaDataPlanePurgesThe number of MPOA Data Plane Purge messages received
by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.21 |
mpcStatTxMpoaDataPlanePurgesThe number of MPOA Data Plane Purge messages transmitted
by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.22 |
mpcStatRxNhrpPurgeRequestsThe number of Purge Requests received by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.23 |
mpcStatTxNhrpPurgeRepliesThe number of Purge Replies transmitted by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.24 |
mpcStatRxErrUnrecognizedExtensionsThe number of Error Indication packets received by
this MPC with the error code `Unrecognized Extension'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.25 |
mpcStatRxErrLoopDetectedsThe number of Error Indication packets received by
this MPC with the error code `Loop Detected'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.26 |
mpcStatRxErrProtoAddrUnreachablesThe number of Error Indication packets received by this
MPC with the error code `Protocol Address Unreachable'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.27 |
mpcStatRxErrProtoErrorsThe number of Error Indication packets received by
this MPC with the error code `Protocol Errors'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.28 |
mpcStatRxErrSduSizeExceededsThe number of Error Indication packets received by
this MPC with the error code `SDU Size Exceeded'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.29 |
mpcStatRxErrInvalidExtensionsThe number of Error Indication packets received by
this MPC with the error code `Invalid Extensions'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.30 |
mpcStatRxErrInvalidRepliesThe number of Error Indication packets received by
this MPC with the error code `Invalid Reply'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.31 |
mpcStatRxErrAuthenticationFailuresThe number of Error Indication packets received by
this MPC with the error code `Authentication Failure'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.32 |
mpcStatRxErrHopCountExceededsThe number of Error Indication packets received by
this MPC with the error code `Hop Count Exceeded'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.33 |
mpcMpsTableThis is a read-only table which contains
information about the MPSs that these MPCs
know about. SEQUENCE OF MpcMpsEntry .1.3.6.1.4.1.353.5.8.1.1.2.8 |
mpcMpsEntryA row created by an MPC. The MPC learns about
an MPS and creates a row. MpcMpsEntry .1.3.6.1.4.1.353.5.8.1.1.2.8.1 |
mpcMpsIndexThe MPS's index which is used to identify
a row in this table. MpsIndex .1.3.6.1.4.1.353.5.8.1.1.2.8.1.1 |
mpcMpsAtmAddrThe Control ATM Address of the MPSro AtmAddr (ATM-TC-MIB) .1.3.6.1.4.1.353.5.8.1.1.2.8.1.2 |
mpcIngressCacheTableThis table contains information for MPC Caches for
the ingress MPC. SEQUENCE OF MpcIngressCacheEntry .1.3.6.1.4.1.353.5.8.1.1.2.12 |
mpcIngressCacheEntryAn entry contains control information
for a row in a MPC's Ingress Cache. MpcIngressCacheEntry .1.3.6.1.4.1.353.5.8.1.1.2.12.1 |
mpcIngressCacheDestInetworkAddrTypeThe type of the destination internetwork layer address.ro InternetworkAddrType .1.3.6.1.4.1.353.5.8.1.1.2.12.1.1 |
mpcIngressCacheDestAddrThe destination internetwork layer address for which
this entry is defined.ro InternetworkAddr .1.3.6.1.4.1.353.5.8.1.1.2.12.1.2 |
mpcIngressCachePrefixLenDefines an equivalence class of addresses that match
Prefix Length bit positions of the destination
internetwork layer address.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.12.1.3 |
mpcIngressCacheDestAtmAddrThe Destination ATM Address received in the MPOA
Resolution Reply.ro AtmAddr (ATM-TC-MIB) .1.3.6.1.4.1.353.5.8.1.1.2.12.1.4 |
mpcIngressCacheSrcAtmAddrThe Source ATM Address for the MPOA Resolution Request.ro AtmAddr (ATM-TC-MIB) .1.3.6.1.4.1.353.5.8.1.1.2.12.1.5 |
mpcIngressCacheEntryStateThe present state of this MPC ingress cache.
The states are:
doesNotExist (1)
inactive (2)
active. For an example, if
using the Finite State Machine
Appendix I.2, then the states
Cached and query are considered
`inactive'.
active (3)
For an example, if using the
Finite State Machine in Appendix I.2,
then the states resolved and refresh
are considered `active'.
negative (4)
which could mean a NAK response was
received, or entry is doing a
retry, etc. For example, if using
the Finite State Machine in Appendix
I.2, then the state `hold down' is
considered `negative'.ro Enumeration .1.3.6.1.4.1.353.5.8.1.1.2.12.1.6 |
mpcIngressCacheEgressCacheTagValidIf the value of this object is true(1), then a valid
Egress Cache Tag is present and the value of the Egress
Cache Tag is in mpcIngressCacheEgressCacheTag. Otherwise,
if this value is false(2), then there was no Egress Cache
Tag, and the value of mpcIngressCacheEgressCacheTag is
undefined.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.12.1.7 |
mpcIngressCacheEgressCacheTagIf a valid Egress Cache Tag is present, then this
object contains the value of that tag. To determine
if this object contains a valid value,
mpcIngressCacheEgressTagValid should be used.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.12.1.8 |
mpcIngressCacheLastNhrpCieCodeThe last NHRP CIE code received for this entry. This
value is valid only during the Hold Down period of the
cache entry. This value is undefined otherwise.ro INTEGER .1.3.6.1.4.1.353.5.8.1.1.2.12.1.9 |
mpcIngressCacheSigErrCodeError code or Success of the last sinalling request
for this cache entry.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.12.1.10 |
mpcIngressCacheRetriesThe current number of times this MPC has issued a
resolution request since it received a valid reply.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.12.1.11 |
mpcIngressCacheTimeUntilNextResolutionRequestThe amount of time the MPC
must wait before issuing the next resolution request.ro TimeInterval (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.12.1.12 |
mpcIngressCacheHoldingTimeThe time that this MPC's Ingress Cache Entry will remain
valid. If the mpcIngressCacheEntryState is not active
this value will be zero.ro TimeInterval (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.12.1.13 |
mpcIngressCacheServiceCategoryThe service categories supported for this shortcut.ro INTEGER .1.3.6.1.4.1.353.5.8.1.1.2.12.1.14 |
mpcEgressCacheTableThis table contains Egress Cache information for
all the MPCs which this agent manages. SEQUENCE OF MpcEgressCacheEntry .1.3.6.1.4.1.353.5.8.1.1.2.15 |
mpcEgressCacheEntryAn entry in the MPOA Client's Egress Cache table. MpcEgressCacheEntry .1.3.6.1.4.1.353.5.8.1.1.2.15.1 |
mpcEgressCacheIdCache ID Provided by the MPS in the Cache
Imposition Request.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.15.1.1 |
mpcEgressCacheInetworkAddrTypeType of Internetwork Address in this cache entry.ro InternetworkAddrType .1.3.6.1.4.1.353.5.8.1.1.2.15.1.2 |
mpcEgressCacheIDestAddrThe destination internetwork layer address
for which this entry is defined.ro InternetworkAddr .1.3.6.1.4.1.353.5.8.1.1.2.15.1.3 |
mpcEgressCachePrefixLenDefines an equivalence class of addresses that match
Prefix Length bit positions of the destination
internetwork layer address.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.15.1.4 |
mpcEgressCacheEntryStateThe present state of this MPC egress cache entry.
The states are:
doesNotExist (1)
inactive (2)
active (3)
For example,if using the Finite State
Machine in Appendix 1.5,
the states active and flooding
are `active' state.
negative (4)
For example,if using the Finite
State Machine in Appendix 1.5,
the state purging is `negative'.ro Enumeration .1.3.6.1.4.1.353.5.8.1.1.2.15.1.5 |
mpcEgressCacheEgressCacheTagValidIf the value of this object is true(1), then a valid
Egress Cache Tag is present and the value of the Egress
Cache Tag is in mpcEgressCacheEgressCacheTag. Otherwise,
if this value is false(2), then there was no Egress
Cache Tag, and the value of mpcEgressCacheEgressCacheTag
is undefined.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.15.1.6 |
mpcEgressCacheEgressCacheTagIf a valid Egress Cache Tag is present, then this
object contains the value of that tag. To determine
if this object contains a valid value,
mpcEgressCacheEgressCacheTagValid should be used.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.15.1.7 |
mpcEgressCacheHoldTimeThe remaining time for which this entry is valid.ro TimeInterval (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.15.1.8 |
mpcEgressCacheDataLinkHeaderThe DataLink header that the egress client rebuilds
the original DataLink packet with.ro OCTET STRING .1.3.6.1.4.1.353.5.8.1.1.2.15.1.9 |
mpcEgressCacheIngressMpcDataAtmAddrThe Data ATM Address of the ingress MPC that issued
the MPOA Resolution requestro AtmAddr (ATM-TC-MIB) .1.3.6.1.4.1.353.5.8.1.1.2.15.1.10 |
mpcEgressCacheLecIndexThis is the lecIndex of the LANE Client that this flow
is associated with. This can be used to get the ELAN
name as well as other LANE parameters.ro LecIndex .1.3.6.1.4.1.353.5.8.1.1.2.15.1.11 |
mpcEgressCacheServiceCategoryThis is a bitmap describing the service categories
supported for this shortcut. This value represents
an inclusive OR of the bits:
bit 1 - if rt-VBR is supported,
bit 2 - if nrt-VBR is supported,
bit 4 - if ABR is supported,
bit 8 - if CBR is supported
A value of 0 (zero) indicates that UBR is supported.ro INTEGER .1.3.6.1.4.1.353.5.8.1.1.2.15.1.12 |
mpcMpsObjects OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.1.2.16 |
mpoaMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.2 |
mpoaMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.2.1 |
mpoaMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.2.2 |