You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
EMA allows you to generate the system diagnostic information which can be used by Sonus support personnel to debug system issues. You can save the diagnostic information in any required location.
To collect the system diagnostics information:
On SBC main screen, go to Administration > System Administration > System Diagnostics. The System Diagnostics window is displayed. Activate the options from the list. Refer to the table below for the options and its descriptions.
The System Diagnostics file can be generated for each option provided.
System Diagnostics Window
Click Generate, to proceed. A message is displayed stating the operations and the time taken to complete the same and requests your confirmation to proceed.
System Diagnostics - Confirmation
Click OK to proceed. Once the files are generated, a confirmation message is displayed.
System Diagnostics - Status
- Click OK to proceed. The generated System Diagnostic file is displayed at the bottom of the page.
Check the radio button of the required file to open or save, click Export.
System Diagnostics - Files
The selected file can either be opened or saved in your directory. To open, Select Open with option and mention the mode from the drop-down menu and to Save the file, select Save File option and click OK. Provide the location for the file to get saved.
System Diagnostics - Files Open or Save
The following table explains the different options to generate the System Diagnostics file.
System Diagnostics parameters
Parameter
| Description
|
---|
a). Saves Cores to sysdump (will increase sysdump size)
| Specifies whether to collect any application core file or not. This option will increase the size of the sysdump. It does not affect core trace files. |
b). Collect the Policy database/oracle directories | This option collects the policy directories to sysdump. |
c). Verbose mode
| This option outputs information on which files and directories are being captured. |
d). Do not save DSP cores to sysdump
| Specifies that DSP core files will not be saved to sysdump. |
e). Do not save CPS cores to sysdump | Specifies that CPS core files will not be saved to sysdump. |
f). Maximum number of core files to save | Specifies the maximum number of application core files to be saved. |
g). Maximum number of DSP core files to save | Specifies the maximum number of DSP application core files to be saved. The default application core processing limit is 10. |
h). Maximum number of CPS core files to save | Specifies the maximum number of CPS application core files to be saved. The default application core processing limit is 10. |
i). Logs or core dumps collected | Use this option to specify a date or date range. The options are: - Number of days Back - Number of days of historical logs to collect. The value ranges from 0 to 31 where 0 represents Today and the default value is 7.
- Specific Date – Collect log and core files created only on this date.
- Equal or older than – Collect log and core files equal to or older than this date.
- Equal or newer than – Collect log and core files equal to or newer than this date.
- From/TO - Collect log and core files within a range of dates.
|
If none of the above options is chosen, and the maximum number of core files, DSP core files or CPS core files are all left blank, the default behavior is to copy only the latest application, DSP and CPS cores and the past seven days of log files.
- Options i) a and i) d are mutually exclusive.
- Options i) a and i) c are mutually exclusive.
- Option i) b is mutually exclusive from i) a, i) c and i) d.
- The default with only option g) specified is to copy all log and existing trace files, up to 10 application core files, and up to 10 CPS core files.
- The default with only option h) specified is to copy all log and existing trace files, up to 10 application core files, and up to 10 DSP core files.
- The default with only option i) specified is to copy all log and existing trace files, up to 10 application core files unless, a different number of core files is specified by the core file count parameter.