The Sonus SBC 1000/2000 Remote Log functionality uses a syslog server per the RFC 5424 standard. Unlike Managing Local Logs, configuring a syslog server for Sonus SBC 1000/2000 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).
Recommendations
- Network: It is highly recommended that the syslog server used to monitor Sonus SBC 1000/2000 log activity be located on the same subnet as the Sonus SBC 1000/2000 system. If Sonus SBC 1000/2000 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 Sonus SBC 1000/2000, it is not advisable to have this many destinations configured during high call churn.
Working with Remote Log Servers
- In the WebUI, click the Settings tab.
- In the left navigation pane, go to Logging Configuration > Remote Log Servers.
Remote Log Configuration
To view a Remote Log Server's properties:
- Click the pop-up icon (
) next to the entry you want to view. - When you are finished, close the window.
To delete an entry, select the checkbox next to the entry and then click the Delete (
) icon.
Overview
Content Tools