Sponsored Content
Operating Systems Solaris Precaution during Quorum Server Reboot Post 303020343 by sb200 on Tuesday 17th of July 2018 05:13:40 AM
Old 07-17-2018
Precaution during Quorum Server Reboot

Hi

I need to know what are the precaution we should take during quorum server reboot as this quorum server is providing quorum devices to five different solaris two node clusters.

Also let me know do I have to follow below procedure as well before and after reboot of quorum server

Do I have to put those cluster quorum devices in maintenance state by running below command in one node of each of the five clusters before reboot of quorum server

Code:
clq disable <quorumdevice>

After reboot of quorum server , I need to enable the quorum device on one node of each of the five clusters by running below command

Code:
clq enable <quorumdevice>

 

9 More Discussions You Might Find Interesting

1. SCO

Reboot the sco server

Dear sir, I am using sco open server 5.06.How we can reboot the system without using root password? Whar are the permision need to change to do this. Thanks, Mostafizur Rahman (3 Replies)
Discussion started by: rahmanm
3 Replies

2. Shell Programming and Scripting

Server Reboot Alert

I want to get an email alert from a cronjob when a server got rebooted unexpectedly. Please help. Thanks! :confused: (2 Replies)
Discussion started by: angloi
2 Replies

3. UNIX for Advanced & Expert Users

server reboot

hi all, :) for a reboot of sun box for patch installation i would like to know where do the reboot logs apart from /var/adm/messages and patch run messages would be available, i would like to know the sequence of messages logged in the file like requesting the users to log out sending a... (1 Reply)
Discussion started by: matrixmadhan
1 Replies

4. AIX

IP setting changes after server reboot

I've recently changed my gateway setting using SMIT. Everything went fine except that the gateway setting kept reverting back to the old one everytime I reboot the server. I'm on AIX 5.2 running p-Series. Thanks for any info. (3 Replies)
Discussion started by: dereklow
3 Replies

5. Solaris

Reboot the server through console

Hi All, I want to know the procedure like if server is down, i want to reboot the server through console ($rsc or $sc prompt).Could you please help me out. I would really appreciate your cooperation. thanks for understanding regards krishna (5 Replies)
Discussion started by: murthy76
5 Replies

6. Linux

Linux server reboot

We reboot our linux servers daily. Is it needed ? (10 Replies)
Discussion started by: linuxadmin
10 Replies

7. UNIX for Advanced & Expert Users

Precaution to access user mode buffers from kernel

When accessing a user mode buffers from kernel space drivers what precautions must we take and how those precautions need to be implemented? (0 Replies)
Discussion started by: rupeshkp728
0 Replies

8. Solaris

Validate mountpoints on solaris server after server reboot

Hi, anyone please let us know how to write shell script to find the missing mountpoints after server reboot. i want to take the mountpount information before server reboot, and validate the mountpoints after server reboot if any missing.please let us know the shell script from begining to end as... (24 Replies)
Discussion started by: VenkatReddy786
24 Replies

9. Red Hat

Server reboot

Hi, The server got rebooted and below messages can be seen in /var/log/messages Sep 7 10:49:12 minersville kernel: Call Trace: <IRQ> <ffffffff80167420>{__alloc_pages+796} Sep 7 10:49:12 minersville kernel: <ffffffff80182814>{kmem_getpages+106} <ffffffff80183c16>{fallback_alloc+304}... (3 Replies)
Discussion started by: admin_db
3 Replies
VOTEQUORUM_OVERVIEW(8)				    Corosync Cluster Engine Programmer's Manual 			    VOTEQUORUM_OVERVIEW(8)

NAME
votequorum_overview - Votequorum Library Overview OVERVIEW
The votequuorum library is delivered with the corosync project. It is the external interface to the vote-based quorum service. This service is optionally loaded into all ndes in a corosync cluster to avoid split-brain situations. It does this by having a number of votes assigned to each system in the cluster and ensuring that only when a majority of the votes are present, cluster operations are allowed to proceed. The library provides a mechanism to: * Query the quorum status * Get a list of nodes known to the quorum service * Receive notifications of quorum state changes * Change the number of votes assigned to a node * Change the number of expected votes for a cluster to be quorate * Connect an additional quorum device to allow small clusters to remain quorate during node outages. votequorum reads its configuration from the objdb. The following keys are read when it starts up: * quorum.expected_votes * quorum.votes * quorum.quorumdev_poll * quorum.disallowed * quorum.two_node Most of those values can be changed while corosync is running with the following exceptions: quorum.disallowed cannot be changed, and two_node cannot be set on-the-fly, though it can be cleared. ie you can start with two nodes in the cluster and add a third without reboot- ing all the nodes. BUGS
This software is not yet production, so there may still be some bugs. SEE ALSO
corosync-quorumtool(8), votequorum_initialize(3), votequorum_finalize(3), votequorum_fd_get(3), votequorum_dispatch(3), votequorum_con- text_get(3), votequorum_context_set(3), corosync Man Page 2009-01-26 VOTEQUORUM_OVERVIEW(8)
All times are GMT -4. The time now is 06:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy