02-16-2017
You don't need to destroy the cluster. First you need to remove node 5 from cluster and re-add it. Eventually it will get the id 3. Same procedure for node 6 and it will get the id 4.
---------- Post updated at 08:35 PM ---------- Previous update was at 08:33 PM ----------
Please make sure that you don't have any degraded hosts in your cluster, which means all hosts are connected to each node in the cluster.
9 More Discussions You Might Find Interesting
1. Solaris
Hi guys,
I want to add a new 'service' to Solaris 10. Does anyone have any documentation that tells how to do that?
I have gone through a bunch of stuff on the net that tells how to enable, disable services, find whats wrong with a service and so on. All conveniently skip mention of how to... (6 Replies)
Discussion started by: blowtorch
6 Replies
2. Filesystems, Disks and Memory
Hello Unix Admins:
Has any one in this distribution list implemented SVC (SAN Volume Contoller - A solution from IBM) in your environment? If you have, do you have any do's / don'ts? Anything which you like sharing would be really appreciated.
For example, my inputs:
I tried implementing... (1 Reply)
Discussion started by: kdossjojo
1 Replies
3. Solaris
I'm having these weird errors.
svc.configd: Fatal error: Backend copy failed: fails to read from /etc/svc/repository.db at offset 106496: Bad file number
svc.configd: Fatal error: unable to create "boot" backup of "/etc/svc/repository.db"
Mar 10 13:04:23 svc.startd:... (5 Replies)
Discussion started by: adelsin
5 Replies
4. Solaris
Hi,
Is it possible to have a Solaris cluster of 2 nodes at SITE-A using SVM and creating metaset using say 2 LUNs (on SAN). Then replicating these 2 LUNs to remote site SITE-B via storage based replication and then using these LUNs by importing them as a metaset on a server at SITE-B which is... (0 Replies)
Discussion started by: dn2011
0 Replies
5. Solaris
After a memory upgrade all network interfaces are misconfigued. How do i resolve this issue. Below are some out puts.thanks.
ifconfig: plumb: SIOCLIFADDIF: eg000g0:2: no such interface
# ifconfig eg1000g0:2 plumb
ifconfig: plumb: SIOCLIFADDIF: eg1000g0:2: no such interface
# ifconfig... (2 Replies)
Discussion started by: andersonedouard
2 Replies
6. Solaris
Hi all
I have a newly installed Oracle X2-4 server running Solaris 10 x86 with the latest patches.
I have one non-global zone configured running an Oracle DB instance.
After configuring IPMP failover between two NICs on the server and rebooting I am seeing the /var/adm/messages being flooded... (7 Replies)
Discussion started by: notreallyhere
7 Replies
7. Homework & Coursework Questions
Hi Experts,
I am in need of running a script from one node say node 1 via node 2.
My scheduling tool dont have access to node2 , so i need to invoke the list file from node1 but the script needs to run from node2. because the server to which i am hitting, is having access only for the node... (5 Replies)
Discussion started by: arun1377
5 Replies
8. 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
9. Solaris
Hey Admins,
I need steps to do an IP changes on 3-node VCS cluster. All IP's (public, cluster IP's, backup IP, etc.)want to change. We have a downtime scheduled. Please let me know the steps to do so.
Thanks in advance. (5 Replies)
Discussion started by: snchaudhari2
5 Replies
LEARN ABOUT HPUX
cmhaltnode
cmhaltnode(1m) cmhaltnode(1m)
NAME
cmhaltnode - halt a node in a high availability cluster
SYNOPSIS
cmhaltnode [-f] [-v] [-t] [node_name...]
DESCRIPTION
cmhaltnode causes a node to halt its cluster daemon and remove itself from the existing cluster.
To halt cluster on the node, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the cluster configu-
ration file. See access policy in cmquerycl.
When cmhaltnode is run on a node, the cluster daemon is halted and, optionally, all packages that were running on that node are moved to
other nodes if possible.
If node_name is not specified, the cluster daemon running on the local node will be halted and removed from the existing cluster.
If you issue this command while a cluster is still in the process of forming, the command will fail with the message "Unable to connect to
daemon." If this happens, wait for the cluster to form successfully, then issue the command again.
Options
cmhaltnode supports the following options:
-f Force the node to halt even if there are packages or group members running on it. The group members on the node will be
terminated. The halt scripts for all packages running on the node will be run; based on priority or dependency relation-
ships, this may affect packages on other nodes. In other words, packages on other nodes may either start or halt based on
this package halting. If the package configuration and current cluster membership permit, and if the package halt script
succeeds, the packages will be started on other nodes. Without this option, if packages are running on the given node,
the command will fail. If a package fails to halt, the node halt will also fail.
-v Verbose output will be displayed.
-t Test only. Provide an assessment of the package placement without affecting the current state of the nodes or packages.
This option validates the node's eligibility with respect to the package dependencies as well as the external dependencies
such as EMS resources, package subnets, and storage before predicting any package placement decisions. If there is a pack-
age in maintenance mode running on the nodes being halted, the package will always be halted and not failover to another
node; the report will not display an assessment for that package.
node_name...
The name of the node(s) to halt.
RETURN VALUE
cmhaltnode returns the following value:
0 Successful completion.
1 Command failed.
EXAMPLES
Halt the cluster daemon on two other nodes:
cmhaltnode node2 node3
AUTHOR
cmhaltnode was developed by HP.
SEE ALSO
cmquerycl(1m), cmhaltcl(1m), cmruncl(1m), cmrunnode(1m), cmviewcl(1m), cmeval(1m).
Requires Optional Serviceguard Software cmhaltnode(1m)