System Freezes - Inter-Tel AXXESS Manual

Hide thumbs Also See for AXXESS:
Table of Contents

Advertisement

Appendix C — CP Server
®
®
INTER-TEL
AXXESS

15. SYSTEM FREEZES

15.1 The ability to back up a file also gives power to system freezes. When a system freeze
is performed, the memory-mapped files are copied into a freeze directory. You can program the
number of freezes that will be saved, up to 100 freezes. Each freeze is tagged with a number.
The freeze marked "00" is always the latest freeze. When another freeze is performed, the "00"
freeze is copied to the next unused number. For example, if there are already freezes "01"
through "23" in the freeze directory, when a freeze occurs, freeze "00" will be copied to freeze
"24." When the number of freezes reaches the limit specified in the ICP Configuration Utility
(30 by default), it wraps back to "01" and overwrites the previous "01" freeze.
15.2 Each freeze also saves copies of the backup files. Using the example in Backup Files
above, a single freeze would contain 21 CP Queue files (the 20 backup files plus the one that
was actively being written). This provides over 20 MB of system data for troubleshooting. On
a large System, that is approximately 30-60 minutes of data, which varies based on the size and
traffic of a particular system. The technician can tune the size and number of files to capture a
typical time frame as needed on a per site basis.
15.3 Note that the system is never really "frozen" when using a the CP Server, so there is no
longer a problem with forgetting to unfreeze; you will not be prevented from freezing the sys-
tem again.
16. RETRIEVING CP HISTORY INFORMATION
16.1 On a phone System that is not equipped with a CP Server, you would use the "Error
Information" option from the Operations menu in DB Programming.
16.2 CP History Retrieval on a phone System equipped with a CP Server is entirely differ-
ent. All call processing logs are stored on the CP Server's hard drive. They are only accessible
via the PC and cannot be retrieved through a DB Programming session.
16.3 Active histories are stored in memory mapped files (mmf). Five specific histories are
separately logged: message print, reset history, exception history, network link information,
and call processing command history. These files, by default, are stored in C:\ICP. To make
the mmf files readable, they must be converted to text (txt) format (or, in the case of the call
processing command history file, to a binary format).
16.4 Backup history files may exist. These are mmf files that have been automatically con-
verted to the proper format and placed in C:\ICP\BACKUP.
16.5 Call processing history logs are used by field staff, Tech Support and Engineering to
troubleshoot the System. In most cases, both active and backup logs are required. Only a sys-
tem freeze will produce current usable history files. When a freeze is performed, all active his-
tory information is flushed from the mmf files, converted to the proper format, and placed in
the freeze directory. All backup files are then renamed and moved to the C:\ICP\FREEZE
directory. The device file, Windows system event logs, application event logs, and a copy of
the customer's database (static_memory.mmf) are also copied to the freeze directory.
NOTE:
files in its ICP directory. If one of the CP Servers fail, make sure you retrieve the files from the
failed server's ICP directory.
16.6 Freezing a System equipped with a CP Server does not actually "freeze" any history
files as it does in a System equipped with a traditional CPU. A picture or snapshot is taken and
placed in the freeze directory. There is no need to "unfreeze" the system. Each freeze is
assigned a number. There can be 100 separate freezes, depending on configuration program-
ming (see
Page C-12
MANUAL VERSION 11.0 – May 2008
In a system with redundant CP Servers, each CP Server stores freeze and CP history
page
C-27). Freeze_00 is always the most current.
System Freezes

Advertisement

Table of Contents
loading

Table of Contents