- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- VMS Cluster
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
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
тАО01-13-2009 02:37 AM
тАО01-13-2009 02:37 AM
If a node which was already in cluster,now made shutdown and another node with a different name and with same decnet address is tried to boot, will the node boot ?
Answer : No,it will be in hung state as connection manager will not allow it to boot (tested already).
My question is :
If at that instance,the old node which has been shutdown,is de-registered and the session control entries are flushed out ( MCR NCLflush session control naming cache entry "*" ) and re-register the new node, will the new node be added as a vaild cluster member ?
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-13-2009 02:52 AM
тАО01-13-2009 02:52 AM
Re: VMS Cluster
Have you check the value of Votes and Expected Votes..is it correct ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-13-2009 03:19 AM
тАО01-13-2009 03:19 AM
Solution>>>
If at that instance,the old node which has been shutdown,is de-registered and the session control entries are flushed out ( MCR NCLflush session control naming cache entry "*" ) and re-register the new node, will the new node be added as a vaild cluster member ?
<<<
That is a definite NO.
The combo nodename<>SCSSYSTEMID is kept in CLUSTER_AUTORISATION.DAT, and matches of one of those MUST match the other.
And SCSSYSTEMID is a direct 1:1 with the DECnet address, so...
Alas, NOT without a fresh cluster-config.
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-13-2009 04:00 AM
тАО01-13-2009 04:00 AM
Re: VMS Cluster
My suggestion would be to use a different DECnet address/SCS ID. To prevent confusion, do not change the connection between DECnet node name and DECnet address.
If there are functions that need be done by particular members of the cluster, use a logical name (system or cluster-wide) to identify which nodes should do that function.
This is far safer for long term operations.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-13-2009 08:39 AM
тАО01-13-2009 08:39 AM
Re: VMS Cluster
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-13-2009 09:20 AM
тАО01-13-2009 09:20 AM
Re: VMS Cluster
This stuff works just fine with native DECnet-Plus and you can add the node back in without issue, assuming the site is using native addressing. With DECnet-Plus using its native addressing, the DECnet host address is not tied to scssystemid in any way.
If you're using DECnet Phase IV addressing with your DECnet-Plus installation on the other hand (and as appears potentially the case, given your goal of re-using an address), then see the herd of answers here, and the manuals, and other related topics. Short answer: nope. can't do that. Either reboot the whole cluster, or pick a different scsnode/scssystemid pair and a different Phase IV address.
The obvious search (for the string scssystemid) in the PDF of the OpenVMS cluster manual shows the following (slightly reformatted for inclusion here) details on page 4-3:
----
What is the node├в s DECnet node name?
If the node is running DECnet, this prompt, the following prompt, and the SCSSYSTEMID prompt are displayed. Enter the DECnet node name or the DECnet├в Plus node synonym (for example, JUPITR). If a node synonym is not de├п┬м ned, SCSNODE can be any name from 1 to 6 alphanumeric characters in length. The name cannot include dollar signs ( $ ) or underscores ( _ ).
SCSNODE
What is the node├в s DECnet node address?
Enter the DECnet node address (for example, a valid address might be 2.211). If an address has not been assigned, enter 0 now and enter a valid address when you start DECnet (discussed later in this chapter).
For DECnet├в Plus, this question is asked when nodes are con├п┬м gured with a Phase IV compatible address. If a Phase IV compatible address is not con├п┬м gured, then the SCSSYSTEMID system parameter can be set to any value.
SCSSYSTEMID
----