Sponsored Content
Full Discussion: Sun Cluster 3.2
Operating Systems Solaris Sun Cluster 3.2 Post 302420495 by xor on Tuesday 11th of May 2010 09:50:36 PM
Old 05-11-2010
Sun Cluster 3.2

Hi,

I am getting these messages constantly at random times there is not visible impact but would like to know what these messages mean?


Cluster.RGM.rgmd: [ID 529407 daemon.notice] resource group
on node change to RG_ON_PENDING_R_RERT

Cluster.RGM.rgmd: [ID 529407 daemon.notice] resource group on node change to RG_ONLINE
 

9 More Discussions You Might Find Interesting

1. 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

2. Solaris

sun cluster

hi can u please send me how to configure cluster in x86 machines. i am using VM ware. Is there any difference in X86 and SPARC cluster installations please help me thaks to all (1 Reply)
Discussion started by: sijocg
1 Replies

3. 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

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 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

6. Solaris

Sun cluster 3.1

Hi, I have upgraded a Sparc T2000 server which is node 2, in a Sun Cluster 3.1 two node cluster from Solaris 10 Update 2, to 10 Update 7. This is a requirement for a NetApps solution as we currently have a Sun 3510 SAN. I am at a stage where I believe the two nodes will not communicate over the... (0 Replies)
Discussion started by: zetex
0 Replies

7. Solaris

Sun cluster

Any body can tell me where i can download sun cluster installation and configuration video. is there any option to install cluster in 32 bit virtual machine. please help (4 Replies)
Discussion started by: sunnybee
4 Replies

8. 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

9. 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
SUNW.SCTelemetry(5)					     Sun Cluster Miscellaneous					       SUNW.SCTelemetry(5)

NAME
SUNW.SCTelemetry, SCTelemetry - resource type for collecting data on system resource usage DESCRIPTION
SUNW.SCTelemetry is the resource type that enables you to collect data on the usage of system resources. SUNW.SCTelemetry stores system resource usage data in a Java DB database for seven days. The resource of type SUNW.SCTelemetry has a dependency on the resource of type SUNW.derby. For more information, see the SUNW.derby(5) man page. The extension properties associated with the SUNW.SCTelemetry resource type are as follows: Extended_accounting_cleanup(boolean) Specifies whether the extended accounting log file is cleaned up, that is whether historical data is deleted. Possible values for Extended_accounting_cleanup are TRUE and FALSE. Category Optional Default TRUE Tunable Anytime Monitor_retry_count(integer) Controls fault-monitor restarts. The property indicates the number of times that the process monitor facility restarts the fault moni- tor. The property corresponds to the -n option passed to the pmfadm(1M) command. The Resource Group Manager (RGM) counts the number of restarts in a specified time window. See the Monitor_retry_interval property for more information. Note that Monitor_retry_count refers to the restarts of the fault monitor itself, not to the resource of type SUNW.SCTelemetry. Category Optional Default 2 Tunable Anytime Monitor_retry_interval(integer) Indicates the time window in minutes during which the RGM counts fault-monitor failures. The property corresponds to the -t option passed to the pmfadm(1M) command. If the number of times the fault monitor fails exceeds the value of the Monitor_retry_count prop- erty, the process monitor facility does not restart the fault monitor. Category Optional Default 2 minutes Tunable Anytime Probe_timeout(integer) Specifies the timeout value, in seconds, for the probe. Category Optional Default 30 seconds Tunable Anytime Sampling_interval(integer) Specifies how often monitoring data is collected. The Telemetry_sampling_interval property must have a value of between 30 and 3600. Category Mandatory Default 60 Tunable Anytime SEE ALSO
pmfadm(1M), SUNW.derby(5) Sun Cluster 3.2 12 Jul 2005 SUNW.SCTelemetry(5)
All times are GMT -4. The time now is 07:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy