1268 BigIron RX Series Configuration Guide53-1001986-01Configuring the Syslog serviceAFor backward compatibility, the software reads the old command syntax from the startupconfiguration, and converts it to the new command syntax in the running configuration.Syntax: logging host | Disabling logging of a message levelTo change the message level, disable logging of specific message levels. You must disable themessage levels on an individual basis.For example, to disable logging of debugging and informational messages, enter the followingcommands.BigIron RX(config)# no logging buffered debuggingBigIron RX(config)# no logging buffered informationalSyntax: [no] logging buffered | The parameter can have one of the following values:• alerts• critical• debugging• emergencies• errors• informational• notifications• warningsThe commands in the example above change the log level to notification messages or higher. Thesoftware will not log informational or debugging messages. The changed message level alsoapplies to the Syslog servers.Logging all CLI commands to SyslogThis feature introduced in version 02.4.00 of the Multi-Service IronWare software allows you to logall 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-commandSyntax: [no] logging cli-commandExample of CLI command loggingIn the following example, two CLI sessions are run. In the first example, a telnet session enables CLIcommand logging and configures router bgp and the BGP no neighbor command as shown.telnet@ BigIron RX(config)# logging cli-commandtelnet@ BigIron RX(config)# router bgptelnet@ BigIron RX(config-bgp)# no nei 10.1.1.8 remote 10In the next example, a console session configures router bgp and the BGP neighbor command asshown.
