- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: broken cluster after autogen
Operating System - OpenVMS
1753379
Members
5366
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
тАО06-28-2009 10:26 AM
тАО06-28-2009 10:26 AM
Re: broken cluster after autogen
> I'm using EXPECTED_VOTES=3 on both nodes, but VOTES=1 only on 1 of the 2 members. I was reading that only one should have VOTES=1
URL or reference, please?
Save for very specific circumstances when you might "play games" or "get creative" with the system parameter settings of votes and expected_votes to get a particular configuration to initially boot or such, whatever you were reading was either confusing, mis-worded, or was telling you how to corrupt your disks.
For a two-node cluster with no shared storage, read this:
http://labs.hoffmanlabs.com/node/967
For more general information, read this:
http://labs.hoffmanlabs.com/node/153
URL or reference, please?
Save for very specific circumstances when you might "play games" or "get creative" with the system parameter settings of votes and expected_votes to get a particular configuration to initially boot or such, whatever you were reading was either confusing, mis-worded, or was telling you how to corrupt your disks.
For a two-node cluster with no shared storage, read this:
http://labs.hoffmanlabs.com/node/967
For more general information, read this:
http://labs.hoffmanlabs.com/node/153
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2009 10:47 AM
тАО06-28-2009 10:47 AM
Re: broken cluster after autogen
Congratulations.
That must feel great. In 10 years of tech support for VNS. I heard so many people blame autogen.
Now that you found it, check where all the add_params are set to and change them to
mid_params=actual value.
Did you find it dif/par setparams.dat?
I always did this after running autogen,
looking to make sure especially it didn't change any cluster of shadow parameters.
I don't know your site but having a pair of eyes there at night you can depend on can
make your life easier.
So, it was hanging ready to form or join a cluster.
Is your quorum disk seen by each system
at the boot prompt?
I really think simplifying your modparams.dat
will greatly help diagnosing in the future.
If you reviewed agen$feedback.dat the change would have been there, along with so much other information you miss it. Dif/par would have made the change more obviouis.
And now, joy of joys, you know you have an autogenable system.
Have fun.
System management, 90% simple stuff,
9% interesting and learning stuff, and
1% utter panic. Somehow we forget the
98% skill and easy stuff, and focus on
the 1% of utter panic!
Please don't forget to add points.
I miss this, I worked tech support for 10 years and two of my specialities were clustering and boot, and your call was both.
That must feel great. In 10 years of tech support for VNS. I heard so many people blame autogen.
Now that you found it, check where all the add_params are set to and change them to
mid_params=actual value.
Did you find it dif/par setparams.dat?
I always did this after running autogen,
looking to make sure especially it didn't change any cluster of shadow parameters.
I don't know your site but having a pair of eyes there at night you can depend on can
make your life easier.
So, it was hanging ready to form or join a cluster.
Is your quorum disk seen by each system
at the boot prompt?
I really think simplifying your modparams.dat
will greatly help diagnosing in the future.
If you reviewed agen$feedback.dat the change would have been there, along with so much other information you miss it. Dif/par would have made the change more obviouis.
And now, joy of joys, you know you have an autogenable system.
Have fun.
System management, 90% simple stuff,
9% interesting and learning stuff, and
1% utter panic. Somehow we forget the
98% skill and easy stuff, and focus on
the 1% of utter panic!
Please don't forget to add points.
I miss this, I worked tech support for 10 years and two of my specialities were clustering and boot, and your call was both.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2009 05:54 PM
тАО06-28-2009 05:54 PM
Re: broken cluster after autogen
Sorry, i cannot find the reference anymore, but it does not matter. I know your information is correct.
I checked with "mcr sysgen - use current - show votes" and the current and default value for votes = 1. I guess that is the reason why it works, even though I do not have votes=1 specified on one of nodes. I will correct it.
Thanks for all the info.
I checked with "mcr sysgen - use current - show votes" and the current and default value for votes = 1. I guess that is the reason why it works, even though I do not have votes=1 specified on one of nodes. I will correct it.
Thanks for all the info.
- « Previous
-
- 1
- 2
- Next »
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