topic Re: Cluster Removal in VMS7.2-1 in Operating System - OpenVMS

Cluster Removal in VMS7.2-1

Learn_1 — Sun, 09 Nov 2003 05:30:18 GMT

I have a system Alpha 4100A running vms7.2-1 in cluster mode.the system and quorum disk are on the shared storage (RA3000).one of the member is no more running and only one system is running.now i want to move the system disk on the local storage and want to remove cluster configuration so that the system keep functiong from local disk (as i will be moving system disk to local storage)without the shared storage as i will be using this shared storage with other system.
i will have to remove the mount opoints that are configured to mount data disks of RA3000 at startup.
how can i accomplish all this smoothly.
Thanks.

Re: Cluster Removal in VMS7.2-1

Martin P.J. Zinser — Sun, 09 Nov 2003 11:42:29 GMT

Well, the easiest solution is to just lower the quorum for the cluster to 1 giving your node 1 vote. Booting form the local disk is just achieved by setting the boot device in the console mode (after you did prepare a local disk with OpenVMS on it ;-)

Re: Cluster Removal in VMS7.2-1

Mike Naime — Sun, 09 Nov 2003 11:56:04 GMT

What Martin replied with will indeed work, you wind up with one cluster member.

If you really want to uncluster thsi node
When you move the system disk from the shared storage to the local disk. You will need to Set VAXCLUSTER = 0 in your modparams.dat file. Run AUTOGEN to implement this change and then re-boot your system. You should now be unclustered on this node.

Note #1: you may want to uncluster the other node as well.

Note#2: Clustering the nodes back together will require aditional re-boots.

Re: Cluster Removal in VMS7.2-1

Åge Rønning — Sun, 09 Nov 2003 12:09:59 GMT

In addition to setting VAXCLUSTER = 0, it's also recomended to remove (if they exist) NISCS_LOAD_PEA0, NISCS_CONV_BOOT, MSCP_LOAD, TMSCP_LOAD from MODPARAMS.DAT.
DISK_QUORUM could also be removed.

Re: Cluster Removal in VMS7.2-1

Martin P.J. Zinser — Sun, 09 Nov 2003 12:18:55 GMT

Yup, my approach is minimalistic.

Advantages:
*Easy ;-)
*You can re-establish the cluster at any time

Disadvantages:
*There is a short delay during boot while the system tries to figure out if there is already an exisiting cluster it could join.
*You continue to need the cluster license on this node.

Re: Cluster Removal in VMS7.2-1

Veli Körkkö — Mon, 10 Nov 2003 00:37:41 GMT

There are additional gotchas too. Some software, e.q. ADVANCED SERVER forces cluster alias setup and also TCPIP stack may have some of services configured in the "cluster common".

See e.q. $TCPIP SHOW CONF ENABLE SERVICE
and $TCPIP SHOW CONF ENABLE SERVICE /COMMON

And on a cluster some licenses have been bound to actual node name, on a non-clustered node this is not needed.

So, going from multinode cluster to a single system cluster is sort of sure approach. The approach of really unclustering the system offers some benefits like maybe 1 minute quicker boot but you may have some additional unexpected work ahead.

_veli

Re: Cluster Removal in VMS7.2-1

Willem Grooters — Mon, 10 Nov 2003 02:56:23 GMT

Martin,
just a small question:

you said:

*You continue to need the cluster license on this node.

what would happen if you removed the license? My idea would be that all custer-related components would fail to start but you would be able to run the rest of VMS - standalone of course. But am I wrong there?

Re: Cluster Removal in VMS7.2-1

Lokesh_2 — Mon, 10 Nov 2003 06:45:11 GMT

in additions can use sys$manager:cluster_config.com ( cluster_config_lan.com ) to remove the root of another node.

For check the startup files to remove the mount points of data disks

Best regards,
Lokesh

Re: Cluster Removal in VMS7.2-1

Learn_1 — Tue, 11 Nov 2003 06:14:11 GMT

