Information Technology Reference
In-Depth Information
Improving CWSI Campus Performance
You can improve the performance of CWSI Campus by reducing the overhead on the CWSI Campus
workstation. To reduce the CPU cycles required by CWSI Campus, follow these steps:
Step 1
Reduce the number of discovery threads. This process causes discovery to take less CPU power, but
discovery will take longer. To change the discovery threads, follow these steps:
The operation of ANI and CWSI campus clients depends on the information in the
ani.properties file. An incorrect entry in this property file can cause CWSI Campus
to operate incorrectly. Follow the instruction carefully, and do not attempt to edit
other information.
Note
Run the stopcwsiserver script.
•
Locate the ani.properties file in the CWSI directory.
•
Locate the following line:
•
Discovery.threads=12.
Change this line so that it now states:
•
Discovery.threads=5.
Run the startcwsiserver script.
•
In UserTracking, increase the VMPSMajor and VMPSMinor time schedules.
Step 2
Increase the discovery time scheduling interval.
Step 3
Change the discovery time scheduling interval to be fixed (once a day, twice a day) based on your need
for timely information.
Step 4
Set up the system for high performance.
Install enough physical memory to handle CWSI Campus and any other programs that you run
simultaneously. You should avoid using swapping.
Ensure a fast network connection; the connection should be better than a 10-MB shared media
connection.
If you are using Windows NT, use ultra-fast wide SCSI drives. Also, place the swap file on its own
partition, if possible, or ensure that it remains unfragmented.
Step 5
Entering Valid Community Strings
To allow CWSI Campus to configure the devices in your network, you must ensure that the proper
community strings are set. These sections will help you troubleshoot problems that you may experience.
Which Community Strings Are Valid?
When entering valid community strings, what determines whether these examples are invalid or valid?
Example 1: Invalid Community Strings Entry
172.26.1.*:sub1::::::sub1:
