|
SYSTEM ADMINISTRATOR GUIDE 82/1543-CRA 119 1170/1-V1 Uen A | |
Copyright
© Copyright Ericsson AB 2009. All rights reserved.
Disclaimer
No part of this document may be reproduced in any form without the written permission of the copyright owner. The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.
Trademark List
| SmartEdge | is a registered trademark of Telefonaktiebolaget L M Ericsson. | |
| NetOp | is a trademark of Telefonaktiebolaget L M Ericsson. |
| 1 | Logging |
| 1.1 | About Logging |
| 1.2 | How to Configure Logging |
2 | Logging Operations Tasks |
This document provides an overview of logging features, describes
the tasks used to configure them, and provides configuration examples
and detailed descriptions of the commands used to configure logging
features using the SmartEdge
router .
The term controller carrier card refers to the controller functions on the carrier card within the SmartEdge 100 chassis; these functions are compatible with the XCRP3 Controller card. The term I/O carrier card refers to the traffic card functions on the carrier card; these functions are compatible with the similar functions that are implemented on the traffic card that are supported on all other SmartEdge routers.
The term chassis refers to any SmartEdge chassis; the term SmartEdge 800 chassis refers to any version of the SmartEdge 800 chassis. The term SmartEdge 1200 chassis refers to any version of the SmartEdge 1200 chassis.
The operating system contains two log buffers: main and debug. By default, messages are stored in the main log. If the system restarts, for example as a result of a logging daemon or system error, and the logger daemon shuts down and restarts cleanly, the log buffers are saved to the /md/loggd_dlog.bin for the main log buffer, and the /md/loggd_ddbg.bin for the debug log buffer. You can view the contents of the main log files that are saved using the show log command (in any mode).
By default, log messages for local contexts are displayed in real time on the console; non-local contexts are not displayed in real time on the console. To change this behavior, and display messages in real time, use the logging console command (in context configuration mode). However, log messages can be displayed in real time from any Telnet session using the terminal monitor command (in exec mode). For more information on the terminal monitor command, see Command List.
In large installations, it is convenient to have all systems log to a remote machine for centralized management and to save space on the device. The operating system uses the UNIX syslog facility for this purpose, and can send log messages to multiple machines concurrently. Logging can be constrained to events occurring on a specific circuit.
All log messages contain a numeric value indicating the severity of the event or condition that caused the message to be logged. Many log messages are normal and do not indicate a system problem.
Table 1 lists event severity levels in log messages and their respective descriptions.
|
Value |
Severity Level |
Description |
|---|---|---|
0 |
emergencies |
Panic condition—the system is unusable. |
1 |
alerts |
Immediate administrator intervention is required. |
2 |
critical |
Critical conditions have been detected. |
3 |
errors |
An error condition has occurred. |
4 |
warnings |
A potential problem exists. |
5 |
notifications |
Normal, but significant, events or conditions exist. |
6 |
informational |
Informational messages only; no problem exists. |
7 |
debugging |
Output from an enabled system debugging function. |
This section describes how to configure logging in several different scenarios.
To configure optional global logging features, perform the tasks described in Table 2; enter all commands in global configuration mode.
|
Task |
Root Command |
Notes |
|---|---|---|
Enable the display of logged system event messages with a millisecond resolution timestamp. |
| |
Enables the logger to send logging and debug messages from the active controller card to the standby controller card. |
Enter the no form of this command to disable this feature. | |
Enables the filtering of debug messages for valid circuits only. |
Enter this command in global configuration mode. | |
Enables the logger to send logging and debug messages from the standby controller card to the active controller card. |
Use the no form of this command to disable this feature. | |
Enables the display of all debug messages in the main log buffer. |
Use the no form of this command to prevent the debug messages from being sent to the main log buffer. |
To configure optional context-specific logging features, perform the tasks described in Table 3; enter all commands in context configuration mode, unless otherwise noted.
|
Task |
Root Command |
Notes |
|---|---|---|
Isolate events from certain facilities in the logs and trim the flow of information. |
| |
Enable event logging messages to the console. |
| |
Enable event logging messages to a file. |
You can configure up to four log files per context. | |
Enable the logging of system events to a remote syslog server that is reachable within the current context. |
You can configure up to four syslog servers per context. |
The following example configures the system to remotely log all system messages to a network syslog server. Information to forward packets to the 10.1.1.1 address specified for the syslog host is derived from routing tables specific to the NewContext context:
[local]Redback(config)#context NewContext [local]Redback(config-ctx)#logging syslog 10.1.1.1
The following example shows a configuration where log messages are sent to a syslog server (198.168.148.99) in the local context using the syslog facility, local6, and to another syslog server (198.168.145.99) in the green context using the syslog facility, local3:
[local]Redback(config)#context local [local]Redback(config-ctx)#logging sys 198.168.148.99 facility local6 [local]Redback(config-ctx)#exit [local]Redback(config)#context green [local]Redback(config-ctx)#logging sys 198.168.145.99 facility local3
Table 4 lists the logging operations tasks. Enter the show commands in any mode; enter all other commands in exec mode.
|
Task |
Root Command |
|---|---|
Clear the system event log buffer. |
|
Clear the contents of the nonvolatile memory (NVRAM) on the active controller card to which you are connected. |
|
Enable the generation of debugging messages for the logging facility (logger). |
|
Enable the generation of debugging messages for the logging facility (logger) RCM. |
|
Saves one of the internal event log buffers to the flash file system. |
|
Display information about system event logs or a previously saved log file. |
|
Display statistics about the system logger, including logger uptime, number of logged messages, number of logged filter messages, and number of logged rate-limited messages. |
|
Display the contents of the NVRAM on the active controller card to which you are connected. |