Polycom 3725-76302-001O Manual De Usuario
Polycom, Inc.
355
Alert 3301
Cluster <cluster> is configured for 2 servers, but only a single server is detected.
One of the servers in the specified cluster is not responding to the other server over the private network that
connects them.
connects them.
This could be a hardware problem, or the server in question may just need to be rebooted. It’s also possible
that the private network connection between the two servers has failed. Check the ethernet cable
connecting the GB2 ports and replace it if necessary.
that the private network connection between the two servers has failed. Check the ethernet cable
connecting the GB2 ports and replace it if necessary.
See also:
Alert 3302
Cluster <cluster> is configured for 1 server, but the private network interface is
enabled and active.
enabled and active.
Either the cluster contains two servers but was misconfigured as a single-server cluster, or there is only one
server in the cluster but something is connected its GB2 port.
server in the cluster but something is connected its GB2 port.
On a single-server cluster, don’t use the server’s GB2 port for anything.
See also:
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.
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.
Or the server in question may just need to be rebooted.
See also:
Alert 3304
Cluster <cluster>: A public management network error exists on <server>.
The specified server has detected a problem with the management (or combined management and
signaling) network connection.
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.
enterprise network switch, or that switch. Or the server in question may just need to be rebooted.
See also: