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.
Parsed from file MPC-MIB.mib
Module: MPC-MIB.mib
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.
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.
Parsed from file MPOA100.MIB.txt
Company: None
Module: MPOA-MIB
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.
mpcNextIndex OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "This object contains an appropriate value to be used for mpcIndex when creating entries in the mpcConfigTable. The value 0 indicates that no new rows can be created. Otherwise, it is recommended that values are assigned contiguously, starting from 1. MPC creation by a Manager: To obtain the mpcIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. If the value retrieved is 0 (zero), the manager cannot create a row. After each retrieval of a non-zero value, the manager should issue a management protocol SET operation using the value just retrieved. If the SET is successful, the agent should update the value to the next unassigned index, or zero if appropriate. NOTE: the manager may also issue a set on this object with a value of its own choosing. If the set is successful, the manager may use this value for the mpcIndex. In this case, the agent would update the value to the next unassigned index, or zero if appropriate. The definition of `next unassigned index' is any mpcNextIndex value that has not yet been set by a manager, or reserved by the agent (see next paragraph), since this agent was last re-initialized. MPC creation by an Agent: When a row in the mpcConfigTable is created by an agent, the agent should reserve the value of the index by updating the value of this object to the next unassigned index or zero if appropriate. Thus, a manager will not be able to set an index reserved by an agent. In the situation of an agent re-initialization, all currently used mpcIndexes must be preserved. In other words, the Agent should store in non-volatile memory all of the currently used mpcIndexes (along with all necessary configuration information from the mpcConfigTable). When the agent is re-initialized, the mpcNextIndex value is any valid Integer32 value which is not being used as an mpcIndex, except 0 which maintains its original definition of indicating that a row cannot be created." ::= { mpcObjects 1 }
mpcNextIndex OBJECT-TYPE SYNTAX INTEGER(0..2147483647) ACCESS read-write STATUS mandatory DESCRIPTION "This object contains an appropriate value to be used for mpcIndex when creating entries in the mpcConfigTable. The value 0 indicates that no new rows can be created. Otherwise, it is recommended that values are assigned contiguously, starting from 1. MPC creation by a Manager: To obtain the mpcIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. If the value retrieved is 0 (zero), the manager cannot create a row. After each retrieval of a non-zero value, the manager should issue a management protocol SET operation using the value just retrieved. If the SET is successful, the agent should update the value to the next unassigned index, or zero if appropriate. NOTE: the manager may also issue a set on this object with a value of its own choosing. If the set is successful, the manager may use this value for the mpcIndex. In this case, the agent would update the value to the next unassigned index, or zero if appropriate. The definition of `next unassigned index' is any mpcNextIndex value that has not yet been set by a manager, or reserved by the agent (see next paragraph), since this agent was last re-initialized. MPC creation by an Agent: When a row in the mpcConfigTable is created by an agent, the agent should reserve the value of the index by updating the value of this object to the next unassigned index or zero if appropriate. Thus, a manager will not be able to set an index reserved by an agent. In the situation of an agent re-initialization, all currently used mpcIndexes must be preserved. In other words, the Agent should store in non-volatile memory all of the currently used mpcIndexes (along with all necessary configuration information from the mpcConfigTable). When the agent is re-initialized, the mpcNextIndex value is any valid Integer32 value which is not being used as an mpcIndex, except 0 which maintains its original definition of indicating that a row cannot be created." ::= { mpcObjects 1 }
Vendor: ATM Forum
Module: MPC-MIB
[Automatically extracted from oidview.com]
mpcNextIndex OBJECT-TYPE SYNTAX Integer32(0..2147483647) ACCESS read-write STATUS mandatory DESCRIPTION "This object contains an appropriate value to be used for mpcIndex when creating entries in the mpcConfigTable. The value 0 indicates that no new rows can be created. Otherwise, it is recommended that values are assigned contiguously, starting from 1. MPC creation by a Manager: To obtain the mpcIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. If the value retrieved is 0 (zero), the manager cannot create a row. After each retrieval of a non-zero value, the manager should issue a management protocol SET operation using the value just retrieved. If the SET is successful, the agent should update the value to the next unassigned index, or zero if appropriate. NOTE: the manager may also issue a set on this object with a value of its own choosing. If the set is successful, the manager may use this value for the mpcIndex. In this case, the agent would update the value to the next unassigned index, or zero if appropriate. The definition of `next unassigned index' is any mpcNextIndex value that has not yet been set by a manager, or reserved by the agent (see next paragraph), since this agent was last re-initialized. MPC creation by an Agent: When a row in the mpcConfigTable is created by an agent, the agent should reserve the value of the index by updating the value of this object to the next unassigned index or zero if appropriate. Thus, a manager will not be able to set an index reserved by an agent. In the situation of an agent re-initialization, all currently used mpcIndexes must be preserved. In other words, the Agent should store in non-volatile memory all of the currently used mpcIndexes (along with all necessary configuration information from the mpcConfigTable). When the agent is re-initialized, the mpcNextIndex value is any valid Integer32 value which is not being used as an mpcIndex, except 0 which maintains its original definition of indicating that a row cannot be created." ::= { mpcObjects 1 }
mpcNextIndex OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "This object contains an appropriate value to be used for mpcIndex when creating entries in the mpcConfigTable. The value 0 indicates that no new rows can be created. Otherwise, it is recommended that values are assigned contiguously, starting from 1. MPC creation by a Manager: To obtain the mpcIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. If the value retrieved is 0 (zero), the manager cannot create a row. After each retrieval of a non-zero value, the manager should issue a management protocol SET operation using the value just retrieved. If the SET is successful, the agent should update the value to the next unassigned index, or zero if appropriate. NOTE: the manager may also issue a set on this object with a value of its own choosing. If the set is successful, the manager may use this value for the mpcIndex. In this case, the agent would update the value to the next unassigned index, or zero if appropriate. The definition of `next unassigned index' is any mpcNextIndex value that has not yet been set by a manager, or reserved by the agent (see next paragraph), since this agent was last re-initialized. MPC creation by an Agent: When a row in the mpcConfigTable is created by an agent, the agent should reserve the value of the index by updating the value of this object to the next unassigned index or zero if appropriate. Thus, a manager will not be able to set an index reserved by an agent. In the situation of an agent re-initialization, all currently used mpcIndexes must be preserved. In other words, the Agent should store in non-volatile memory all of the currently used mpcIndexes (along with all necessary configuration information from the mpcConfigTable). When the agent is re-initialized, the mpcNextIndex value is any valid Integer32 value which is not being used as an mpcIndex, except 0 which maintains its original definition of indicating that a row cannot be created." ::= { mpcObjects 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.353.5.8.1.1.2.1.0 | mpcNextIndex | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.353.5.8.1.1.2.2 | mpcConfigTable, mpcStatusTable | 1 | 12 | The MPOA Client Configuration Table. This table contains configuration information for all MPOA Clients which this agent manages. |
| 1.3.6.1.4.1.353.5.8.1.1.2.3 | mpcActualTable | 1 | 9 | MPOA Client Actual Table. A read-only table which contains state information and reflects the actual values which these MPOA Clien… |
| 1.3.6.1.4.1.353.5.8.1.1.2.4 | mpcDataAtmAddressTable | 1 | 3 | A table which shows all the data ATM addresses associated with all MPOA Clients. |
| 1.3.6.1.4.1.353.5.8.1.1.2.5 | mpcStatisticsTable | 1 | 34 | A read-only table which contains statistical information for all MPOA Clients that this agent manages. |
| 1.3.6.1.4.1.353.5.8.1.1.2.6 | mpcProtocolTable, mpcMPSTable | 1 | 4 | List of protocols, per MPC, for which flow detection is enabled |
| 1.3.6.1.4.1.353.5.8.1.1.2.7 | mpcMappingTable | 1 | 3 | A table mapping the `lecIndex' values of LANE Clients to the `mpcIndex' values of corresponding MPOA Clients. |
| 1.3.6.1.4.1.353.5.8.1.1.2.8 | mpcMpsTable | 1 | 3 | This is a read-only table which contains information about the MPSs that these MPCs know about. |
| 1.3.6.1.4.1.353.5.8.1.1.2.9 | mpcMpsMacAddressTable | 1 | 3 | This is a read-only table which contains information about all the MPSs' MAC Addresses that these MPCs know about. |
| 1.3.6.1.4.1.353.5.8.1.1.2.10 | mpcIngressCacheTxTotalPackets | 1 | 1 | The total number of packets transmitted over MPC Short Cuts. |
| 1.3.6.1.4.1.353.5.8.1.1.2.11 | mpcIngressCacheTxTotalOctets | 1 | 1 | The total number of octets transmitted over MPC Short Cuts. |
| 1.3.6.1.4.1.353.5.8.1.1.2.12 | mpcIngressCacheTable | 1 | 16 | This table contains information for MPC Caches for the ingress MPC. |
| 1.3.6.1.4.1.353.5.8.1.1.2.13 | mpcEgressCacheRxTotalPackets | 1 | 1 | This counts the total number of packets received by MPC Short Cuts. |
| 1.3.6.1.4.1.353.5.8.1.1.2.14 | mpcEgressCacheRxTotalOctets | 1 | 1 | This counts the total number of octets received by MPC Short Cuts. |
| 1.3.6.1.4.1.353.5.8.1.1.2.15 | mpcEgressCacheTable | 1 | 14 | This table contains Egress Cache information for all the MPCs which this agent manages. |
| 1.3.6.1.4.1.353.5.8.1.1.2.16 | mpcMpsObjects | 1 | 5 | None |