
Basic system management configuration task list
95
IPLink Software Configuration Guide
8 • Basic system management
Displaying the system logs
The system logs contain warnings and information from the system components of IPLink software. In case of
problems it is often useful to check the event or the supervisor logs for information about malfunctioning sys-
tem components. The event log stores general events such as flash full, DSP failed etc., comparable with the
event log on Windows NT. The supervisor log stores information from the system supervisor such as memory
full, task failed etc.
System resets may have a number of reasons, the most prominent being a manual reset issued on the Telnet/
console (‘reload’). Other reset reasons include power off failures and system failures. In order to pinpoint the
problem, the reset log contains the reset cause.
Mode: Administrator execution
Example:
Displaying system logs
The following example shows how to display event log warnings and information of your device, if you start
from the operator execution mode.
IPLink#show log event
2001-12-10T14:57:18 : LOGINFO : Link down on interface internal.
2001-12-10T14:57:39 : LOGINFO : Warm start.
2001-12-14T08:51:09 : LOGINFO : Slot 2: Event Logging Service for ic-4brvoip - started.
2001-12-14T08:51:09 : LOGINFO : Slot 2: DrvPckt_Dsp_Ac48xx: DSP driver for AC481xx cre-
ated!
Controlling command execution
The IPLink software command shell includes a basic set of commands that allow you to control the execution
of other running commands. In IPLink software, the commands
jobs
and
fg
are used for such purposes. The
command
jobs
lists all running commands, and
fg
allows switching back a suspended command to the fore-
ground. Moreover using
<ctrl>-<z>
suspends an active command and lets the system prompt reappear. With
<ctrl>-<c>
the currently active command can be terminated.
Mode: Administrator execution
Step
Command
Purpose
1
node#show log [event]
Show event log.
2
node#show log supervisor
Show log of the system supervisor. Used For example, after an unex-
pectedly reboot.
3
node#show log reset
Output a list of reset reasons (with date and time).
4
node#show log boot
Displays the console and log messages captured during startup of the
IPLink.
5
node#show log login
Displays a list of succeeded and failed CLI login attempts.
6
node#show log file-
transfer
Displays the history of all recently executed file transfer operations
(up to 50 entries).
Step
Command
Purpose
1
Execute the first command
2
node#<Ctrl-Z>
Suspend the active command and get system prompt back