MPC-MIB

All MIBs › MPC-MIB

Organization: ATM Forum LANE/MPOA Working Group

Last Updated: 1998-11-09

Category: ATM

Description: Manages ATM Forum MPOA Client configuration and shortcut virtual circuit state.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is MPC-MIB?

MPC-MIB is an ATM Forum standards-based MIB for Multiprotocol Over ATM (MPOA) Clients, which let ATM-attached devices establish direct shortcut virtual circuits to bypass intermediate routers for better performance. It exposes configuration and state data describing MAC-address-to-shortcut-VC bindings maintained by the MPOA client. Its monitoring value is mainly about protocol/connection state rather than physical hardware: polling it reveals whether shortcut circuits have actually been established for a given destination or whether traffic is still falling back to default hop-by-hop routing. It explicitly depends on and revises the ATM Forum's af-mpoa-0092.000 specification per the MPOA v1.1 errata, obsoleting the older mpcMpsMacAddressTable in favor of mpcMpsMultipleMacAddressTable. It is typically deployed on legacy ATM-based enterprise or carrier backbone edge devices supporting MPOA client/server functionality. Engineers implementing or auditing this functionality typically reference the MPC-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in MPC-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

ATM Forum MPOA-capable ATM switches/edge devices
vendor-neutral, standards-based MIB, not tied to a specific manufacturer

Monitoring Examples

No sample object names were provided for this module, so specific identifiers cannot be quoted here. Based on the module description, the mpcMpsMultipleMacAddressTable (which replaced the obsoleted mpcMpsMacAddressTable) would map MAC addresses to established ATM shortcut virtual circuits. An administrator polling this table would confirm shortcut circuits are established for active destinations, and their absence would reveal that traffic is unexpectedly using slower default routing instead of a direct ATM shortcut.

What Can Be Monitored

MAC-address-to-shortcut-VC bindings
shortcut virtual circuit establishment state

Imported Objects

From ATM-TC-MIB

AtmAddr

From LAN-EMULATION-CLIENT-MIB

lecIndex

OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Counter64
Integer32
MODULE-IDENTITY
OBJECT-TYPE
enterprises

From SNMPv2-TC

MacAddress
RowStatus
TEXTUAL-CONVENTION
TimeInterval
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using mpcStatTxMpoaResolveRequests OID:

