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.
Parsed from file MPOA-MIB.mib
Module: MPOA-MIB
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.
This table gives the basic information about
connections being used by the MPOA Servers and
Clients. All additional information should
be retreived from the AToM MIB.
Parsed from file MPOA100.MIB.txt
Company: None
Module: MPOA-MIB
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.
mpsNextIndex OBJECT-TYPE SYNTAX Integer32(0..2147483647) ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { mpsObjects 1 }
mpsNextIndex OBJECT-TYPE SYNTAX INTEGER(0..2147483647) ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { mpsObjects 1 }
Vendor: ATM Forum
Module: MPOA-MIB
[Automatically extracted from oidview.com]
mpoaConnTable OBJECT-TYPE SYNTAX SEQUENCE OF MpoaConnEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table gives the basic information about connections being used by the MPOA Servers and Clients. All additional information should be retreived from the AToM MIB." REFERENCE "Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2, RFC-1695." ::= { mpoaConnectionObjects 1 }
mpsNextIndex OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { mpsObjects 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.353.5.8.1.1.3.1.0 | mpsNextIndex | 0 | 0 | None |
| 1.3.6.1.4.1.353.5.8.1.1.3.1.1 | mpoaConnEntry | 5 | 5 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.353.5.8.1.1.3.2 | mpsConfigTable, mpsStatusTable | 1 | 11 | The MPOA Server Configuration Table. This table represents the configuration information for all MPOA Servers which this agent ma… |
| 1.3.6.1.4.1.353.5.8.1.1.3.3 | mpsActualTable | 1 | 10 | A read-only table containing identification, status, and operational information about the MPOA Servers this agent manages. |
| 1.3.6.1.4.1.353.5.8.1.1.3.4 | mpsStatisticsTable | 1 | 41 | This table represents the statistical information for the MPSs, which this agent manages. |
| 1.3.6.1.4.1.353.5.8.1.1.3.5 | mpsProtocolTable | 1 | 4 | List of protocols, per MPS, for which MPOA resolution is enabled. |
| 1.3.6.1.4.1.353.5.8.1.1.3.6 | mpsMappingTable, mpsAddressResTable | 1 | 6 | A table mapping the `lecIndex' values of LANE Clients to the `mpsIndex' values of corresponding MPOA Servers. |
| 1.3.6.1.4.1.353.5.8.1.1.3.7 | mpsIngressCacheTable, mpsImpositionsTable | 1 | 13 | This table tracks all the Ingress Cache information of the MPSs which this agents manages. |
| 1.3.6.1.4.1.353.5.8.1.1.3.8 | mpsEgressCacheTable | 1 | 15 | This table contains information regarding the Egress MPOA Server Cache Table. |
| 1.3.6.1.4.1.353.5.8.1.1.3.9 | mpsMpcTable | 1 | 3 | This read-only table contains information about the MPCs that these MPSs know about. |