Cmruncl validating cluster lock disk unable to execute command remotely Chat de sexo gratis
Here I will describe the configuration procedure of a basic two node HP Serviceguard Cluster on HP-Unix. There is a handful of discussion on these topics on internet. I am not going to discuss any theoretical concept like why someone will use a cluster or what actually a single point of failure is etc etc.Use the following commands to create the required group file on 2nd node and import the lock VG using the map file that was transferred from the first node.Minor number of a VG must be same on all the cluster nodes.Done Gathering storage information Found 23 devices on node node01 Found 23 devices on node node02 Analysis of 46 devices should take approximately 5 seconds 0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100% Found 2 volume groups on node node01 Found 2 volume groups on node node02 Analysis of 4 volume groups should take approximately 1 seconds 0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100% Note: Disks were discovered which are not in use by either LVM or Vx VM.Use pvcreate(1M) to initialize a disk for LVM or, use vxdiskadm(1M) to initialize a disk for Vx VM.
/dev/dsk/c4t0d5 # rcp /etc/lvmconf/node02:/etc/lvmconf/ If you don’t deactivate before exporting the VG, then you will get a warning which you can ignore.
Create the group file for the volume group: The minor number (0x010000) of the group file must be unique for all VG.
To check the minor number of any existing group file use ‘ls -l /dev/*/group’. This VG will be used as lock VG: # vgcreate -s 32 vglock /dev/dsk/c4t0d5 Increased the number of physical extents per physical volume to 6399.
Refer to the comments in the cluster configuration ascii file or Serviceguard manual for more information on this parameter. Please make sure that the proper security access is configured on node node01 through either file-based access (pre-A.11.16 version) or role-based access (version A.11.16 or higher) and/or that the host name lookup on node node01 resolves the IP address correctly.
cmapplyconf: Failed to gather configuration information As you see from the above output, the command is failed to run successfully. It says, there are some problems in name resolution.
Refer to the comments in the cluster configuration ascii file or Serviceguard manual for more information on this parameter. Use the cmapplyconf command to apply the configuration.# cmapplyconf -v -C crmcluster.ascii Checking cluster file: crmcluster.ascii Note : a NODE_TIMEOUT value of 2000000 was found in line 127.