| OID | 1.3.6.1.2.1.90.1.2.1.1 |
| Module | DISMAN-EXPRESSION-MIB (CISCO) |
| Nom | expExpressionEntry |
| Status | current |
| Description | Information about a single expression. New expressions
can be created using expExpressionRowStatus.
To create an expression first create the named entry in this
table. Then use expExpressionName to populate expObjectTable.
For expression evaluation to succeed all related entries in
expExpressionTable and expObjectTable must be 'active'. If
these conditions are not met the corresponding values in
expValue simply are not instantiated.
Deleting an entry deletes all related entries in expObjectTable
and expErrorTable.
Because of the relationships among the multiple tables for an
expression (expExpressionTable, expObjectTable, and
expValueTable) and the SNMP rules for independence in setting
object values, it is necessary to do final error checking when
an expression is evaluated, that is, when one of its instances
in expValueTable is read or a delta interval expires. Earlier
checking need not be done and an implementation may not impose
any ordering on the creation of objects related to an
expression.
To maintain security of MIB information, when creating a new row in
this table, the managed system must record the security credentials
of the requester. These security credentials are the parameters
necessary as inputs to isAccessAllowed from the Architecture for
Describing SNMP Management Frameworks. When obtaining the objects
that make up the expression, the system must (conceptually) use
isAccessAllowed to ensure that it does not violate security.
The evaluation of the expression takes place under the
security credentials of the creator of its expExpressionEntry.
Values of read-write objects in this table may be changed
at any time. |
| Module | DISMAN-EXPRESSION-MIB (ietf) |
| Nom | expExpressionEntry |
| Status | current |
| Description | Information about a single expression. New expressions
can be created using expExpressionRowStatus.
To create an expression first create the named entry in this
table. Then use expExpressionName to populate expObjectTable.
For expression evaluation to succeed all related entries in
expExpressionTable and expObjectTable must be 'active'. If
these conditions are not met the corresponding values in
expValue simply are not instantiated.
Deleting an entry deletes all related entries in expObjectTable
and expErrorTable.
Because of the relationships among the multiple tables for an
expression (expExpressionTable, expObjectTable, and
expValueTable) and the SNMP rules for independence in setting
object values, it is necessary to do final error checking when
an expression is evaluated, that is, when one of its instances
in expValueTable is read or a delta interval expires. Earlier
checking need not be done and an implementation may not impose
any ordering on the creation of objects related to an
expression.
To maintain security of MIB information, when creating a new row in
this table, the managed system must record the security credentials
of the requester. These security credentials are the parameters
necessary as inputs to isAccessAllowed from the Architecture for
Describing SNMP Management Frameworks. When obtaining the objects
that make up the expression, the system must (conceptually) use
isAccessAllowed to ensure that it does not violate security.
The evaluation of the expression takes place under the
security credentials of the creator of its expExpressionEntry.
Values of read-write objects in this table may be changed
at any time. |