Table Of Contents

Additional Information about Syslog Capabilities

Internal Log Levels

Enabling Syslog Functionality

Additional Information about Syslog Capabilities

---

You may decide to use the syslog protocol in order to see debug messages from the SBC application. This appendix describes how use the syslog protocol to set the appropriate logging level.

For information about the commands used in this appendix, see the Application Control Engine Module Command Reference at http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/v3.00_A1/command/reference/cmdref.html.

Internal Log Levels

The SBC application uses an internal log-level in order to control logging to the file and console (separate log-levels can be set for both). The default SBC logging level is 63 for both file and console. You can change the default SBC logging level using the debug services sbc log-level console command or the debug services sbc log-level file command.

The internal SBC application log-levels are mapped to syslog levels (<1-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

---

Note The SBC internal log-level default (63) is OK for most purposes.

---

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 level of 63 (no further action is needed if this is a fresh reboot).

1. First, enable logging using the following commands:

host1/Admin# configure

host1/Admin(config)# logging enable

host1/Admin(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>

host1/Admin(config)# logging console severity-level

· Buffer: logging buffer <1-7>

host1/Admin(config)# logging buffered severity-level

---

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

---

---

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

---

Syslog server: logging trap <1-7>

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

host1/Admin(config)# logging trap severity-level

host1/Admin(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.

---

host1/Admin(config)# logging facility number

· Telnet sessions: logging monitor <1-7>

host1/Admin(config)# logging monitor severity-level

host1/Admin# terminal monitor

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

host1/Admin(config)# logging history severity-level

· Supervisor: logging supervisor <1-7>

host1/Admin(config)# logging supervisor severity-level

3. Next, configure specific syslog message manipulation:

host1/Admin(config)# logging message syslog_id [level severity_level]

host1/Admin# show logging message

host1/Admin# clear logging

4. Finally, configure global syslog settings:

host1/Admin(config)# logging queue queue-size

host1/Admin# show logging queue

host1/Admin(config)# logging timestamp

host1/Admin(config)# logging rate-limit {num {interval | level severity_level |

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

host1/Admin# show logging

---

Note The logging queue size for the Admin context will be 8192.

---