All MIBs › MPOA-MIB
Organization: ATM Forum LANE/MPOA Working Group
Last Updated: 1998-11-09
Category: ATM
Description:
Manages ATM Forum MPOA server and client configuration and cache state.
Imported Objects
| 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 |
What Is MPOA-MIB?
MPOA-MIB is a standards-based MIB, derived from the ATM Forum's MPOA specification (af-mpoa-0092.000), for managing Multiprotocol Over ATM clients (MPCs) and servers (MPSs) that enable direct ATM shortcut connections between LANs across a routed ATM network. It exposes configuration and cache-state data for MPOA clients/servers, most notably a MAC-address-to-ATM-address cache — originally via mpcMpsMacAddressTable, now obsoleted and replaced by mpcMpsMultipleMacAddressTable to support multiple MAC addresses per entry. Anyone consulting an MPOA-MIB reference today is most likely maintaining legacy ATM equipment rather than deploying new infrastructure, since MPOA itself is largely obsolete. Monitoring this MIB centers on the software/control-plane status of MPOA shortcut resolution — verifying that MAC/ATM address cache entries are correctly populated and current — rather than physical hardware sensors, helping diagnose failed shortcut setup or stale ATM cache entries. It depends on the underlying ATM MIB framework for the ATM interfaces and virtual circuits that MPOA shortcuts ride on. It is deployed in legacy ATM-based campus/backbone networks using MPOA for LAN-to-LAN traffic acceleration over ATM.
IPNetwork Monitor allows you to monitor SNMP objects defined in MPOA-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.
What Can Be Monitored
- MAC-to-ATM address cache entries
- MPOA client/server configuration
- shortcut cache state
Supported Devices
- vendor-neutral, standards-based MIB (ATM Forum MPOA spec), not tied to a specific manufacturer — applies to ATM-capable routers/switches acting as MPOA clients and servers
Monitoring Examples
An administrator would poll the mpcMpsMultipleMacAddressTable to review the cached MAC-address-to-ATM-address mappings maintained by an MPOA client/server; an entry that fails to populate or repeatedly ages out would indicate a broken MPOA shortcut resolution, forcing traffic back onto the slower default routed path instead of a direct ATM connection.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| atmForum | 1.3.6.1.4.1.353 | |||
| atmForumNetworkManagement | 1.3.6.1.4.1.353.5 | |||
| atmfMpoa | 1.3.6.1.4.1.353.5.8 | |||
| 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. | ||
| mpoaMIBObjects | 1.3.6.1.4.1.353.5.8.1.1 | |||
| mpoaCommonObjects | 1.3.6.1.4.1.353.5.8.1.1.1 | |||
| deviceTypeTable | 1.3.6.1.4.1.353.5.8.1.1.1.1 | not-accessible | The device type table represents the mapping of the Lane Data ATM address to the MAC device capability. The unique key is the Lane data ATM address and Lec Index of the LEC associated with the MAC addresses. This table contains information which was gathered from its environment about neighboring machines. This Device type table represents the information of other/remote MPOA devices, discovered/gathered by each MPOA device. This MIB is not the device type of MPS/MPC itself; it is DISCOVERED information. | |
| deviceTypeEntry | 1.3.6.1.4.1.353.5.8.1.1.1.1.1 | not-accessible | An entry in this table and corresponding entries in the deviceTypeMpsMacAddressTable represent a mapping of a MAC device capability (i.e. the set of MAC addresses from a device) to the LEC ATM Address. | |
| INT deviceTypeIndex | 1.3.6.1.4.1.353.5.8.1.1.1.1.1.1 | INTEGER | not-accessible | Index into this table and also used as one of the indices for the deviceTypeMpsMacAddressTable. This index has local significance within the mpoaDeviceGroup. Entries in the `deviceTypeMpsMacAddressTable' which correspond to this index, and have the `deviceTypeType' value of `mps' or `mpsAndMps' are considered to be MPS MAC addresses. |
| LEC deviceTypeLecIndex | 1.3.6.1.4.1.353.5.8.1.1.1.1.1.2 | LecIndex | read-only | LecIndex of LEC that supports this data ATM address |
| ATM deviceTypeRemoteLecAtmAddress | 1.3.6.1.4.1.353.5.8.1.1.1.1.1.3 | AtmAddr | read-only | The ATM address learned by LE ARP. |
| INT deviceTypeType | 1.3.6.1.4.1.353.5.8.1.1.1.1.1.4 | INTEGER | read-only | same as the TLV |
| ATM deviceTypeMpsAtmAddress | 1.3.6.1.4.1.353.5.8.1.1.1.1.1.5 | AtmAddr | read-only | Associated MPS address, zeros for non-MPOA and mpc |
| ATM deviceTypeMpcAtmAddress | 1.3.6.1.4.1.353.5.8.1.1.1.1.1.6 | AtmAddr | read-only | Associated MPC address, zeros for non-MPOA & mps |
| deviceTypeMpsMacAddressTable | 1.3.6.1.4.1.353.5.8.1.1.1.2 | not-accessible | This table contains MPS MAC Address information gathered from the MPOA DeviceTypeTLV. | |
| deviceTypeMpsMacAddressEntry | 1.3.6.1.4.1.353.5.8.1.1.1.2.1 | not-accessible | Each entry represents an MPS MAC Address. Each entry corresponds to a deviceTypeIndex value for which the deviceTypeType attribute is `mps' or `mpsAndMpc'. | |
| MAC deviceTypeMpsMacAddress | 1.3.6.1.4.1.353.5.8.1.1.1.2.1.1 | MacAddress | read-only | MPS MAC address contained in the Device Type TLV which is identified by the deviceTypeIndex in the deviceTypeTable. |
| mpcObjects | 1.3.6.1.4.1.353.5.8.1.1.2 | |||
| 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. |
| 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. | |
| 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. | |
| 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. |
| 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' |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. | |
| 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. | |
| 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. |
| 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. |
| 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. |
| 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. |
| 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 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. |
| mpcDataAtmAddressTable | 1.3.6.1.4.1.353.5.8.1.1.2.4 | not-accessible | A table which shows all the data ATM addresses associated with all MPOA Clients. | |
| mpcDataAtmAddressEntry | 1.3.6.1.4.1.353.5.8.1.1.2.4.1 | not-accessible | Each row defines one data ATM address associated with an MPC. NOTE: if an MPC has more than one data ATM address then there will be another entry which contains the same mpcIndex subIdentifier, with a different mpcDataAtmAddress. | |
| ATM mpcDataAtmAddress | 1.3.6.1.4.1.353.5.8.1.1.2.4.1.1 | AtmAddr | not-accessible | A data ATM Address which is associated with an MPOA Client specified by the mpcIndex. |
| ROW mpcDataAtmAddressRowStatus | 1.3.6.1.4.1.353.5.8.1.1.2.4.1.2 | RowStatus | read-create | This object allows creation and deletion of an MPOA Client's Data ATM Addresses. The row can be created/deleted by either an NMS or by the SNMP agent. |
| 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. | |
| 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. | |
| C32 mpcStatTxMpoaResolveRequests | 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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. |
| 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 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 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 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. |
| mpcProtocolTable | 1.3.6.1.4.1.353.5.8.1.1.2.6 | not-accessible | List of protocols, per MPC, for which flow detection is enabled | |
| mpcProtocolEntry | 1.3.6.1.4.1.353.5.8.1.1.2.6.1 | not-accessible | Each row indicates one protocol for which an MPC will do flow detection. If the LECS was contacted for configuration information, and the Control Octet of the MPC-p3 has the value of 0x01, `Enable', then protocol values retrieved from the LECS are reflected in this table and the mpcLECSValue object will be (1) true. Also, the user or agent can create rows which appropriately correspond to the MPC denoted by mpcIndex, and the mpcLECSValue object will be set to (2) false. NOTE: if the LECS does not return information for the MPC-p3 parameter, or if in manual mode, the user or agent should create at least one entry for the corresponding MPC. Both, LECS and user and/or agent created rows may exist in this Table. | |
| NUM mpcFlowDetectProtocol | 1.3.6.1.4.1.353.5.8.1.1.2.6.1.1 | InternetworkAddrType | not-accessible | The protocol on which flow detection is performed. If this value was obtained from the LECS then this value is one of the collection of values returned in the MPC-p3 parameter. |
| T/F mpcLECSValue | 1.3.6.1.4.1.353.5.8.1.1.2.6.1.2 | TruthValue | read-only | This object reflects if the current entry is due to a retrieval from the LECS or not. If this entry is due to the LECS, then true(1) is the value for this object, otherwise, false (2). |
| ROW mpcProtocolRowStatus | 1.3.6.1.4.1.353.5.8.1.1.2.6.1.3 | RowStatus | read-create | This object is used by an agent or manager to create, delete or modify a row in this table. |
| mpcMappingTable | 1.3.6.1.4.1.353.5.8.1.1.2.7 | not-accessible | A table mapping the `lecIndex' values of LANE Clients to the `mpcIndex' values of corresponding MPOA Clients. | |
| mpcMappingEntry | 1.3.6.1.4.1.353.5.8.1.1.2.7.1 | not-accessible | Each row defines one lecIndex --> mpcIndex mapping. The mpcIndex that a lecIndex maps to is not necessarily unique (an MPC can serve many LECs, however, a LEC cannot be served by more than one MPC). | |
| ROW mpcMappingRowStatus | 1.3.6.1.4.1.353.5.8.1.1.2.7.1.1 | RowStatus | read-create | This object is used by an agent or manager to create, delete or modify a row in this table. |
| MPC mpcMappingIndex | 1.3.6.1.4.1.353.5.8.1.1.2.7.1.2 | MpcIndex | read-create | The mpcIndex of the MPOA Client that is performing flow detection for the LANE Client represented by the lecIndex. |
| 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. | |
| 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. |
| 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 |
| mpcMpsMacAddressTable | 1.3.6.1.4.1.353.5.8.1.1.2.9 | not-accessible | This is a read-only table which contains information about all the MPSs' MAC Addresses that these MPCs know about. | |
| mpcMpsMacAddressEntry | 1.3.6.1.4.1.353.5.8.1.1.2.9.1 | not-accessible | A row is created by an MPC. The MPC learns about an MPS's MAC Address and creates a row. | |
| LEC mpcLecIndex | 1.3.6.1.4.1.353.5.8.1.1.2.9.1.1 | LecIndex | not-accessible | The lecIndex which represents the associated LEC. |
| MAC mpcMpsMacAddress | 1.3.6.1.4.1.353.5.8.1.1.2.9.1.2 | MacAddress | read-only | The MAC Address of the MPS. |
| C32 mpcIngressCacheTxTotalPackets | 1.3.6.1.4.1.353.5.8.1.1.2.10 | Counter32 | read-only | The total number of packets transmitted over MPC Short Cuts. |
| C64 mpcIngressCacheTxTotalOctets | 1.3.6.1.4.1.353.5.8.1.1.2.11 | Counter64 | read-only | The total number of octets transmitted over MPC Short Cuts. |
| 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. | |
| 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. | |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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'. |
| 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. |
| 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. |
| 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 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. |
| 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. |
| 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. |
| 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 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. |
| C32 mpcEgressCacheRxTotalPackets | 1.3.6.1.4.1.353.5.8.1.1.2.13 | Counter32 | read-only | This counts the total number of packets received by MPC Short Cuts. |
| C64 mpcEgressCacheRxTotalOctets | 1.3.6.1.4.1.353.5.8.1.1.2.14 | Counter64 | read-only | This counts the total number of octets received by MPC Short Cuts. |
| 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. | |
| 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. | |
| 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 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. |
| 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. |
| 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 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'. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| mpcMpsObjects | 1.3.6.1.4.1.353.5.8.1.1.2.16 | |||
| mpcMpsMultipleMacAddressTable | 1.3.6.1.4.1.353.5.8.1.1.2.16.1 | not-accessible | This is a read-only table which contains information about all the MPSs' MAC Addresses that these MPCs use during flow detection. Note that due to the multinetted case an MPC may learn about more than one MAC address from an MPS, thus there may be more than one MAC address for the same MPC - MPS - LecIndex represented in this Table. These MacAddresses are differentiated by the mpcMpsMacAddressIndex. | |
| mpcMpsMultipleMacAddressEntry | 1.3.6.1.4.1.353.5.8.1.1.2.16.1.1 | not-accessible | A row is created by an MPC. The MPC learns about a MPS and the one or more MAC Address of the MPS which the MPC uses during flow detection. Each row represents an MPS MAC Address used by an MPC during flow detection. | |
| LEC mpcFlowDetectLecIndex | 1.3.6.1.4.1.353.5.8.1.1.2.16.1.1.1 | LecIndex | not-accessible | The lecIndex which represents the associated LEC. |
| I32 mpcMpsMacAddressIndex | 1.3.6.1.4.1.353.5.8.1.1.2.16.1.1.2 | Integer32 | not-accessible | This value is used to differentiate MAC Addresses from the same MPS used by the same MPC during flow detection. This value should be unique within the scope of this table. |
| MAC mpcMpsFlowDetectMacAddress | 1.3.6.1.4.1.353.5.8.1.1.2.16.1.1.3 | MacAddress | read-only | An MPS MAC Address used by an MPC during flow detection. |
| mpsObjects | 1.3.6.1.4.1.353.5.8.1.1.3 | |||
| I32 mpsNextIndex | 1.3.6.1.4.1.353.5.8.1.1.3.1 | Integer32 | read-only | This object contains an appropriate value to be used for mpsIndex when creating entries in the mpsConfigTable. The value 0 indicates that no new rows can be created. Otherwise, it is recommended that values are assigned contiguously, starting from 1. MPS creation by a Manager: To obtain the mpsIndex 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 mpsIndex. 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 mpsNextIndex 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. MPS creation by an Agent: When a row in the mpsConfigTable 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 mpsIndexes must be preserved. In other words, the Agent should store in non-volatile memory all the currently used mpsIndexes (along with all necessary configuration information from the mpsConfigTable). When the agent is re-initialized, the mpsNextIndex value is any valid Integer32 which is not being used as an mpsIndex, except 0 which maintains its original definition of indicating that a row cannot be created. |
| mpsConfigTable | 1.3.6.1.4.1.353.5.8.1.1.3.2 | not-accessible | The MPOA Server Configuration Table. This table represents the configuration information for all MPOA Servers which this agent manages. | |
| mpsConfigEntry | 1.3.6.1.4.1.353.5.8.1.1.3.2.1 | not-accessible | MPOA Server Configuration Entry. Each entry contains configuration information for one MPOA Server. | |
| MPS mpsIndex | 1.3.6.1.4.1.353.5.8.1.1.3.2.1.1 | MpsIndex | not-accessible | A value which uniquely identifies this conceptual row in the mpsConfigTable. The `mpsNextIndex' object needs to be used to determine the value of this object. A row cannot be added, unless the mpsCtrlAtmAddress is unique. In the event of an MPS re-initialization, the value of this mpsIndex must remain the same. However, in the event of an agent re-initialization, this value does not need to be preserved. |
| ROW mpsRowStatus | 1.3.6.1.4.1.353.5.8.1.1.3.2.1.2 | RowStatus | read-create | This object allows creation and deletion of MPOA Servers. Within each conceptual mpsConfigTable row, objects which are writable may be modified regardless of the value of mpsRowStatus. It is not necessary to set a row's status to `notInService' first. A row cannot be created, unless the mpsAtmCtrlAddress in this table is unique. When an MPOA Server is created via this object, it will initially have `mpsActualState' = `initialState'. |
| INT mpsConfigMode | 1.3.6.1.4.1.353.5.8.1.1.3.2.1.3 | INTEGER | read-create | Indicates whether this MPS should auto-configure the next time it is (re-)initialized. In automatic(1) mode the LECS is contacted and requests are made for the MPS-p* parameters. In manual(2) mode, the values of the configuration parameters are obtained from the mpsConfigTable and the mpsProtocolTable. |
| ATM mpsCtrlAtmAddr | 1.3.6.1.4.1.353.5.8.1.1.3.2.1.4 | AtmConfigAddr | read-create | The MPS's Control ATM Address. There exists one Control ATM Address per MPS, therefore, the value of this entry is unique within the table. |
| I32 mpsKeepAliveTime | 1.3.6.1.4.1.353.5.8.1.1.3.2.1.5 | Integer32 | read-create | MPS-p1 Keep-alive time is max interval between the MPS sending MPOA Keep-Alives in seconds. |
| I32 mpsKeepAliveLifeTime | 1.3.6.1.4.1.353.5.8.1.1.3.2.1.6 | Integer32 | read-create | MPS-p2 Keep-Alive Lifetime The length of time an MPC may consider a Keep-Alive valid in seconds. This value must be at least three times the mpsKeepAliveTime (MPS-p1). |
| I32 mpsInitialRetryTime | 1.3.6.1.4.1.353.5.8.1.1.3.2.1.7 | Integer32 | read-create | MPS-p4 is initial value in seconds for the MPOA retry mechanism. |
| I32 mpsRetryTimeMaximum | 1.3.6.1.4.1.353.5.8.1.1.3.2.1.8 | Integer32 | read-create | MPS-p5 cumulative max value in seconds for Retry Time (MPS-p4). |
| I32 mpsGiveupTime | 1.3.6.1.4.1.353.5.8.1.1.3.2.1.9 | Integer32 | read-create | MPS-p6 Give Up Time. Minimum time in seconds to wait before giving up on a pending resolution request. |
| I32 mpsDefaultHoldingTime | 1.3.6.1.4.1.353.5.8.1.1.3.2.1.10 | Integer32 | read-create | MPS-p7 Default Holding Time in minutes. The default Holding Time used in NHRP Resolution Replies. An egress MPS may use local information to determine a more appropriate Holding Time. |
| mpsActualTable | 1.3.6.1.4.1.353.5.8.1.1.3.3 | not-accessible | A read-only table containing identification, status, and operational information about the MPOA Servers this agent manages. | |
| mpsActualEntry | 1.3.6.1.4.1.353.5.8.1.1.3.3.1 | not-accessible | An entry in the MPS Actual Table. An entry represents a specific MPOA Server's status and operation information. | |
| INT mpsActualState | 1.3.6.1.4.1.353.5.8.1.1.3.3.1.1 | INTEGER | read-only | This object indicates the current operational status of the MPOA Server. |
| TIM mpsDiscontinuityTime | 1.3.6.1.4.1.353.5.8.1.1.3.3.1.2 | TimeStamp | read-only | The value of sysUpTime on the most recent occasion at which any one or more of this MPS's counters experienced a discontinuity. The relevant counters are the specific instances associated with this MPS. If discontinuities have not occurred since the last re-initialization of the local management subsystem, then this object contains a zero value. |
| INT mpsActualConfigMode | 1.3.6.1.4.1.353.5.8.1.1.3.3.1.3 | INTEGER | read-only | Indicates whether this MPS auto-configured when it was last (re-)initialized. |
| I32 mpsActualKeepAlive | 1.3.6.1.4.1.353.5.8.1.1.3.3.1.5 | Integer32 | read-only | The maximum amount of time in seconds this MPS waits between sending MPOA Keep-Alives. |
| I32 mpsActualKeepAliveLifeTime | 1.3.6.1.4.1.353.5.8.1.1.3.3.1.6 | Integer32 | read-only | The length of time in seconds this MPS considers a Keep-Alive valid. |
| I32 mpsActualInitialRetryTime | 1.3.6.1.4.1.353.5.8.1.1.3.3.1.7 | Integer32 | read-only | The actual initial value in seconds for the MPOA retry mechanism. |
| I32 mpsActualRetryTimeMaximum | 1.3.6.1.4.1.353.5.8.1.1.3.3.1.8 | Integer32 | read-only | The actual cumulative max value in seconds for Retry Time. |
| I32 mpsActualGiveupTime | 1.3.6.1.4.1.353.5.8.1.1.3.3.1.9 | Integer32 | read-only | Minimum time in seconds that this MPS waits before giving up on a pending resolution request. |
| I32 mpsActualDefaultHoldingTime | 1.3.6.1.4.1.353.5.8.1.1.3.3.1.10 | Integer32 | read-only | The actual Holding Time in minutes used in NHRP Resolution Replies. |
| mpsStatisticsTable | 1.3.6.1.4.1.353.5.8.1.1.3.4 | not-accessible | This table represents the statistical information for the MPSs, which this agent manages. | |
| mpsStatisticsEntry | 1.3.6.1.4.1.353.5.8.1.1.3.4.1 | not-accessible | Each row in this table contains statistics for one MPOA server. | |
| C32 mpsStatRxMpoaResolveRequests | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.1 | Counter32 | read-only | The number of MPOA Resolve Requests received by this MPS which are translated to NHRP resolve requests. Discontinuities in the value of this counter can occur at re-initialization of the management system, and/or re-initialization of the MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatTxMpoaResolveReplyAcks | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.2 | Counter32 | read-only | The number of MPOA Resolve Replies transmitted by this MPS which contain the 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 MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatTxMpoaResolveReplyInsufECResources | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.3 | Counter32 | read-only | The number of MPOA Resolve Replies transmitted by this MPS which contain the 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 MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatTxMpoaResolveReplyInsufSCResources | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.4 | Counter32 | read-only | The number of MPOA Resolve Replies transmitted by this MPS which contain the 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 MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatTxMpoaResolveReplyInsufEitherResources | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.5 | Counter32 | read-only | The number of MPOA Resolve Replies transmitted by this MPS which contain the 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 MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatTxMpoaResolveReplyUnsupportedInetProt | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.6 | Counter32 | read-only | The number of MPOA Resolve Replies transmitted by this MPS which contain the 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 MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatTxMpoaResolveReplyUnsupportedMacEncaps | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.7 | Counter32 | read-only | The number of MPOA Resolve Replies transmitted by this MPS which contain the 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 MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatTxMpoaResolveReplyUnspecifiedOther | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.8 | Counter32 | read-only | The number of MPOA Resolve Replies transmitted by this MPS which contain the 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 MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatTxMpoaResolveReplyOther | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.9 | Counter32 | read-only | The number of MPOA Resolve Replies transmitted by this MPS which are not counted above. NOTE: this would include NHRP errors. Discontinuities in the value of this counter can occur at re-initialization of the management system, and/or re-initialization of the MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatGiveupTimeExpireds | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.10 | Counter32 | read-only | The number of times the MPS Give up Time (MPS-p6) has expired while waiting for a reply from a re-originated MPOA resolution request, i.e. a reply for a translated NHRP resolution request. Discontinuities in the value of this counter can occur at re-initialization of the management system, and/or re-initialization of the MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatTxMpoaImpRequests | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.11 | Counter32 | read-only | The number of MPOA Cache Imposition Requests transmitted by this MPS. Discontinuities in the value of this counter can occur at re-initialization of the management system, and/or re-initialization of the MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatRxMpoaImpReplyAcks | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.12 | Counter32 | read-only | The number of successful MPOA Cache Imposition Replies received by this MPS which contain 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 MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatRxMpoaImpReplyInsufECResources | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.13 | Counter32 | read-only | The number of MPOA Cache Imposition Replies received by this MPS which contain the 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 MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatRxMpoaImpReplyInsufSCResources | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.14 | Counter32 | read-only | The number of MPOA Cache Imposition Replies received by this MPS which contain the 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 MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatRxMpoaImpReplyInsufEitherResources | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.15 | Counter32 | read-only | The number of MPOA Cache Imposition Replies received by this MPS which contain the 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 MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatRxMpoaImpReplyUnsupportedInetProt | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.16 | Counter32 | read-only | The number of MPOA Cache Imposition Replies received by this MPS which contain the 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 MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatRxMpoaImpReplyUnsupportedMacEncaps | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.17 | Counter32 | read-only | The number of MPOA Cache Imposition Replies received by this MPS which contain the 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 MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatRxMpoaImpReplyUnspecifiedOther | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.18 | Counter32 | read-only | The number of MPOA Cache Imposition Replies received by this MPS which contain the 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 MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatRxMpoaImpReplyOther | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.19 | Counter32 | read-only | The number of MPOA Cache Imposition Replies received by this MPS which are not counted previously. NOTE: this would include NHRP errors. Discontinuities in the value of this counter can occur at re-initialization of the management system, and/or re-initialization of the MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatRxMpoaEgressCachePurgeRequests | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.20 | Counter32 | read-only | The number of MPOA Egress Cache Purges Requests received by this MPS. Discontinuities in the value of this counter can occur at re-initialization of the management system, and/or re-initialization of the MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatTxMpoaEgressCachePurgeReplies | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.21 | Counter32 | read-only | The number of MPOA Egress Cache Purge Replies transmitted by this MPS. Discontinuities in the value of this counter can occur at re-initialization of the management system, and/or re-initialization of the MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatTxMpoaTriggers | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.22 | Counter32 | read-only | The number of MPOA Trigger messages transmitted by this MPS. Discontinuities in the value of this counter can occur at re-initialization of the management system, and/or re-initialization of the MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatTxNhrpResolveRequests | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.23 | Counter32 | read-only | Total count of MPOA Resolution Requests received by the Ingress MPS which were translated to NHRP Resolution Requests and transmitted to the NHS. Discontinuities in the value of this counter can occur at re-initialization of the management system, and/or re-initialization of the MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatRxNhrpResolveReplies | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.24 | Counter32 | read-only | Total count of NHRP Resolution Replies received by the Ingress. Discontinuities in the value of this counter can occur at re-initialization of the management system, and/or re-initialization of the MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatRxNhrpResolveRequests | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.25 | Counter32 | read-only | Total count of NHRP Resolution Requests received by the Egress MPS from the NHS. Discontinuities in the value of this counter can occur at re-initialization of the management system, and/or re-initialization of the MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| C32 mpsStatTxNhrpResolveReplies | 1.3.6.1.4.1.353.5.8.1.1.3.4.1.26 | Counter32 | read-only | Total count of NHRP Resolution Replies transmitted by the Egress MPS to the NHS. Discontinuities in the value of this counter can occur at re-initialization of the management system, and/or re-initialization of the MPS, and at other times, as indicated by the value of mpsDiscontinuityTime. |
| mpsProtocolTable | 1.3.6.1.4.1.353.5.8.1.1.3.5 | not-accessible | List of protocols, per MPS, for which MPOA resolution is enabled. | |
| mpsProtocolEntry | 1.3.6.1.4.1.353.5.8.1.1.3.5.1 | not-accessible | Each row indicates one protocol for which an MPS will perform MPOA resolution. If the LECS was contacted for configuration information, and the MPS-p3's control octet is set to Enable, 0x01, then protocol values retrieved from the LECS are reflected in this table and the mpsLECSValue object will be (1) true. Also, the user or agent can create rows which appropriately correspond to the MPS denoted by mpsIndex, and the mpsLECSValue object will be set to (2) false. NOTE: if the LECS does not return information for the MPS-p3 parameter, or if in manual mode, the user or agent should create at least one entry for the corresponding MPS. Both, LECS and user and/or agent created rows may exist in this Table. | |
| NUM mpsInternetworkLayerProtocol | 1.3.6.1.4.1.353.5.8.1.1.3.5.1.1 | InternetworkAddrType | not-accessible | MPS-p3 A protocol on which to perform MPOA resolution. |
| T/F mpsLECSValue | 1.3.6.1.4.1.353.5.8.1.1.3.5.1.2 | TruthValue | read-only | This object reflects if the current entry is due to a retrieval from the LECS or not. If this entry is due to the LECS, then true(1) is the value for this object, otherwise, false (2). |
| ROW mpsProtocolRowStatus | 1.3.6.1.4.1.353.5.8.1.1.3.5.1.3 | RowStatus | read-create | This object allows network managers to enable resolution for the `mpsInternetworkLayerProtocol'. |
| mpsMappingTable | 1.3.6.1.4.1.353.5.8.1.1.3.6 | not-accessible | A table mapping the `lecIndex' values of LANE Clients to the `mpsIndex' values of corresponding MPOA Servers. | |
| mpsMappingEntry | 1.3.6.1.4.1.353.5.8.1.1.3.6.1 | not-accessible | Each row defines one lecIndex --> mpsIndex mapping. The mpsIndex that a lecIndex maps to is not necessarily unique. In other words, there can be multiple LECs associated with one MPS. | |
| ROW mpsMappingRowStatus | 1.3.6.1.4.1.353.5.8.1.1.3.6.1.1 | RowStatus | read-create | Allows creation, enabling/disabling of this row. |
| MPS mpsMappingIndex | 1.3.6.1.4.1.353.5.8.1.1.3.6.1.2 | MpsIndex | read-create | The mpsMappingIndex of the MPOA Server that is associated with this LEC. The mpsMappingIndex corresponds to the mpsIndex. |
| mpsIngressCacheTable | 1.3.6.1.4.1.353.5.8.1.1.3.7 | not-accessible | This table tracks all the Ingress Cache information of the MPSs which this agents manages. | |
| mpsIngressCacheEntry | 1.3.6.1.4.1.353.5.8.1.1.3.7.1 | not-accessible | A entry contains parameters and state variables for a row in a MPS's Ingress Cache. | |
| NUM mpsIngressCacheDestInternetworkAddrType | 1.3.6.1.4.1.353.5.8.1.1.3.7.1.1 | InternetworkAddrType | read-only | The type of internetwork layer address of the Destination Address. |
| NUM mpsIngressCacheDestAddr | 1.3.6.1.4.1.353.5.8.1.1.3.7.1.2 | InternetworkAddr | read-only | The Ingress MPS Destination Internetwork Layer Address. |
| I32 mpsIngressCachePrefixLen | 1.3.6.1.4.1.353.5.8.1.1.3.7.1.3 | Integer32 | read-only | The Prefix Length of the mpsIngressCacheDestAddr. |
| INT mpsIngressCacheEntryState | 1.3.6.1.4.1.353.5.8.1.1.3.7.1.4 | INTEGER | read-only | The state of this MPS Ingress cache. The states are: doesNotExist (1) -- the state is not yet available inactive (2) -- state exists, entry is not yet active For example,if using the Finite State Machine in Appendix I.3, the state resolving is `inactive'. active (3) -- state exists, entry is active. For example,if using the Finite State Machine in Appendix I.3, the state resolved is `active' state. negative (4) -- state exists, entry is negative. For example,if using the Finite State Machine in Appendix I.3, the state purging is `negative'. |
| NUM mpsIngressCacheSrcInternetworkAddrType | 1.3.6.1.4.1.353.5.8.1.1.3.7.1.5 | InternetworkAddrType | read-only | The type of internetwork layer address of the Source Address. |
| NUM mpsIngressCacheSrcAddr | 1.3.6.1.4.1.353.5.8.1.1.3.7.1.6 | InternetworkAddr | read-only | The Ingress MPS Source Internetwork Layer Address. |
| ATM mpsIngressCacheSourceMpcCtrlAtmAddr | 1.3.6.1.4.1.353.5.8.1.1.3.7.1.7 | AtmAddr | read-only | The ATM Address from the source of this MPOA request. In other words, the Ingress MPC's Control Atm Address. |
| ATM mpsIngressCacheResolvedAtmAddr | 1.3.6.1.4.1.353.5.8.1.1.3.7.1.8 | AtmAddr | read-only | The ATM Address which has been resolved by an Egress MPC. |
| NUM mpsIngressCacheHoldTime | 1.3.6.1.4.1.353.5.8.1.1.3.7.1.9 | TimeInterval | read-only | Time interval that this value is valid. |
| I32 mpsIngressCacheMpoaRequestId | 1.3.6.1.4.1.353.5.8.1.1.3.7.1.10 | Integer32 | read-only | The request ID contained in the MPOA resolution request from the local Ingress MPC. |
| I32 mpsIngressCacheNhrpRequestId | 1.3.6.1.4.1.353.5.8.1.1.3.7.1.11 | Integer32 | read-only | The request ID which this MPS generates to identify the NHRP resolution request. |
| INT mpsIngressCacheServiceCategory | 1.3.6.1.4.1.353.5.8.1.1.3.7.1.12 | INTEGER | read-only | The service categories supported for this shortcut. |
| mpsEgressCacheTable | 1.3.6.1.4.1.353.5.8.1.1.3.8 | not-accessible | This table contains information regarding the Egress MPOA Server Cache Table. | |
| mpsEgressCacheEntry | 1.3.6.1.4.1.353.5.8.1.1.3.8.1 | not-accessible | An entry represents an entry in the MPS's Egress cache Table which keeps track of the state of the impositions. | |
| INT mpsEgressCacheId | 1.3.6.1.4.1.353.5.8.1.1.3.8.1.1 | INTEGER | read-only | The id which identifies this cache entry. |
| NUM mpsEgressCacheDestInternetworkAddrType | 1.3.6.1.4.1.353.5.8.1.1.3.8.1.2 | InternetworkAddrType | read-only | The destination protocol address type. |
| NUM mpsEgressCacheDestAddr | 1.3.6.1.4.1.353.5.8.1.1.3.8.1.3 | InternetworkAddr | read-only | The destination protocol address. |
| INT mpsEgressCachePrefixLen | 1.3.6.1.4.1.353.5.8.1.1.3.8.1.4 | INTEGER | read-only | The destination prefix length. |
| NUM mpsEgressCacheHoldTime | 1.3.6.1.4.1.353.5.8.1.1.3.8.1.5 | TimeInterval | read-only | Time interval that this value is valid. |
| INT mpsEgressCacheEntryState | 1.3.6.1.4.1.353.5.8.1.1.3.8.1.6 | INTEGER | read-only | The present states of this MPS egress cache entry. The states are: doesNotExist (1) -- the state is not yet available inactive (2) -- state exists, entry is not yet active For example,if using the Finite State Machine in Appendix 1.4, the state imposing is `inactive'. active (3) -- state exists, entry is active. For example,if using the Finite State Machine in Appendix 1.4, the state imposed is `active' state. negative (4) -- state exists, entry is negative. For example,if using the Finite State Machine in Appendix 1.4, the states purging and clearing are `negative'. |
| OCT mpsEgressCacheDataLinkHeader | 1.3.6.1.4.1.353.5.8.1.1.3.8.1.7 | OCTET STRING | read-only | Data-Link Layer Header. |
| I32 mpsEgressCacheElanId | 1.3.6.1.4.1.353.5.8.1.1.3.8.1.8 | Integer32 | read-only | The elan id that this Cache Imposition is sent on. |
| ATM mpsEgressCacheSourceClientAtmAddr | 1.3.6.1.4.1.353.5.8.1.1.3.8.1.9 | AtmAddr | read-only | The Ingress NHC's Atm Address used in the original cache imposition. |
| I32 mpsEgressCacheNhrpRequestId | 1.3.6.1.4.1.353.5.8.1.1.3.8.1.10 | Integer32 | read-only | The request id from the original NHRP Resolution Request, may be only useful in the Resolving State. |
| I32 mpsEgressCacheMpoaRequestId | 1.3.6.1.4.1.353.5.8.1.1.3.8.1.11 | Integer32 | read-only | The new request id which is generated for this imposition's request, may be only useful in the Resolving State. |
| INT mpsEgressCacheServiceCategory | 1.3.6.1.4.1.353.5.8.1.1.3.8.1.12 | INTEGER | read-only | The service categories supported for this shortcut. |
| NUM mpsEgressCacheNextHopInternetworkAddrType | 1.3.6.1.4.1.353.5.8.1.1.3.8.1.13 | InternetworkAddrType | read-only | The NextHop protocol address type. |
| NUM mpsEgressCacheNextHopAddr | 1.3.6.1.4.1.353.5.8.1.1.3.8.1.14 | InternetworkAddr | read-only | The NextHop protocol address. |
| mpsMpcTable | 1.3.6.1.4.1.353.5.8.1.1.3.9 | not-accessible | This read-only table contains information about the MPCs that these MPSs know about. | |
| mpsMpcEntry | 1.3.6.1.4.1.353.5.8.1.1.3.9.1 | not-accessible | A row created by an MPS. The MPS learns about the MPC and creates a row. | |
| MPC mpsMpcIndex | 1.3.6.1.4.1.353.5.8.1.1.3.9.1.1 | MpcIndex | not-accessible | The local index for the mpc represented by this entry |
| ATM mpsMpcCtrlAtmAddr | 1.3.6.1.4.1.353.5.8.1.1.3.9.1.2 | AtmAddr | read-only | MPC control ATM address |
| 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 | |||
| mpoaDeviceTypeGroup | 1.3.6.1.4.1.353.5.8.1.2.1.1 | A collection of objects which exists when the MPOA device learns the MPOA device type and MPOA control addresses of neighboring MPOA devices using the LANEv2 Device Type TLV. | ||
| mpoaDeviceTypeMpsMacGroup | 1.3.6.1.4.1.353.5.8.1.2.1.2 | A collection of objects which is present when the MPOA device learns the MPOA device type and MPOA control addresses of neighboring MPOA devices using the LANEv2 Device Type TLV. | ||
| mpcConfigGroup | 1.3.6.1.4.1.353.5.8.1.2.1.3 | A collection of objects used for creating and configuring MPOA Clients. | ||
| mpcActualGroup | 1.3.6.1.4.1.353.5.8.1.2.1.4 | A collection of objects describing the status and operational parameters of the managed MPC. | ||
| mpcDataAtmAddressGroup | 1.3.6.1.4.1.353.5.8.1.2.1.5 | A collection of objects which describe the set of data ATM addresses for the MPCs. | ||
| mpcStatisticsGroup | 1.3.6.1.4.1.353.5.8.1.2.1.6 | A collection of objects that provide statistics on the MPOA protocol parameters. | ||
| mpcProtocolGroup | 1.3.6.1.4.1.353.5.8.1.2.1.7 | A collection of objects to specify which parameters this MPC is enabled for. | ||
| mpcMappingGroup | 1.3.6.1.4.1.353.5.8.1.2.1.8 | A collection of objects to map from LEC to MPC | ||
| mpcMpsGroup | 1.3.6.1.4.1.353.5.8.1.2.1.9 | A collection of objects which aid the MPCs to track information for all the MPSs which are known by the MPCs. | ||
| mpcMpsMacAddressGroup | 1.3.6.1.4.1.353.5.8.1.2.1.10 | A collection of objects which aid the MPCs to track MAC Address information for all the MPSs which are known by the MPCs. | ||
| mpcIngressCacheTotalPacketGroup | 1.3.6.1.4.1.353.5.8.1.2.1.11 | A collection of objects which count the total number of packets transmitted over MPC short cuts. | ||
| mpcIngressCacheTotalOctetGroup | 1.3.6.1.4.1.353.5.8.1.2.1.12 | A collection of objects which count the total number of octets transmitted over MPC short cuts. | ||
| mpcIngressCacheGroup | 1.3.6.1.4.1.353.5.8.1.2.1.13 | A collection of objects used to monitor the MPOA ingress cache. | ||
| mpcEgressCacheTotalPacketGroup | 1.3.6.1.4.1.353.5.8.1.2.1.14 | A collection of objects which count the total number of packets received by MPC short cuts. | ||
| mpcEgressCacheTotalOctetGroup | 1.3.6.1.4.1.353.5.8.1.2.1.15 | A collection of objects which count the total number of octets received by MPC short cuts. | ||
| mpcEgressCacheGroup | 1.3.6.1.4.1.353.5.8.1.2.1.16 | A collection of objects used to monitor the MPOA egress cache. | ||
| mpsConfigGroup | 1.3.6.1.4.1.353.5.8.1.2.1.17 | A collection of objects used for creating and configuring MPOA Servers. | ||
| mpsActualGroup | 1.3.6.1.4.1.353.5.8.1.2.1.18 | A collection of objects describing the status and operational parameters of the managed MPS. | ||
| mpsStatisticsGroup | 1.3.6.1.4.1.353.5.8.1.2.1.19 | A collection of objects that provide statistics on the MPOA Server protocol parameters. | ||
| mpsProtocolGroup | 1.3.6.1.4.1.353.5.8.1.2.1.20 | A collection of objects to specify which parameters this MPS is enabled for. | ||
| mpsMappingGroup | 1.3.6.1.4.1.353.5.8.1.2.1.21 | A collection of objects to map from MPSs to LECs. | ||
| mpsMpcGroup | 1.3.6.1.4.1.353.5.8.1.2.1.22 | A collection of objects which aid the MPSs to track information for all the MPCs which are known by the MPSs. | ||
| mpsIngressCacheGroup | 1.3.6.1.4.1.353.5.8.1.2.1.23 | A collection of objects to monitor the MPS ingress cache. | ||
| mpsEgressCacheGroup | 1.3.6.1.4.1.353.5.8.1.2.1.24 | A collection of objects to monitor MPS's egress cache parameters. | ||
| mpcMpsMultipleMacAddressGroup | 1.3.6.1.4.1.353.5.8.1.2.1.25 | A collection of objects which aid the MPCs to track MAC Address information for all the MPSs which are used during flow detection by the MPCs. | ||
| mpoaMIBCompliances | 1.3.6.1.4.1.353.5.8.1.2.2 | |||
| mpoaMpcMibBasicCompliance | 1.3.6.1.4.1.353.5.8.1.2.2.1 | The basic implementation requirements for SNMP entities which support MPOA Clients. | ||
| mpoaMpcMibAdvancedCompliance | 1.3.6.1.4.1.353.5.8.1.2.2.2 | The advanced implementation requirements for SNMP entities which support MPOA Clients. | ||
| mpoaMpcMibAdvancedPlusOctetsCompliance | 1.3.6.1.4.1.353.5.8.1.2.2.3 | The AdvancedPlusOctets implementation requirements for SNMP entities which support MPOA Clients. This includes supporting the 64 bit octet counters. | ||
| mpoaMpsMibBasicCompliance | 1.3.6.1.4.1.353.5.8.1.2.2.4 | The implementation requirements for SNMP entities which support MPOA Servers. | ||
| mpoaMpsMibAdvancedCompliance | 1.3.6.1.4.1.353.5.8.1.2.2.5 | The advanced implementation requirements for SNMP entities which support MPOA Servers. |
RFC description
ATM Forum MPOA (Multiprotocol Over ATM) MIB for managing MPOA clients and servers in ATM networks.
Start monitoring Vendor-neutral ATM Forum standard (ATM-capable router/switch, MPOA client/server) 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.