The
(SBC) Remote Log functionality uses a syslog server per the
RFC 5424 standard. Unlike
Managing Local Logs, configuring a syslog server for SBC system logging allows you to manage logging resources separately from the system being monitored.
Depending on the size and configuration of your existing network infrastructure you may already have a syslog server. If your existing network infrastructure does not have a syslog server, there are many products available, including servers for Microsoft Windows (Kiwi Sys Log Server, SL4NT) and Linux systems (syslogd).
| Info |
|---|
Recommendations - Network: It is highly recommended that the syslog server used to monitor SBC log activity be located on the same subnet as the SBC system. If the SBC and syslog server are not on the same network, increased log level detail and large amount of calls may result in high bandwidth utilization.
- Total Destinations: While you can *configure up to 6 remote log server destinations* on the SBC, it is not advisable to have this many destinations configured during high call churn.
|
Working with Remote Log Servers
| Excerpt |
|---|
- In the WebUI, click the Settings tab.
- In the left navigation pane, go to Logging Configuration > Remote Log Servers.
| Panel |
|---|
| | Caption |
|---|
| 0 | Figure |
|---|
| 1 | Remote Log Configuration |
|---|
| 
|
|
|
To view a Remote Log Server's properties:
| Include Page |
|---|
| _View_Entry_Values |
|---|
| _View_Entry_Values |
|---|
|
| Include Page |
|---|
| _Delete_Entry_Procedure |
|---|
| _Delete_Entry_Procedure |
|---|
|