Troubleshooting guide

Chapter 7 Troubleshooting Security Servers and Content Security
Troubleshooting Security Server Performance problems
Advanced Technical Reference Guide 4.1 • June 2000 64
What are the possible causes?
It is worth defining the possible causes of the problem. Assume that every one of the
involved objects can be a cause of the problem, and that the problem may arise from a
combination of causes.
Possible causes for each object:
The Solaris machines
1. Overloaded CPU
2. Memory problem
3. Running out of File descriptors
The VPN/FireWall module
1. Limitation of kernel tables
2. A loaded kernel blocking the security servers
The security servers
1. A general security server bug
2. A security server with a CVP/UFP resource bug
3. CVP server saturation.
The CVP server
1. A bug
The test
Start with a low load, and then build up to a higher load. Either start the tests at a quiet time or divide the load
on the security and the CVP servers via the Rule Base.
1. Run all the following measurements before starting
top
for CPU and memory usage on both machines,
lsof (lsof | grep <process name> | wc –l)
for file descriptors checks, on both machines
fw tab –s
for the firewall kernel tables counts.
Snoop
Save the log and ahttpd.log files.
2.
Turn the CVP resource on and start the measurements again. Look for changes.
3. If you see nothing unusual, increase the load by performing the test at a busier period.
4. If you see the problem or its symptoms, determine the cause. See the above list of
possible causes.