Disabling Logging Of A Message Level; Logging All Cli Commands To Syslog - Dell PowerConnect B-RX Configuration Manual

A
Configuring the Syslog service
For backward compatibility, the software reads the old command syntax from the startup
configuration, and converts it to the new command syntax in the running configuration.
Syntax: logging host <ip-addr> | <server-name>

Disabling logging of a message level

To change the message level, disable logging of specific message levels. You must disable the
message levels on an individual basis.
For example, to disable logging of debugging and informational messages, enter the following
commands.
BigIron RX(config)# no logging buffered debugging
BigIron RX(config)# no logging buffered informational
Syntax: [no] logging buffered <level> | <num-entries>
The <level> parameter can have one of the following values:
•
•
•
•
•
•
•
•
The commands in the example above change the log level to notification messages or higher. The
software will not log informational or debugging messages. The changed message level also
applies to the Syslog servers.

Logging all CLI commands to Syslog

This feature introduced in version 02.4.00 of the Multi-Service IronWare software allows you to log
all valid CLI command from each user session into the system log.
To enable CLI command logging, enter the following command.
BigIron RX(config)# logging cli-command
Syntax: [no] logging cli-command
Example of CLI command logging
In the following example, two CLI sessions are run. In the first example, a telnet session enables CLI
command logging and configures router bgp and the BGP no neighbor command as shown.
telnet@ BigIron RX(config)# logging cli-command
telnet@ BigIron RX(config)# router bgp
telnet@ BigIron RX(config-bgp)# no nei 10.1.1.8 remote 10
In the next example, a console session configures router bgp and the BGP neighbor command as
shown.
1268
alerts
critical
debugging
emergencies
errors
informational
notifications
warnings
BigIron RX Series Configuration Guide
53-1001986-01