MCSG in stand Alone

[Matrah]

Hi all ,
I'm running MSCG in 2 nodes.there is 1 pkg in each node.PkgA running in the node 1 and PkgB running in the node 2.
When node1 is out of order,PkgA switch in node2,same thing for node2..
How can i run in stand alone PkgA in node 1 and Pkg2 in node 2.

Thanks for your help.

[linuxfan]

Hi,

When you run stand-alone, do you mean you want to prevent package switchover(temporarily or permanently)? or do you want to run your applications which are configured in MC-SG to run in stand-alone mode (without MC-SG)?

If you are trying to do the latter, run your application in stand-alone without MC-SG,

1. active your VGs exlusively on the node
# vgchange -a e VGname
2. mount all your filesystems applicable to your application
3. Activate your relocatable package ip address
ifconfig lan0:1 ip.address.of.packacage netmask 255.255.xxx.0
(choose the right netmask)
4. now you should be able to bring up your application

Do the same steps for the other package on the other node.

-HTH
Ramesh

[Sridhar Bhaskarla]

Matrah,

You could have configured two nodes seperately as two single-node clusters. Even you can do it now.

To run them as standalone packages without auto failover

Edit the package configuration file and change the configuraition as follows

FAILOVER_POLICY MANUAL

And do a cmapplyconf -P package_conf. This way the package will not failover automatically and you have control over it.

I hope I understood your question.

-Sridhar

[A. Clay Stephenson · Accepted solution]

Hi:

If I understand your question and do not want to run as a cluster you need to do a few things.

1) Halt the cluster using cmhaltcl.
2) Edit /etc/rc.config.d/cmcluster and set AUTOSTART_CMCLD=0 so that the cluster does not try to start on reboot.
3) On each volume group that was part of the cluster do a vgchange -c n /dev/vgxx.
4) You then execute the commands that the package scripts would do automatically except that the vgchange -a e /dev/vgxx should be vgchange -a y /dev/vgxx. Other commands might be start the database, etc.

5) Because you no longer have a package IP address you need to either let any client connect to the stationary IP address or change the stationary IP address to that of the package.

--------------------------------------

If you simply want to run the packages manually while still in ServiceGuard that is much easier.

Do a cmmodpkg to disable package switching so that Pkga can only run on Node1.

cmmodpkg -d -v Pkga
then run the package on Node1
cmrunpkg -n Node1 -v Pkga

Man cmhaltcl, cmrunpkg, cmmodpkg, cmhaltpkg, cmruncl for details.

Clay

[Santosh Nair_1]

In addition to Clay's comments, if you want to maintain the same IP addresses for the packages, you could use ifconfig lan[n]:[i] $IPADDR to activate the IP address on the each node (one per package). The [n] is the lan card instance and the [i] is the IP index number.

-Santosh

[Stephen Doud]

In order to activate a "clustered" volume group using
# vgchange -a e

.. the node must be running cmlvmd - so the node must be running
ServiceGuard.

------

Note: With the exception of the SERVICE_* features of a package
control script, the script can be exploited to bring up the package
application manually.

Do the following:
Because ServiceGuard won't be expecting any SERVICE_NAME,
SERVICE_CMD or SERVICE_RESTART feedback from the package control
script, comment out the following lines at the bottom of the package
control script:

# start_services
- and -
# halt_services


INSURE THE PACKAGE IS NOT BEING OPERATED BY SERVICEGUARD:
$ cmhaltpkg pkg1

To start the application:

$ /etc/cmcluster/pkg1/control.sh start
The SERVICE_CMDs must be run manually.

To stop the application:

The SERVICE_CMDs must be halted manually.
$ /etc/cmcluster/pkg1/control.sh stop


=Stephen

[Sanjay_6]

Hi Matrah,

There are a lot many ways to do what you want. I think you want to run a package on each node and they should not failover to the other node.

One way to do that is to disable the switching for the package.

cmmodpkg -d -v package_name

The other way would be remove the alternate node name from the package configuration script. This will be the 2nd entry for NODE_NAME in the package ascii script.. If the package is already configured in the cluster config, and you do any modification in the package conf, you have to do a "cmapplyconf".

The third way would be to start the package manually. For this you have to proceed like this.
Activate the VG --> Start the package --> disable the package switching (if configured for multiple nodes).

Hope this helps.

thanks