IBM E027SLL-H Troubleshooting Guide - Page 197
later monitoring server inadvertently uncon s the monitoring
![]() |
View all IBM E027SLL-H manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 197 highlights
The monitoring agent does not support the displayname/atomization, so the SNMP alert emitter will only emit an SNMP alert for the first row in the disk table where the situation is true. This limitation applies to subnodes as well. An instance of a subnode agent collects metrics for all subnodes in one table. These metrics are filtered by subnode when displayed in the Tivoli Enterprise Portal, but situations running against multiple subnodes in an instance are running against a single table. If a situation becomes True for 1 subnode, an SNMP alert defined for that situation will be emitted, but no SNMP alerts will be emitted for any other subnodes for that situation, since no further rows are processed in the table. Binary Path attribute of the Windows OS agent does not show a value On 64 bit systems with an installed 32 bit Windows OS agent, the value of the Binary Path attribute of the NT_Process attribute group is null if the process is running as 64 bit native. Installing pre-v6.2.1 Monitoring Agent for Windows OS onto a v6.2.1 or later monitoring server inadvertently unconfigures the monitoring server When a pre-v6.2.1 Monitoring Agent for Windows OS is installed onto a system that has a v6.2.1 or later monitoring server, the agent installation inadvertently unconfigures the monitoring server. This results in the monitoring server being left in a stopped state. Settings for the monitoring server remain preserved in the monitoring server ini and env files. Attempts to manually start the monitoring server fail with the message: Unable to start tems service. Check the event log. Monitoring Agents for Windows OS that are v6.2.1 and higher can be installed onto a monitoring server with no adverse side effects. IBM Tivoli Monitoring Application Agents regardless of version can also be installed onto a monitoring server with no adverse side effects. If this issue is encountered, the monitoring server should be re-configured and restarted from Manage Tivoli Enterprise Monitoring Server or through the CLI. Settings for the monitoring server from before the installation (preserved in the monitoring server ini and env files) will automatically be used. OS agent restarted unexpectedly on heavily loaded systems When Agent Management Services has a high workload, the OS agent is restarted automatically. At this point the OS agent is stopped, and its workspace on the Tivoli Enterprise Portal is grayed out, then the monitoring agent starts automatically by Agent Management Services in several seconds. When the OS agent is started, refresh workspace, you find only the Watchdog's management status workspace as "managed", all of the other agents'workspaces' status display "Not managed." On a heavily loaded system, increase the command time out parameter (KCA_CMD_TIMEOUT) in the OS agent's ini file from its default value to something larger, up to 120 seconds. Also, you may need to increase the checkFrequency value in the OS agent's availability checking policy file to a larger value. See the IBM Tivoli Monitoring Administration Guide's chapter on Tivoli Agent Management Services for information on how to change the parameters of this file. Chapter 10. Monitoring agent troubleshooting 179
-
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
-
135
-
136
-
137
-
138
-
139
-
140
-
141
-
142
-
143
-
144
-
145
-
146
-
147
-
148
-
149
-
150
-
151
-
152
-
153
-
154
-
155
-
156
-
157
-
158
-
159
-
160
-
161
-
162
-
163
-
164
-
165
-
166
-
167
-
168
-
169
-
170
-
171
-
172
-
173
-
174
-
175
-
176
-
177
-
178
-
179
-
180
-
181
-
182
-
183
-
184
-
185
-
186
-
187
-
188
-
189
-
190
-
191
-
192
-
193
-
194
-
195
-
196
-
197
-
198
-
199
-
200
-
201
-
202
-
203
-
204
-
205
-
206
-
207
-
208
-
209
-
210
-
211
-
212
-
213
-
214
-
215
-
216
-
217
-
218
-
219
-
220
-
221
-
222
-
223
-
224
-
225
-
226
-
227
-
228
-
229
-
230
-
231
-
232
-
233
-
234
-
235
-
236
-
237
-
238
-
239
-
240
-
241
-
242
-
243
-
244
-
245
-
246
-
247
-
248
-
249
-
250
-
251
-
252
-
253
-
254
-
255
-
256
-
257
-
258
-
259
-
260
-
261
-
262
-
263
-
264
-
265
-
266
-
267
-
268
-
269
-
270
-
271
-
272
-
273
-
274
-
275
-
276
-
277
-
278
-
279
-
280
-
281
-
282
-
283
-
284
-
285
-
286
-
287
-
288
-
289
-
290
-
291
-
292
-
293
-
294
-
295
-
296
-
297
-
298
-
299
-
300
-
301
-
302
-
303
-
304
-
305
-
306
-
307
-
308
-
309
-
310
![]() |
![]() |
![](/manual_guide/products/ibm-e027sllh-troubleshooting-guide-7c8d102/197.png)