cc/td/doc/product/rtrmgmt/bluelist/cwblue31
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Improving Performance
Stopping the Monitor Daemon
Stopping the Poller Daemon While Doing Discovery
Limiting Remote Users
Closing Unused Maps Windows
Improving DLSw Poller Performance
Clean Up Log Files

Improving Performance


This chapter provides information on techniques you can use to improve the performance of the CiscoWorks Blue applications.

This chapter includes the following main sections:

Stopping the Monitor Daemon

If you are locked out of Maps views due to continual view updates, try stopping the monitor daemon so that it will not keep trying to update the maps. To stop the monitor daemon, use the Process Manager client or use the cwb stop cwbmonitord command. You must now manually refresh the Maps views because they are no longer automatically updated.

Stopping the Poller Daemon While Doing Discovery

Before you select Administration > Discover to discover your DLSw or RSRB network, stop the poller daemon using either the cwb stop cwbrsrbpollerd or cwb stop cwbdlswpollerd command or the Process Manager. When discovery is done, you can restart the poller daemon using the cwb start cwbrsrbpollerd or cwb start cwbdlswpollerd command or the Process Manager.

Limiting Remote Users

If you are running short of memory at the Maps workstation, you should limit the number of remote Maps users. Each Maps session requires approximately 20 MB of system memory in addition to the memory needed to display each graphical map.

Closing Unused Maps Windows

You should close the Maps windows when you no longer need them open. When several Maps windows are open, any change in a view to any one of the open windows causes all Maps windows to hang until the changing view has been completely refreshed. The delay is especially noticeable when a change occurs in a global view, in which any network change can result in a lengthy update cycle.

Improving DLSw Poller Performance

There are several changes you can make to improve the performance of the DLSw poller. You can customize the number of active threads to improve the bandwidth or the response time, and you can limit the amount of polling in the network.

Improving Bandwidth or Response Time

You can make changes to the DLSw poller's threads and sleep times on UNIX workstations (described in the "Using cwbinit to Configure Polling Intervals" section) that will improve either bandwidth (the amount of network resources consumed by DLSw) or response time (the time it takes the DLSw application to detect a change in the network):

Changing the Number of Threads

You can change the number of threads by changing the values of these numKeyPeerPollThreads, numNonKeyPeerPollThreads, and numKeyCircuitPollThreads variables in the cwbinit file.

Changing the Sleep Times

You can change the sleep times by changing the values of the keyCircuitPollSleepTime, nonKeyPeerPollSleepTime, and directedPollSleepTime variables in the cwbinit file.

Limiting Polling

You can make changes that will limit the amount of polling done by the DLSw application.

Clean Up Log Files

If CiscoWorks Blue has been running for a long time, some of the log files might grow quite large and impact performance. You can clean up the log files by running the cwb maintenance command manually or schedule maintenance as a cron job by customizing the /opt/CSCOcb/etc/cwbinit file and running the cwb start maintenance command. See "Database and Log File Maintenance" section for more details about this command.

Note that the cwb maintenance command stops and restarts all of the CiscoWorks Blue processes. If you would prefer to keep the CiscoWorks Blue processes active, you may clean up some of the log files manually. The safest way is to save a copy of the files, then remove the file contents, as shown in the following set of commands:

cp /opt/CSCOcwbC/apache/logs/access_log /opt/CSCOcwbC/apache/logs/access_log.bak
cat /dev/null > /opt/CSCOcwbC/apache/logs/access_log

cp /opt/CSCOcwbC/apache/logs/error_log /opt/CSCOcwbC/apache/logs/error_log.bak
cat /dev/null > /opt/CSCOcwbC/apache/logs/error_log

cp /opt/CSCOcb/logs/cwbcmd.log /opt/CSCOcb/logs/cwbcmd.log.bak
cat /dev/null > /opt/CSCOcb/logs/cwbcmd.log

cp /opt/CSCOcb/logs/DataBase.log /opt/CSCOcb/logs/DataBase.log.bak
cat /dev/null > /opt/CSCOcb/logs/DataBase.log

hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Aug 5 15:54:19 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.