HP Visualize c160L HP-UX DMI 2.0 Developer's Guide: HP-UX/HP 9000 Computers, - Page 108

Monitoring Events

Get HP Visualize c160L - Workstation PDF manuals and user guides View all HP Visualize c160L manuals
Add to My Manuals
Save this manual to your list of manuals

Page 108 highlights

Events and Indications Monitoring Events Monitoring Events In order for a management application to monitor these events it must: 1. Register with the SP of the host it will monitor. 2. Create a DCE/RPC end point for these indication RPCs. 3. Add a row to SP's indication subscription table giving SP the address of the created DCE/RPC end point, and add a row to SP's filter information table indicating which component ID and which class name it wishes to monitor (wild cards can be used to monitor all components and classes). 4. Register procedural entry points for the monitored indications. Registering With a Host's SP The management application registers with a host's SP by using the DmiRemoteRegister() call as described in the Management Interface section. Creating a DCE/RPC Endpoint The DCE/RPC end point is created so that SP can issue a DCE/RPC call to the management application. The end point is set up by calling DmiIndicationListen(). This procedure has no parameters. Adding Rows to the SP Tables When SP generates indications, it needs the following information: The addressing information of management applications that are registered to receive indications. The components a registered management application is monitoring. The group classes a registered management application is monitoring. There are a certain number of addressing entries in the SP Indication Subscription table. There are a certain number of component and group entries in the SP Filter Information table. There must be one entry in the SP Indication Subscription table for each management application that is monitoring events. There must be at least one corresponding SP Filter Information table entry and there can be more than one filter. To determine which subscription entries belong to which filter entries, you look at the first four attributes. You add entries into these tables using DmiAddRow(). Wild cards can be used in SP Filter Information table entries to describe components and group classes being monitored. 108 Chapter 10

  • 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
108
Chapter 10
Events and Indications
Monitoring Events
Monitoring Events
In order for a management application to monitor these events it must:
1.
Register with the SP of the host it will monitor.
2.
Create a DCE/RPC end point for these indication RPCs.
3. Add a row to SP's indication subscription table giving SP the address
of the created DCE/RPC end point, and add a row to SP's filter
information table indicating which component ID and which class
name it wishes to monitor (wild cards can be used to monitor all
components and classes).
4.
Register procedural entry points for the monitored indications.
Registering With a Host's SP
The management application registers with a host's SP by using the
DmiRemoteRegister() call as described in the Management Interface
section.
Creating a DCE/RPC Endpoint
The DCE/RPC end point is created so that SP can issue a DCE/RPC call
to the management application. The end point is set up by calling
DmiIndicationListen(). This procedure has no parameters.
Adding Rows to the SP Tables
When SP generates indications, it needs the following information:
The addressing information of management applications that are
registered to receive indications.
The components a registered management application is monitoring.
The group classes a registered management application is monitoring.
There are a certain number of addressing entries in the SP Indication
Subscription table. There are a certain number of component and group
entries in the SP Filter Information table. There must be one entry in
the SP Indication Subscription table for each management application
that is monitoring events. There must be at least one corresponding SP
Filter Information table entry and there can be more than one filter. To
determine which subscription entries belong to which filter entries, you
look at the first four attributes. You add entries into these tables using
DmiAddRow().
Wild cards can be used in SP Filter Information table entries to
describe components and group classes being monitored.