Filter
Top Products
Polycom, Inc. 358
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 Alerting 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 342
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.
Create a new backup and download it, and then contact Polycom Global Services.
See also:
Alerts on page 342
Alert 3406
Server <server> CPU utilization > 75%.
The specified server’s CPU and/or I/O bandwidth usage is exceptionally 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.
Create a new backup and download it, and then contact Polycom Global Services.
See also:
Alerts on page 342
Alert 3601
Cluster <cluster>: System version differs between servers.
The specified cluster is supposed to have two servers, but a software version mismatch makes it impossible
for them to form a redundant two-server cluster.