IBM Tivoli Monitoring, Version 6.3

tacmd editEventDest

Description

Use the tacmd editEventDest command to modify an existing event destination server definition on the server.

CLI syntax

tacmd editEventDest
                      {-i|--id|--serverID} ID
                      {-p|--property|--properties} NAME=VALUE...
                      [{-f|--force}]

where:

-i|--id|–serverID

Identifies the Server Destination Id of the event destination server definition to modify on the server. The value must be a value between 1 and 999.

-f|--force

Modifies the event destination server definition on the server without prompting for confirmation.

-p|--property|--properties

Specifies one or more NAME=VALUE pairs that identify the properties and values to modify.

Host properties should be specified in the format:

HOST{1|2|3|4|5|6|7|8}=HOSTNAME[:PORT]

Host entries must be defined such that they are sequential in existence; for example, you cannot specify the HOST3 property if HOST2 is not also specified. If a port value is not provided for a host entry, the port will default to 0.

A maximum of 5 default servers are allowed. To designate this event destination server as a default server, specify the DEFAULT|DEFAULTSERVER property with a value of Y.

To delete the value for a property, specify the property in the format NAME=. The NAME|SERVERNAME, TYPE|SERVERTYPE, and HOST1 properties cannot be deleted. When you delete a HOST property, all subsequent HOST properties are shifted down, such that if you delete HOST3, HOST3 will assume the value for HOST4, HOST4 will assume the value for HOST5, and so on.

The property TYPE indicates whether the event destination server is a TEC server or OMNIbus server. Although this indication alters the internal behavior of the code, it is transparent to the user.

The following property names are valid:

DESC|DESCRIPTION
NAME|SERVERNAME
TYPE|SERVERTYPE
DEFAULT|DEFAULTSERVER
HOST1
HOST2
HOST3
HOST4
HOST5
HOST6
HOST7
HOST8

CLI example

This example modifies an existing event destination server definition 150 on the server, changes the TYPE from ‘T’ (TEC) to ‘M’ (Micromuse/Omnibus), adds a new HOST entry and also modifies the description:

tacmd editEventDest  -i 150  -p  TYPE=M HOST2=HDCHASDSTC0816:5529 
DESCRIPTION="Local OMNI server"

These commands set multiple default event servers.

tacmd createEventDest -i 123 -p host1=bigTECserver:4567 default=Y name=myTEC
tacmd createEventDest -i 124 -p host1=bigTECserver1:4577 default=Y name=myTEC1

or with the tacmd editEventDest command, you can set DEFAULT=Y for existing event servers.

To send a situation to all three default event servers (the two that are defined and the basic one), specify an empty destination for the situation, as depicted in the following example.

C:\ODI>tacmd viewsit -s test_tec1
Name                   : test_tec1
Full Name              :
Description            :
Type                   : Windows OS
Formula                : *IF *VALUE NT_Cache.Copy_Read_Hits_% *EQ 1
Sampling Interval      : 0/0:15:0
Run At Start Up        : Yes
Distribution           :
Text                   :
Action Location        : Agent
Action Selection       : System Command
System Command         : *NONE
True For Multiple Items: Action on First Item only
TEC Severity           : Critical
TEC Forwarding         : Y
TEC Destination        :

Note: The TEC Destination field is empty, but TEC Forwarding is set to Y.

In this example, the situation is sent to the <default receiver>, myTEC and myTEC1 event servers. In the TEC interface, only <Default EIF Receiver> displays in the left column (Assigned EIF Receivers), while myTEC and myTEC1 display in the right column (Available EIF Receivers), despite being set as DEFAULT servers. This is a known Tivoli Enterprise Portal limitation.

To change a situation from a specified TEC destination to an unspecified (empty) TEC destination, perform the following steps:

Export the situation to an XML file:

C:\ODI>tacmd viewsit -s test_tec1 -e c:\test_tec1.xml

Edit the XML file and change
```
<SITINFO>
<![CDATA[SEV=Critical;TFWD=Y;~;"]] >
</SITINFO>
```
accordingly, to specify a null destination server.
Delete the original situation and import the situation back to the server:
```
tacmd createsit -i c:\test_tec1.xml
```

Return values

See Table 1.

Related commands

Return to Table 1.

Feedback