HP-UX - serviceguard - How to change Node timeout value and reform cluster

View previous topic View next topic Go down

HP-UX - serviceguard - How to change Node timeout value and reform cluster

Post  satheesh on Thu Jun 24, 2010 2:15 am

Modifying NODE_TIMEOUT value from 2000000 to 20000000 while cluster BI_CLX1 is running

1. Take a backup of /etc/cmcluster/cmclconfig and cmclconfig.ascii
2. you should use commands to get the cluster configured and follow the MCSG Refernces as mentioned in the earlier post.

cmquerycl -v -n node1 -n node2 -C /etc/cmcluster/cmclconfig.ascii

edit the ascii file to set the cluseter name and parametres
vi /etc/cmcluster/cmclconfig.ascii

check the configuration

cmchceckconf -v -C /etc/cmcluster/cmclconfig.ascii

if no errors returned do


cmapplyconf -v -C /etc/cmcluster/cmclconfig.ascii

cmruncl -v : to start the clsuter

Find below the example and output.

NODE1@root:/etc/cmcluster> cmapplyconf -v -C bi_clx.conf
Begin cluster verification...
Checking cluster file: bi_clx.conf
Checking nodes ... Done
Checking existing configuration ... Done
Gathering storage information
Found 7 devices on node NODE1
Found 29 devices on node NODE2
Analysis of 36 devices should take approximately 6 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Found 3 volume groups on node NODE1
Found 4 volume groups on node NODE2
Analysis of 7 volume groups should take approximately 1 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Volume group /dev/lckBIvg is configured differently on node NODE1 than on node NODE2
Volume group /dev/lckBIvg is configured differently on node NODE2 than on node NODE1
Volume group /dev/vgsap is configured differently on node NODE1 than on node NODE2
Volume group /dev/vgsap is configured differently on node NODE2 than on node NODE1
Gathering network information
Beginning network probing (this may take a while)


NODE1@root:/etc/cmcluster> cmapplyconf -v -C bi_clx.conf
Begin cluster verification...
Checking cluster file: bi_clx.conf
Checking nodes ... Done
Checking existing configuration ... Done
Gathering storage information
Found 7 devices on node NODE1
Found 29 devices on node NODE2
Analysis of 36 devices should take approximately 6 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Found 3 volume groups on node NODE1
Found 4 volume groups on node NODE2
Analysis of 7 volume groups should take approximately 1 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Volume group /dev/lckBIvg is configured differently on node NODE1 than on node NODE2
Volume group /dev/lckBIvg is configured differently on node NODE2 than on node NODE1
Volume group /dev/vgsap is configured differently on node NODE1 than on node NODE2
Volume group /dev/vgsap is configured differently on node NODE2 than on node NODE1
Gathering network information
Beginning network probing (this may take a while)
Completed network probing
Cluster BI_CLX1 is an existing cluster
Modifying NODE_TIMEOUT value from 2000000 to 20000000 while cluster BI_CLX1 is running.
Cluster BI_CLX1 is an existing cluster
Checking for inconsistencies
Maximum configured packages parameter is 150.
Configuring 1 package(s).
149 package(s) can be added to this cluster.
200 access policies can be added to this cluster.
Modifying configuration on node NODE1
Modifying configuration on node NODE2
Modifying the cluster configuration for cluster BI_CLX1

Modify the cluster configuration ([y]/n)?
Marking/unmarking volume groups for use in the cluster
Unable to apply the configuration change: No such file or directory
. Check the syslog file(s) for additional information.
cmapplyconf: Unable to apply the configuration
NODE1@root:/etc/cmcluster>

satheesh

Posts : 7
Join date : 2010-06-24

View user profile

Back to top Go down

View previous topic View next topic Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum