Amer Networks E5Web GUI - Manual (Page 106)

2.5. Diagnostic Tools
2.5.1. Overview
In the case of a serious system problem cOS Core provides some tools to aid in identifying the
cause. These are:
• Diagnostic CLI commands
• The pcapdump CLI command
Both of these provide output which can be sent to support staff at Clavister to help identify the
circumstances that led to the problem in question.
2.5.2. Diagnostic CLI Commands
The stat CLI Command
If a serious cOS Core problem is suspected then the first step should be to use the CLI command:
Device:/> stat
The stat command will indicate the date and time of the last system shutdown and can indicate if
there has been a serious error in cOS Core operation. It should be remembered however that the
buffer which stat uses is cleared by certain operations such as reconfigure and the output will not
therefore show what occurred prior to buffer clearance.
The dconsole CLI Command
The next step is to use the CLI command:
Device:/> dconsole
This can be abbreviated to:
Device:/> dcon
The dconsole command provides a list of important events that have occurred during cOS Core
operation and can help to establish the date, time and nature of events leading up to a serious
problem occurring. The output might look similar like the following:
Showing diagnose entries since 2008-05-22:
2008-06-21 11:54:58
Start (10.20.02-0:131)
2008-06-21 11:56:16 Stop (RECONFIGURE)
2008-06-21 11:56:21 Start (10.20.02-0:131)
2008-06-21 11:57:29 Stop (RECONFIGURE)
2008-06-21 11:59:31 Start (10.20.02-0:131)
2008-06-21 11:59:49 Stop (NORMAL)
"
"
Output from dconsole can include a dump of the system memory in the case of serious runtime
errors. Such a dump will look similar to the following:
'
'
Reason: Exception 'DataAbort' occurred at address 0x7aaea34
Chapter 2: Management and Maintenance
106