IBM E027SLL-H Troubleshooting Guide - Page 210

One monitoring agent's workspaces are listed under another agent, node on the portal client

Get IBM E027SLL-H - Tivoli Monitoring - PC PDF manuals and user guides View all IBM E027SLL-H manuals
Add to My Manuals
Save this manual to your list of manuals

Page 210 highlights

v For i5/OS agents, find the QAUTOTMP/KMSPARM library in member KBBENV. 2. If you cannot find the CTIRA_HOSTNAME environment variable, you must add it to the configuration file of the monitoring agent: v On Windows: Use the Advanced > Edit Variables option. v On UNIX and Linux: Add the variable to the config/product_code.ini and to config/product_code.config files. v On z/OS: Add the variable to the RKANPAR library, member Kproduct_codeENV. v On i5/OS: Add the variable to the QAUTOTMP/KMSPARM library in member KBBENV. 3. Some monitoring agents (for example, the monitoring agent for MQ Series) do not reference the CTIRA_HOSTNAME environment variable to generate component names. Check the documentation for the monitoring agent that you are using for information on name generation. If necessary, contact IBM Software Support. Other symptoms that can be observed when multiple instances of a monitoring agent with the same managed system name attempt to connect to a Tivoli Enterprise Monitoring Server include the following: v A managed system name's status toggles ON and OFF line constantly as one agent heartbeat overlays the other's information. v High CPU usage is observed that is caused by a constant thrashing of the Tivoli Enterprise Portal Server or Tivoli Enterprise Monitoring Server. v Situation distribution, Tivoli Enterprise Monitoring Server table relationship updates, Tivoli Enterprise Portal Server topology view updates; all could be initiated as each agent heartbeat registers its changing properties. Other solutions besides ensuring that each managed system name is unique are the following: v Detect and stop the agent process that is running improperly. This can be done by checking the Tivoli Enterprise Portal Server Managed System Status network address of the managed system name that seems to toggle ON and OFF line. Go to the system indicated in the network address and check for multiple running monitoring agents. v If the agents running on the same system are the same product, stop or kill the unintended agent process. v Delete the faulty agent managed system name from the enterprise managed system status so that the new managed system name can register properly with the Tivoli Enterprise Monitoring Server. You might need to stop the correct agent process so that it is OFF line. One monitoring agent's workspaces are listed under another agent node on the portal client About this task This problem has been seen in monitoring agents that exist on the same system. Set the CTIRA_HOSTNAME environment variable configuration file for the monitoring agent as follows: 1. Open the configuration file for the monitoring agent, which is located in the following path: 192 IBM Tivoli Monitoring: Troubleshooting Guide

  • 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
v
For i5/OS agents, find the
QAUTOTMP/KMSPARM
library in member
KBBENV
.
2.
If you cannot find the
CTIRA_HOSTNAME
environment variable, you must add it to
the configuration file of the monitoring agent:
v
On Windows: Use the
Advanced
>
Edit Variables
option.
v
On UNIX and Linux: Add the variable to the
config/product_code.ini
and
to
config/product_code.config
files.
v
On z/OS: Add the variable to the
RKANPAR
library, member
Kproduct_codeENV.
v
On i5/OS: Add the variable to the
QAUTOTMP/KMSPARM
library in member
KBBENV
.
3.
Some monitoring agents (for example, the monitoring agent for MQ Series) do
not reference the
CTIRA_HOSTNAME
environment variable to generate component
names. Check the documentation for the monitoring agent that you are using
for information on name generation. If necessary, contact IBM Software
Support.
Other symptoms that can be observed when multiple instances of a monitoring
agent with the same managed system name attempt to connect to a Tivoli
Enterprise Monitoring Server include the following:
v
A managed system name's status toggles ON and OFF line constantly as one
agent heartbeat overlays the other's information.
v
High CPU usage is observed that is caused by a constant thrashing of the Tivoli
Enterprise Portal Server or Tivoli Enterprise Monitoring Server.
v
Situation distribution, Tivoli Enterprise Monitoring Server table relationship
updates, Tivoli Enterprise Portal Server topology view updates; all could be
initiated as each agent heartbeat registers its changing properties.
Other solutions besides ensuring that each managed system name is unique are the
following:
v
Detect and stop the agent process that is running improperly. This can be done
by checking the Tivoli Enterprise Portal Server Managed System Status network
address of the managed system name that seems to toggle ON and OFF line. Go
to the system indicated in the network address and check for multiple running
monitoring agents.
v
If the agents running on the same system are the same product, stop or kill the
unintended agent process.
v
Delete the faulty agent managed system name from the enterprise managed
system status so that the new managed system name can register properly with
the Tivoli Enterprise Monitoring Server. You might need to stop the correct agent
process so that it is OFF line.
One monitoring agent's workspaces are listed under another agent
node on the portal client
About this task
This problem has been seen in monitoring agents that exist on the same system.
Set the CTIRA_HOSTNAME environment variable configuration file for the
monitoring agent as follows:
1.
Open the configuration file for the monitoring agent, which is located in the
following path:
192
IBM Tivoli Monitoring: Troubleshooting Guide