10 More Discussions You Might Find Interesting
1. HP-UX
Hi,
We have HP UX service guard cluster on OS 11.23. Recently 40+ LUNs presented to both nodes by SAN team but I was asked to mount them on only one node. I created required VGs/LVs, created VxFS and mounted all of them and they are working fine. Now client requested those FS on 2nd node as... (4 Replies)
Discussion started by: prvnrk
4 Replies
2. AIX
Setting up HACMP 6.1 on a two node cluster. The other node works fine and can start properly on STABLE state (VGs varied, FS mounted, Service IP aliased). However, the other node is always stuck on ST_JOINING state. Its taking forever and you can't stop the cluster as well or recover from script... (2 Replies)
Discussion started by: depam
2 Replies
3. UNIX for Advanced & Expert Users
We have two node cluster with OS disk mirrored under SVM. There is slight disk problem on one of the mirror disk causing cluster to panic.
Failure of one mirror disk causing VCS to panic the node. Why VCS is not able to write /var filesystem, as one of the disk is healthy.
... (1 Reply)
Discussion started by: amlanroy
1 Replies
4. Solaris
I have one disk that is reporting I/O errors but the same LUN mounted on a different node is able to access it without issue, is there a way to identify which HBA is being used for the LUN without swapping each out at a time? (4 Replies)
Discussion started by: thmnetwork
4 Replies
5. Solaris
Dear all,
I have created a shared metaset(500gb) having 3 hosts in which 2 hosts are in cluster and 1 is non cluster. I have taken the ownership in cluster node from non cluster node but the problem is i am unable to mount the file system it is giving error "/dev/md/eccdb-ds/d100 or /eccdb-ds... (1 Reply)
Discussion started by: spandhan
1 Replies
6. High Performance Computing
hi,
i am trying to setup a 2 node cluster environment. following is what i have;
1. 2 x sun ultra60 - 450MHz procs, 1GB RAM, 9GB HDD, solaris 10
2. 2 x HBA cards
3. 2 x Connection leads to connect ultra60 with D1000
4. 1 x D1000 storage box.
5. 3 x 9GB HDD + 2 x 36GB HDD
first of all,... (1 Reply)
Discussion started by: solman17
1 Replies
7. High Performance Computing
All-
I am new to these forums so please excuse me if this post is in the wrong place.
I had a node crash in a 4 node cluster and mgmt has determined this node will not be part of the cluster when rebuilt. I am researching how to remove it from the cluster information on the other 3 nodes and... (2 Replies)
Discussion started by: bluescreen
2 Replies
8. HP-UX
Need help guys!
when running cmrunnode batch i'm getting this error
cmrunnode : Waiting for cluster to... (1 Reply)
Discussion started by: Tris
1 Replies
9. Solaris
I m not able to copy the text present on the tree's node to terminal or other text editor in solaris. I m using <Shift><control> C and V comaand for the same but the text is not being copied and pasted on the text pad or the terminal window.
While the same is possible in windows OS using ctrl+c... (3 Replies)
Discussion started by: friendanoop
3 Replies
10. Shell Programming and Scripting
Hello,
Under ksh I have to run a script on one of the nodes of a Solaris 8 cluster which at some time must execute a command on the alternate node:
# rsh <name> "command"
I have to implement this script on all the clusters of my company (a lot of...).
Fortunately, the names of the two nodes... (11 Replies)
Discussion started by: heartwork
11 Replies
cmdeleteconf(1m) cmdeleteconf(1m)
NAME
cmdeleteconf - Delete either the cluster or the package configuration
SYNOPSIS
cmdeleteconf [-f] [-v] [-c cluster_name] [[-p package_name]...]
DESCRIPTION
cmdeleteconf deletes either the entire cluster configuration, including all its packages, or only the specified package configuration. If
neither cluster_name nor package_name is specified, cmdeleteconf will delete the local cluster's configuration and all its packages. If
the local node's cluster configuration is outdated, cmdeleteconf without any argument will only delete the local node's configuration. If
only the package_name is specified, the configuration of package_name in the local cluster is deleted. If both cluster_name and pack-
age_name are specified, the package must be configured in the cluster_name, and only the package package_name will be deleted. cmdelete-
conf with only cluster_name specified will delete the entire cluster configuration on all the nodes in the cluster, regardless of the con-
figuration version. The local cluster is the cluster that the node running the cmdeleteconf command belongs to.
Only a superuser, whose effective user ID is zero (see id(1) and su(1)), can delete the configuration.
To delete the cluster configuration, halt the cluster first. To delete a package configuration you must halt the package first, but you do
not need to halt the cluster (it may remain up or be brought down). To delete the package VxVM-CVM-pkg (HP-UX only), you must first delete
all packages with STORAGE_GROUP defined.
While deleting the cluster, if any of the cluster nodes are powered down, the user can choose to continue deleting the configuration. In
this case, the cluster configuration on the down node will remain in place and, therefore, be out of sync with the rest of the cluster. If
the powered-down node ever comes up, the user should execute the cmdeleteconf command with no argument on that node to clean up the config-
uration before doing any other Serviceguard command.
Options
cmdeleteconf supports the following options:
-f Force the deletion of either the cluster configuration or the package configuration.
-v Verbose output will be displayed.
-c cluster_name
Name of the cluster to delete. The cluster must be halted already, if intending to delete the cluster.
-p package_name
Name of an existing package to delete from the cluster. The package must be halted already. There should not be any
packages in the cluster with STORAGE_GROUP defined before having a package_name of VxVM-CVM-pkg (HP-UX only).
RETURN VALUE
Upon completion, cmdeleteconf returns one of the following values:
0 Successful completion.
1 Command failed.
EXAMPLES
The high availability environment contains the cluster, clusterA , and a package, pkg1.
To delete package pkg1 in clusterA, do the following:
cmdeleteconf -f -c clusterA -p pkg1
To delete the cluster clusterA and all its packages, do the following:
cmdeleteconf -f -c clusterA
AUTHOR
cmdeleteconf was developed by HP.
SEE ALSO
cmcheckconf(1m), cmapplyconf(1m), cmgetconf(1m), cmmakepkg(1m), cmquerycl(1m).
Requires Optional Serviceguard Software cmdeleteconf(1m)