Thanks Guys,
According to your suggestions i ahve modified the the modparams.dat.infactthe original system disk was on the shared storage and the image backup of the system disk was on the local storage.i have disconnected the shared storage and after booting from OS cd and mounting the local system disk modified the MODparams.dat file.the values that i have modified are as under.
1.remarked NISCS_LOAD_PEA0=1
2.VAXCLUSTER=0
3.remarked disk_quorum="$1$dka301" (this was the system disk on the shared storage).
4.remarked QDSKVOTES
5.REMARKED INTERCONNECT="N1"
6.Remarked MSCP_LOAd=1
7.Remarked MSCP_SERVE_ALL=2
8.remarked MC_SERVICES_P2=1
9.Remarked interconnect ="NIMC"

after doing this when i do
RUN SYS$SYSTEM:SYSMAN
SYSMAN>DO @SYS$UPDATE:AUTOGEN GETDATA SETPARAMS
The system just keep prompting but no result.
similarly when i boot from the local disk the system stops at
"AITOMATIC DISK SERVING"

What can i do to configure this node so that this node (this is the only node in the cluster configuration as other node is already down)boot from local system disk.
how can cluster_configure.com can help to resolve this issue.

Your urgent reply innthis regard will help to resolve this issue asap.

Re: Cluster Removal in VMS7.2-1

Learn_1 — Tue, 11 Nov 2003 06:23:51 GMT

A bit clarification.
if i boot the system from local system disk it just stops at
"MSCPLOAD-I-CONFIGSCAN,Enabled automatic disk serving.
The system just stops at this point and does not go any further.

Re: Cluster Removal in VMS7.2-1

Lokesh_2 — Tue, 11 Nov 2003 06:48:12 GMT

Hi Anwar,

Check the votes and expected votes parameters. Do a conversational boot and set them to 1 .

SYSBOOT> show expected_votes ! note current value
SYSBOOT> show votes ! note current value
SYSBOOT> set votes 1
SYSBOOT> set expected_votes 1
SYSBOOT> continue

Best regards,
Lokesh

Re: Cluster Removal in VMS7.2-1

Learn_1 — Tue, 11 Nov 2003 08:06:18 GMT

Hi lokesh,
i am attaching the modparams file contents following so that you may have a good look at the file to suggest.
==================================
this is the file that is located on the shared storage system disk
====================================
LPHA-4100>ty JUP_DISK01:[JUPITER.USER.IF.VMS]modparams.dat
! SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT
! Created during installation of OpenVMS AXP V6.2 28-FEB-1996 21:54:27.95
!
SCSNODE="HACKLE"
SCSSYSTEMID=1042
!
! End of SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT
! Created during installation of OpenVMS AXP V6.2 28-FEB-1996 21:54:27.95
! CLUSTER_CONFIG appending for ADD operation on 28-FEB-1996 21:59:25.49
VOTES=1
AGEN$INCLUDE_PARAMS SYS$MANAGER:AGEN$NEW_NODE_DEFAULTS.DAT
SCSNODE="HACKLE"
SCSSYSTEMID=1042
NISCS_LOAD_PEA0=1
VAXCLUSTER=2
DISK_QUORUM="DKB100"
QDSKVOTES=1
MSCP_LOAD=1
MSCP_SERVE_ALL=2
ALLOCLASS=1
INTERCONNECT="NI"
BOOTNODE="NO"
Security_policy="71"
!
! ADDED BY IF ON 28/05/98
MIN_NPAGEDYN = 16400000
MIN_CTLPAGES = 150
MIN_CHANNELCNT = 1024
KSTACKPAGES = 3
GH_EXEC_CODE =2048
GH_EXEC_DATA =2048
!
! EDITED BY IF 18/06/98 as per KSCL recommendation (Audit Report)
Max_PQL_DWSEXTENT = 16384
Max_PQL_MWSEXTENT = 16384

