Help contents >
Advanced topics >
Logging using syslog
|
Search/Print Index |
You can send the Event log to one or more syslog servers on the network for storage or analysis.
To configure the syslog facility, go to
.On this page:
Refer to this table for assistance when configuring Syslog settings:
Field | Field description | Usage tips |
---|---|---|
Host address 1 to 4 | Enter the IP addresses of up to four Syslog receiver hosts. |
The number of packets sent to each configured host will be displayed next to its IP address. |
Facility value | A configurable value for the purposes of identifying events from the MCU on the Syslog host. Choose from the following options:
|
Choose a value that you will remember as being the MCU. Note: Various operating system daemons and processes have been found to utilize Facilities 4, 10, 13 and 14 for security/authorization, audit, and alert messages which seem to be similar. Various operating systems have been found to utilize both Facilities 9 and 15 for clock (cron/at) messages. Processes and daemons that have not been explicitly assigned a Facility value may use any of the "local use" facilities (16 to 21) or they may use the "user-level" facility (1) - and these are the values that we recommend you select.
|
The events that are forwarded to the syslog receiver hosts are controlled by the event log capture filter.
To define a syslog server, simply enter its IP address and then click
. The number of packets sent to each configured host is displayed next to its IP address.If the MCU is being managed by a remote management system, for instance TANDBERG TMS, information on that remote system may be shown on this page. In certain circumstances you may need to remove the link between the external system and the MCU. To do so, click
.(c) Copyright TANDBERG 2003-2010, License information |