- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Clustering question.
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
тАО09-30-2010 05:05 AM
тАО09-30-2010 05:05 AM
Clustering question.
I am making changes to the interconnectivity of my (mixed architecture, I64/Alpha) cluster. Basically, I run 3 bl860c blades as the core of my cluster, however I have an alpha (DS10) which is a non-voting member of my cluster. I need the alpha to run some old legacy stuff (Advanced Server, Faxsr, etc.)
Because the alpha is in a different network, I currently have a direct connection from one of the Alpha NICs to the VC module on my c7000. This connection allows the SCS traffic to move between the Alpha and the Blades.
The connect is however a single point of failure and is a problem when Blade enclosure maintenance it taking place. Because of this, I am in the process of connecting the alpha through the network to the blades, using a defined VLAN (801) to overcome the network problems. Since I am not a network person, (and this is not really a network question), I have been trying to come up with a method of determining whether the SCS communication between the Alpha and the blades it good, or not, after moving to the Network connection. The problem is that when the alpha boots, it mounts the itanium sys disk in order to access the QMan files, Sysuaf, etc. Therefore I really need to know that the SCS communications are working before the alpha mounts the itanium disk and partitions the cluster.
I know that I can avoid partition by setting votes to 0 and Expected_Votes to 1 on the Alpha, so boot can only take place if another cluster node supplies the required vote (actual settings are VOTES=0, EXPECTED_VOTES=3, so all three blades are required for the Alpha to boot). (I am considering setting Expected_votes down to 1 so that I can resolve this communication question with only one blade up (time saving.))
So my question is this; If I have one (IA64) cluster node up, supplying 1 vote, and the alpha boots with VOTES=0 and EXPECTED_VOTES greater than the available votes (i.e. > 1), What will happen when the alpha gets to the
"Waiting to form or join an VMSCluster" pointтАЭ??
Will it just hang because it doesn't have enough votes,
And if it does, will the OPCOM on the Blade still get the
"Node Blade received VMScluster membership request from node Alpha" message.
I am thinking that if the blade receives the Membership request from the Alpha, then this confirms that the communication path is OK, even though there are not enough votes for the Alpha to join the cluster.
Is this reasonable? Or am I missing something.
Thanks
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-30-2010 05:51 AM
тАО09-30-2010 05:51 AM
Re: Clustering question.
By default, unless you run lavc_stop_bus or stop an interface with scacp, SCS is started on all network interfaces.
If you want to see the SCS traffic, you have several options, among them 2 spring to mind
1) $ sh clu/c
add loc_proc_nam
remove conn/type=noopen
2) $ mc scacp
sh vc
sh chan
among others
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-30-2010 06:14 AM
тАО09-30-2010 06:14 AM
Re: Clustering question.
I can obviously stop the alpha from booting into the cluster, or booting as a standalone by setting its VOTES=0 and EXPECTED_VOTES=3. Now there is only 1 vote available (from the booted blade) and this is not enough for the Alpha to boot.
But I'm thinking that it must have communicated with the existing cluster node in order to find out if there were enough votes.
So I am assuming that the "Membership Request" message will appear on the OPCOM of the existing node.
The point is, does this "prove" that SCS traffic will flow between the alpha and the blade. I am assuming - Yes.
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-30-2010 06:18 AM
тАО09-30-2010 06:18 AM
Re: Clustering question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-30-2010 06:22 AM
тАО09-30-2010 06:22 AM
Re: Clustering question.
But, will the "Membership Request" show up on the existing cluster nodes OPCOM?
The other question is
Will the Alpha console show anything to indicate that it is "..waiting for Votes.."
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-30-2010 06:43 AM
тАО09-30-2010 06:43 AM
Re: Clustering question.
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-30-2010 07:19 AM
тАО09-30-2010 07:19 AM
Re: Clustering question.
The Alpha will show a message akin to:
Waiting to join...
I will test and post the receiving systems messages (if any).
Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-30-2010 07:37 AM
тАО09-30-2010 07:37 AM
Re: Clustering question.
You'll get a wait for votes, too.
This is the disk data integrity and data consistency preservation wait state. Also known as the quorum hang.
I don't know off-hand if the OPCOM messages will repeat at periodic intervals; I usually don't have boxes kicking around in that state for very long, and (when I do) I'm usually looking to fix whatever was triggering that wait...
This requires VOTES and EXPECTED_VOTES to be set correctly on all hosts in the cluster, or (for some specific cluster cases where this is required) that the startup sequence be carefully established and manually followed, lest Bad Things happen.
Bad Things here includes massive disk data corruptions far before the login prompt is reached. If that prompt can be even be reached, given the data corruptions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-30-2010 10:20 PM
тАО09-30-2010 10:20 PM
Re: Clustering question.
You're probably spending more than the $20 in time looking at the networking question at the moment...
FWIW, I *think* that the "waiting to form or join a VMScluster..." message repeats but, like Hoff, I don't normally have a system in that state long enough to verify. One thing I do know is that in the days of 6.2-1H3 the cluster formation broadcasts could go across the network that I had between Bracknell and North Carolina but the normal SCS cluster comm's wouldn't. Since I'm not a network person I'm not sure what the config was.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2010 03:10 AM
тАО10-01-2010 03:10 AM
Re: Clustering question.
Will boot the Blade from a current backup of the I64 system disk.
Will also boot the Alpha from a current backup of the Alpha System Disk. The only difference will be that the Mount of the I64 system disk will be commented out of the sylogicals.com.
Alpha will have Votes=0, Expected_Votes=1, the blade will have Votes=1, Expected_Votes=1.
The alpha will either succeed in joining the cluster, indicating that the network setup is OK. In this case I can shutdown both nodes and boot correctly from the correct disks.
Or it will fail, indicating that the network setup is NOT OK. In which case, "No harm done", back to the drawing boards.
I should say, that with the VOTES and EXPECTED_VOTES set correctly, I have (almost) total confidence that there will not be an issue, (I am just being overly paranoid, having been recently bitten)
thanks
Dave.