Cisco GSS-4492R-K9 Administration Manual page 191

Chapter 8 Viewing Log Files
Viewing System Message Logging
Viewing Subsystem Log Files from the CLI
Note
OL-10410-01
Jul 14 21:42:02 gss-css2 KAL-7-KALAP[1240] Retrying IP [192.10.4.1]
(Retry Count 3)
Jul 14 21:42:07 gss-css2 KAL-7-KALAP[1240] Timeout: Found outstanding
KAL [192.10.2.1]
Jul 14 21:42:07 gss-css2 KAL-7-KALAP[1240] KAL-AP (seq# 29411)=> Host
192.10.2.1
Jul 14 21:42:07 gss-css2 KAL-7-KALAP[1240] Retrying IP [192.10.2.1]
(Retry Count 1)
Jul 14 21:42:09 gss-css2 KAL-7-KALCRA[1240] rtt_task: waiting 10000
mseconds
Jul 14 21:42:12 gss-css2 KAL-7-KALAP[1240] KAL-AP (seq# 29412)=> Host
192.10.2.1
Jul 14 21:42:12 gss-css2 KAL-7-KALAP[1240] Retrying IP [192.10.2.1]
(Retry Count 2)
Jul 14 21:42:16 gss-css2 KAL-7-KALAP[1240] Sending circuit keepalive
=> [192.10.2.1]
...
You can display the system message log configuration for a GSS device by using
the show logging command.
For example, enter:
gssm1.example.com# show logging
Logging to disk is enabled.
Priority for disk logging is Informational(6).
Logging to host is disabled.
Priority for host logging is Warning(4).
In addition to the gss.log file, each GSS device maintains a number of other log
files that record GSS subsystem-specific information (for example, the keepalive
engine or DNS server component of the GSS). You can view these log files from
the CLI using the type command.
The type command lists all logged subsystem information in your terminal
session. This output may be quite large and may exceed the buffer size set for the
terminal. If you want to capture all logged information, use the terminal-length
Viewing Device Logs from the CLI
Cisco Global Site Selector Administration Guide
8-11