IBM E027SLL-H Troubleshooting Guide - Page 253

Event status updates in Netcool/OMNIbus are not forwarded, to Tivoli Monitoring

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

Table 19. Resolving problems sending events to Netcool/OMNIbus (continued) Cause Resolution Events are cached at the Tivoli Enterprise Monitoring Server. The EIF cache file lists events. On Windows, you can find the EIF cache file in %ITM_HOME%\CMS\TECLIB directory of the hub monitoring server. On UNIX or Linux, you can find the EIF cache file in $ITMHOME/tables/tems_name/TECLIB directory of the hub monitoring server. v Check to see if the OMNIbus/Netcool Probe for Tivoli EIF is running. On Windows, if it is running as a service, determine whether the service is running. If it is not running as a service, look for the nco_p_nonnative.exe process. If the process is not running, start the process using %OMNIHOME%\probes\win32\nco_p_tivoli_eif.bat command. On UNIX or Linux, use - grep for the nco_p_tivoli_eif process. If the process is not running, start the process using $OMNIHOME/probes/nco_p_tivoli_eif command. v Check to see if the port number used to send events from the IBM Tivoli Monitoring side matches the port number used by the EIF Probe. To check the port number information on the IBM Tivoli Monitoring side, you can use the IBM Tivoli Monitoring CLI commands listeventdest and vieweventdest to find the server and port information. See the example above. On the OMNIbus side, you can look at the PortNumber property in the $OMNIHOME/probes/$ARCH/tivoli_eif.props file. If you are using Netcool/OMNIbus Probe for Tivoli EIF Version 8 or later, the default port number is 9998. If Tivoli Business Service Manager Version 4.2.1 was used to install the probe, the default probe port number is 5530. Note: You can also check the Netcool/OMNIbus Probe for Tivoli EIF log file and the Netcool/OMNIbus ObjectServer log file to determine if those components are unable to process the events. See "Log files for Netcool/OMNIbus Event Synchronization" on page 232 to determine the location of the log files. Event status updates in Netcool/OMNIbus are not forwarded to Tivoli Monitoring If status updates for acknowledgements, deacknowledgements, and clearing of events are not forwarded from Netcool/OMNIbus to Tivoli Monitoring, consider the following possible causes and resolutions: Chapter 14. Event synchronization troubleshooting 235

  • 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
Table 19. Resolving problems sending events to Netcool/OMNIbus (continued)
Cause
Resolution
Events are cached at the
Tivoli Enterprise
Monitoring Server.
The EIF cache file lists events. On Windows, you can find the
EIF cache file in
%ITM_HOME%\CMS\TECLIB
directory of the hub
monitoring server. On UNIX or Linux, you can find the EIF
cache file in
$ITMHOME/tables/tems_name/TECLIB
directory of the
hub monitoring server.
v
Check to see if the OMNIbus/Netcool Probe for Tivoli EIF is
running. On Windows, if it is running as a service, determine
whether the service is running. If it is not running as a
service, look for the
nco_p_nonnative.exe
process. If the
process is not running, start the process using
%OMNIHOME%\probes\win32\nco_p_tivoli_eif.bat
command.
On UNIX or Linux, use
- grep
for the
nco_p_tivoli_eif
process. If the process is not running, start the process using
$OMNIHOME/probes/nco_p_tivoli_eif
command.
v
Check to see if the port number used to send events from the
IBM Tivoli Monitoring side matches the port number used by
the EIF Probe.
To check the port number information on the IBM Tivoli
Monitoring side, you can use the IBM Tivoli Monitoring CLI
commands
listeventdest
and
vieweventdest
to find the
server and port information. See the example above.
On the OMNIbus side, you can look at the PortNumber
property in the
$OMNIHOME/probes/$ARCH/tivoli_eif.props
file.
If you are using Netcool/OMNIbus Probe for Tivoli EIF
Version 8 or later, the default port number is 9998. If Tivoli
Business Service Manager Version 4.2.1 was used to install the
probe, the default probe port number is 5530.
Note:
You can also check the Netcool/OMNIbus Probe for Tivoli EIF log file and
the Netcool/OMNIbus ObjectServer log file to determine if those components are
unable to process the events. See “Log files for Netcool/OMNIbus Event
Synchronization” on page 232 to determine the location of the log files.
Event status updates in Netcool/OMNIbus are not forwarded
to Tivoli Monitoring
If status updates for acknowledgements, deacknowledgements, and clearing of
events are not forwarded from Netcool/OMNIbus to Tivoli Monitoring, consider
the following possible causes and resolutions:
Chapter 14. Event synchronization troubleshooting
235