[Info-vax] Expected votes Was: troubles with quorum disk

[Tom Linden]

On Wed, 09 Jan 2013 12:21:53 -0800, Stephen Hoffman  
<seaohveh at hoffmanlabs.invalid> wrote:

> On 2013-01-09 19:50:52 +0000, Tom Linden said:
>
>> ...A while ago we had a power outage that lasted longer than the
>> UPS batteries.  The cluster did not come back up automatically.  The  
>> licenses had not
>> been updated on one of the nodes, an oversight.  On closer exam I noted  
>> that expected_votes
>> in the 4 node cluster was set at 3 on the other 3 nodes and 7 on the  
>> errant node.   The cluster
>> was once 7 nodes but have reduced it.  I tried setting expected votes  
>> to 4 in SYSGEN and did a
>> WRITE CURRENT  but it did not change it.  What do I need to do?
>
> o set the EXPECTED_VOTES parameter to the total number of votes expected  
> within the cluster, both in MODPARAMS.DAT and in the system parameters

It has been a number of years since I last did this, but IIRC,  
MODPARAMS.DAT
is hand edited and the system parameters are set through SYSGEN, n'est-ce  
pas?

Thanks
Tom
>
> o WRITE CURRENT saves the settings in the database.  It's applicable  
> here, as it's the value preserved over reboot.  Also update  
> MODPARAMS.DAT.
>
> o WRITE ACTIVE saves the running values.  It's not applicable here.
>
> o update your preferred calendar to give you a month or a week advance  
> of notice of the PAK expiration(s).
>
> o to avoid rebooting the cluster to adjust the quorum value, you can  
> tweak the current cluster quorum settings.  See the HELP for the SET  
> CLUSTER /EXEPECTED command for details.
>
> o test your cluster reboot periodically, either as a rolling reboot or  
> as a cluster reboot.  Server uptime is a measure of how long it's been  
> since you've last tested your critical processes, after all.
>
>
>
>


-- 
PL/I for OpenVMS
www.kednos.com