Table of Contents
Advertisement
See also:
Alerts
Alert 3303
Cluster <cluster>: A private network error exists on <server>.
The specified server has detected a problem with the private network that connects the two servers in the
cluster.
This could be a problem with the GB2 port (eth1 interface) or the ethernet cable connecting the GB2 ports.
Or the server in question may just need to be rebooted.
See also:
Alerts
Alert 3304
Cluster <cluster>: A public network error exists on <server>.
The specified server has detected a problem with the management (or combined management and
signaling) network connection.
This could be a problem with the GB1 port (eth0 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
Alert 3305
Cluster <cluster>: A 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
Alert 3306
DNS <address of DNS server> settings are inconsistent with network configuration on
Cluster <cluster>: <issue-text>.
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
Polycom, Inc.
System Management and Maintenance
363
Advertisement
Table of Contents
