IBM E027SLL-H Troubleshooting Guide - Page 107
Self-describing capability might be overwritten by UNIX, monitoring server application support
![]() |
View all IBM E027SLL-H manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 107 highlights
Self-describing capability might be overwritten by UNIX monitoring server application support Under the following conditions, if self-describing product installation is expected, one or more Tivoli Monitoring products might not be properly enabled for monitoring: v The self-describing product installation for a hub or remote monitoring server might not run v The product application support installation (seeding) step might not take place on the hub or remote monitoring server v The self-describing product installation on the Tivoli Enterprise Portal Server might not take place If your environment has a self-describing monitoring agent that is at a lower version of IBM Tivoli Monitoring than the Tivoli Enterprise Monitoring Server on Linux or UNIX that it connects to, it is possible that the installation of application support to the monitoring server overwrites the monitoring agent's self-describing capability. Diagnosing that the self-describing capability is not available Installation of a monitoring server on Linux or UNIX is different from that on Windows in that application support for all base monitoring agents and other supported agents are automatically installed on the monitoring server. The automatic installation of application support files for the agents might affect the self-describing agent capability. Check the monitoring server and portal server to ensure that self-describing agent products are installed as expected. To determine if the monitoring server self-describing agent product installation and seeding took place, check the enterprise self-describing agent installation status with the following command: tacmd listappinstallrecs -t PC where PC is the product code for the self-describing agent in question, such as nt for the Windows OS agent. The following example of the output from tacmd listappinstallrecs -t nt shows how the results of a successful installation might look: HUB/RTEMS HUB_TEMS HUB_TEMS HUB_TEMS REMOTE_TEMS_ZOS PRODUCT NT NT NT NT VERSION GRPID ID IDVER SEEDSTATE STATE STATUS 06230000 5655 TMS 06230000 Y IC 0 06230000 5655 TPS 06230000 IC 0 06230000 5655 TPW 06230000 IC 0 06230000 5655 TMS 06230000 Y IC 0 The command output has entries for the HUB TEMS and any REMOTE_TEMS that the agent can be connected to. The entries for PRODUCT NT with ID TMS have a value of IC in the STATE column, Y in the SEEDSTATE column, and 0 in the STATUS column. An unsuccessful installation and seeding might generate results like those in the following example: HUB/RTEMS HUB_TEMS PRODUCT VERSION GRPID ID IDVER SEEDSTATE STATE STATUS NT 06230000 5655 TMS 06230000 0 The record for PRODUCT NT and ID TMS might not exist or, if it does exist, the STATE and SEEDSTATE columns are empty. In this example, the results show that the product NT was manually installed at the hub (STATE column is empty and there is an entry only for ID TMS). Chapter 5. Installation and configuration troubleshooting 89
-
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/107.png)