|
|
Description:
|
diffServActionStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION "This object is used to create a new row, modify or
delete an existing row in this table.
The status column has six defined values:
The status column has six defined values:
- 'active', which indicates that the conceptual row
is available for use by the managed device;
- 'notInService', which indicates that the conceptual
row exists in the agent, but is unavailable for use
by the managed device (see NOTE below);
- 'notReady', which indicates that the conceptual row
exists in the agent, but is missing information
necessary in order to be available for use by the
managed device;
- 'createAndGo', which is supplied by a management
station wishing to create a new instance of a
conceptual row and to have its status automatically
set to active, making it available for use by the
managed device;
- 'createAndWait', which is supplied by a management
station wishing to create a new instance of a
conceptual row (but not make it available for use by
the managed device); and,
- 'destroy', which is supplied by a management
station wishing to delete all of the instances
associated with an existing conceptual row.
Whereas five of the six values (all except 'notReady') may
be specified in a management protocol set operation, only
three values will be returned in response to a management
protocol retrieval operation: 'notReady', 'notInService'
or 'active'. That is, when queried, an existing
conceptual row has only three states: it is either
available for use by the managed device (the status column
has the value 'active'); it is not available for use by
the managed device, though the agent has sufficient
information to make it so (the status column has the value
'notInService'); or, it is not available for use by the
managed device, and an attempt to make it so would fail
because the agent has insufficient information (the state
column has the value 'notReady').
For a detailed description of this object, please refer to
SNMPv2-TC MIB."
|
|
|
|
