Sponsored Content
Full Discussion: Sun Cluster question
Operating Systems Solaris Sun Cluster question Post 302790633 by abohmeed on Saturday 6th of April 2013 05:13:04 AM
Old 04-06-2013
Thanks hergp
Yes we do have a shared storage among both nodes containing the data files. Did this "maintenance window" implies that we break and rebuild the whole cluster?
 

9 More Discussions You Might Find Interesting

1. High Performance Computing

SUN Cluster Vs Veritas Cluster

Dear All, Can anyone explain about Pros and Cons of SUN and Veritas Cluster ? Any comparison chart is highly appreciated. Regards, RAA (4 Replies)
Discussion started by: RAA
4 Replies

2. Solaris

Sun cluster setup question

I have 2 sun blade 1500 with Qlogic card and T3 storedge. I can connect to the T3 storedge through my boxes. Now I want to setup cluster, in order to setup I need to buy a Fiber Channel switch. Can I buy any fiber channel switch? Can you recommend some old switches? I can get it from ebay. ... (4 Replies)
Discussion started by: mokkan
4 Replies

3. Solaris

Sun Cluster

Hi All I hav working knowledge on solarois 10. Could anyone suggest me any doc or material for learning SUN cluster from scratch. Anything from basic level . Thanks in advance!! (1 Reply)
Discussion started by: ningy
1 Replies

4. Solaris

Sun cluster and Veritas cluster question.

Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC. Am thinking how to migrate to sun cluster setup instead. My plan as follows leave the existing vcs intact as a fallback plan. Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies

5. Solaris

Sun cluster 3.2

Hi I have a new mount point which is to added to to an existing resource group. I read many docs but I am not able to find the exact methods. Could anyone help me pls. (1 Reply)
Discussion started by: ningy
1 Replies

6. Solaris

Sun cluster

Any body can tell me where i can download sun cluster installation and configuration video. is there any option to install cluster in 32 bit virtual machine. please help (4 Replies)
Discussion started by: sunnybee
4 Replies

7. Solaris

Sun cluster 4.0 - zone cluster failover doubt

Hello experts - I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts. (1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over) (2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies

8. Solaris

Sun Cluster/Storage question

Hi Bros, I am a newbie to this cluster environment...my workplace is a mess of Sun solaris server, oracle database, Cisco switch, router, MS Server, Windows PC..so and so..now my boss ask me to come out with a procedure for maintenance of storage array in our sun cluster environment..I read few... (12 Replies)
Discussion started by: xavierantony
12 Replies

9. Solaris

Sun cluster v3.2 - Is this right?

Running Sun Cluster v3.2 it appears. Two clustered physcial servers both running Solaris 10. Both servers run a number of Oracle DBs etc. BUT I'm a bit concerned that its been set up but will never switch in the even of failure of one of the hosts? Some of the cluster groups we've... (3 Replies)
Discussion started by: psychocandy
3 Replies
cmhaltpkg(1m)															     cmhaltpkg(1m)

NAME
cmhaltpkg - halt a high availability package SYNOPSIS
cmhaltpkg [-v] [-t] [-n node_name]... package_name... cmhaltpkg [-v] [-s] [-n node_name]... package_name... DESCRIPTION
cmhaltpkg connects to the Serviceguard cluster manager and halts the specified package(s) or multi-node package instance(s). When a package or package instance is halted, global switching (AUTO_RUN) is disabled for that package. cmhaltpkg may be run on any node within the cluster and may operate on any package within the cluster. To halt a package, a user must either be a superuser with effective user ID of zero (see id(1) and su(1)), or have an access policy of PACKAGE_ADMIN allowed in the cluster or package configuration file. See access policy in cmquerycl(1m) or cmmakepkg(1m). If no node_name arguments are supplied, each package will be halted on any and all nodes where it is running. If the package is not running on any nodes, the command will fail. cmhaltpkg should not be used to halt SYSTEM_MULTI_NODE packages (HP-UX only). Use cmhaltnode or cmhaltcl to halt SYSTEM_MULTI_NODE packages instead. Packages of other types may be halted on a subset of the configured nodes by specifying one or more node_name arguments. cmhaltpkg will fail if each specified package is not running on all the specified nodes. Packages are halted in the order required by their configured dependencies. Packages without configured dependencies are halted in the order specified on the command line. To successfully halt a package, all required dependent packages must either be previously halted or specified as a package_name argument in the cmhaltpkg command. Packages configured with STORAGE_GROUP are implicitly dependent on the cor- responding multi-node cluster volume manager (CVM) package. (HP-UX only) cmhaltpkg validates its command line prior to halting any package and returns an error if the user does not have correct access to complete the operation or if illegal combinations of node_name and package_name arguments are encountered. If a problem is detected while halting a package, cmhaltpkg exits with an error indication and remaining package_name arguments are not processed. A package in maintenance mode that was start up to and including a specified module can be halted from that specified module. Only those modules which were started are halted. Options cmhaltpkg supports the following options: -n node_name Acts only on a specific node. If the package is not running on the specified node, it will not be halted. -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 pack- ages. 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. This option is not legal for package in maintenance mode. -s Symmetric halt is only for packages in maintenance mode. If a package in maintenance mode has been started up to a module as specified by cmrunpkg -m, then cmhaltpkg -s will halt the package up to that module. Otherwise, cmhaltpkg -s will halt the package for all the modules specified in its configuration file. RETURN VALUE
cmhaltpkg returns the following value: 0 Successful completion. 1 Command failed. 2 Command failed due to a transient condition. EXAMPLES
A sequence of cmhaltpkg and cmrunpkg commands may be used to move a package from one node to another. For example, the package may be halted on one node and then run on a new node, provided that the package is enabled for the new node. To move package package1 to node node2, do the following: cmhaltpkg package1 cmrunpkg -n node2 package1 cmmodpkg -e package1 (to enable package switching, if desired) AUTHOR
cmhaltpkg was developed by HP. SEE ALSO
cmmakepkg(1m), cmquerycl(1m), cmmodpkg(1m), cmrunpkg(1m), cmviewcl(1m), cmeval(1m). Requires Optional Serviceguard Software cmhaltpkg(1m)
All times are GMT -4. The time now is 11:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy