[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Resource State - IETF + ITU references
Hi,
As an individual contribution to the discussion on resource state, I've
compiled some objects developed by the the following IETF working
groups: rmonmib, entity-mib, madman, disman. These items are presented
as survey of existing models.
The applOperStatus object was designed to model the state of a network
service (e.g. smtp, www) and is likely the most similar to the state of
a web service of all the IETF developed objects.
The Textual-Conventions defined for the entity mib state MIB (in draft) rely
upon IEC/ISO X.731 (a link to the specific document is provided below).
Hope this helps!
Regards,
Mark
----------------------------------------------------------------------------
from rfc2788 (NETWORK-SERVICES-MIB) madman WG
[note: I belive this object, designed to monitor a network service, is
similar to the states to model for a web service. A network service
that does not model the concept of one (or more) of the enumerated
states would not return the corresponding enumerated value.]
applOperStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1),
down(2),
halted(3),
congested(4),
restarting(5),
quiescing(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the operational status of the network service
application. 'down' indicates that the network service is
not available. 'up' indicates that the network service
is operational and available. 'halted' indicates that the
service is operational but not available. 'congested'
indicates that the service is operational but no additional
inbound associations can be accommodated. 'restarting'
indicates that the service is currently unavailable but is
in the process of restarting and will be available soon.
'quiescing' indicates that service is currently operational
but is in the process of shutting down. Additional inbound
associations may be rejected by applications in the
'quiescing' state."
::= {applEntry 6}
------------------------------------------------------------------------------
From rfc3165 (DISMAN-SCRIPT-MIB) disman wg
[Note: This object for modeling life cycle of remotely executing script
in a distributed SNMP management domain.]
smRunState OBJECT-TYPE
SYNTAX INTEGER {
initializing(1),
executing(2),
suspending(3),
suspended(4),
resuming(5),
aborting(6),
terminated(7)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object indicates the script's execution
state. If the script has been invoked but has not yet
begun execution, the value will be `initializing'. If the
script is running, the value will be `executing'.
A running script which received a request to suspend
execution first transitions into a temporary `suspending'
state. The temporary `suspending' state changes to
`suspended' when the script has actually been suspended. The
temporary `suspending' state changes back to `executing' if
the attempt to suspend the running script fails.
A suspended script which received a request to resume
execution first transitions into a temporary `resuming'
state. The temporary `resuming' state changes to `running'
when the script has actually been resumed. The temporary
`resuming' state changes back to `suspended' if the attempt
to resume the suspended script fails.
A script which received a request to abort execution but
which is still running first transitions into a temporary
`aborting' state.
A script which has finished its execution is `terminated'."
::= { smRunEntry 10 }
----------------------------------------------------------------------------------
From rfc2024 (DLSW-MIB) DLSw wg
[Note: This MIB models a transport connections, so likely an different
paradigm than that of WSDM]
dlswTConnOperState OBJECT-TYPE
SYNTAX INTEGER {
connecting (1),
initCapExchange (2),
connected (3),
quiescing (4),
disconnecting (5),
disconnected (6)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The state of this transport connection. The transport
connection enters `connecting' state when DLSw makes
a connection request to the transport layer. Once initial
Capabilities Exchange is sent, the transport connection
enters enters `initCapExchange' state. When partner
capabilities have been determined and the transport
connection is ready for sending CanUReach (CUR) messages,
it moves to the `connected' state. When DLSw is in the
process of bringing down the connection, it is in the
`disconnecting' state. When the transport layer
indicates one of its connections is disconnected, the
transport connection moves to the `disconnected' state.
Whereas all of the values will be returned in response
to a management protocol retrieval operation, only two
values may be specified in a management protocol set
operation: `quiescing' and `disconnecting'. Changing
the value to `quiescing' prevents new circuits from being
established, and will cause a transport disconnect when
he last circuit on the connection goes away. Changing
the value to `disconnecting' will force off all circuits
immediately and bring the connection to `disconnected'
state."
::= { dlswTConnOperEntry 6 }
------------------------------------------------------------------
TCs from draft-ietf-entmib-state-02.txt (a product of the Entity MIB
working group)
[note: These Textual-Conventions are derived from ITU Recommendation
X.731 (ISO/IEC 10164- 2: 1992) this set of TCs is the most architected
of the bunch. A serach at http://webstore.ansi.org/ansidocstore
"10164-2:1993" yeilded proper results. The main document is priced at US$78]
-- Textual conventions
AdminState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the various possible administrative states.
A value of 'locked' means the resource is administratively
prohibited from use. A value of 'shuttingDown' means that
usage is administratively limited to current instances of
use. A value of 'unlocked' means the resource is not
administratively prohibited from use."
REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State
Management Function', 1992"
SYNTAX INTEGER
{
notSupported(1),
locked(2),
shuttingDown(3),
unlocked(4)
}
OperState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of operational states.
A value of 'disabled' means the resource is totally
inoperable. A value of 'enabled' means the resource
is partially or fully operable."
REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State
Management Function', 1992"
SYNTAX INTEGER
{
notSupported (1),
disabled(2),
enabled(3)
}
UsageState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of usage states.
A value of 'idle' means the resource is servicing no
users. A value of 'active' means the resource is
currently in use and it has sufficient spare capacity
to provide for additional users. A value of 'busy'
means the resource is currently in use, but it
currently has no spare capacity to provide for
additional users."
REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State
Management Function', 1992"
SYNTAX INTEGER
{
notSupported (1),
idle(2),
active(3),
busy(4)
}
AlarmStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the possible values of alarm status.
When no bits of this attribute are set, then none of the
status conditions described below are present. When the
value of under repair is set, the resource is currently
being repaired.
When the value of 'critical' is set, one or more critical
alarms are active against the resource. When the value of
'major' is set, one or more major alarms are active against
the resource. When the value of 'minor' is set, one or more
minor alarms are active against the resource. When the
value of 'warning' is set, one or more warning alarms are
active against the resource. When the value of
'indeterminate' is set, one or more alarms of
indeterminate severity are active against the resource.
When the value of 'alarmOutstanding' is set, one or more
alarms is active against the resource. The fault may or may
not be disabling. "
REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State
Management Function', 1992"
SYNTAX BITS
{
notSupported (0),
underRepair(1),
critical(2),
major(3),
minor(4),
alarmOutstanding(5),
-- The following are not defined in X.733
warning (6),
indeterminate (7)
}
StandbyStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of standby status.
A value of 'hotStandby' means the resource is not
providing service, but is will be immediately able to
take over the role of the resource to be backed-up,
without the need for initialization activity, and will
contain the same information as the resource to be
backed up. A value of 'coldStandy' means that the
resource is to back-up another resource, but will not
be immediately able to take over the role of a resource
to be backed up, and will require some initialization
activity. A value of 'providingService' means the
resource is providing service."
REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State
Management Function', 1992"
SYNTAX INTEGER
{
notSupported (1),
hotStandby(2),
coldStandby(3),
providingService(4)
}
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]