Advanced Debugging - Avaya



The Advanced Debugging option under the CentreVu / Avaya CMS Supervisor Tools menu provides an interface to CentreVu / Avaya CMS Supervisor’s debugging features. Its use is for setting debug options and getting debug history, system, and error log files from the local PC for remote analysis. Only Avaya support organizations are expected to analyze information provided by Advanced Debugging. The regular end user will probably not gain any better understanding of a problem by viewing this data.

By clicking on the Tools option from the menu bar, then select Advanced, you will see the following screen. Select ‘No’.

[pic]

After selecting No, the next screen seen will be the default Advanced Debugging screen.

[pic]

In order to obtain the proper level on information, the default parameters need to be changed as follows:

Error Level Settings – from 2 to 5.

Rollover count – this can remain at 3 provided you can turn off the trace or shut down the Supervisor application in time so as the files are not overwritten. I have had some set this as high as 6.

Rollover size – this can remain 256 kb.

Notice the Stop Date and Stop Time will automatically populate the current date and the top of the next hour. Only if you can duplicate the problem during that short time, it should not be necessary to check the box Stop Time OverRide. In a scenario trying to troubleshoot an intermittent issue, you will want to check the Stop Time OverRide box.

You should have a screen looking like this:

[pic]

Once the Trace Parameters have been defined, you then check the Trace Log Options Enabled box. Once the Trace Log Options Enabled box is checked you will notice the parameters have been grayed out preventing them from being changed.

[pic]

In order to complete the initialization of the trace, you must click on ‘OK’.

After clicking OK, you will see the screen:

[pic]

Click on ‘OK’ again and completely exit the Supervisor application.

We want to ensure we have fresh data captured in the trace logs. The next steps will be done within the Windows Explorer feature.

In Windows Explorer you want to navigate to the Logs sub-directory of the Supervisor directory, by default located in

C:\Program Files\Avaya\CMS Supervisor V11 [or whichever version you have installed].

[pic]

Once at the Logs directory, you need to highlight all of the files within that directory and delete them.

[pic]

When Supervisor restarts these files will be recreated and will continue to log data as long as the application is running. Once the problem has been duplicated, exit the Supervisor application and send these log files to your Avaya engineer for analysis and continued troubleshooting.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download