=====================================
this is the modparams file that is located in the local system disk
============LPHA-4100>ty $4$DKA100:[SYS0.SYSEXE]MODPARAMS.DAT;6
! SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT
! Created during installation of OpenVMS AXP V7.2-1 9-NOV-1999 18:37:35.44
!
SCSNODE="JACK"
SCSSYSTEMID=1044
!
! End of SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT
! Created during installation of OpenVMS AXP V7.2-1 9-NOV-1999 18:37:35.44
! CLUSTER_CONFIG appending for ADD operation on 10-NOV-1999 11:25:21.04
VOTES=1
AGEN$INCLUDE_PARAMS SYS$MANAGER:AGEN$NEW_NODE_DEFAULTS.DAT
SCSNODE="JACK"
SCSSYSTEMID=1044
NISCS_LOAD_PEA0=1
VAXCLUSTER=2
DISK_QUORUM="$1$DKA301"
QDSKVOTES=1
INTERCONNECT="NI"
BOOTNODE="N"
DEVICE_NAMING=1
! CLUSTER_CONFIG end
! CLUSTER_CONFIG appending for CHANGE operation on 10-NOV-1999 13:35:27.95
NISCS_LOAD_PEA0=1
INTERCONNECT="NI"
! CLUSTER_CONFIG end
! CLUSTER_CONFIG appending for CHANGE operation on 10-NOV-1999 13:37:26.10
!ALLOCLASS=0
DEVICE_NAMING=1
! CLUSTER_CONFIG end
! CLUSTER_CONFIG appending for CHANGE operation on 10-NOV-1999 13:38:57.26
!ALLOCLASS=1
DEVICE_NAMING=1
! CLUSTER_CONFIG end
! CLUSTER_CONFIG appending for CHANGE operation on 10-NOV-1999 14:05:00.92
!ALLOCLASS=0
DEVICE_NAMING=1
! CLUSTER_CONFIG end
! CLUSTER_CONFIG appending for CHANGE operation on 10-NOV-1999 14:16:24.50
!ALLOCLASS=1
DEVICE_NAMING=1
! CLUSTER_CONFIG end
! CLUSTER_CONFIG appending for CHANGE operation on 10-NOV-1999 18:07:05.64
!ALLOCLASS=1
DEVICE_NAMING=1
! CLUSTER_CONFIG end
! CLUSTER_CONFIG appending for CHANGE operation on 10-NOV-1999 18:29:56.19
!ALLOCLASS=0
DEVICE_NAMING=1
! CLUSTER_CONFIG end
! CLUSTER_CONFIG appending for CHANGE operation on 11-NOV-1999 10:30:53.14
ALLOCLASS=2
DEVICE_NAMING=1
! CLUSTER_CONFIG end
! Added by IF on 13-11-1999
Security_Policy = 71
MIN_NPAGEDYN = 17000000
MIN_CHANNELCNT = 1024
MIN_CTLPAGES = 150
KSTACKPAGES = 3
MIN_VIRTUALPAGECNT = 1500000
MAX_PQL_DWSEXTENT = 16384
MAX_PQL_MWSEXTENT = 16384
MIN_VIRTUALPAGECNT =71
LOAD_SYS_IMAGES = 7 !required by POSIX
MIN_MAXPROCESSCNT = 30 !required by POSIX
ADD_GBLPAGES = 5650 !required by POSIX
ADD_GBLSECTIONS = 300 !required by decnet plus
ADD_NPAGEDYN = 25600 !required by POSIX
! CLUSTER_CONFIG appending for CHANGE operation on 30-NOV-1999 13:26:32.22
ALLOCLASS=2
DEVICE_NAMING=1
! CLUSTER_CONFIG end
! CLUSTER_CONFIG appending for CHANGE operation on 30-NOV-1999 13:28:08.07
MSCP_LOAD=1
MSCP_SERVE_ALL=2
ALLOCLASS=2
DEVICE_NAMING=1
! CLUSTER_CONFIG end
! CLUSTER_CONFIG appending for CHANGE operation on 19-APR-2001 17:51:23.67
!MC_SERVICES_P2=1
!INTERCONNECT="NIMC"
! CLUSTER_CONFIG end
! CLUSTER_CONFIG appending for CHANGE operation on 24-APR-2001 23:44:12.63
MC_SERVICES_P2=1
INTERCONNECT="NIMC"
! CLUSTER_CONFIG end
======================

in the above stated 2nd file
DISK_QUORUM="$1$DKA301"
whereas this disk is located in the shared storage so do i need to change this disk to dkb300 which will be the location after moving the shared storage system disk to local storage.

Thanks.

Re: Cluster Removal in VMS7.2-1

Lokesh_2 — Tue, 11 Nov 2003 08:56:22 GMT

Hi Anwar,

First of all the MODPARAMS is used by AUTOGEN to set system parameters. It is not necessary that the values shown in MODPARAMS.DAT is also defined in system paramter file VAXVMSSYS.PAR or ALPHAVMSSYS.PAR. So, my suggestion is to forget about modparams.dat at the moment. First of all , try to boot the system from local system disk. This you can achieve by doing conversational boot ( convesational boot flags are hardware specific, if you are using alpha, then you can do it by B -fl 0,1 ) . Then at the SYSBOOT> prompt, set the appropriate system parameters. I would recommend to set the following system parameters at the sysboot prompt:

