System Logging And Debugging - Alcatel-Lucent OmniAccess 700 Cli Configuration Manual

Release versions: 2.2, 2.2-r02, 2.3
Hide thumbs Also See for OmniAccess 700:
Table of Contents

Advertisement

Left running head:
Chapter name (automatic)
System Configuration and Monitoring
S
L
YSTEM
OGGING AND
The OA-700 can be configured for logging, based on severity of the message and
module. The severity of the log messages are indicated by the priority, which
varies from 0-7. Lower the numerical value of priority, higher is the criticality of the
message.
0 - emergency
1 - alert
2 - critical
3 - errors
4 - warnings
5 - notifications
6 - informational
7 - debugging
The logging information can further be directed to the logging buffer, console,
terminal, or remote Syslog server. By default, logging to the console and buffer
logging is "ON".
[no] logging on
[no] logging buffered
[priority <0-7>|size <4-
16384>]
[no] logging remote <ip-
address> [port <0-65535>
priority <0-7>]
[no] logging console priority
<0-7>
[no] logging system
81
Beta
D
EBUGGING
Command (in CM)
Alcatel-Lucent
Description
This command is used to enable logging
of messages.
By default, logging of messages is
enabled.
The 'no' command disables logging.
This command is used to store the log
information in the memory buffer. If a
priority value is given, messages of that
priority and higher (numerically lower)
will be buffered. Size denotes the buffer
size in kilobytes and can vary from 4 -
16384 kilobytes.
This command is used to configure an
external server to store log messages.
The default port is 514 and default
priority level is 7.
This command is used to display the log
messages of the specified priority and
higher on the console.
This command is used to log all the
Kernel messages.
By default, messages with a priority of 5
and lower will be logged.
CLI Configuration Guide
Beta

Advertisement

Table of Contents
loading

Table of Contents