cmapplyconf online......

[Matrah]

Hi ,
I'm running MCSG A.11.07
1)After to add a disk in a VG Cluster,Can I run cmapplyconf even if my system is running ?
or may i halt the package and then, run cmapplyconf ?
2) same question if i add a new VG in the cluster.
thanks for your help...

[melvyn burnard]

If the VG does not already exist in the cluster configuration, you need to bring down the cluster.
May I recommend you read the Managing MC/ServiceGuard Manual at:
http://docs.hp.com/hpux/ha/#ServiceGuard

this is all documented in there.
You might also want to consider taking the course on MC/ServiceGuard to help you here.

[linuxfan · Accepted solution]

Hi,

1. When you add a disk to an VG already defined in the MC-SG package, you do not need to do any reconfiguration from MC-SG perspective, you will however have to re-export and import the VG on the other node.
vgexport -v -p -s -m /tmp/vgname.map /dev/vgname
copy the map file to the other node
On the other node
ls -al /dev/vgname/group
(so that you can recreate the VG with the same minor number)
mkdir /dev/vgname
mknod /dev/vgname/group c 64 0x???000
vgimport -v -s -m /tmp/vgname.map /dev/vgname

2. When you add a new VG, you can update the the cluster ascii file and do a cmcheckconf and cmapplyconf while the cluster is running,
look at the link for things you can do on VGs

http://docs.hp.com/cgi-bin/onlinedocs.py?mpn=B3936-90045&service=hpux&path=../B3936-90045/00/00/49&title=Managing%20MC/ServiceGuard

-HTH
Ramesh

[Sanjay_6]

Hi,

If you add a disk to an existing VG which is part of the cluster, you don't have to do a cmapplyconf. The only thing required for you to do is to do a see that the VG info is consistent on the nodes where the VG will get activated. This means a vgexport and vgimport and maybe a modification of /etc/lvmpvg on the other nodes. Depends on the type of configuration you have.

When you want to add a new VG to the cluster, you will have to do a cmapplyconf. you will be genearte a ascii file for the present configuration, modify that file, add this new VG and do a "cmapplyconf". you can do this while the VG is still active.

Here is a thread for you to look at.

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B3936-90045/B3936-90045_top.html&con=/hpux/onlinedocs/B3936-90045/00/00/49-con.html&toc=/hpux/onlinedocs/B3936-90045/00/00/49-toc.html&searchterms=online%20configuration&queryid=20010924-104256

Hope this helps.

thanks

[Santosh Nair_1]

If you're adding a disk to a VG that's part of the cluster, then all you would need to do on the node which has the VG activated:

add the diskt (vgextend
vgexport -s -p -m

[Victor_5]

Here is the detail steps for your reference. For example, pv:c4t5d0, vg:vg05

Adding a PV into a VG
On the original node
1. pvcreate /dev/rdsk/c4t5d0
2. vgextend /dev/vg05 /dev/dsk/c4t5d0
3. lvcreate -L size /dev/vg05
4. newfs -F model /dev/vg05/rlvol1
5. mount /dev/vg05/lvol1 /mount_point_name
6. vgexport -pvs -m /etc/lvmconf/vg05.map /dev/vg05
7. rcp /etc/lvmconf/vg05.map node2:/etc/lvmconf

On the second node:
1. vgexport /dev/vg05
2. mkdir /dev/vg05
3. mknod /dev/vg05/group c 64 0x050000
4. vgimport -vs -m /etc/lvmconf/vg05.map /dev/vg05
5. vi the control file, update the lvol and mount point and distribute the control script to all adoptive nodes


Adding a VG to a cluster

it can be done online, it is not necessary to halt the package.

1. same steps with the above using the vgexport/vgimport pair
2. cd /etc/cmcluster
3. cmcheckconf -C CONF -p pkg1/conf -p pkg2/conf ...
4. add the combination of lvol and mount point to the package control script that controls the new VG
5. leave the cluster up
cmapplyconf -C CONF -p pkg1/conf -p pkg2/conf ...
6. skip this step if the package is down
On the node where the package is active, activate the VG in exclusive mode and mount the new lvols where necessary. When the package comes down, it must be able to deactivate the resources listed in the updated control script.

vgchange -a e vg05
mount /dev/vg05/lvol1 /vg05/mount_point_name

7. copy the control script to all adoptive nodes

[John Poff]

Hello,

You can add a volume group without bringing down the cluster. I did it here two days ago.

Adding a new VG to an existing package usually requires you to halt that package, but if you are careful you can do it without halting the package. You just need to be sure you get a chance to test the package control scripts as soon as you can after doing it.

JP

[Stephen Doud]

To add a VG to a cluster:
- create the VG on one node and vgimport it into other nodes that will activate the VG when they operate the package.

- add it to the cluster config file at the bottom

- Perform this command on an adoptive node running in the cluster to "cluster" the VG:
# vgchange -c y

- Insure the VG and lvol references are listed in the package control script on each adoptive node.

-Stephen