Modify cntl file:
1.) Make a copy of the control file
2.) Edit and make changes to this copy.
3.) Keep another backup copy.
Stop the package
4.) Copy the new control file on all nodes where the package will get activated.
5.) Start the package and test the operations of the package on all nodes.
On the primary node :
———————–
1.#pvcreate <new row diskfiel>
2.#vgextend vgname <new block device file>
3.export the map file in preview mode
#vgexport -v -p -s -m /tmp/vgname.map <vgname>
4.copy the map file to the adoptive node
On the adoptive node.
——————–
1.Note the minor number of the VG which ur goung to remove.
#ll /dev/vgname/group
2. remove the VG from the node.
#vgexport <vgname>
3.create the VG directory and group file
#mkdir /dev/vgname
#mknod /dev/vgname/group c 64 <minor number, eg 0×090000 in the below eg. “get it from the ll command” >
eg:
# ll /dev/vg10/group
crw-r–r– 1 root sys 64 0×090000 Mar 14 23:21 /dev/vg99/group
4.import the volume group.
#vgimport -v -s -m /tmp/vgname.map vgname
5. Activate the vgname in read only mode to verify and then deactivate it once is ie verified.
#vgchange -a r vgname
#vgdisplay -v vgname # u can see the new disk
#vgchange -a n vgname
vgchange -c n /dev/vg & then vgchange -a y /dev/vg
vgchange -c y /dev/vg & then vgchange -a e /dev/vg
0) cmhaltcl
1 ) cd /etc/cmcluster
2) cmgetconf CLS.ASC
3) edit CLS.ASC and locate:
FIRST_CLUSTER_LOCK_VG
and in each node section:
FIRST_CLUSTER_LOCK_PV
4) identify a new VG that will remain under cluster control after the SAN migration has completed
5) identify a PV in that VG (in /etc/lvmtab)
6) edit the CLS.ASC file, with the new lock VG reference and for each node, lock PV reference.
7) cmcheckconf -C CLS.ASC
8) If step 7 succeeds, halt the cluster and apply the configuration change
9) cmapplyconf -C CLS.ASC
# cmmakepkg -p /etc/cmcluster/TU4/dbTU4.conf
Package template is created.
This file must be edited before it can be used.
Edit conf file Enter package Name. Enter Node name. Change Auto_run= yes. Enter package cntl file path name in run_script. (ex.
#cmmakepkg -s /etc/cmcluster/TU4/dbTU4.cntl
Package control script is created.
This file must be edited before it can be used.
Edit cntl file Enter Volume group Name (ex:-vg01,vg02 ) and file system name which are created in lvol.Enter the IP of package and subnet mask.
#cmcheckconf -v -P package.conf
#cmapplyconf -v -P package.conf
#cmrunpkg -v [-n node] package_name
Possible solution:
check that /etc/hosts is up-to-date and:
mv /etc/resolv.conf /etc/resolv.conf.orig
rmsf /dev/vgcm3/homjun and /dev/vgcm3/rhomjun
gunzip /tmp/EMCPower.HPUX.PI.5.1.0.GA.b160.tar.gz
swinstall -x autoreboot=true -x mount_all_filesystems=false -s /tmp/EMCPower.HPUX.PI.5.1.0.GA.b160.tar EMCpower