How do you reset the peak resource usage statistics within Communications Server for Linux (CS Linux)?
When displaying the sna.usage file, the peak resource usage statistics do not appear to change. The following attempts were made to reset the peak resource usage statistics:
1. Restart CS Linux
2. Restart the Linux machine that CS Linux is running on
Restarting the Linux machine that CS Linux is running on resets the current and peak values. Restarting CS Linux resets the current values.
The new record is written to the /var/opt/ibm/sna/sna.usage file every 30 minutes with the first one coming 30 minutes after the CS Linux kernel modules are loaded (in other words, when the snastart script is run by the Linux boot process). These kernel modules are only unloaded and reloaded by an uninstall, re-install or by a Linux reboot. The 30 minute value is not configurable. Use the sna.usage file long-term history. For more information on the sna.usage file, see "Usage Logging" in Chapter 3 "Using Logging and Tracing" of IBM Communications Server for Linux V6.4 Diagnostics Guide (GC31-6779-03).
You may want to use the 'snaadmin query_node_limits' command, which you can run at any time. It displays the same information as is stored in the sna.usage file and its values will be reset in the following ways:
- when the node is stopped or restarted the current values are reset
- when the kernel modules are unloaded or reloaded the peak values are reset.
For more information on the 'snaadmin query_node_limits' command, see the section on "query_node_limits in Chapter 2. "Administration Commands" of IBM Communications Server for Linux V6.4 Administration Command Reference (SC31-6770-03).
|Networking||Communications Server for Linux on zSeries||Linux Red Hat - zSeries, Linux SUSE - zSeries, Linux zSeries||6.2.1, 6.2.2, 6.2.3, 18.104.22.168, 6.4, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168||All Editions|