Table Of Contents

Syslog Capabilities

Internal Log Levels

Enabling Syslog Functionality

Syslog Capabilities

---

This appendix describes the Cisco IOS syslog, the internal log levels, the SBC PD log, and how to enable syslog.

All the Cisco Unified Border Element (SP Edition) debug messages that are displayed on the console are recorded in the Cisco IOS syslog. All the Cisco IOS syslog commands that configure log size, persistence, and redirection may be used for managing the syslog.

In addition to the console messages, Cisco Unified Border Element (SP Edition) records a log in its own internal buffer. This is known as the PD log and is dumped in the event of a software forced reload or as a result of using the sbc dump-diagnostics command. When you compile your problem reports, the PD log file should be included as part of the problem reports.

Internal Log Levels

The SBC application uses an internal log level to control the verbosity of the console and PD log. While both the console and PD log levels can be changed independently, we do not recommend changing the PD log level because the PD log buffer is of limited size and important logs may be lost.

The default SBC PD logging level is 63 for both the PD log and console. The SBC internal log level default of 63 is adequate for most purposes. You can change the default SBC PD logging level using the debug sbc log-level console command or the debug sbc log-level file command.

The internal SBC application log-levels are mapped to syslog severity levels 1 through 7, where 1-alert; 2-critical; 3-error; 4-warning; 5-notif; 6-informational; 7-debug, as follows:

Log Level	Syslog Level
80	alert
70	critical
63	error
60	warning
50	notice
40	informational
-	debug

Enabling Syslog Functionality

To enable syslog functionality on the SBC, first set the internal log-levels, and then issue syslog-specific logging commands. The following assumes a default PD level of 63 (no further action is needed if this is a fresh reboot).

1. First, enable logging using the following commands:

Router# configure

Router(config)# logging enable

Router(config)# logging standby

---

Note The logging standby command allows synchronization of active and standby syslog settings.

---

2. Next, configure where you want the syslog messages to be sent:

· Console: logging console <1-7>

Router(config)# logging console severity-level

· Buffer: logging buffer <1-7>

Router(config)# logging buffered severity-level

---

Note Use the show logging command to see logging statistics and the logging buffer.Router

---

---

Note Use the clear logging command to clear the logging buffer.

---

Syslog server: logging trap <1-7>

Router(config)# logging host ip_address [tcp[/port] | udp[/port]]

Router(config)# logging trap severity-level

Router(config)# logging device-id {hostname | ipaddress interface_name | string

text | context-name}

---

Note The logging device-id command allows customization of syslog message when sending thelog to a remote server.

---

Router(config)# logging facility number

· Telnet sessions: logging monitor <1-7>

Router(config)# logging monitor severity-level

Router# terminal monitor

· SNMP management station: logging history <1-7>

Router(config)# logging history severity-level

· Supervisor: logging supervisor <1-7>

Router(config)# logging supervisor severity-level

3. Next, configure specific syslog message manipulation:

Router(config)# logging message syslog_id [level severity_level]

Router# show logging message

Router# clear logging

4. Finally, configure global syslog settings:

Router(config)# logging queue queue-size

Router# show logging queue

Router(config)# logging timestamp

Router(config)# logging rate-limit {num {interval | level severity_level |

message syslog_id} | unlimited {level severity_level | message syslog_id}}

Router# show logging