Adding new LV to cluster

[joseph51]

Hi I have created and added a new LV to the cluster .means added the entry in configuration file . But After that is it required to initiate cmcheck conf and cmapply conf .
This is A.11.19.00 version of servie guard and its a modular package ,

Please let me know for adding a new vg / lv in the cluster any cmcheckconf and cmapplyconf need to initiate ,both in the case of legacy and modular package ,
Also share the command format in the case of both packages

[g3jza]

Hello,

after you added new LV to the active system (the one which has the shared VG active), then you need to distribute the map file to other nodes in the cluster.
#vgexport -v -p -s -m /tmp/vgname.map vgname

Then copy the map file to other nodes and correctly import the map file:

on the other nodes:
#vgexport vgname
#mkdir /dev/vgname
#mknod /dev/vgname/group c 64 0x0Y0000 where 'Y' should be the same minor number as in the node, which has the VG now activated.
#vgimport -v -s -m /path_to_your_mapfile vgname
(might even use -N option to import agile DSFs)

After all this is done, then get the actual configuration for the package:
#cmgetconf -p package_name > package.ascii

Edit the package.ascii:
#vi package.ascii
and add the new FS/LV to the config.

Check that the new config is syntactically correct:
#cmcheckconf -P package.ascii

Apply the new config:
#cmapplyconf -P package.ascii

The addition of new LV is online operation in 11.19, so there's no need to halt the package. (as far as I know for the modular package, legacy might be different, not sure about this)

Don't forget to create a mount point for the new LV on other nodes....

[joseph51]

Yes . I have done export and import . But only doubt whetehr to initiate cmcheck and cmapply . look the files below

root@host1:/etc/cmcluster : ls -l cluster.ascii
-rw-r----- 1 root sys 19541 Jun 25 2010 cluster.ascii
root@host1:/etc/cmcluster :

root@host1:/etc/cmcluster/SID : ls -l dbciSID.conf
-rwx------ 1 root sys 30004 Jun 8 18:42 dbciSID.conf
root@host1:/etc/cmcluster/SID :

and the entry I added is like give below

fs_name /dev/vgsapSID/lvusrsapput
fs_directory /usr/sap/put
fs_type "vxfs"
fs_mount_opt "-o delaylog,largefiles"
fs_umount_opt ""
fs_fsck_opt ""

This seems like Modular package right . Do I need to copy this to other partner nodes ..?

is this the same command cmcheckconf -P dbciSID.conf
and cmapplyconf -P dbciSID.conf

I need to issue ..?

Please clarify

[g3jza · Accepted solution]

Yes that's a modular package, you can tell the difference by having a look at the parameters/attributes. If it's in lower case, then it's a modular package, older legacy packages were using upper case characters.

So in your case:
fs_name /dev/vgsapSID/lvusrsapput
fs_directory /usr/sap/put
....it's a modular package

Also at the beginning of the modular package configuration file should be the listing of modules being used in that config....

You don't need to copy the dbciSID.conf from one node to the others, just do the cmcheckconf & cmapplyconf commands from the node, which has updated dbciSID.conf:

So:

cmcheckconf -P dbciSID.conf
and cmapplyconf -P dbciSID.conf
is the way to go....

[joseph51]

Thank you very much for the response ,
Let me ask one more thing , In the case of legacy package , to add new lv or vg to package

1 need to stop and start package ..?

2) need to copy pkg.conf file to other nodes ..?

3) need to issue cmcheckconf and cmapplyconf ...?

[g3jza]

1) I'm not sure about the legacy packages, so please read the user guide for SG 11.19, it contains info about which operations are online/offline:

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&taskId=101&prodClassId=10008&contentType=SupportManual&docIndexId=64255&prodTypeId=18964&prodSeriesId=4162060

2) package configuration file needs not to be edited, only the package control files (pkg.cntl), which needs to be edited and then distributed to other nodes in the cluster.

3) No need to do the cmcheckconf & cmapplyconf when adding the LV, as only the package control script (run & halt script) is edited manually...