Brocade BigIron RX Series Configuration Guide - Manual (Page 1465)

BigIron RX Series Configuration Guide 1387
53-1002484-04
Configuring the Syslog service
A
In the next example, a console session configures router bgp and the BGP neighbor command as
shown.
BigIron RX(config)# router bgp
BigIron RX(config-bgp)# nei 10.1.1.8 remote 10
Using the show log command, you would see a series of log records as shown in the following.
BigIron RX(config-bgp)# show log
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
Buffer logging: level ACDMEINW, 24 messages logged
level code: A=alert C=critical D=debugging M=emergency E=error
I=informational N=notification W=warning
Dynamic Log Buffer (50 lines):
Sep 9 18:38:23:I:CLI CMD: "nei 10.1.1.8 remote 10" from console
Sep 9 18:38:21:I:CLI CMD: "router bgp" from console
Sep 9 18:38:07:I:CLI CMD: "no nei 10.1.1.8 remote 10" from telnet client 10.1.1.1
Sep 9 18:38:05:I:CLI CMD: "router bgp" from telnet client 10.1.1.1
Changing the number of entries the local buffer
can hold
The number of entries that the Syslog buffer can hold cannot be changed. The buffer can hold up
to 3800 lines.
Changing the log facility
The Syslog daemon on the Syslog server uses a facility to determine where to log the messages
from the device. The default facility for messages the device sends to the Syslog server is “user”.
You can change the facility using the following command.
NOTE
You can specify only one facility. If you configure the device to use two Syslog servers, the device
uses the same facility on both servers.
BigIron RX(config)# logging facility local0
Syntax: logging facility <facility-name>
The <facility-name> can be one of the following:
• kern – kernel messages
• user – random user-level messages
• mail – mail system
• daemon – system daemons
• auth – security or authorization messages
• syslog – messages generated internally by Syslog
• lpr – line printer subsystem
• news – netnews subsystem
• uucp – uucp subsystem
• sys9 – cron/at subsystem