Initial System Set-up
About GRF logs and dumps
GRF 400/1600 Getting Started - 1.4 Update 2
October, 1998
4-9
About GRF logs and dumps
Logs
When the GRF first boots and loads, logging is not enabled. System memory restrictions on the
GRF control board require that logging be to external storage. If target external storage is not
specified to receive log entries, log entries are not saved. You should configure logging as part
of initial system set up.
There are three options for logging. Procedures for each are in the next several sections:
–
“local” logging and dumping to an external PCMCIA flash device inserted in the
control board
–
remote logging (network) to a syslog server
–
remote logging (network) to an NFS-mounted file system
Three logs provide specific information useful for monitoring and debugging GRF operations.
If you are working with Customer Support, these are the three logs they will need to see:
–
/var/log/gr.console
–
/var/log/gr.boot
–
/var/log/messages
The
gr.console
log is the most useful log (also called grconslog or the conslog). You will
need the information logged to this file to manage the GRF. It contains status and events for the
GRF system and all media cards. When a media card resets, many events of the resetting are
reported, including initializing, loading run-time code, requesting and reading configuration
parameters, and so on. At the end, you see a message that indicates the cause of the reset.
The grconslog command opens a window to the log that displays messages as they are logged.
It is common practice to telnet into the GRF, enter
grconslog -vf
, and keep the window
open to monitor ongoing system events as they are reported. Use the abort or equivalent key to
quit the log. The
gr.console.log
displays all types of events including card resets and
panics, user log ons, and configuration changes. Refer to the GRF Reference Guide for a
description of grconslog options.
The
gr.boot
log contains events reported during system and media card boot. These can be
helpful if a card has problems booting and coming up.
The
messages
log contains system-related events connected usually with the management
software, also referred to as RMS (Router Management System), and the operating system
kernel.
Examples of logs are in the “Management Commands and Tools” chapter of the GRF
Configuration and Management manual. Other log files in the
/var/log
directory collect
low-level information useful primarily to system developers.
