Filter
Top Products
Polycom, Inc. 356
Alert 3305
Cluster <cluster>: A public signaling network error exists on <server>.
The specified server has detected a problem with the signaling network connection.
This could be a problem with the GB3 port (eth2 interface), the ethernet cable connecting the server to the
enterprise network switch, or that switch. Or, the server in question may just need to be rebooted.
See also:
Alerts on page 342
Alert 3306
DNS <address of DNS server> settings are inconsistent with network
configuration on Cluster <cluster>: <issue-text>. (FTL20281)
The system has found issues with the DNS configuration on the Admin > Local Cluster > Network
Settings page for the specified cluster. This could indicate one of the following possible problems:
● The virtual or management host name A or AAAA record configured in the specified DNS server is
missing
● The virtual or management host name A or AAAA record configured in the specified DNS server
references the incorrect address
The alert text describes the nature of the problem, which may require additional configuration of the DNS
server(s) or network settings for the cluster.
Refer to Chapter 2 of the Polycom RealPresence DMA 7000 System Operations Guide for more information
regarding DNS configuration.
Click the link to go to the Admin > Local Cluster > Network Settings page.
See also:
Alerts on page 342
Add Required DNS Records for the Polycom RealPresence DMA System on page 30
Alert 3309
<cluster>: DNS <address of DNS server> is unresponsive. <service> at <FQDN>
<referenced by> {will use <IP address> | cannot be reached}.
One or more configured DNS servers are not responding to requests from the specified cluster. The system
will use the last cached IP address for the DNS server, but if no IP address is known, this DNS server is
considered unreachable.
This could indicate a network problem, or that a DNS server is out of service.
Click the link to go to the Admin > Local Cluster > Network Settings page.
See also:
Alerts on page 342