HP Model 755/125cL HP-UX DMI 2.0 Developer's Guide: HP-UX/HP 9000 Computers, - Page 28

Direct Interface vs. Overlay Instrumentation, Direct-Interface Instrumentation, Debugging Direct-

Get HP Model 755/125cL - Workstation PDF manuals and user guides View all HP Model 755/125cL manuals
Add to My Manuals
Save this manual to your list of manuals

Page 28 highlights

Component Interface Concepts Static vs. Dynamic Data End Group End Component When you choose to use dynamic data, you must also decide what type of component instrumentation accesses the data. The HP-UX DMI 2.0 implementation supports two types of component instrumentation. They are Direct Interface (DI) and Overlay Interface. The following sections describe each type. Direct Interface vs. Overlay Instrumentation Both Direct Interface (DI) and Overlay Interface component instrumentation interact with the SP through the Component Interface to provide dynamic attribute data. Direct-Interface Instrumentation Direct Interface component instrumentation is implemented as a separate application loaded into memory independently of the SP. In HP-UX, this type of component instrumentation is an HP-UX daemon. DI is advantageous when system overhead to get or set attributes is high. However, with DI system resources remain in use. HP recommends using DI component instrumentation only when the associated MIF file has large amounts of dynamic data or the system overhead for retrieving and setting the dynamic data is high. Debugging Direct-Interface Instrumentation The DMI SP has a configurable timeout for communication with a Direct CI. Adjust this value so that the DMI SP will not return the error code DMIERR_SP_INACTIVE to the Management Interface requesting information from the CI you are debugging. Modify the timeout environment variable, DMISP_DITIMEOUT, and restart the DMI SP: Ksh $ export DMISP_DITIMEOUT=some_number The maximum value is two hours and the default value is 100 seconds. Be cautious of semaphores when debugging Direct Interface components. Terminate Component Instrumentation properly by calling DmiUnregisterCi() and exiting. The current implementation of the Service Provider will not allow Direct Interface Component Instrumentation to remain running over a Service Provider restart. If the Service Provider goes down, the instrumentation will return from the DmiMainLoop() function. Overlay Instrumentation Overlay components are implemented as shared libraries that are identified by an associated MIF file and are loaded by the SP to get and 28 Chapter 3

  • 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
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
28
Chapter 3
Component Interface Concepts
Static vs. Dynamic Data
End Group
End Component
When you choose to use dynamic data, you must also decide what type
of component instrumentation accesses the data. The HP-UX DMI 2.0
implementation supports two types of component instrumentation.
They are Direct Interface (DI) and Overlay Interface. The following
sections describe each type.
Direct Interface vs. Overlay Instrumentation
Both Direct Interface (DI) and Overlay Interface component
instrumentation interact with the SP through the Component Interface
to provide dynamic attribute data.
Direct-Interface Instrumentation
Direct Interface component instrumentation is implemented as a
separate application loaded into memory independently of the SP. In
HP-UX, this type of component instrumentation is an HP-UX daemon.
DI is advantageous when system overhead to get or set attributes is
high. However, with DI system resources remain in use.
HP recommends using DI component instrumentation only when the
associated MIF file has large amounts of dynamic data or the system
overhead for retrieving and setting the dynamic data is high.
Debugging Direct-Interface Instrumentation
The DMI SP has a configurable timeout for communication with a
Direct CI. Adjust this value so that the
DMI SP
will not return the error
code
DMIERR_SP_INACTIVE
to the Management Interface requesting
information from the CI you are debugging. Modify the timeout
environment variable,
DMISP_DITIMEOUT
, and restart the
DMI SP:
Ksh $ export DMISP_DITIMEOUT=some_number
The maximum value is two hours and the default value is 100 seconds.
Be cautious of semaphores when debugging Direct Interface
components. Terminate Component Instrumentation properly by
calling
DmiUnregisterCi()
and exiting.
The current implementation of the Service Provider will not allow
Direct Interface Component Instrumentation to remain running over a
Service Provider restart. If the Service Provider goes down, the
instrumentation will return from the
DmiMainLoop()
function.
Overlay Instrumentation
Overlay components are implemented as shared libraries that are
identified by an associated MIF file and are loaded by the SP to get and