Select a device implementing MPC-MIB as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type mpcStatTxMpoaResolveRequests into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of MPOA Resolve Requests transmitted by this MPC. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
atmfMpoa	1.3.6.1.4.1.353.5.8
atmForum	1.3.6.1.4.1.353
atmForumNetworkManagement	1.3.6.1.4.1.353.5
INT mpcActualConfigMode	1.3.6.1.4.1.353.5.8.1.1.2.3.1.3	INTEGER	read-only	Indicates whether this MPC auto-configured when it was last (re-)initialized.
mpcActualEntry	1.3.6.1.4.1.353.5.8.1.1.2.3.1		not-accessible	An 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.
I32 mpcActualHoldDownTime	1.3.6.1.4.1.353.5.8.1.1.2.3.1.8	Integer32	read-only	MPC-p6 Hold Down Time Minimum time to wait before reinitiating a failed resolution attempt. The default value is mpcRetryTimeMaximum * 4.
I32 mpcActualInitialRetryTime	1.3.6.1.4.1.353.5.8.1.1.2.3.1.6	Integer32	read-only	Actual MPC-p4 is initial value for the retry time out.
I32 mpcActualRetryTimeMaximum	1.3.6.1.4.1.353.5.8.1.1.2.3.1.7	Integer32	read-only	MPC-p5 cumulative maximum value for Retry Time (MPC-p4). Retries are attempted at intervals determined by the algorithm described in the definition of mpcActualInitialRetryTime.
I32 mpcActualSCSetupFrameCount	1.3.6.1.4.1.353.5.8.1.1.2.3.1.4	Integer32	read-only	MPC-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.
I32 mpcActualSCSetupFrameTime	1.3.6.1.4.1.353.5.8.1.1.2.3.1.5	Integer32	read-only	Actual MPC-p2 Short-cut setup frame time, in seconds.
INT mpcActualState	1.3.6.1.4.1.353.5.8.1.1.2.3.1.1	INTEGER	read-only	This object indicates the actual state of the MPOA Client.
mpcActualTable	1.3.6.1.4.1.353.5.8.1.1.2.3		not-accessible	MPOA 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.
mpcConfigEntry	1.3.6.1.4.1.353.5.8.1.1.2.2.1		not-accessible	MPOA 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.
INT mpcConfigMode	1.3.6.1.4.1.353.5.8.1.1.2.2.1.3	INTEGER	read-create	Indicates 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.
mpcConfigTable	1.3.6.1.4.1.353.5.8.1.1.2.2		not-accessible	The MPOA Client Configuration Table. This table contains configuration information for all MPOA Clients which this agent manages.
ATM mpcCtrlAtmAddr	1.3.6.1.4.1.353.5.8.1.1.2.2.1.4	AtmConfigAddr	read-create	The 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.
TIM mpcDiscontinuityTime	1.3.6.1.4.1.353.5.8.1.1.2.3.1.2	TimeStamp	read-only	The 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.
OCT mpcEgressCacheDataLinkHeader	1.3.6.1.4.1.353.5.8.1.1.2.15.1.9	OCTET STRING	read-only	The DataLink header that the egress client rebuilds the original DataLink packet with.
I32 mpcEgressCacheEgressCacheTag	1.3.6.1.4.1.353.5.8.1.1.2.15.1.7	Integer32	read-only	If 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.
T/F mpcEgressCacheEgressCacheTagValid	1.3.6.1.4.1.353.5.8.1.1.2.15.1.6	TruthValue	read-only	If 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.
mpcEgressCacheEntry	1.3.6.1.4.1.353.5.8.1.1.2.15.1		not-accessible	An entry in the MPOA Client's Egress Cache table.
INT mpcEgressCacheEntryState	1.3.6.1.4.1.353.5.8.1.1.2.15.1.5	INTEGER	read-only	The present state of this MPC egress cache entry. The states are: doesNotExist (1) -- the state is not yet available, inactive (2) -- state exists, entry is not yet active, active (3) -- state exists, entry is active. For example,if using the Finite State Machine in Appendix 1.5, the states active and flooding are `active' state. negative (4) -- state exists, entry is negative. For example,if using the Finite State Machine in Appendix 1.5, the state purging is `negative'.
NUM mpcEgressCacheHoldTime	1.3.6.1.4.1.353.5.8.1.1.2.15.1.8	TimeInterval	read-only	The remaining time for which this entry is valid.
I32 mpcEgressCacheId	1.3.6.1.4.1.353.5.8.1.1.2.15.1.1	Integer32	read-only	Cache ID Provided by the MPS in the Cache Imposition Request.
NUM mpcEgressCacheIDestAddr	1.3.6.1.4.1.353.5.8.1.1.2.15.1.3	InternetworkAddr	read-only	The destination internetwork layer address for which this entry is defined.
NUM mpcEgressCacheInetworkAddrType	1.3.6.1.4.1.353.5.8.1.1.2.15.1.2	InternetworkAddrType	read-only	Type of Internetwork Address in this cache entry.
ATM mpcEgressCacheIngressMpcDataAtmAddr	1.3.6.1.4.1.353.5.8.1.1.2.15.1.10	AtmAddr	read-only	The Data ATM Address of the ingress MPC that issued the MPOA Resolution request
LEC mpcEgressCacheLecIndex	1.3.6.1.4.1.353.5.8.1.1.2.15.1.11	LecIndex	read-only	This 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.
I32 mpcEgressCachePrefixLen	1.3.6.1.4.1.353.5.8.1.1.2.15.1.4	Integer32	read-only	Defines an equivalence class of addresses that match Prefix Length bit positions of the destination internetwork layer address.
INT mpcEgressCacheServiceCategory	1.3.6.1.4.1.353.5.8.1.1.2.15.1.12	INTEGER	read-only	This 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.
mpcEgressCacheTable	1.3.6.1.4.1.353.5.8.1.1.2.15		not-accessible	This table contains Egress Cache information for all the MPCs which this agent manages.
I32 mpcHoldDownTime	1.3.6.1.4.1.353.5.8.1.1.2.2.1.9	Integer32	read-create	MPC-p6 Hold Down Time Minimum time to wait before reinitiating a failed resolution attempt. Default is mpcRetryTimeMaximum * 4.
MPC mpcIndex	1.3.6.1.4.1.353.5.8.1.1.2.2.1.1	MpcIndex	not-accessible	A 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.
NUM mpcIngressCacheDestAddr	1.3.6.1.4.1.353.5.8.1.1.2.12.1.2	InternetworkAddr	read-only	The destination internetwork layer address for which this entry is defined.
ATM mpcIngressCacheDestAtmAddr	1.3.6.1.4.1.353.5.8.1.1.2.12.1.4	AtmAddr	read-only	The Destination ATM Address received in the MPOA Resolution Reply.
NUM mpcIngressCacheDestInetworkAddrType	1.3.6.1.4.1.353.5.8.1.1.2.12.1.1	InternetworkAddrType	read-only	The type of the destination internetwork layer address.
I32 mpcIngressCacheEgressCacheTag	1.3.6.1.4.1.353.5.8.1.1.2.12.1.8	Integer32	read-only	If 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.
T/F mpcIngressCacheEgressCacheTagValid	1.3.6.1.4.1.353.5.8.1.1.2.12.1.7	TruthValue	read-only	If 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.
mpcIngressCacheEntry	1.3.6.1.4.1.353.5.8.1.1.2.12.1		not-accessible	An entry contains control information for a row in a MPC's Ingress Cache.
INT mpcIngressCacheEntryState	1.3.6.1.4.1.353.5.8.1.1.2.12.1.6	INTEGER	read-only	The present state of this MPC ingress cache. The states are: doesNotExist (1) -- the state is not yet available inactive (2) -- state exists, entry is not yet active. For an example, if using the Finite State Machine Appendix I.2, then the states Cached and query are considered `inactive'. active (3) -- state exists, entry is active. For an example, if using the Finite State Machine in Appendix I.2, then the states resolved and refresh are considered `active'. negative (4) -- state exists, entry is negative, 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'.
NUM mpcIngressCacheHoldingTime	1.3.6.1.4.1.353.5.8.1.1.2.12.1.13	TimeInterval	read-only	The time that this MPC's Ingress Cache Entry will remain valid. If the mpcIngressCacheEntryState is not active this value will be zero.
INT mpcIngressCacheLastNhrpCieCode	1.3.6.1.4.1.353.5.8.1.1.2.12.1.9	INTEGER	read-only	The 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.
I32 mpcIngressCachePrefixLen	1.3.6.1.4.1.353.5.8.1.1.2.12.1.3	Integer32	read-only	Defines an equivalence class of addresses that match Prefix Length bit positions of the destination internetwork layer address.
C32 mpcIngressCacheRetries	1.3.6.1.4.1.353.5.8.1.1.2.12.1.11	Counter32	read-only	The current number of times this MPC has issued a resolution request since it received a valid reply.
INT mpcIngressCacheServiceCategory	1.3.6.1.4.1.353.5.8.1.1.2.12.1.14	INTEGER	read-only	The service categories supported for this shortcut.
I32 mpcIngressCacheSigErrCode	1.3.6.1.4.1.353.5.8.1.1.2.12.1.10	Integer32	read-only	Error code or Success of the last sinalling request for this cache entry.
ATM mpcIngressCacheSrcAtmAddr	1.3.6.1.4.1.353.5.8.1.1.2.12.1.5	AtmAddr	read-only	The Source ATM Address for the MPOA Resolution Request.
mpcIngressCacheTable	1.3.6.1.4.1.353.5.8.1.1.2.12		not-accessible	This table contains information for MPC Caches for the ingress MPC.
NUM mpcIngressCacheTimeUntilNextResolutionRequest	1.3.6.1.4.1.353.5.8.1.1.2.12.1.12	TimeInterval	read-only	The amount of time the MPC must wait before issuing the next resolution request.
I32 mpcInitialRetryTime	1.3.6.1.4.1.353.5.8.1.1.2.2.1.7	Integer32	read-create	MPC-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.
ATM mpcMpsAtmAddr	1.3.6.1.4.1.353.5.8.1.1.2.8.1.2	AtmAddr	read-only	The Control ATM Address of the MPS
mpcMpsEntry	1.3.6.1.4.1.353.5.8.1.1.2.8.1		not-accessible	A row created by an MPC. The MPC learns about an MPS and creates a row.
MPS mpcMpsIndex	1.3.6.1.4.1.353.5.8.1.1.2.8.1.1	MpsIndex	not-accessible	The MPS's index which is used to identify a row in this table.
mpcMpsObjects	1.3.6.1.4.1.353.5.8.1.1.2.16
mpcMpsTable	1.3.6.1.4.1.353.5.8.1.1.2.8		not-accessible	This is a read-only table which contains information about the MPSs that these MPCs know about.
I32 mpcNextIndex	1.3.6.1.4.1.353.5.8.1.1.2.1	Integer32	read-write	This 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.
mpcObjects	1.3.6.1.4.1.353.5.8.1.1.2
I32 mpcRetryTimeMaximum	1.3.6.1.4.1.353.5.8.1.1.2.2.1.8	Integer32	read-create	MPC-p5 cumulative max value for Retry Time (MPC-p4). Retries are attempted at intervals determined by the algorithm described in the definition of mpcIntialRetryTime.
ROW mpcRowStatus	1.3.6.1.4.1.353.5.8.1.1.2.2.1.2	RowStatus	read-create	This 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'
I32 mpcSCSetupFrameCount	1.3.6.1.4.1.353.5.8.1.1.2.2.1.5	Integer32	read-create	This 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.
I32 mpcSCSetupFrameTime	1.3.6.1.4.1.353.5.8.1.1.2.2.1.6	Integer32	read-create	MPC-p2 Short-cut setup frame time, in seconds.
mpcStatisticsEntry	1.3.6.1.4.1.353.5.8.1.1.2.5.1		not-accessible	Each row in this table contains statistics for one MPOA Client.
mpcStatisticsTable	1.3.6.1.4.1.353.5.8.1.1.2.5		not-accessible	A read-only table which contains statistical information for all MPOA Clients that this agent manages.
C32 mpcStatRxErrAuthenticationFailures	1.3.6.1.4.1.353.5.8.1.1.2.5.1.32	Counter32	read-only	The 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.
C32 mpcStatRxErrHopCountExceededs	1.3.6.1.4.1.353.5.8.1.1.2.5.1.33	Counter32	read-only	The 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.
C32 mpcStatRxErrInvalidExtensions	1.3.6.1.4.1.353.5.8.1.1.2.5.1.30	Counter32	read-only	The 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.
C32 mpcStatRxErrInvalidReplies	1.3.6.1.4.1.353.5.8.1.1.2.5.1.31	Counter32	read-only	The 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.
C32 mpcStatRxErrLoopDetecteds	1.3.6.1.4.1.353.5.8.1.1.2.5.1.26	Counter32	read-only	The 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.
C32 mpcStatRxErrProtoAddrUnreachables	1.3.6.1.4.1.353.5.8.1.1.2.5.1.27	Counter32	read-only	The 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.
C32 mpcStatRxErrProtoErrors	1.3.6.1.4.1.353.5.8.1.1.2.5.1.28	Counter32	read-only	The 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.
C32 mpcStatRxErrSduSizeExceededs	1.3.6.1.4.1.353.5.8.1.1.2.5.1.29	Counter32	read-only	The 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.
C32 mpcStatRxErrUnrecognizedExtensions	1.3.6.1.4.1.353.5.8.1.1.2.5.1.25	Counter32	read-only	The 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.
C32 mpcStatRxMpoaDataPlanePurges	1.3.6.1.4.1.353.5.8.1.1.2.5.1.21	Counter32	read-only	The 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.
C32 mpcStatRxMpoaEgressCachePurgeReplies	1.3.6.1.4.1.353.5.8.1.1.2.5.1.18	Counter32	read-only	The 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.
C32 mpcStatRxMpoaImpRequests	1.3.6.1.4.1.353.5.8.1.1.2.5.1.9	Counter32	read-only	The 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.
C32 mpcStatRxMpoaKeepAlives	1.3.6.1.4.1.353.5.8.1.1.2.5.1.19	Counter32	read-only	The 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.
C32 mpcStatRxMpoaResolveReplyAcks	1.3.6.1.4.1.353.5.8.1.1.2.5.1.2	Counter32	read-only	The 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.
C32 mpcStatRxMpoaResolveReplyInsufECResources	1.3.6.1.4.1.353.5.8.1.1.2.5.1.3	Counter32	read-only	The 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.
C32 mpcStatRxMpoaResolveReplyInsufEitherResources	1.3.6.1.4.1.353.5.8.1.1.2.5.1.5	Counter32	read-only	The 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.
C32 mpcStatRxMpoaResolveReplyInsufSCResources	1.3.6.1.4.1.353.5.8.1.1.2.5.1.4	Counter32	read-only	The 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.
C32 mpcStatRxMpoaResolveReplyUnspecifiedOther	1.3.6.1.4.1.353.5.8.1.1.2.5.1.8	Counter32	read-only	The 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.
C32 mpcStatRxMpoaResolveReplyUnsupportedInetProt	1.3.6.1.4.1.353.5.8.1.1.2.5.1.6	Counter32	read-only	The 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.
C32 mpcStatRxMpoaResolveReplyUnsupportedMacEncaps	1.3.6.1.4.1.353.5.8.1.1.2.5.1.7	Counter32	read-only	The 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.
C32 mpcStatRxMpoaTriggers	1.3.6.1.4.1.353.5.8.1.1.2.5.1.20	Counter32	read-only	The 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.
C32 mpcStatRxNhrpPurgeRequests	1.3.6.1.4.1.353.5.8.1.1.2.5.1.23	Counter32	read-only	The 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.
C32 mpcStatTxMpoaDataPlanePurges	1.3.6.1.4.1.353.5.8.1.1.2.5.1.22	Counter32	read-only	The 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.
C32 mpcStatTxMpoaEgressCachePurgeRequests	1.3.6.1.4.1.353.5.8.1.1.2.5.1.17	Counter32	read-only	The 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.
C32 mpcStatTxMpoaImpReplyAcks	1.3.6.1.4.1.353.5.8.1.1.2.5.1.10	Counter32	read-only	The 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.
C32 mpcStatTxMpoaImpReplyInsufECResources	1.3.6.1.4.1.353.5.8.1.1.2.5.1.11	Counter32	read-only	The 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.
C32 mpcStatTxMpoaImpReplyInsufEitherResources	1.3.6.1.4.1.353.5.8.1.1.2.5.1.13	Counter32	read-only	The 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.
C32 mpcStatTxMpoaImpReplyInsufSCResources	1.3.6.1.4.1.353.5.8.1.1.2.5.1.12	Counter32	read-only	The 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.
C32 mpcStatTxMpoaImpReplyUnspecifiedOther	1.3.6.1.4.1.353.5.8.1.1.2.5.1.16	Counter32	read-only	The 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.
C32 mpcStatTxMpoaImpReplyUnsupportedInetProt	1.3.6.1.4.1.353.5.8.1.1.2.5.1.14	Counter32	read-only	The 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.
C32 mpcStatTxMpoaImpReplyUnsupportedMacEncaps	1.3.6.1.4.1.353.5.8.1.1.2.5.1.15	Counter32	read-only	The 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.
C32 mpcStatTxMpoaResolveRequestsEx	1.3.6.1.4.1.353.5.8.1.1.2.5.1.1	Counter32	read-only	The 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.
C32 mpcStatTxNhrpPurgeReplies	1.3.6.1.4.1.353.5.8.1.1.2.5.1.24	Counter32	read-only	The 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.
mpoaCommonObjects	1.3.6.1.4.1.353.5.8.1.1.1
mpoaMIB	1.3.6.1.4.1.353.5.8.1			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.
mpoaMIBCompliances	1.3.6.1.4.1.353.5.8.1.2.2
mpoaMIBConformance	1.3.6.1.4.1.353.5.8.1.2
mpoaMIBGroups	1.3.6.1.4.1.353.5.8.1.2.1
mpoaMIBObjects	1.3.6.1.4.1.353.5.8.1.1

RFC description

MPOA (Multiprotocol Over ATM) MPC (Multiprotocol Client) MIB for ATM-based LAN emulation and MPOA protocol management.

Start monitoring Vendor-neutral ATM Forum standard (MPOA-capable ATM switch/edge device) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download MPC-MIB