HP dx7200 HP Client Management Interface Technical White Paper - Page 16

Example applications

Page 16 highlights

Status "Critical Failure" (25) - The element is non-functional and recovery MAY NOT be possible. "Major Failure" (20) - The element is failing. It is possible the some or all of the functionality of this component is degraded or not working. "Minor Failure" (15) - All functionality is available but some MAY be degraded. "Degraded/Warning" (10) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element may not be operating at optimal performance or it may be reporting recoverable errors. "OK" (5) - The element is fully functional and is operating within normal operational parameters and without error. "Unknown" (0) - The implementation can not report on Severity at this time. Indicates the current status(es) of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. However, a few are not and are described in more detail. "Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, etc. "Predictive Failure" indicates that an element is functioning nominally but predicting a failure in the near future. "In Service" describes an element being configured, maintained, cleaned, or otherwise administered. "No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. "Lost Communication" indicates that the ManagedSystemElement is known to exist and has been contacted successfully in the past, but is currently unreachable. "Stopped" and "Aborted" are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the element's state and configuration may need to be updated. "Dormant" indicates that the element is inactive or quiesced. "Supporting Entity in Error" describes that this element may be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower layer networking problems. "Completed" indicates the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can till if the complete operation passed (Completed with OK), and failure (Completed with Error). Completed with Degraded would imply the operation finished, but did not complete OK or report an error. "Power Mode" indicates the element has additional power model information contained in the Associated PowerManagementService association. Example applications Retrieving BIOS Settings The following script will enumerate all the available settings within a computer. This example uses semi-synchronous access for the purpose of simplifying the example. However, the interface supports either semisynchronous or asynchronous access. 16

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26

16
"Critical Failure" (25) - The element is non-functional and recovery
MAY NOT be possible.
"Major Failure" (20) - The element is failing. It is possible the some or
all of the functionality of this component is degraded or not working.
"Minor Failure" (15) - All functionality is available but some MAY be
degraded.
"Degraded/Warning" (10) - The element is in working order and all
functionality is provided. However, the element is not working to the
best of its abilities. For example, the element may not be operating at
optimal performance or it may be reporting recoverable errors.
"OK" (5) - The element is fully functional and is operating within normal
operational parameters and without error.
"Unknown" (0) - The implementation can not report on Severity at this
time.
Status
Indicates the current status(es) of the element. Various operational
statuses are defined. Many of the enumeration's values are
self-explanatory. However, a few are not and are described in more
detail.
"Stressed" indicates that the element is functioning, but needs attention.
Examples of "Stressed" states are overload, overheated, etc.
"Predictive Failure" indicates that an element is functioning nominally
but predicting a failure in the near future.
"In Service" describes an element being configured, maintained,
cleaned, or otherwise administered.
"No Contact" indicates that the monitoring system has knowledge of
this element, but has never been able to establish communications with
it.
"Lost Communication" indicates that the ManagedSystemElement is
known to exist and has been contacted successfully in the past, but is
currently unreachable.
"Stopped" and "Aborted" are similar, although the former implies a
clean and orderly stop, while the latter implies an abrupt stop where
the element's state and configuration may need to be updated.
"Dormant" indicates that the element is inactive or quiesced.
"Supporting Entity in Error" describes that this element may be "OK"
but that another element, on which it is dependent, is in error. An
example is a network service or endpoint that cannot function due to
lower layer networking problems.
"Completed" indicates the element has completed its operation. This
value should be combined with either OK, Error, or Degraded so that a
client can till if the complete operation passed (Completed with OK),
and failure (Completed with Error). Completed with Degraded would
imply the operation finished, but did not complete OK or report an
error.
"Power Mode" indicates the element has additional power model
information contained in the Associated PowerManagementService
association.
Example applications
Retrieving BIOS Settings
The following script will enumerate all the available settings within a computer. This example uses
semi-synchronous access for the purpose of simplifying the example. However, the interface supports
either semisynchronous or asynchronous access.