The ClusterX client does not detect a cluster connected to the same network.
| Article:TECH1421 | | | Created: 1999-01-19 | | | Updated: 2004-01-21 | | | Article URL http://www.symantec.com/docs/TECH1421 |
Problem
The ClusterX client does not detect a cluster connected to the same network.
Solution
The detection of a cluster connected to the same network as
the ClusterX client relies on several factors, such as system state, client
configuration, security configuration, and network configuration. The
configuration settings applicable to these four categories are described
below.
SYSTEM STATE
SYSTEM STATE
* The MSCS Cluster Service
(clussvc.exe) needs to be started on both nodes.
* The RPC Service needs to
be started on both nodes.
* The Cluster Group (a
group created during the MSCS installation) needs to be online.
* If all of these
conditions are met, verify that the Event Viewer does not display any MSCS or
RPC related errors.
CLIENT CONFIGURATION
* The client must be
configured to search the domain that contains the cluster to be detected. In the
ClusterX client, go to Options > Domain and Cluster Selection... The options
here allow ClusterX to search the local domain, specific domains, all domains,
or specific names and IPs. If the specific domains option is used, verify that
the cluster's domain is listed, or add it.
SECURITY CONFIGURATION
* If the account is in a
domain other than the domain that the cluster resides in, verify that the
cluster domain trusts the domain containing the user account. If this is not the
case, use User Manager for Domains to create a trust between the two domains.
This will allow the account to be added to local groups in the cluster's
domain.
* Verify that the account
is a member of the local administrators group for both domains. Add the account
to the local administrators group through User Manager for Domains, if this is
not the case.
* Confirm that the account
is "allowed access" to the cluster. To do this, open Cluster Administrator,
highlight the cluster in the left window and go to Properties. On the
General tab, select the Permissions option. If the account is not
listed with "Full Control," then add the account and grant it this
access.
NETWORK CONFIGURATION
* Ping the IP address of
each cluster node's client NIC. If the ping is not returned, ping any routers
between the client and the server to determine if the ping is being lost at a
specific point along the path. If not, this may indicate a network configuration
issue on the client.
* Ping the cluster and its
nodes by name. If the ping does not reach its destination, this may indicate a
problem with the client's WINS server.
|
|
Legacy ID
181602
Article URL http://www.symantec.com/docs/TECH1421
Terms of use for this information are found in Legal Notices
Thank you.