Alcatel-Lucent 5620 Troubleshooting Manual page 122

Release 12.0 R4 | August 2014 | 3HE 08864 AAAD TQZZA Edition 01
10 — Troubleshooting the 5620 SAM platform
7 Store the files in a secure location to ensure that the files are not overwritten. For
example, if there are two 5620 SAM clients that experience problems, rename the
files to identify each 5620 SAM client and to prevent the overwriting of one file
with another of the same name.
8 Send the files to Alcatel-Lucent technical support, as required.
Procedure 10-2 Problem: Poor performance on a RHEL or Solaris
station
When a station is taking too long to perform a task, you can check the CPU status to
ensure that one process is not using most of the CPU resources, and then use commands
to review the CPU usage.
When CPU usage remains high and performance degrades, contact Alcatel-Lucent
technical support. Provide the data that you collect when you perform this procedure.
You can also perform other procedures to monitor performance: If you are you
performing a large listing operation using the 5620 SAM client GUI or OSS, check the
LAN throughput using the netstat command, as described in Procedure 14-3.
1 Log on to the station as the root user.
2 Open a console window.
3 If the station OS is Solaris, go to step 7.
4 Perform the following steps to check for processes that are consuming excessive
CPU cycles:
i
ii
iii
5 Perform the following steps to view a CPU activity summary.
i
10-6
To list the top CPU processes using the UNIX utility prstat, type:
# top ↵
Depending on your system configuration, approximately the top 20 processes
are displayed.
Review the output.
The top 5620 SAM process in the CPU column should be the Java process.
However, the Java process should not be consuming too much CPU. Some
Oracle processes may also consume CPU, depending on the database load.
Press CTRL-C to stop the command.
Enter the following command:
# mpstat time ↵
where time is the interval, in seconds, between CPU polls; a value between 10 and 60 is
recommended
Alcatel-Lucent 5620 Service Aware Manager
Troubleshooting Guide
5620 SAM