MPOA-MIB
AI MIB Summary
The MPOA-MIB provides management interfaces for Multiprotocol Over ATM (MPOA) clients and servers, specifically monitoring MPC MPS MAC address mappings and session states. It facilitates the tracking of ATM virtual circuit associations and client-server interactions within legacy MPOA v1.1 environments, utilizing the `mpcMpsMultipleMacAddressTable` to replace the obsolete single-address table.
This module defines a portion of the management information base (MIB) for managing Multiprotocol Over ATM clients and servers which was revised based on MPOA Errata contained in MPOA v1.1.
The difference between af-mpoa-0092.000 and this version is the mpcMpsMacAddressTable has been obsoleted. The mpcMpsMultipleMacAddressTable has been added. The mpcMpsMultipleMacAddressTable replaces the mpcMpsMacAddressTable.
Main OID:
mpoaMIB.1.3.6.1.4.1.353.5.8.1
235
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
235 total| Object Name |
|---|
atmForum OBJECT IDENTIFIER .1.3.6.1.4.1.353 |
atmForumNetworkManagement OBJECT IDENTIFIER .1.3.6.1.4.1.353.5 |
atmfMpoa OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8 |
mpoaMIBThis module defines a portion of the management
information base (MIB) for managing Multiprotocol Over
ATM clients and servers which was revised based
on MPOA Errata contained in MPOA v1.1.
The difference between af-mpoa-0092.000 and this
version is the mpcMpsMacAddressTable has been
obsoleted. The mpcMpsMultipleMacAddressTable
has been added. The mpcMpsMultipleMacAddressTable
replaces the mpcMpsMacAddressTable. MODULE-IDENTITY .1.3.6.1.4.1.353.5.8.1 |
mpoaMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.1 |
mpoaCommonObjects OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.1.1 |
deviceTypeTableThe 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. SEQUENCE OF DeviceTypeEntry .1.3.6.1.4.1.353.5.8.1.1.1.1 |
deviceTypeEntryAn 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. DeviceTypeEntry .1.3.6.1.4.1.353.5.8.1.1.1.1.1 |
deviceTypeIndexIndex 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. INTEGER .1.3.6.1.4.1.353.5.8.1.1.1.1.1.1 |
deviceTypeLecIndexLecIndex of LEC that supports this
data ATM addressro LecIndex .1.3.6.1.4.1.353.5.8.1.1.1.1.1.2 |
deviceTypeRemoteLecAtmAddressThe ATM address learned by LE ARP.ro AtmAddr .1.3.6.1.4.1.353.5.8.1.1.1.1.1.3 |
deviceTypeTypesame as the TLVro Enumeration .1.3.6.1.4.1.353.5.8.1.1.1.1.1.4 |
deviceTypeMpsAtmAddressAssociated MPS address, zeros for non-MPOA and mpcro AtmAddr .1.3.6.1.4.1.353.5.8.1.1.1.1.1.5 |
deviceTypeMpcAtmAddressAssociated MPC address, zeros for non-MPOA & mpsro AtmAddr .1.3.6.1.4.1.353.5.8.1.1.1.1.1.6 |
deviceTypeMpsMacAddressTableThis table contains MPS MAC Address information gathered from
the MPOA DeviceTypeTLV. SEQUENCE OF DeviceTypeMpsMacAddressEntry .1.3.6.1.4.1.353.5.8.1.1.1.2 |
deviceTypeMpsMacAddressEntryEach entry represents an MPS MAC Address. Each entry
corresponds to a deviceTypeIndex value for which the
deviceTypeType attribute is `mps' or `mpsAndMpc'. DeviceTypeMpsMacAddressEntry .1.3.6.1.4.1.353.5.8.1.1.1.2.1 |
deviceTypeMpsMacAddressMPS MAC address contained in the Device Type TLV which
is identified by the deviceTypeIndex in the deviceTypeTable.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.1.2.1.1 |
mpcObjects OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.1.2 |
mpcNextIndexThis object contains an appropriate value to
be used for mpcIndex when creating entries in
the mpcConfigTable. The value 0 indicates that
no new rows can be created. Otherwise, it is
recommended that values are assigned contiguously,
starting from 1.
MPC creation by a Manager: To obtain the mpcIndex value
for a new entry, the manager issues a management protocol
retrieval operation to obtain the current value of this
object. If the value retrieved is 0 (zero), the manager
cannot create a row.
After each retrieval of a non-zero value, the manager
should issue a management protocol SET operation using
the value just retrieved. If the SET is successful,
the agent should update the value to the next unassigned
index, or zero if appropriate.
NOTE: the manager may also issue a set on this object
with a value of its own choosing. If the set is successful,
the manager may use this value for the mpcIndex. In this
case, the agent would update the value to the next
unassigned index, or zero if appropriate.
The definition of `next unassigned index' is any
mpcNextIndex value that has not yet been set by a manager,
or reserved by the agent (see next paragraph), since this
agent was last re-initialized.
MPC creation by an Agent: When a row in the
mpcConfigTable is created by an agent, the agent should
reserve the value of the index by updating the value of
this object to the next unassigned index
or zero if appropriate. Thus, a manager will not
be able to set an index reserved by an agent.
In the situation of an agent re-initialization, all currently
used mpcIndexes must be preserved.
In other words, the Agent should store in non-volatile memory
all of the currently used mpcIndexes (along with all necessary
configuration information from the mpcConfigTable). When the
agent is re-initialized, the mpcNextIndex value is
any valid Integer32 value which is not being used
as an mpcIndex, except 0 which maintains its original
definition of indicating that a row cannot be created.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.1 |
mpcConfigTableThe MPOA Client Configuration Table.
This table contains configuration information
for all MPOA Clients which this agent manages. SEQUENCE OF MpcConfigEntry .1.3.6.1.4.1.353.5.8.1.1.2.2 |
mpcConfigEntryMPOA Client Configuration Entry.
Each entry contains configuration information
for one MPOA Client. The configuration information, including
the mpcIndex, must be restored after a re-initialization of an
MPC or a re-initialization of the SNMP agent. MpcConfigEntry .1.3.6.1.4.1.353.5.8.1.1.2.2.1 |
mpcIndexA value which uniquely identifies this conceptual
row in the mpcConfigTable. The `mpcNextIndex' object
needs to be used to determine the value of this object.
A row cannot be added, unless the mpcCtrlAtmAddress is unique.
In the event of either an MPC re-initialization or an agent
re-initialization, the value of this mpcIndex must remain the
same. In other words, the row needs to be saved and restored
in the event of an MPC or SNMP Agent re-initialization. MpcIndex .1.3.6.1.4.1.353.5.8.1.1.2.2.1.1 |
mpcRowStatusThis object allows creation and deletion of
MPOA Clients.
Within each conceptual mpcConfigTable row, writable objects
may be modified, regardless of the value of mpcRowStatus.
It is not necessary to set a row's status to `notInService'
first.
A row cannot be created, unless the mpcAtmCtrlAddress
in this table is unique.
When an MPOA Client is created via this object,
it will initially have
`mpcActualState' = `initialState'rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.2.1.2 |
mpcConfigModeIndicates whether this MPC should auto-configure
the next time it is (re-)initialized.
During the (re-)initialization of this MPC, if
the mode is automatic(1), the LECS is contacted and
requests are made for all MPC-p* parameters.
Otherwise, if the mode is manual(2), the values of the
configuration parameters are obtained from the
mpcConfigTableand the mpcProtocolTable. In other words, when
the MPC is first initialized, it can use the default or
configured values from the mpcConfigTable and
mpcProtocolTable. If the mode is manual (2), no further
action is required. If the mode is automatic (1), then
the LECS should be contacted and all available MPC-p1
to MPC-p6 parameters would be retrieved.
These parameters would then overwrite the existing MPC-p1 to
MPC-p6 parameters. The actual values are reflected in the
mpcActualTable.rw Enumeration .1.3.6.1.4.1.353.5.8.1.1.2.2.1.3 |
mpcCtrlAtmAddrThe MPC's Control ATM Address. There exists one
Control ATM Address per MPC, therefore, the value
of this entry is unique within the table. The control ATM
Address is the address which is used by the MPC in its requests
to the MPS. The value of this object should not change, once
created.rw AtmConfigAddr .1.3.6.1.4.1.353.5.8.1.1.2.2.1.4 |
mpcSCSetupFrameCountThis represents the MPC-p1 Short-cut setup frame count
parameter.
The MPC-p1 value is frames measured over mpcSCFrameTime seconds.
Flow detection is protocol independent. i.e. all network layers
mpcProtocolEntries for this MPC share the flow rate
specification.
A value of 1 causes all flows to initiate resolution/shortcut
process.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.2.1.5 |
mpcSCSetupFrameTimeMPC-p2 Short-cut setup frame time, in seconds.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.2.1.6 |
mpcInitialRetryTimeMPC-p4 is the initial value for the retry time out
period used for timing out MPOA Resolution Requests
in seconds. Retry time consists of this initial
time-out (MPC-p4) and a retry multiplier (MPC-c1).
If a response is not received, then another request
is sent with a timeout of `retry time' * MPC-c1
seconds, or until mpcRetryTimeMaximum.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.2.1.7 |
mpcRetryTimeMaximumMPC-p5 cumulative max value for Retry Time (MPC-p4).
Retries are attempted at intervals determined by the
algorithm described in the definition of mpcIntialRetryTime.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.2.1.8 |
mpcHoldDownTimeMPC-p6 Hold Down Time
Minimum time to wait before reinitiating
a failed resolution attempt. Default is
mpcRetryTimeMaximum * 4.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.2.1.9 |
mpcActualTableMPOA Client Actual Table.
A read-only table which contains state
information and reflects the actual values which
these MPOA Clients are using. The actual
values may differ from the configured values.
For example, the mpcConfigMode takes affect
only during (re-)initialization of the MPC.
The MPC-p1 to MPC-p6 parameters may differ
from the configured values because, if the
MPC was (re-)initialized and the mpcConfigMode
was set to automatic (1) then some, perhaps all,
of the MPC-p1 to MPC-p6 parameters were retrieved
from the LECS and the values from the LECS may
differ from the configured/default values of the
mpcConfigTable. NOTE: after re-initialization
a set to an object in the mpcConfigTable which
changes the value of the object will be reflect
in this Table, except for a set to the
mpcConfigMode which takes effect only during
re-initialization. SEQUENCE OF MpcActualEntry .1.3.6.1.4.1.353.5.8.1.1.2.3 |
mpcActualEntryAn entry in the MPC Actual Table.
An entry represents a specific MPOA Client's
state information and the actual values
which are being used by the MPOA Client.
For example, the corresponding mpcConfigEntry contains
default and/or configured parameters, if mpcConfigMode was
set to manual, then these are the objects values' which are
reflected for the mpcActualEntry. However, if the
mpcConfigMode is automatic, then the mpcActualEntry
will be all the corresponding mpcConfigEntry's object,
excluding any objects which were retrieved from the LECS.
In other words, the objects retrieved from the LECS during
the (re-)initialization of the MPC overwrite any of the default
and/or configured values.
NOTE: any subsequent `set' to the configured values, e.g. an
SNMP
set operation, which is successful could result in a change to an
mpcConfigTable value, and will be reflected in this table as
well. MpcActualEntry .1.3.6.1.4.1.353.5.8.1.1.2.3.1 |
mpcActualStateThis object indicates the actual state
of the MPOA Client.ro Enumeration .1.3.6.1.4.1.353.5.8.1.1.2.3.1.1 |
mpcDiscontinuityTimeThe value of sysUpTime on the most recent occasion at
which any one or more of this MPC's counters
experienced a discontinuity. The relevant counters
are the specific instances associated with this
MPC. If discontinuities have not occurred since the
last re-initialization of the local management subsystem,
then this object contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.3.1.2 |
mpcActualConfigModeIndicates whether this MPC auto-configured
when it was last (re-)initialized.ro Enumeration .1.3.6.1.4.1.353.5.8.1.1.2.3.1.3 |
mpcActualSCSetupFrameCountMPC-p1 Short-cut setup frame count.
In frames measured over mpcShortcutFrameTime seconds.
Flow detection is protocol independent. i.e. all
network layers mpcProtocolEntry share the flow rate
specification.
A value of 1 implies that resolutions for short-cuts
are attempted for all flows.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.3.1.4 |
mpcActualSCSetupFrameTimeActual MPC-p2 Short-cut setup frame time, in seconds.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.3.1.5 |
mpcActualInitialRetryTimeActual MPC-p4 is initial value for the
retry time out.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.3.1.6 |
mpcActualRetryTimeMaximumMPC-p5 cumulative maximum value for Retry Time (MPC-p4).
Retries are attempted at intervals determined by the
algorithm described in the definition of
mpcActualInitialRetryTime.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.3.1.7 |
mpcActualHoldDownTimeMPC-p6 Hold Down Time
Minimum time to wait before reinitiating a failed
resolution attempt. The default value is
mpcRetryTimeMaximum * 4.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.3.1.8 |
mpcDataAtmAddressTableA table which shows all the data ATM addresses
associated with all MPOA Clients. SEQUENCE OF MpcDataAtmAddressEntry .1.3.6.1.4.1.353.5.8.1.1.2.4 |
mpcDataAtmAddressEntryEach 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. MpcDataAtmAddressEntry .1.3.6.1.4.1.353.5.8.1.1.2.4.1 |
mpcDataAtmAddressA data ATM Address which is associated with
an MPOA Client specified by the mpcIndex. AtmAddr .1.3.6.1.4.1.353.5.8.1.1.2.4.1.1 |
mpcDataAtmAddressRowStatusThis 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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.4.1.2 |
mpcStatisticsTableA read-only table which contains statistical
information for all MPOA Clients that
this agent manages. SEQUENCE OF MpcStatisticsEntry .1.3.6.1.4.1.353.5.8.1.1.2.5 |
mpcStatisticsEntryEach row in this table contains statistics
for one MPOA Client. MpcStatisticsEntry .1.3.6.1.4.1.353.5.8.1.1.2.5.1 |
mpcStatTxMpoaResolveRequestsThe number of MPOA Resolve Requests transmitted
by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.1 |
mpcStatRxMpoaResolveReplyAcksThe number of positively acknowledged MPC
Resolved Replies received by this MPC with an MPOA
CIE Code of 0x00 (Success).
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and/or re-
initialization
of the MPC, and at other times, as indicated by the value of
mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.2 |
mpcStatRxMpoaResolveReplyInsufECResourcesThe number of MPOA Resolution Replies received with
an MPOA CIE Code of 0x81, `Insufficient resources to
accept egress cache entry'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.3 |
mpcStatRxMpoaResolveReplyInsufSCResourcesThe number of MPOA Resolution Replies received with
an MPOA CIE Code of 0x82, `Insufficient resources to
accept the shortcut'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.4 |
mpcStatRxMpoaResolveReplyInsufEitherResourcesThe number of MPOA Resolution Replies received with
an MPOA CIE Code of 0x83, `Insufficient resources to
accept either shortcut or egress cache entry'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.5 |
mpcStatRxMpoaResolveReplyUnsupportedInetProtThe number of MPOA Resolution Replies received with
an MPOA CIE Code of 0x84, `Unsupported Internework
Layer protocol'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.6 |
mpcStatRxMpoaResolveReplyUnsupportedMacEncapsThe number of MPOA Resolution Replies received with
an MPOA CIE Code of 0x85, `Unsupported MAC layer encapsulation'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.7 |
mpcStatRxMpoaResolveReplyUnspecifiedOtherThe number of MPOA Resolution Replies received with
an MPOA CIE Code of 0x88, `Unspecified/Other'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.8 |
mpcStatRxMpoaImpRequestsThe number of MPOA Cache Imposition Requests received
by this MPC.
Discontinuities in the value of this counter can occur at re-
initialization
of the management system, and/or re-initialization of the MPC,
and at
other times, as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.9 |
mpcStatTxMpoaImpReplyAcksThe number of successful MPOA Cache Imposition replies
transmitted by this MPC with an MPOA CIE Code of 0x00
`Success'.
Discontinuities in the value of this counter can occur at re-
initialization
of the management system, and/or re-initialization of the MPC,
and at
other times, as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.10 |
mpcStatTxMpoaImpReplyInsufECResourcesThe number of MPOA Cache Imposition Replies transmitted with
an MPOA CIE Code of 0x81, `Insufficient resources to
accept egress cache entry'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.11 |
mpcStatTxMpoaImpReplyInsufSCResourcesThe number of MPOA Imposition Replies transmitted with
an MPOA CIE Code of 0x82, `Insufficient resources to
accept shortcut'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.12 |
mpcStatTxMpoaImpReplyInsufEitherResourcesThe number of MPOA Imposition Replies transmitted with
an MPOA CIE Code of 0x83, `Insufficient resources to
accept either shortcut or egress cache entry'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.13 |
mpcStatTxMpoaImpReplyUnsupportedInetProtThe number of MPOA Imposition Replies transmitted with
an MPOA CIE Code of 0x84, `Unsupported Internetwork Layer
protocol'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.14 |
mpcStatTxMpoaImpReplyUnsupportedMacEncapsThe number of MPOA Imposition Replies transmitted with
an MPOA CIE Code of 0x85, `Unsupported MAC Layer
encapsulation'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.15 |
mpcStatTxMpoaImpReplyUnspecifiedOtherThe number of MPOA Imposition Replies transmitted with
an MPOA CIE Code of 0x88, `Unspecified/Other'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.16 |
mpcStatTxMpoaEgressCachePurgeRequestsThe number of MPOA Egress Cache Purge Requests transmitted
by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.17 |
mpcStatRxMpoaEgressCachePurgeRepliesThe number of MPOA Egress Cache Purge Replies received by
this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.18 |
mpcStatRxMpoaKeepAlivesThe number of MPOA Keep Alive messages received by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.19 |
mpcStatRxMpoaTriggersThe number of MPOA Trigger messages received by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.20 |
mpcStatRxMpoaDataPlanePurgesThe number of MPOA Data Plane Purge messages received
by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.21 |
mpcStatTxMpoaDataPlanePurgesThe number of MPOA Data Plane Purge messages transmitted
by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.22 |
mpcStatRxNhrpPurgeRequestsThe number of Purge Requests received by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.23 |
mpcStatTxNhrpPurgeRepliesThe number of Purge Replies transmitted by this MPC.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.24 |
mpcStatRxErrUnrecognizedExtensionsThe number of Error Indication packets received by
this MPC with the error code `Unrecognized Extension'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.25 |
mpcStatRxErrLoopDetectedsThe number of Error Indication packets received by
this MPC with the error code `Loop Detected'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.26 |
mpcStatRxErrProtoAddrUnreachablesThe number of Error Indication packets received by this
MPC with the error code `Protocol Address Unreachable'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.27 |
mpcStatRxErrProtoErrorsThe number of Error Indication packets received by
this MPC with the error code `Protocol Errors'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.28 |
mpcStatRxErrSduSizeExceededsThe number of Error Indication packets received by
this MPC with the error code `SDU Size Exceeded'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.29 |
mpcStatRxErrInvalidExtensionsThe number of Error Indication packets received by
this MPC with the error code `Invalid Extensions'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.30 |
mpcStatRxErrInvalidRepliesThe number of Error Indication packets received by
this MPC with the error code `Invalid Reply'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.31 |
mpcStatRxErrAuthenticationFailuresThe number of Error Indication packets received by
this MPC with the error code `Authentication Failure'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.32 |
mpcStatRxErrHopCountExceededsThe number of Error Indication packets received by
this MPC with the error code `Hop Count Exceeded'.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and/or
re-initialization of the MPC, and at other times,
as indicated by the value of mpcDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.5.1.33 |
mpcProtocolTableList of protocols, per MPC, for which flow
detection is enabled SEQUENCE OF MpcProtocolEntry .1.3.6.1.4.1.353.5.8.1.1.2.6 |
mpcProtocolEntryEach 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. MpcProtocolEntry .1.3.6.1.4.1.353.5.8.1.1.2.6.1 |
mpcFlowDetectProtocolThe 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. InternetworkAddrType .1.3.6.1.4.1.353.5.8.1.1.2.6.1.1 |
mpcLECSValueThis 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).ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.6.1.2 |
mpcProtocolRowStatusThis object is used by an agent or manager to
create, delete or modify a row in this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.6.1.3 |
mpcMappingTableA table mapping the `lecIndex' values of
LANE Clients to the `mpcIndex' values of
corresponding MPOA Clients. SEQUENCE OF MpcMappingEntry .1.3.6.1.4.1.353.5.8.1.1.2.7 |
mpcMappingEntryEach row defines one lecIndex
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). MpcMappingEntry .1.3.6.1.4.1.353.5.8.1.1.2.7.1 |
mpcMappingRowStatusThis object is used by an agent or manager to create, delete
or modify a row in this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.7.1.1 |
mpcMappingIndexThe mpcIndex of the MPOA Client that is performing
flow detection for the LANE Client represented by
the lecIndex.rw MpcIndex .1.3.6.1.4.1.353.5.8.1.1.2.7.1.2 |
mpcMpsTableThis is a read-only table which contains
information about the MPSs that these MPCs
know about. SEQUENCE OF MpcMpsEntry .1.3.6.1.4.1.353.5.8.1.1.2.8 |
mpcMpsEntryA row created by an MPC. The MPC learns about
an MPS and creates a row. MpcMpsEntry .1.3.6.1.4.1.353.5.8.1.1.2.8.1 |
mpcMpsIndexThe MPS's index which is used to identify
a row in this table. MpsIndex .1.3.6.1.4.1.353.5.8.1.1.2.8.1.1 |
mpcMpsAtmAddrThe Control ATM Address of the MPSro AtmAddr .1.3.6.1.4.1.353.5.8.1.1.2.8.1.2 |
mpcMpsMacAddressTableThis is a read-only table which contains
information about all the MPSs' MAC Addresses
that these MPCs know about.obsolete SEQUENCE OF MpcMpsMacAddressEntry .1.3.6.1.4.1.353.5.8.1.1.2.9 |
mpcMpsMacAddressEntryA row is created by an MPC. The MPC learns about an
MPS's MAC Address and creates a row.obsolete MpcMpsMacAddressEntry .1.3.6.1.4.1.353.5.8.1.1.2.9.1 |
mpcLecIndexThe lecIndex which represents the associated LEC.obsolete LecIndex .1.3.6.1.4.1.353.5.8.1.1.2.9.1.1 |
mpcMpsMacAddressThe MAC Address of the MPS.roobsolete MacAddress (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.9.1.2 |
mpcIngressCacheTxTotalPacketsThe total number of packets transmitted over MPC Short Cuts.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.10 |
mpcIngressCacheTxTotalOctetsThe total number of octets transmitted over MPC Short Cuts.ro Counter64 .1.3.6.1.4.1.353.5.8.1.1.2.11 |
mpcIngressCacheTableThis table contains information for MPC Caches for
the ingress MPC. SEQUENCE OF MpcIngressCacheEntry .1.3.6.1.4.1.353.5.8.1.1.2.12 |
mpcIngressCacheEntryAn entry contains control information
for a row in a MPC's Ingress Cache. MpcIngressCacheEntry .1.3.6.1.4.1.353.5.8.1.1.2.12.1 |
mpcIngressCacheDestInetworkAddrTypeThe type of the destination internetwork layer address.ro InternetworkAddrType .1.3.6.1.4.1.353.5.8.1.1.2.12.1.1 |
mpcIngressCacheDestAddrThe destination internetwork layer address for which
this entry is defined.ro InternetworkAddr .1.3.6.1.4.1.353.5.8.1.1.2.12.1.2 |
mpcIngressCachePrefixLenDefines an equivalence class of addresses that match
Prefix Length bit positions of the destination
internetwork layer address.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.12.1.3 |
mpcIngressCacheDestAtmAddrThe Destination ATM Address received in the MPOA
Resolution Reply.ro AtmAddr .1.3.6.1.4.1.353.5.8.1.1.2.12.1.4 |
mpcIngressCacheSrcAtmAddrThe Source ATM Address for the MPOA Resolution Request.ro AtmAddr .1.3.6.1.4.1.353.5.8.1.1.2.12.1.5 |
mpcIngressCacheEntryStateThe present state of this MPC ingress cache.
The states are:
doesNotExist (1)
inactive (2)
active. For an example, if
using the Finite State Machine
Appendix I.2, then the states
Cached and query are considered
`inactive'.
active (3)
For an example, if using the
Finite State Machine in Appendix I.2,
then the states resolved and refresh
are considered `active'.
negative (4)
which could mean a NAK response was
received, or entry is doing a
retry, etc. For example, if using
the Finite State Machine in Appendix
I.2, then the state `hold down' is
considered `negative'.ro Enumeration .1.3.6.1.4.1.353.5.8.1.1.2.12.1.6 |
mpcIngressCacheEgressCacheTagValidIf the value of this object is true(1), then a valid
Egress Cache Tag is present and the value of the Egress
Cache Tag is in mpcIngressCacheEgressCacheTag. Otherwise,
if this value is false(2), then there was no Egress Cache
Tag, and the value of mpcIngressCacheEgressCacheTag is
undefined.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.12.1.7 |
mpcIngressCacheEgressCacheTagIf a valid Egress Cache Tag is present, then this
object contains the value of that tag. To determine
if this object contains a valid value,
mpcIngressCacheEgressTagValid should be used.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.12.1.8 |
mpcIngressCacheLastNhrpCieCodeThe last NHRP CIE code received for this entry. This
value is valid only during the Hold Down period of the
cache entry. This value is undefined otherwise.ro INTEGER .1.3.6.1.4.1.353.5.8.1.1.2.12.1.9 |
mpcIngressCacheSigErrCodeError code or Success of the last sinalling request
for this cache entry.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.12.1.10 |
mpcIngressCacheRetriesThe current number of times this MPC has issued a
resolution request since it received a valid reply.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.12.1.11 |
mpcIngressCacheTimeUntilNextResolutionRequestThe amount of time the MPC
must wait before issuing the next resolution request.ro TimeInterval (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.12.1.12 |
mpcIngressCacheHoldingTimeThe time that this MPC's Ingress Cache Entry will remain
valid. If the mpcIngressCacheEntryState is not active
this value will be zero.ro TimeInterval (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.12.1.13 |
mpcIngressCacheServiceCategoryThe service categories supported for this shortcut.ro INTEGER .1.3.6.1.4.1.353.5.8.1.1.2.12.1.14 |
mpcEgressCacheRxTotalPacketsThis counts the total number of packets
received by MPC Short Cuts.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.2.13 |
mpcEgressCacheRxTotalOctetsThis counts the total number of octets
received by MPC Short Cuts.ro Counter64 .1.3.6.1.4.1.353.5.8.1.1.2.14 |
mpcEgressCacheTableThis table contains Egress Cache information for
all the MPCs which this agent manages. SEQUENCE OF MpcEgressCacheEntry .1.3.6.1.4.1.353.5.8.1.1.2.15 |
mpcEgressCacheEntryAn entry in the MPOA Client's Egress Cache table. MpcEgressCacheEntry .1.3.6.1.4.1.353.5.8.1.1.2.15.1 |
mpcEgressCacheIdCache ID Provided by the MPS in the Cache
Imposition Request.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.15.1.1 |
mpcEgressCacheInetworkAddrTypeType of Internetwork Address in this cache entry.ro InternetworkAddrType .1.3.6.1.4.1.353.5.8.1.1.2.15.1.2 |
mpcEgressCacheIDestAddrThe destination internetwork layer address
for which this entry is defined.ro InternetworkAddr .1.3.6.1.4.1.353.5.8.1.1.2.15.1.3 |
mpcEgressCachePrefixLenDefines an equivalence class of addresses that match
Prefix Length bit positions of the destination
internetwork layer address.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.15.1.4 |
mpcEgressCacheEntryStateThe present state of this MPC egress cache entry.
The states are:
doesNotExist (1)
inactive (2)
active (3)
For example,if using the Finite State
Machine in Appendix 1.5,
the states active and flooding
are `active' state.
negative (4)
For example,if using the Finite
State Machine in Appendix 1.5,
the state purging is `negative'.ro Enumeration .1.3.6.1.4.1.353.5.8.1.1.2.15.1.5 |
mpcEgressCacheEgressCacheTagValidIf the value of this object is true(1), then a valid
Egress Cache Tag is present and the value of the Egress
Cache Tag is in mpcEgressCacheEgressCacheTag. Otherwise,
if this value is false(2), then there was no Egress
Cache Tag, and the value of mpcEgressCacheEgressCacheTag
is undefined.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.15.1.6 |
mpcEgressCacheEgressCacheTagIf a valid Egress Cache Tag is present, then this
object contains the value of that tag. To determine
if this object contains a valid value,
mpcEgressCacheEgressCacheTagValid should be used.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.15.1.7 |
mpcEgressCacheHoldTimeThe remaining time for which this entry is valid.ro TimeInterval (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.15.1.8 |
mpcEgressCacheDataLinkHeaderThe DataLink header that the egress client rebuilds
the original DataLink packet with.ro OCTET STRING .1.3.6.1.4.1.353.5.8.1.1.2.15.1.9 |
mpcEgressCacheIngressMpcDataAtmAddrThe Data ATM Address of the ingress MPC that issued
the MPOA Resolution requestro AtmAddr .1.3.6.1.4.1.353.5.8.1.1.2.15.1.10 |
mpcEgressCacheLecIndexThis is the lecIndex of the LANE Client that this flow
is associated with. This can be used to get the ELAN
name as well as other LANE parameters.ro LecIndex .1.3.6.1.4.1.353.5.8.1.1.2.15.1.11 |
mpcEgressCacheServiceCategoryThis is a bitmap describing the service categories
supported for this shortcut. This value represents
an inclusive OR of the bits:
bit 1 - if rt-VBR is supported,
bit 2 - if nrt-VBR is supported,
bit 4 - if ABR is supported,
bit 8 - if CBR is supported
A value of 0 (zero) indicates that UBR is supported.ro INTEGER .1.3.6.1.4.1.353.5.8.1.1.2.15.1.12 |
mpcMpsObjects OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.1.2.16 |
mpcMpsMultipleMacAddressTableThis 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. SEQUENCE OF MpcMpsMultipleMacAddressEntry .1.3.6.1.4.1.353.5.8.1.1.2.16.1 |
mpcMpsMultipleMacAddressEntryA 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. MpcMpsMultipleMacAddressEntry .1.3.6.1.4.1.353.5.8.1.1.2.16.1.1 |
mpcFlowDetectLecIndexThe lecIndex which represents the associated LEC. LecIndex .1.3.6.1.4.1.353.5.8.1.1.2.16.1.1.1 |
mpcMpsMacAddressIndexThis 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. Integer32 .1.3.6.1.4.1.353.5.8.1.1.2.16.1.1.2 |
mpcMpsFlowDetectMacAddressAn MPS MAC Address used by an MPC during flow detection.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.2.16.1.1.3 |
mpsObjects OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.1.3 |
mpsNextIndexThis 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.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.1 |
mpsConfigTableThe MPOA Server Configuration Table.
This table represents the configuration information for
all MPOA Servers which this agent manages. SEQUENCE OF MpsConfigEntry .1.3.6.1.4.1.353.5.8.1.1.3.2 |
mpsConfigEntryMPOA Server Configuration Entry.
Each entry contains configuration information
for one MPOA Server. MpsConfigEntry .1.3.6.1.4.1.353.5.8.1.1.3.2.1 |
mpsIndexA 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. MpsIndex .1.3.6.1.4.1.353.5.8.1.1.3.2.1.1 |
mpsRowStatusThis 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'.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.3.2.1.2 |
mpsConfigModeIndicates 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.rw Enumeration .1.3.6.1.4.1.353.5.8.1.1.3.2.1.3 |
mpsCtrlAtmAddrThe MPS's Control ATM Address. There exists one
Control ATM Address per MPS, therefore, the value
of this entry is unique within the table.rw AtmConfigAddr .1.3.6.1.4.1.353.5.8.1.1.3.2.1.4 |
mpsKeepAliveTimeMPS-p1 Keep-alive time is max interval between
the MPS sending MPOA Keep-Alives in seconds.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.2.1.5 |
mpsKeepAliveLifeTimeMPS-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).rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.2.1.6 |
mpsInitialRetryTimeMPS-p4 is initial value in seconds for the
MPOA retry mechanism.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.2.1.7 |
mpsRetryTimeMaximumMPS-p5 cumulative max value in seconds
for Retry Time (MPS-p4).rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.2.1.8 |
mpsGiveupTimeMPS-p6 Give Up Time.
Minimum time in seconds to wait before giving up on a
pending resolution request.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.2.1.9 |
mpsDefaultHoldingTimeMPS-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.rw Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.2.1.10 |
mpsActualTableA read-only table containing identification, status,
and operational information about the MPOA
Servers this agent manages. SEQUENCE OF MpsActualEntry .1.3.6.1.4.1.353.5.8.1.1.3.3 |
mpsActualEntryAn entry in the MPS Actual Table.
An entry represents a specific MPOA Server's
status and operation information. MpsActualEntry .1.3.6.1.4.1.353.5.8.1.1.3.3.1 |
mpsActualStateThis object indicates the current operational
status of the MPOA Server.ro Enumeration .1.3.6.1.4.1.353.5.8.1.1.3.3.1.1 |
mpsDiscontinuityTimeThe 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.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.3.3.1.2 |
mpsActualConfigModeIndicates whether this MPS auto-configured
when it was last (re-)initialized.ro Enumeration .1.3.6.1.4.1.353.5.8.1.1.3.3.1.3 |
mpsActualKeepAliveThe maximum amount of time in seconds this MPS waits
between sending MPOA Keep-Alives.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.3.1.5 |
mpsActualKeepAliveLifeTimeThe length of time in seconds this MPS
considers a Keep-Alive valid.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.3.1.6 |
mpsActualInitialRetryTimeThe actual initial value in seconds for the MPOA
retry mechanism.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.3.1.7 |
mpsActualRetryTimeMaximumThe actual cumulative max value in seconds
for Retry Time.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.3.1.8 |
mpsActualGiveupTimeMinimum time in seconds that this MPS waits
before giving up on a pending resolution request.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.3.1.9 |
mpsActualDefaultHoldingTimeThe actual Holding Time in minutes used in
NHRP Resolution Replies.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.3.1.10 |
mpsStatisticsTableThis table represents the statistical information
for the MPSs, which this agent manages. SEQUENCE OF MpsStatisticsEntry .1.3.6.1.4.1.353.5.8.1.1.3.4 |
mpsStatisticsEntryEach row in this table contains statistics
for one MPOA server. MpsStatisticsEntry .1.3.6.1.4.1.353.5.8.1.1.3.4.1 |
mpsStatRxMpoaResolveRequestsThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.1 |
mpsStatTxMpoaResolveReplyAcksThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.2 |
mpsStatTxMpoaResolveReplyInsufECResourcesThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.3 |
mpsStatTxMpoaResolveReplyInsufSCResourcesThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.4 |
mpsStatTxMpoaResolveReplyInsufEitherResourcesThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.5 |
mpsStatTxMpoaResolveReplyUnsupportedInetProtThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.6 |
mpsStatTxMpoaResolveReplyUnsupportedMacEncapsThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.7 |
mpsStatTxMpoaResolveReplyUnspecifiedOtherThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.8 |
mpsStatTxMpoaResolveReplyOtherThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.9 |
mpsStatGiveupTimeExpiredsThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.10 |
mpsStatTxMpoaImpRequestsThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.11 |
mpsStatRxMpoaImpReplyAcksThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.12 |
mpsStatRxMpoaImpReplyInsufECResourcesThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.13 |
mpsStatRxMpoaImpReplyInsufSCResourcesThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.14 |
mpsStatRxMpoaImpReplyInsufEitherResourcesThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.15 |
mpsStatRxMpoaImpReplyUnsupportedInetProtThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.16 |
mpsStatRxMpoaImpReplyUnsupportedMacEncapsThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.17 |
mpsStatRxMpoaImpReplyUnspecifiedOtherThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.18 |
mpsStatRxMpoaImpReplyOtherThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.19 |
mpsStatRxMpoaEgressCachePurgeRequestsThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.20 |
mpsStatTxMpoaEgressCachePurgeRepliesThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.21 |
mpsStatTxMpoaTriggersThe 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.22 |
mpsStatTxNhrpResolveRequestsTotal 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.23 |
mpsStatRxNhrpResolveRepliesTotal 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.24 |
mpsStatRxNhrpResolveRequestsTotal 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.25 |
mpsStatTxNhrpResolveRepliesTotal 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.ro Counter32 .1.3.6.1.4.1.353.5.8.1.1.3.4.1.26 |
mpsProtocolTableList of protocols, per MPS, for which
MPOA resolution is enabled. SEQUENCE OF MpsProtocolEntry .1.3.6.1.4.1.353.5.8.1.1.3.5 |
mpsProtocolEntryEach 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. MpsProtocolEntry .1.3.6.1.4.1.353.5.8.1.1.3.5.1 |
mpsInternetworkLayerProtocolMPS-p3 A protocol on which to perform MPOA resolution. InternetworkAddrType .1.3.6.1.4.1.353.5.8.1.1.3.5.1.1 |
mpsLECSValueThis 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).ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.3.5.1.2 |
mpsProtocolRowStatusThis object allows network managers to enable
resolution for the `mpsInternetworkLayerProtocol'.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.3.5.1.3 |
mpsMappingTableA table mapping the `lecIndex' values of
LANE Clients to the `mpsIndex' values of
corresponding MPOA Servers. SEQUENCE OF MpsMappingEntry .1.3.6.1.4.1.353.5.8.1.1.3.6 |
mpsMappingEntryEach row defines one lecIndex
The mpsIndex that a lecIndex maps to is not
necessarily unique. In other words, there can be
multiple LECs associated with one MPS. MpsMappingEntry .1.3.6.1.4.1.353.5.8.1.1.3.6.1 |
mpsMappingRowStatusAllows creation, enabling/disabling of this row.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.3.6.1.1 |
mpsMappingIndexThe mpsMappingIndex of the MPOA Server that is associated with
this LEC. The mpsMappingIndex corresponds to the mpsIndex.rw MpsIndex .1.3.6.1.4.1.353.5.8.1.1.3.6.1.2 |
mpsIngressCacheTableThis table tracks all the Ingress Cache information
of the MPSs which this agents manages. SEQUENCE OF MpsIngressCacheEntry .1.3.6.1.4.1.353.5.8.1.1.3.7 |
mpsIngressCacheEntryA entry contains parameters and state variables
for a row in a MPS's Ingress Cache. MpsIngressCacheEntry .1.3.6.1.4.1.353.5.8.1.1.3.7.1 |
mpsIngressCacheDestInternetworkAddrTypeThe type of internetwork layer address of the
Destination Address.ro InternetworkAddrType .1.3.6.1.4.1.353.5.8.1.1.3.7.1.1 |
mpsIngressCacheDestAddrThe Ingress MPS Destination Internetwork Layer Address.ro InternetworkAddr .1.3.6.1.4.1.353.5.8.1.1.3.7.1.2 |
mpsIngressCachePrefixLenThe Prefix Length of the mpsIngressCacheDestAddr.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.7.1.3 |
mpsIngressCacheEntryStateThe state of this MPS Ingress cache.
The states are:
doesNotExist (1)
inactive (2)
For example,if using the Finite
State Machine in Appendix I.3,
the state resolving is `inactive'.
active (3)
For example,if using the Finite
State Machine in Appendix I.3,
the state resolved
is `active' state.
negative (4)
For example,if using the Finite
State Machine in Appendix I.3,
the state purging is `negative'.ro Enumeration .1.3.6.1.4.1.353.5.8.1.1.3.7.1.4 |
mpsIngressCacheSrcInternetworkAddrTypeThe type of internetwork layer address of the
Source Address.ro InternetworkAddrType .1.3.6.1.4.1.353.5.8.1.1.3.7.1.5 |
mpsIngressCacheSrcAddrThe Ingress MPS Source Internetwork Layer Address.ro InternetworkAddr .1.3.6.1.4.1.353.5.8.1.1.3.7.1.6 |
mpsIngressCacheSourceMpcCtrlAtmAddrThe ATM Address from the source of this MPOA request.
In other words, the Ingress MPC's Control Atm Address.ro AtmAddr .1.3.6.1.4.1.353.5.8.1.1.3.7.1.7 |
mpsIngressCacheResolvedAtmAddrThe ATM Address which has been resolved by an Egress MPC.ro AtmAddr .1.3.6.1.4.1.353.5.8.1.1.3.7.1.8 |
mpsIngressCacheHoldTimeTime interval that this value is valid.ro TimeInterval (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.3.7.1.9 |
mpsIngressCacheMpoaRequestIdThe request ID contained in the MPOA resolution request
from the local Ingress MPC.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.7.1.10 |
mpsIngressCacheNhrpRequestIdThe request ID which this MPS generates to identify the
NHRP resolution request.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.7.1.11 |
mpsIngressCacheServiceCategoryThe service categories supported for this shortcut.ro INTEGER .1.3.6.1.4.1.353.5.8.1.1.3.7.1.12 |
mpsEgressCacheTableThis table contains information regarding the
Egress MPOA Server Cache Table. SEQUENCE OF MpsEgressCacheEntry .1.3.6.1.4.1.353.5.8.1.1.3.8 |
mpsEgressCacheEntryAn entry represents an entry in the MPS's Egress
cache Table which keeps track of the state of the
impositions. MpsEgressCacheEntry .1.3.6.1.4.1.353.5.8.1.1.3.8.1 |
mpsEgressCacheIdThe id which identifies this cache entry.ro INTEGER .1.3.6.1.4.1.353.5.8.1.1.3.8.1.1 |
mpsEgressCacheDestInternetworkAddrTypeThe destination protocol address type.ro InternetworkAddrType .1.3.6.1.4.1.353.5.8.1.1.3.8.1.2 |
mpsEgressCacheDestAddrThe destination protocol address.ro InternetworkAddr .1.3.6.1.4.1.353.5.8.1.1.3.8.1.3 |
mpsEgressCachePrefixLenThe destination prefix length.ro INTEGER .1.3.6.1.4.1.353.5.8.1.1.3.8.1.4 |
mpsEgressCacheHoldTimeTime interval that this value is valid.ro TimeInterval (SNMPv2-TC) .1.3.6.1.4.1.353.5.8.1.1.3.8.1.5 |
mpsEgressCacheEntryStateThe present states of this MPS egress cache entry.
The states are:
doesNotExist (1)
inactive (2)
For example,if using the Finite
State Machine in Appendix 1.4,
the state imposing is `inactive'.
active (3)
For example,if using the Finite
State Machine in Appendix 1.4,
the state imposed
is `active' state.
negative (4)
For example,if using the Finite
State Machine in Appendix 1.4,
the states purging and clearing
are `negative'.ro Enumeration .1.3.6.1.4.1.353.5.8.1.1.3.8.1.6 |
mpsEgressCacheDataLinkHeaderData-Link Layer Header.ro OCTET STRING .1.3.6.1.4.1.353.5.8.1.1.3.8.1.7 |
mpsEgressCacheElanIdThe elan id that this Cache Imposition is sent on.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.8.1.8 |
mpsEgressCacheSourceClientAtmAddrThe Ingress NHC's Atm Address used in the
original cache imposition.ro AtmAddr .1.3.6.1.4.1.353.5.8.1.1.3.8.1.9 |
mpsEgressCacheNhrpRequestIdThe request id from the original NHRP Resolution Request,
may be only useful in the Resolving State.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.8.1.10 |
mpsEgressCacheMpoaRequestIdThe new request id which is generated for this imposition's
request, may be only useful in the Resolving State.ro Integer32 .1.3.6.1.4.1.353.5.8.1.1.3.8.1.11 |
mpsEgressCacheServiceCategoryThe service categories supported for this shortcut.ro INTEGER .1.3.6.1.4.1.353.5.8.1.1.3.8.1.12 |
mpsEgressCacheNextHopInternetworkAddrTypeThe NextHop protocol address type.ro InternetworkAddrType .1.3.6.1.4.1.353.5.8.1.1.3.8.1.13 |
mpsEgressCacheNextHopAddrThe NextHop protocol address.ro InternetworkAddr .1.3.6.1.4.1.353.5.8.1.1.3.8.1.14 |
mpsMpcTableThis read-only table contains information about the
MPCs that these MPSs know about. SEQUENCE OF MpsMpcEntry .1.3.6.1.4.1.353.5.8.1.1.3.9 |
mpsMpcEntryA row created by an MPS. The MPS learns about the MPC and
creates a row. MpsMpcEntry .1.3.6.1.4.1.353.5.8.1.1.3.9.1 |
mpsMpcIndexThe local index for the mpc represented by this entry MpcIndex .1.3.6.1.4.1.353.5.8.1.1.3.9.1.1 |
mpsMpcCtrlAtmAddrMPC control ATM addressro AtmAddr .1.3.6.1.4.1.353.5.8.1.1.3.9.1.2 |
mpoaMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.2 |
mpoaMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.2.1 |
mpoaMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.353.5.8.1.2.2 |