Event Management and Best Practices

364 Event Management and Best Practices

GatewayQueueSize=40000

BufEvtPath=C:\WINNT\system32\drivers\etc\Tivoli/tec/tec_gateway_sce.cache

Pre37Server=no

UseStateCorrelation=YES

StateCorrelationConfigURL=file:///C:/WINNT/system32/drivers/etc/Tivoli/tec/tecr

oot.xml

SendEventPort=5561

ReceiveAckPort=5562

ReceiveEventPort=5563

SendAckPort=5564

gwr_ActiveConnections=20

gwr_ActiveConnectionsSafety=80

gwr_Enable=yes

LogLevel=ALL

LogFileName=c:\temp\tec_gateway.log

TraceLevel=ALL

TraceFileName=c:\temp\tec_gateway.trc

#

7.2.2 NetView

We do not encounter installation issues during the NetView installation.

7.2.3 IBM Tivoli Switch Analyzer

On AIX, ensure that there is at least 50 MB in /tmp, or run the installation using

another temporary directory with at least 50 MB by issuing the following

command:

./switchanalyzer_install -is:tempdir alternate temp directory

Make sure you have X Window System capability, since the InstallShield wizard

is used.

Use the ./switchanalyzer_install command to invoke the InstallShield wizard

and answer the appropriate questions. Figure 7-2 shows the initial window. Then

click Next.

Chapter 7. A case study 365

Figure 7-2 InstallShield wizard initial window

The Software License Agreement panel (Figure 7-3) opens. Agree to the

licenses and click Next.

Figure 7-3 License agreement window

366 Event Management and Best Practices

You see a window similar to the one in Figure 7-4. If you are ready to begin the

installation, select Yes and click Next.

Figure 7-4 Confirmation window

Chapter 7. A case study 367

You see a summary window (Figure 7-5). Confirm the information and click Next.

Figure 7-5 Summary window

The installation begins. When it completes, you see a window similar to the

example in Figure 7-6.

Figure 7-6 Completion window

368 Event Management and Best Practices

When the installation is completed, verify that the daemon is running using the

ovstatus itsl2 command. Use the following procedure to manually start the

itsl2 daemon:

򐂰 For UNIX, if the Tivoli NetView product is not started, always use the

/usr/OV/bin/serversetup utility to start the daemons. This utility automatically

starts the Tivoli Switch Analyzer product. If the Tivoli NetView product is

started, use the Tivoli NetView ovstop and ovstart commands to start and

stop itsl2 daemon. For example, use the following command to start the itsl2

daemon:

/usr/OV/bin/ovstart itsl2

򐂰 For Windows, use the following command to start IBM Tivoli Switch Analyzer:

\usr\ov\bin\ovstart itsl2

Layer 2 root cause events and topology status updates are available immediately

after IBM Tivoli Switch Analyzer is installed and started. IBM Tivoli Switch

Analyzer reports are enabled immediately for the SuperUser role. However, you

must activate them as follows:

1. From the main menu of the Tivoli NetView native console, select

Administrator

→Security Administration →Web Console Security to start

the security console.

2. From the main menu, select File

→Save, and then click File →Restart Web

Server.

IBM Tivoli Switch Analyzer reports are not available for other user roles until you

enable and activate them as follows:

1. From the main menu of the Tivoli NetView native console, select

Administrator

→Security Administration →Web Console Security to start

the security console.

2. Check the following Tivoli Switch Analyzer reports for the required roles. The

SuperUser role includes them all as the default value.

– Impact Analysis

– Impact Analysis (connectors)

–Discovery

–Rediscovery

3. From the main menu, select File

→Save, and then click File →Restart Web

Server to integrate the menu items, as shown in Figure 7-7.