IBM E027SLL-H Troubleshooting Guide - Page 65

Setting the trace option for the universal agent, Setting the trace option for the Warehouse Proxy

Page 65 highlights

Setting the trace option for the universal agent About this task Use the universal agent trace facility to diagnose problems . The universal agent uses RAS1 tracing. By default, universal agent trace data is written to a file in the logs subdirectory. The default RAS1 trace level is ERROR for all universal agent components and modules. On Windows, the kumras1.log is overwritten each time the universal agent starts and there is no method for archiving previous RAS1 log files. Therefore, you must obtain the RAS1 log that matches the problem occurrence before contacting IBM Software Support. You can set tracing options for individual universal agent components and modules in the KUMENV file on Windows or the um.ini file on UNIX-based systems. RAS1 supports pattern matching. For example, (UNIT:kums options) traces all SNMP data provider modules because they all begin with kums. Detailed RAS1 tracing can degrade universal agent performance due to high CPU usage and I/O overhead. Therefore, set the universal agent RAS1 tracing to KBB_RAS1=ERROR after problem diagnosis. If a module produces excessive error messages and fills the RAS1 log, set (UNIT:modulename None) to suppress the module until you resolve the errors. If you discover an old Windows RAS1 log file, the KBB_RAS1 environment was erased or commented out in the KUMENV file, add KBB_RAS1=ERROR to the install_dir\logs\hostname_um_timestamp.log to reactivate universal agent RAS1 tracing. Set the universal agent trace from Manage Tivoli Enterprise Monitoring Services: 1. Right-click the universal agent. 2. Select Advanced > Edit Trace Parms. 3. Select the RAS1 filters. The default setting is ERROR 4. Accept the defaults for the rest of the fields. 5. Click OK to set the new trace options. 6. Click Yes to recycle the service. Setting the trace option for the Warehouse Proxy agent Procedure 1. On Windows systems, on the computer where the Tivoli Enterprise Monitoring Server is installed, select Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services. 2. Right-click Warehouse Proxy. 3. Select Advanced > Edit Trace Parms. 4. Select the RAS1 filters. The default setting is ERROR. 5. Accept the defaults for the rest of the fields. 6. Click OK to set the new trace options. 7. Click Yes to recycle the service. Warehouse Proxy agent trace configuration: You can edit the handler configuration file $CANDLEHOME%\Config\ ITMConfigRAS.properties for UNIX systems and the %CANDLEHOME%\Config\ ITMConfigRAS.properties file for Windows systems, and set the handler99 as the configuration handler and set the debug tracing to the maximum DEBUG_MAX as shown below: Handler99.name=config Handler99.scope=* Handler99.scopeName=Config Chapter 4. Tools 47

  • 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

Setting the trace option for the universal agent
About this task
Use the universal agent trace facility to diagnose problems . The universal agent
uses RAS1 tracing. By default, universal agent trace data is written to a file in the
logs subdirectory. The default RAS1 trace level is ERROR for all universal agent
components and modules. On Windows, the
kumras1.log
is overwritten each time
the universal agent starts and there is no method for archiving previous RAS1 log
files. Therefore, you must obtain the RAS1 log that matches the problem
occurrence before contacting IBM Software Support. You can set tracing options for
individual universal agent components and modules in the
KUMENV
file on
Windows or the
um.ini
file on UNIX-based systems.
RAS1 supports pattern matching. For example, (UNIT:kums options) traces all
SNMP data provider modules because they all begin with
kums
. Detailed RAS1
tracing can degrade universal agent performance due to high CPU usage and I/O
overhead. Therefore, set the universal agent RAS1 tracing to
KBB_RAS1=ERROR
after
problem diagnosis. If a module produces excessive error messages and fills the
RAS1 log, set (
UNIT:modulename None
) to suppress the module until you resolve the
errors. If you discover an old Windows RAS1 log file, the KBB_RAS1 environment
was erased or commented out in the
KUMENV
file, add
KBB_RAS1=ERROR
to the
install_dir\logs\hostname_um_timestamp.log
to reactivate universal agent RAS1
tracing.
Set the universal agent trace from Manage Tivoli Enterprise Monitoring Services:
1.
Right-click the universal agent.
2.
Select
Advanced
>
Edit Trace Parms
.
3.
Select the RAS1 filters. The default setting is ERROR
4.
Accept the defaults for the rest of the fields.
5.
Click
OK
to set the new trace options.
6.
Click
Yes
to recycle the service.
Setting the trace option for the Warehouse Proxy agent
Procedure
1.
On Windows systems, on the computer where the Tivoli Enterprise Monitoring
Server is installed, select
Start
>
Programs
>
IBM Tivoli Monitoring
>
Manage
Tivoli Enterprise Monitoring Services
.
2.
Right-click
Warehouse Proxy
.
3.
Select
Advanced
>
Edit Trace Parms
.
4.
Select the RAS1 filters. The default setting is ERROR.
5.
Accept the defaults for the rest of the fields.
6.
Click
OK
to set the new trace options.
7.
Click
Yes
to recycle the service.
Warehouse Proxy agent trace configuration:
You can edit the handler configuration file
$CANDLEHOME%\Config\
ITMConfigRAS.properties
for UNIX systems and the
%CANDLEHOME%\Config\
ITMConfigRAS.properties
file for Windows systems, and set the handler99 as the
configuration handler and set the debug tracing to the maximum DEBUG_MAX as
shown below:
Handler99.name=config
Handler99.scope=*
Handler99.scopeName=Config
Chapter 4. Tools
47