Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Its been a long time to be here. Now, I'm again here with couple of questions. As usual, I got the help earlier, I'm expecting the same kinda thing this time also.
I'm working on redhat clusters (RHEL 5/6) from past few years but few of the options available with RHEL cluster, I have never used. Need you help/guidance on them. Please tell what is the exact use of them and when should one need to use them? Answers with example would be more appreciable.
Here are the options -
1) clusvcadm -s ( I know it is to stop the cluster, then why -d is there? And what is the functional difference between "stop" & "disable" options?
2) clusvcadm -Z (Its for Freeze, but why one should use this, and would be the impact if someone use this option?)
3) clusvcadm -U (Unfreeze :-S )
4) clusvcadm -c
5) Final one... Why should we add a multicast address in cluster (in case if we need to do so)?
Thanks in advance.
Last edited by arunabh_biswas; 09-28-2014 at 01:51 PM.
Hi Experts,
Its been a long time to be here. Now, I'm again here with couple of questions. As usual, I got the help earlier, I'm expecting the same kinda thing this time also. I'm working on redhat clusters (RHEL 5/6) from past few years but few of the options available with RHEL cluster, I have never used. Need you help/guidance on them. Please tell what is the exact use of them and when should one need to use them? Answers with example would be more appreciable.
Here are the options -
1) clusvcadm -s ( I know it is to stop the cluster, then why -d is there? And what is the functional difference between "stop" & "disable" options?
2) clusvcadm -Z (Its for Freeze, but why one should use this, and would be the impact if someone use this option?)
3) clusvcadm -U (Unfreeze :-S )
4) clusvcadm -c
5) Final one... Why should we add a multicast address in cluster (in case if we need to do so)?
Your question is confusing...if you have been using Red Hat clusters for a few YEARS, how can you NOT know what the basics of cluster administration are? The man page for the clusvcadm command explains what the options are: http://linux.die.net/man/8/clusvcadm
...and what they do. The differences between the -s and -d are clearly spelled out, as well as the -c option. Freezing and un-freezing a service is a common task, and covered well in the RHEL documentation? https://access.redhat.com/documentat...ns-cli-CA.html
As far as multicasting goes...if you've been using clustering for a few years now, did you not research what it did, and why, before using it?
Quote:
Originally Posted by RHEL Cluster Documentation
Cluster members use multicast communication to discover other cluster members and when a message must be communicated to multiple members of the cluster. The cluster protocol makes very judicious use of multicast and avoids things such as multicast storms. By default, data is only transmitted over multicast if it is intended for more than 25% of the cluster members. The vast majority of traffic is transmitted using unicast even when multicast is enabled. For typical partitioned cache based clusters, most transmissions is point-to-point and only cluster membership and partition ownership is broadcast to the entire cluster.
Sorry for the late response. I just came back from a long vacation.
Sorry if there any ambiguity in my questions.
Yes, I've been working on linux clusters for a while but it doesn't mean I should try all the available commands/options in production environment. I tried only those which I knows what it does (which usually accomlish my needs).
I know what is multicasting and what it does. May be I was not able to put my question properly. Let me put it in simple way ;-)
Usaually, we does setup or assign any multicast address to cluster nodes. We goes with default settings (system assigned multicast addresses). In our setup, I found couple of RHEL6 clusters where multicast IP addresses are defined exclusively in the /etc/cluster/cluster.conf file (the persons those have configured these servers are no more with company and nothing has been shared). (Note: I've found couple of old mails sent by those guys within the team which suggests that they had requested for multicast addresses from network team).
So, my question is, if the cluster can be setup/configured with default multicast settings, then why someone needs to set it up manually?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.