Polycom 7000 ユーザーズマニュアル
Local Cluster Configuration
Polycom, Inc.
78
See also:
Alerting Settings
The Alerting Settings page allows you to configure thresholds for system alerts. Here, you can enable or
disable certain alerts, and control when they will be triggered.
disable certain alerts, and control when they will be triggered.
The Threshold Value column on the right of the page lists the configurable value for each alert’s threshold.
Use the arrows next to each field or enter a new number to change the default value. Click the Update
button to save your changes, or the Select Defaults button to revert them (Select Defaults returns the
values in all fields on this page to their factory defaults).
Use the arrows next to each field or enter a new number to change the default value. Click the Update
button to save your changes, or the Select Defaults button to revert them (Select Defaults returns the
values in all fields on this page to their factory defaults).
See the following table for descriptions of each alert’s condition.
Retention period (days)
The number of days to keep log archives. For most systems, we recommend
setting this to 7.
setting this to 7.
Local log forwarding
Checking the Enable forwarding check box allows you to forward selected
log entries to a central log management server (such as
log entries to a central log management server (such as
). The log
management server should be configured to accept log entries via UDP port
514.
Specify:
•
514.
Specify:
•
The address of the destination server. It must be running some version of
syslog.
syslog.
•
The facility value. Default is Local0.
•
The log or logs to forward. The source log file name is included in each of
the forwarded messages.
the forwarded messages.
Note: The RealPresence DMA system’s server.log entries are mapped to
syslog-compliant severities (for example, a “warn” message from server.log
arrives at the destination server with the syslog-compliant “warn” level, and an
“info” message arrives with the “info” level). All other logs being forwarded are
assigned the syslog-compliant “notice” severity.
Each log message is forwarded with the RealPresence DMA system’s
timestamp intact. The receiving syslog adds its own timestamp, but preserving
the RealPresence DMA-applied timestamp makes it easier to accurately
troubleshoot time-sensitive events.
syslog-compliant severities (for example, a “warn” message from server.log
arrives at the destination server with the syslog-compliant “warn” level, and an
“info” message arrives with the “info” level). All other logs being forwarded are
assigned the syslog-compliant “notice” severity.
Each log message is forwarded with the RealPresence DMA system’s
timestamp intact. The receiving syslog adds its own timestamp, but preserving
the RealPresence DMA-applied timestamp makes it easier to accurately
troubleshoot time-sensitive events.
Note: SNMP and system alerts configuration
Since the triggering of SNMP alerts coincides with system alerts, configuration on this page applies to
both system alerts and SNMP alerts.
Since the triggering of SNMP alerts coincides with system alerts, configuration on this page applies to
both system alerts and SNMP alerts.
Field
Description