This section contains the variables for customizing the behavior of event status processing when agent switching is used.
ITM_HOME\cms\KBBENV
For example: C:\IBM\ITM\cms\KBBENV
ITM_HOME/config/tems_hostname_ms_tems_name.config
For example: /opt/IBM/ITM/config/edinburg_ms_labtems.config
For
Linux/UNIX systems, you must add the variables to the .config and
the .ini files. The name and location of the .ini file
is ITM_HOME/config/ms.ini.&shilev.&rtename.RKANPARU(KDSENV)
For example: ITM.SYP1.RKANPARU(KDSENV)
Variable | Architecture Type | Details | Administrator |
---|---|---|---|
IRA_MIN_NO_DATA_WAIT_TIME | Unidirectional and bidirectional | The minimum time to wait before the monitoring
server closes a situation event. This parameter is defined in number
of seconds. The default value is zero. By default, after an agent is disconnected from a Tivoli Enterprise Monitoring Server, situations already open will remain open for three situation polling intervals. For example, take two sampled situations, S1 and S2, with intervals of 30 seconds and 15 minutes respectively. Both situations are open when the agent loses connection. Situation S1 closes after at least one minute and 30 seconds. Situation S2 closes after at least 45 minutes. With agent switching, if a situation closes too soon it might generate duplicate events because the agent did not have sufficient time to connect to the backup monitoring server before the primary server closes the original event. This is particularly true for situations with very short polling intervals. In such
a scenario you can use the IRA_MIN_NO_DATA_WAIT_TIME variable
to set the minimum wait time before a situation is closed. Using the
example above, if IRA_MIN_NO_DATA_WAIT_TIME is set to 300 (5 minutes),
S1 will close after 5 minutes not 90 seconds. S2 is unaffected and
will close after 45 minutes as before.
Note: You should set this variable
in the environment file for all of your monitoring servers.
|
IBM® Tivoli Monitoring |
CMS_SIT_TIME_VALIDATION | Unidirectional and bidirectional | Valid entries are Y or N. The default is N. By default, the monitoring server handles situation events on a first-come-first-serve basis. In a scenario where agent switching is enabled an agent might send events through two different monitoring servers. The events that arrive first might not necessarily be the earlier events if one of the monitoring servers encountered connection issues. This generally has little impact on situation event processing, except when a monitoring server is shutdown and some situations might be closed prematurely even though the agent is already connected to a different monitoring server. You must perform two actions to avoid this scenario:
|
IBM Tivoli Monitoring |
CMS_SIT_CHECK_NODESTS | Unidirectional and bidirectional | Valid entries are Y or N. The default is N. This variable is only applicable for users of event integration with Tivoli Enterprise Console® and Omnibus. When the CMS_SIT_CHECK_NODESTS variable is set to Y in the environment file, the hub monitoring servers check the agent status whenever a close status update event is forwarded to Netcool/Omnibus. The CMS_SIT_CHECK_NODESTS variable should only be added to the hub monitoring server environment file. If the agent is offline the close status update event is tagged with a special OFFLINE indicator in the situation_eventdata EIF slot. If you
do not want events to be closed in Netcool/OMNIbus when an agent goes
offline, you can customize the EIF probe rules to ignore close events
where the situation_status slot is set to N and the situation_eventdata
EIF slot is set to OFFLINE. See Customizing the rules file for details on how to
add customizations to the EIF probe rules. You should also consider
setting the IRA_MIN_NO_DATA_WAIT_TIME environment variables described
in this table so that close status events are not sent to Netcool/OMNIbus
until after the agent offline condition has been detected. (If the
default agent heartbeat interval is used, it can take between 10 to
20 minutes before the monitoring server detects that the agent is
no longer online.)
Note: You should only set the CMS_SIT_CHECK_NODESTS
variable in the environment file of your hub monitoring server.
|
IBM Tivoli Monitoring |