Deployment Guide Series: IBM Tivoli Monitoring V6.2

318 Deployment Guide Series: IBM Tivoli Monitoring V6.2

where:

– /tmp/<agent_baroc_file> specifies the location and name of the monitoring

agent .baroc file. The example above uses the /tmp directory as the

location.

– <rb_name> is the name of the rule base that you are using for Event

Synchronization.

4. Compile and load the rule base by running the following commands:

wrb -comprules <rb_name>

wrb -loadrb <rb_name>

5. Stop and restart the event server by running the following commands:

wstopesvr

wstartesvr

When you have loaded each of the agent .baroc files into the rule base and

restarted the event server, the event server is ready to receive and correctly

parse any events it receives from the monitoring server from one of the installed

monitoring agents.

5.1.3 Configuring your monitoring server to forward events

Before the monitoring server forwards any situation events to Tivoli Enterprise

Console, you have to enable the forwarding of events.

Configuring Windows monitoring servers

Use the following steps to enable event forwarding on your monitoring server:

1. Select Start → Programs → IBM Tivoli Monitoring → Manage Tivoli

Monitoring Services. The Manage Tivoli Enterprise Monitoring Services

window is displayed.

2. Right-click the monitoring server and click Reconfigure.

3. In the configuration options window, select Tivoli Event Integration Facility.

4. Click OK and OK.

5. Complete the fields as described in Table 5-4 on page 319.

Chapter 5. Integrating event management systems 319

Table 5-4 Tivoli Monitoring Server Information

6. Click OK.

Configuring UNIX monitoring servers

If you installed the monitoring server using the configuration instructions in this

chapter, you probably have already configured the TEC Server and TEC Port

information for the UNIX monitoring server during installation. However, if you did

not configure this information, see “Hub monitoring server configuration on a

Linux or UNIX server” on page 74. Example 5-1 describes the TEC Server

configuration.

Example 5-1 TEC Server configuration

[root@server2][/opt/IBM/ITM/bin]-> ./itmcmd config -S -t HUB_TEMS

Configuring TEMS...

Hub or Remote [1=*LOCAL, 2=*REMOTE] (Default is: 1):

TEMS Host Name (Default is: server2):

Network Protocol 1 [ip, sna, ip.pipe or ip.spipe] (Default is:

ip.pipe):

Now choose the next protocol number from one of these:

- ip

- sna

- ip.spipe

- 0 for none

Network Protocol 2 (Default is: ip):

Now choose the next protocol number from one of these:

- sna

- ip.spipe

- 0 for none

Network Protocol 3(Default is: ip.spipe):

IP Port Number (Default is: 1918):

IP.PIPE Port Number (Default is: 1918):

Field Description

Server or EIF Probe

Location

Type the host name or IP address for the computer where

the IBM Tivoli Enterprise Console event server is

installed.

Port Number Type the port number for the event server. If the event

server is using port mapping, set this value to 0. If the

event server was configured to use a specific port

number, specify that number.

320 Deployment Guide Series: IBM Tivoli Monitoring V6.2

Enter name of KDC_PARTITION (Default is: null):

Enter path and name of KDC_PARTITIONFILE (Default is:

/opt/IBM/ITM/tables/HUB_TE

MS/partition.txt):

IP.SPIPE Port Number (Default is: 3660):

Configuration Auditing? [1=YES, 2=NO] (Default is: 1):

Hot Standby TEMS Host Name or type 0 for "none" (Default is: 0):

Enter Optional Primary Network Name or type 0 for "none" :(Default is:

0):

Security: Validate User ? [1=YES, 2=NO] (Default is: 1):

LDAP Security: Validate User with LDAP ? [1=YES, 2=NO](Default is: 2):

Tivoli Event Integration Facility? [1=YES, 2=NO] (Default is: 2): 1

EIF Server?(Default is: none): nottingham

EIF Port? (Default is: 5529):

Disable Workflow Policy/Tivoli Emitter Agent Event Forwarding? [1=YES,

2=NO] (De

fault is: 2):

... Writing to database file for ms.

Hubs

## CMS_Name

1 ip.pipe:HUB_TEMS[1918]

1)Add, 2)Remove ##, 3)Modify Hub ##, 4)UserAccess ##, 5)Cancel,

6)Save/exit: 6

... creating config file

"/opt/IBM/ITM/config/server2_ms_HUB_TEMS.config"

... creating file "/opt/IBM/ITM/tables/HUB_TEMS/glb_site.txt."

... updating "/opt/IBM/ITM/config/kbbenv"

... verifying Hot Standby.

Info - Checking TEMS User Authentication requirements.

Info - OK, TEMS User Authentication requirements complete.

TEMS configuration completed...