- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Cluster with EVA
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО05-25-2005 08:41 AM
тАО05-25-2005 08:41 AM
May somebody give me some idea about what is necessary to tuning.
I was getting a problem with the quorum disk , it was not possible to form the cluster when I had my quorum disk as a separate disk.
The solution was that the quorom be the boot disk in one of the two system,
Both machines can see the quorum and the boot disk from the prompt.
thank you
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2005 06:16 PM
тАО05-25-2005 06:16 PM
SolutionMight this be related to the problem discussed in another thread?
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=886474
To form a cluster with a quorum disk, the 1st node to boot up will try to create the QUORUM.DAT file on the quorum disk. That disk has to be mounted quite early in the boot sequence, and the booting node must have enough votes to form the cluster.
Regards,
Kris (aka Qkcl)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2005 11:52 PM
тАО05-25-2005 11:52 PM
Re: Cluster with EVA
what you have created now, is a cluster that depeends much too heavily on the quorum disk.
Since it is also the system disk for one node, loosing it also looses your cluster.
And maybe unrelated, but out of pure curiosity: WHY two system disks? Things get SOOOO much easier if you have only one common system disk!
... and if you DO have those disks available anyhow, then combining them into one shadow set adds A LOT of extra redundancy (just contrary to your single-system-dependant quorum disk.
hth,
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2005 11:55 PM
тАО05-25-2005 11:55 PM
Re: Cluster with EVA
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-26-2005 12:14 AM
тАО05-26-2005 12:14 AM
Re: Cluster with EVA
Now there is an issue with using a quorum disk on fiber. It can reply quicker than a a keep alive message from the lan. Than the other node will clue exit.
This is a problem especially with large clusters where a small part of the cluster sees the quorum disk and loses connection to the rest of the cluster, and the rest of the cluster clue exits.
That said, for a two node cluster, there is no point in having a local system disk as a quorum disk, since that node has to be up. All you are doing is adding overhead, might as well give that system one vote and the other node 0 votes.
I suspect you weren't able to build quorum.dat on the eva disks, because you didn't have enough votes to boot without the quorum disk vote. Try setting the quorum disk to a shared device, and conversationally setting the votes on the booting node to a large number. It will then build quorum.dat. Then you can reset your voting scheme.
Bob C
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-26-2005 02:07 AM
тАО05-26-2005 02:07 AM
Re: Cluster with EVA
The quorum disk also is in the EVA, but at first was a separate Virtual disk.
I am from the hardware support team; I asked to the software support about why the quorum has been set in one of the operating system disk, they explain to me that it was the only way that they were able to form the cluster.
When they try to form the cluster there was a lot of error and the only disk that was able to be take as an option of quorum was the
1$1dga1 and not the 1$1dga3 that was the initial disk that I have been presented to the system as the quorum disk.
1$1dga1 was the OS for the DS25
1$1dga2 the second disk that the customer need as a separated OS system disk for a ES45
1$1dga3 the quorum disk
All these disk were configured using the wwidmgr for that the systems can be able to see the disk from the >>> prompt.
The cluster has 3 votes,
I am going to ask them about the exact parameter that has been set in the nodes.
Have someone the guided procedure to form install the cluster using and EVA and VMS as the operating system (7.3-1),
All the Vms patches have been applied.
Thank I will appreciate your help.
W.S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-28-2005 05:28 AM
тАО05-28-2005 05:28 AM
Re: Cluster with EVA
Something is configured wrong, the quorum disk should be viewable from both systems at boot time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-28-2005 06:41 PM
тАО05-28-2005 06:41 PM
Re: Cluster with EVA
there is no need to configure the quorum disk access path with WWIDMGR. This is only needed for boot (and dump) disks.
Boot your first node with EXPECTED_VOTES=1 (temporarily), DISK_QUORUM="$1$DGA3:" and QDSKVOTES=1. Once the system is up, mount/sys $1$DGA3: and CLUSTER_SERVER will create the QUORUM file. Check with SHOW CLUSTER/CONT 'add cluster', you should see QF_VOTES=YES
Once this is done, reset EXPECTED_VOTES=3 and reboot the node, this will prove, that everything works as expected and that one node together with the quorum disk works fine. Then boot your second node and check, whether it can also acess the QUORUM disk locally.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-30-2005 06:29 AM
тАО05-30-2005 06:29 AM
Re: Cluster with EVA
I build my cluster with same machines and same eva storage..
The principal issue was because you have
4 principal network cards for each machines.
you needs to define the principal network card
ewa-0 and eia-0 ( close in decnet the circuits and links) fisicly put in your principal card speed 100 full duplex
and the quorum will be found inmediatly.
If you have more issues with your cluster tell me I will put in production next week the mine.
Edgar
eulloa@tecnasa.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-30-2005 06:44 AM
тАО05-30-2005 06:44 AM
Re: Cluster with EVA
If both nodes cannot talk over the network interconnect, then you have a problem that is completely independent from a potential quorum disk problem.
WATCH OUT! In that case, do NOT play with VOTES and EXPECTED_VOTES settings, because that can cause a 'partitioned' cluster - well, better call that two single-node clusters on the same storage array which will happily corrupt your disks.
You only hope is that you have properly configured your quorum disk, so that both node learn from each other through the quorum file and prevent any corruption.