Using Shell Commands When A System Is Busy - Mitel MiVoice Business Troubleshooting Manual

12/4/9 10:44:23, PID 01 - appStartup -
private,1304280,6228280,171,5430,7627,1147,1117936
12/4/9 10:44:23, PID 01 - appStartup - public,134896,0,1,0,134896,0,134896
12/4/9 10:54:23, silo-nodes, 475048,53064, 1,1977, 475948,26,475048
12/4/9 10:54:23, PID 00 - kernel - private,0,0,0,0,0,0,0
12/4/9 10:54:23, PID 00 - kernel - public,81864,136592360,,15,1201,5457,28886,72680
12/4/9 10:54:23, PID 01 - appStartup -
private,1304280,6228280,171,5430,7627,1147,1117936
12/4/9 10:54:23, PID 01 - appStartup - public,134896,0,1,0,134896,0,134896
System resource history file
Information such as free memory, cluster, DSP resources active is collected one every 60
seconds. Here is an example of a resource file (first 4 lines). This file includes memory use per
silo.
Time, Memory, Clusters, DTMF Det, DTMF Gen, ,
2012/04/09 10:54:00, 512,4000, 32, 32,
2012/04/09 10:54:00, 164,3800,1,1
2012/04/09 10:55:00, 164,3700,5,5
The second line in the example shows that data collection began on April 9th, 2012 at 10:54:00.
At that time, the system had a total of 512M of memory available, 4000 clusters, 32 DTMF
detectors, and 32 DTMF generators.
The 3rd row, at the same time, shows that 164M of memory is available, 3800 clusters are
available, 1 DTMF detector and 1 DTMF generator is in use.
The fourth row shows that at 10:55, there was still 164M of memory available, the number of
free clusters reduced from 100 to 3700, and the number of DTMF detectors and generators
increased by 4 to 5.

USING SHELL COMMANDS WHEN A SYSTEM IS BUSY

Use the following shell commands when a system is very busy and Embedded System
Management (ESM) resource commands are slow or not available:
• systemInfo: The equivalent to the ESM maintenance command SHOW STATUS
RESOURCE.
Diagnosing Problems
193