- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- OpenVMS cluster - expected_votes
Operating System - OpenVMS
1753257
Members
5738
Online
108792
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-15-2009 03:40 PM
тАО07-15-2009 03:40 PM
I have a 4 node cluster with 3 of them being voting nodes (vote=1). On one node the value for expected_votes had a typo so the expected votes was calculated. Of this I would have expected to see expected_votes calculated to 3 however its coming back as 4. This is openvms 7.3-2.
I hardcoded the expected votes in modparams.
Except from SYS$SYSROOT:[SYSEXE]AGEN$PARAMS.REPORT
EXPECTED_VOTES parameter information:- AUTOGEN parameter calculation has been overridden. The calculated value was 4. The value 3 will be used in accordance with the following requirements:EXPECTED_VOTES has been specified by a hard-coded value of 3.
I checked the systems and qdskvotes=0 on all and votes are 1 where they are suppose to be. When I had a node reboot is when I found out the expected_votes was wrong - had to do a set cluster/expected=3.
Is my understanding how expected_votes is calculated wrong?
I hardcoded the expected votes in modparams.
Except from SYS$SYSROOT:[SYSEXE]AGEN$PARAMS.REPORT
EXPECTED_VOTES parameter information:- AUTOGEN parameter calculation has been overridden. The calculated value was 4. The value 3 will be used in accordance with the following requirements:EXPECTED_VOTES has been specified by a hard-coded value of 3.
I checked the systems and qdskvotes=0 on all and votes are 1 where they are suppose to be. When I had a node reboot is when I found out the expected_votes was wrong - had to do a set cluster/expected=3.
Is my understanding how expected_votes is calculated wrong?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-15-2009 05:50 PM
тАО07-15-2009 05:50 PM
Solution
Here, just establish the VOTES and EXPECTED_VOTES values as appropriate; this is VOTES=1 (for each of three cluster hosts) and EXPECTED_VOTES=3, based on your comments.
At its core, this looks to be an AUTOGEN question more than anything else, and particularly around how AUTOGEN picks a default value for this parameter when you don't establish one.
This calculation of the default is not related to the operational processing of VOTES and EXPECTED_VOTES and the downstream calculation of quorum within a cluster.
See the AUTOGEN.COM DCL below for the logic used:
$temp = 1
$IF cluster THEN GOTO genparams55
$mscp_device = (F$GETDVI(F$TRNLNM("sys$sysdevice"),"devchar2") .AND. 32) / 32
$IF .NOT. mscp_device THEN GOTO genparams55
$temp = 0
$genparams55:
$GOSUB Check_overrides
$IF temp .NE. vaxcluster THEN GOSUB output_overrides
$temp = F$GETSYI("CLUSTER_EVOTES")
$temp1= F$GETSYI("EXPECTED_VOTES")
$IF temp .LT. temp1 THEN temp = temp1
$param_name = "EXPECTED_VOTES"
$GOSUB Check_overrides
$IF temp .NE. expected_votes THEN GOSUB output_overrides
$temp = agen$d_votes
$IF satellite THEN temp = 0
$param_name = "VOTES"
$GOSUB Check_overrides
$IF temp .NE. votes THEN GOSUB output_overrides
$temp = agen$d_mvtimeout
$param_name = "MVTIMEOUT"
$GOSUB Check_overrides
$IF temp .NE. mvtimeout THEN GOSUB output_overrides
At its core, this looks to be an AUTOGEN question more than anything else, and particularly around how AUTOGEN picks a default value for this parameter when you don't establish one.
This calculation of the default is not related to the operational processing of VOTES and EXPECTED_VOTES and the downstream calculation of quorum within a cluster.
See the AUTOGEN.COM DCL below for the logic used:
$temp = 1
$IF cluster THEN GOTO genparams55
$mscp_device = (F$GETDVI(F$TRNLNM("sys$sysdevice"),"devchar2") .AND. 32) / 32
$IF .NOT. mscp_device THEN GOTO genparams55
$temp = 0
$genparams55:
$GOSUB Check_overrides
$IF temp .NE. vaxcluster THEN GOSUB output_overrides
$temp = F$GETSYI("CLUSTER_EVOTES")
$temp1= F$GETSYI("EXPECTED_VOTES")
$IF temp .LT. temp1 THEN temp = temp1
$param_name = "EXPECTED_VOTES"
$GOSUB Check_overrides
$IF temp .NE. expected_votes THEN GOSUB output_overrides
$temp = agen$d_votes
$IF satellite THEN temp = 0
$param_name = "VOTES"
$GOSUB Check_overrides
$IF temp .NE. votes THEN GOSUB output_overrides
$temp = agen$d_mvtimeout
$param_name = "MVTIMEOUT"
$GOSUB Check_overrides
$IF temp .NE. mvtimeout THEN GOSUB output_overrides
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-16-2009 07:33 AM
тАО07-16-2009 07:33 AM
Re: OpenVMS cluster - expected_votes
You know I should have thought about drilling into autogen.
Apparently when it first joined the cluster it thought it was a voting member. I changed the votes but didn't set expected_votes at that time. So it still remembered its old one and didn't do any calculation but just kept recalling its old value.
Thanks.
Apparently when it first joined the cluster it thought it was a voting member. I changed the votes but didn't set expected_votes at that time. So it still remembered its old one and didn't do any calculation but just kept recalling its old value.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-16-2009 07:56 AM
тАО07-16-2009 07:56 AM
Re: OpenVMS cluster - expected_votes
Closing the thread.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP