sun cluster problem


 
Thread Tools Search this Thread
Operating Systems Solaris sun cluster problem
# 1  
Old 02-28-2012
sun cluster problem

Hello everyone,

Can you please help me understand what happened; here is the problem:

We have a sun cluster composed by two nodes (E4900; sSolaris 9), suddenly one of them were inaccessible by PUTTY, however we were able to ping on it. The cluster haven't basculated and after 20 minutes the problem were fixed without any action from us. There is any error's message on the logs.

thank you for your help
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Sun cluster v3.2 - Is this right?

Running Sun Cluster v3.2 it appears. Two clustered physcial servers both running Solaris 10. Both servers run a number of Oracle DBs etc. BUT I'm a bit concerned that its been set up but will never switch in the even of failure of one of the hosts? Some of the cluster groups we've... (3 Replies)
Discussion started by: psychocandy
3 Replies

2. Solaris

Sun cluster 4.0 - zone cluster failover doubt

Hello experts - I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts. (1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over) (2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies

3. Solaris

Sun cluster 3.2

Hi I have a new mount point which is to added to to an existing resource group. I read many docs but I am not able to find the exact methods. Could anyone help me pls. (1 Reply)
Discussion started by: ningy
1 Replies

4. Solaris

Sun cluster and Veritas cluster question.

Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC. Am thinking how to migrate to sun cluster setup instead. My plan as follows leave the existing vcs intact as a fallback plan. Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies

5. Solaris

Sun Cluster

Hi All I hav working knowledge on solarois 10. Could anyone suggest me any doc or material for learning SUN cluster from scratch. Anything from basic level . Thanks in advance!! (1 Reply)
Discussion started by: ningy
1 Replies

6. Emergency UNIX and Linux Support

Sun Cluster-Metaset problem

Hi Guys i have two servers which are n cluster prd1 and prd2.. I already have a metaset configured in it..My job was to create a 1.8 tb LUN in my storage which is having Hardware raid5 pre-configured..i Created 1.8 tb with raid 5 in my storage and it got detected in both t servers... (5 Replies)
Discussion started by: madanmeer
5 Replies

7. Solaris

Sun Cluster-Metaset problem

Hi Guys i have two servers which are n cluster prd1 and prd2.. I already have a metaset configured in it..My job was to create a 1.8 tb LUN in my storage which is having Hardware raid5 pre-configured..i Created 1.8 tb with raid 5 in my storage and it got detected in both t servers prd1... (4 Replies)
Discussion started by: madanmeer
4 Replies

8. Solaris

sun cluster 3.2 + oracle 11g HA problem C748634 ,C135343

Dear Cluster Guru, I had installed sc 3.2 on 2 box sunfire 240 (solaris 10 update 7 ,each node 2 gb ram) and use scsi juke box as share storage . i had test cluster application : 1. apache HA 2 oracleHA (oracle 9i) all running well (switch over between... (3 Replies)
Discussion started by: hadibn
3 Replies

9. High Performance Computing

SUN Cluster Vs Veritas Cluster

Dear All, Can anyone explain about Pros and Cons of SUN and Veritas Cluster ? Any comparison chart is highly appreciated. Regards, RAA (4 Replies)
Discussion started by: RAA
4 Replies
Login or Register to Ask a Question
cmrunnode(1m)															     cmrunnode(1m)

NAME
cmrunnode - run a node in a high availability cluster SYNOPSIS
cmrunnode [-v] [node_name...] [-t | -w none] DESCRIPTION
cmrunnode causes a node to start its cluster daemon to join the existing cluster. This command verifies the network configuration before causing the node to start its cluster daemon. To start a cluster on one of its nodes, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the clus- ter configuration file. See access policy in cmquerycl(1m). Starting a node will not cause any active packages to be moved to the new node. However, if a package is DOWN, has its switching enabled, and is able to run on the new node, that package will automatically run there. If node_name is not specified, the cluster daemon will be started on the local node and will join the existing cluster. Options cmrunnode supports the following options: -v Verbose output will be displayed. -t Test only. Provide an assessment of the package placement without affecting the current state of the nodes or packages. The -w option is not required with the -t option as -t does not validate network connectivity, but assumes that all the nodes can meet any external dependencies such as EMS resources, package subnets, and storage. node_name... Start the cluster daemon on the specified node(s). -w none By default network probing is performed to check that the network connectivity is the same as when the cluster was configured. Any anomalies are reported before the cluster daemons are started. The -w none option disables this probing. The option should only be used if this network configuration is known to be correct from a recent check. RETURN VALUE
cmrunnode returns the following value: 0 Successful completion. 1 Command failed. EXAMPLES
Run the cluster daemon on the current node: cmrunnode Run the cluster daemons on node1 and node2: cmrunnode node1 node2 AUTHOR
cmrunnode was developed by HP. SEE ALSO
cmquerycl(1m), cmhaltcl(1m), cmhaltnode(1m), cmruncl(1m), cmviewcl(1m), cmeval(1m). Requires Optional Serviceguard Software cmrunnode(1m)