Diagnostic Parameters and Commands
Using diagnostics-related DO commands
MAX Administration Guide
B-17
Clr-History
Description: Clears the fatal-error log.
Usage: Enter
clr-history
at the command prompt. To display the log before clearing it,
enter the
fatal-history
command.
Example:
> fatal-history
OPERATOR RESET: Index: 99 Load: ti.m40 Revision: 5.0A
Date: 02/13/1997. Time: 04:22:47
DEBUG Reset from unknown in security profile 1.
SYSTEM IS UP: Index: 100 Load: ti.m40 Revision: 5.0A
Date: 02/13/1997. Time: 04:23:50
> clr-history
The log is now empty:
> fatal-history
>
See Also: Fatal-History
CoreDump
Description: Enables or disables the ability of the MAX to send the contents of its memory
(core) to a specified UNIX host. When you use the function, the core file created can be several
megabytes in size. Also, the UNIX host must be running the
ascendump
daemon, which is
available by contacting Lucent Technologies Technical Support.
The CoreDump command is a particularly useful tool for the Lucent Technologies
development engineering, and Technical Support occasionally requests its use to help
troubleshoot specific issues.
Include the
now
option to instruct the MAX to dump its core immediately. Include the
enable
option to direct the MAX to dump its core when it has logged an entry to the fatal
error log.
!
Caution:
This command causes active connections to be disconnected and the MAX unit to
reboot after its memory (core) has been dumped. Do not use the command unless specifically
requested to do so by a Lucent Technologies representative.
Usage: coredump [enable] [disable] [now]
ip address
where:
•
enable
instructs the MAX to dump its core to the specified IP address when an entry is
logged to the fatal-error log.
•
disable
cancels the command if it has been enabled.
•
now
instructs the MAX to dump its core immediately to the specified IP address.
Example: Following are examples of entering the CoreDump command, and possible
response messages: