Troubleshooting Guide

Table Of Contents
Activate tracing on one software module at a time.
Initially activate tracing at lower verbosity settings (that is, 2 rather than 3). Increase to
verbosity level 3 or 4 only if required, and after level 2 runs safely.
Avoid leaving traces active for extended periods of time. For high CPU utilizations, a few
seconds (typically less than 5 seconds) is generally sufficient to identify the cause for sustained
high CPU utilization.
General diagnostic tools
January 2017 Troubleshooting 35
Comments on this document? infodev@avaya.com