Alerts System Management and Maintenance
Polycom, Inc. 351
Click the link to go to the System Log Files page. We recommend routinely
downloading archived logs and then deleting them from the system.
See also:
“Alerts” on page 338
Alert 3403 Cluster <cluster>: Log files on server <server> exceed the capacity limit and will
be purged within 24 hours.
Log archives on the specified cluster exceed the 1GB capacity limit for logs.
After midnight, the system will delete sufficient log archives to get below the
1GB limit.
Click the link to go to the System Log Files page. We recommend routinely
downloading archived logs and then deleting them from the system.
See also:
“Alerts” on page 338
Alert 3404 Cluster <cluster>: Log files on server <server> are close to capacity limit and
may be purged within 24 hours.
Log archives on the specified cluster have reached the percentage of capacity
that triggers an alert, set on the Logging Settings page.
Click the link to go to the System Log Files page. We recommend routinely
downloading archived logs and then deleting them from the system.
See also:
“Alerts” on page 338
Alert 3405 Server <server> CPU utilization >50% and <75%.
The specified server’s CPU and/or I/O bandwidth usage is unusually high.
This can be caused by activities such as backup creation, CDR downloading,
logging at too high a level, or refreshing an extremely large Active Directory
cache.
The cause may also be a system health problem or a runaway process. Go to
Maintenance > Troubleshooting Utilities > Top to see if a process is
monopolizing CPU resources.