SET SCSNODE "JACK"
SET SCSSYSTEMID 1044
SET VOTES 1
SET EXPECTED_VOTES 1
SET VAXCLUSTER 0
SET DISK_QUORUM ""
SET QDSKVOTES 0

after that boot the system with continue command at sysboot prompt:

SYSBOOT> CONTINUE

I guess the system will be rebooted then. Once your system get booted with the local disk, then you can set the same parameters in MODPARAMS.DAT and run autogen.

Let me know you findings,
Best regards,
Lokesh

Re: Cluster Removal in VMS7.2-1

Learn_1 — Tue, 11 Nov 2003 09:41:24 GMT

Hi lokesh
with your points i did manage to boot from local system disk and logged in accordingly.but when i try to run procedure it states that the JUP_disk01[users.billrun..]does not exist.this point to the shared storage system disk which is now no more there as i have disconnected the shared storage disk from this server.now how can i resolve this problem.
if i image backup this user data disk on a local system disk and reconfigure so that it goes to local disk for user data files.
need ur opinion in this regard.

Re: Cluster Removal in VMS7.2-1

Lokesh_2 — Tue, 11 Nov 2003 09:56:58 GMT

Hi Anwar,

By booting successfully from local system disk, you have just cleared the first step. Now, you have many more hurdles in front of you ( like you are facing right now ) . You have sort each issue one by one. I will suggest, first you rectify your modparams.dat, then run full autogen. Once you are confident that you can boot your system from local system disk, ( without using assistance of conversational boot ) then only proceed step by step with you problems.

Best regards,
Lokesh Jain

Re: Cluster Removal in VMS7.2-1

Lokesh_2 — Tue, 11 Nov 2003 10:02:44 GMT

one more thing, while modifying modparams.dat, use appropriate values for system parameters . You can get cluster related system parameters with the following command:

$MC SYSGEM SHO /CLUSTER

This command will list all the cluster related parameters. Go through the help of each parameter and set them accordingly.

I believe, most important command in VMS is HELP command.

Best regards,
Lokesh

Re: Cluster Removal in VMS7.2-1

Learn_1 — Tue, 11 Nov 2003 10:47:39 GMT

lokesh,
if you check the modparams file,which parameters you think that i need to modify.
what if i keep using conversational boot as i just need to use x25 link that is configured on this server and i will be moving this x25 link to GS80 server shortly.is there any problem if i keep using this conversational boot.right now i am taking image backup of user disk from shared disk to local disk.after this i will reconfigure the login user profile to redirect it to go to local disk for userdata instead to shared disk.
Do check the modparams file i have pasted in my last reply to suggest which parameters do i need to modify.so parameters are suggested in the the replies by other guys.
Hi other Guys if anyone there do suggest modifications keeping in view my recent replies.
Thanks.

Re: Cluster Removal in VMS7.2-1

Lokesh_2 — Tue, 11 Nov 2003 11:09:09 GMT

Hi Anwar,

If you are using this system for temporary basis, then no need of changing modparams. As I said earlier too, that modparams is used only by AUTOGEN. So, if you do not run autogen, then whatever the modparams be, is doesn't matter.

Also, the system parameter which you have set during conversational boot are permanent. So, no need of using conversational boot procedure now. You can boot you system straight off.

As you said, right now you are copying user data just to enable you X 25 link, then I think you go ahead with that ( as this is only temporary arrangement !! why to bother much :) )

Best regards,
Lokesh

Re: Cluster Removal in VMS7.2-1

Learn_1 — Tue, 11 Nov 2003 11:44:59 GMT

going through the backup procedure.will let u know of problens(hope that no more problem exist).
thanks for the help.your points are due.

Re: Cluster Removal in VMS7.2-1

Learn_1 — Wed, 12 Nov 2003 22:58:09 GMT

Hi lokesh,
with ur suggested procedure i am finally able to unconfigure the cluster.after this i did transfer userdata disk from shared to local disk,modifying user device parameters and now system is up and running.
Thanks to everone for contribution.points for everyone.