IBM E027SLL-H Troubleshooting Guide - Page 199

Failure when importing situation xml file edited with WordPad

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 199 highlights

There can be a variety of factors that lead to a failed history collection: v The size of the history data file affects the amount of time it takes the agent to read the file. v The amount of data the agent is trying to send to the monitoring server. v The bandwidth of the communications (for example, a slow data rate). Situations with attributes from more than 1 group not supported with autonomous agent When using autonomous agent in Manage Connected Mode, creating situations with AND and OR logic, and using values from two different attribute groups, the traps do not list the predicates in an expected way. If you have defined a situation that attempts to combine attributes across more than 1 attribute group, this is not currently supported by any autonomous agent processing mode or private situations. The monitoring server performs the evaluation of situations having combined attribute groups. This can be either from embedded situations, or two or more attribute groups in the same predicate, for example, WHERE USER=abc AND LOCALTIME=today. Failure when importing situation xml file edited with WordPad If you edit an xml file for a situation using WordPad, and then import the situation (tacmd createsit-i xml), the command fails. If you edit the xml file using Notepad, it works correctly. Use Notepad to edit situation xml files. Printer details of another system are displayed on the Tivoli Enterprise Portal When connecting to a system remotely, printers on that local system can be seen from the Tivoli Enterprise Portal on the remote system. You should be aware that by using a remote desktop, printer information might be displayed in the Tivoli Enterprise Portal and shared with others. CTIRA_MAX_RECONNECT_TRIES environment variable is now obsolete The agent now attempts communication with a monitoring server until a connection is successfully established. There is no longer a limit on the number of connection attempts. If the CTIRA_MAX_RECONNECT_TRIES environment variable is specified, it is accepted, and results in the agent reverting to the previous behavior of there being a limit on connection attempts. A trace message is also produced, indicating that this variable is obsolete. If you specify this variable and the number of connection attempts to the monitoring server exceeds CTIRA_MAX_RECONNECT_TRIES, the agent attempts to shutdown. If the Agent Management Services Watchdog is running, it immediately restarts the agent. If you want the agent to shutdown when CTIRA_MAX_RECONNECT_TRIES is exceeded, this Watchdog process must be disabled. Use the AMS Stop Management action to disable this watchdog process. Chapter 10. Monitoring agent troubleshooting 181

  • 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
There can be a variety of factors that lead to a failed history collection:
v
The size of the history data file affects the amount of time it takes the agent to
read the file.
v
The amount of data the agent is trying to send to the monitoring server.
v
The bandwidth of the communications (for example, a slow data rate).
Situations with attributes from more than 1 group not supported with
autonomous agent
When using autonomous agent in Manage Connected Mode, creating situations
with AND and OR logic, and using values from two different attribute groups, the
traps do not list the predicates in an expected way.
If you have defined a situation that attempts to combine attributes across more
than 1 attribute group, this is not currently supported by any autonomous agent
processing mode or private situations. The monitoring server performs the
evaluation of situations having combined attribute groups. This can be either from
embedded situations, or two or more attribute groups in the same predicate, for
example, WHERE USER=abc AND LOCALTIME=today.
Failure when importing situation xml file edited with WordPad
If you edit an xml file for a situation using WordPad, and then import the situation
(
tacmd createsit-i xml
), the command fails. If you edit the xml file using
Notepad, it works correctly. Use Notepad to edit situation
xml
files.
Printer details of another system are displayed on the Tivoli Enterprise
Portal
When connecting to a system remotely, printers on that local system can be seen
from the Tivoli Enterprise Portal on the remote system. You should be aware that
by using a remote desktop, printer information might be displayed in the Tivoli
Enterprise Portal and shared with others.
CTIRA_MAX_RECONNECT_TRIES environment variable is now
obsolete
The agent now attempts communication with a monitoring server until a
connection is successfully established. There is no longer a limit on the number of
connection attempts. If the CTIRA_MAX_RECONNECT_TRIES environment
variable is specified, it is accepted, and results in the agent reverting to the
previous behavior of there being a limit on connection attempts. A trace message is
also produced, indicating that this variable is obsolete.
If you specify this variable and the number of connection attempts to the
monitoring server exceeds CTIRA_MAX_RECONNECT_TRIES, the agent attempts
to shutdown. If the Agent Management Services Watchdog is running, it
immediately restarts the agent. If you want the agent to shutdown when
CTIRA_MAX_RECONNECT_TRIES is exceeded, this Watchdog process must be
disabled. Use the AMS Stop Management action to disable this watchdog process.
Chapter 10. Monitoring agent troubleshooting
181