06-29-2014
1) Yes, but with disastrous results ( just a question of time (short…)). So that is why you mount VG in SGMC as exclusive the same is true with AIX HACMP etc..
Normally you choose one server as the master, the reason is that server gets all new/change configuration when validated are replicated to the other node (when 2 nodes).
So to be sure you are talking of same VG both sides it is wise to give them same name and same major number when you create the VG on both side…
From home and not having touched to a HP cluster for now 8 years, it is difficult for me to say more…( notes are at work…)
One thing be sure you have same devices both sides, when a VG ( on master) is completed with all its PV and Lv defined, you use vgexport command with -p (preview) to create a map file etc you copy on the second node and use vgimport
2) a cluster is in short 2 servers configured to "host" on or more package that could be seen as virtual servers if you added LUNs that are for a package, they should be included to it… Not the same as creating a new package
There are scripts to help you through, and most important there are scripts after all change to update the package both sides and TEST both sides, the very important part of an admin life with cluster is to check its integrity, if the MCSG checking script fails, you are to correct promptly before anything happens or you will be in big trouble...
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I need to find out when a file has been created. 'ls -l' just lists the last date the file was modified, not the creation date. I have also noticed when viewing the attributes through NT, the last modified date is the same as the file creation date. I thought maybe this was a fault due to Samba.
... (2 Replies)
Discussion started by: dpalmer
2 Replies
2. 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
3. UNIX for Dummies Questions & Answers
I have a program (written by me, for educational purposes) called "analyzer".
The program takes a parameter, a filename, and does some statistics on it (for example, word's number, line's number, ... ) at regular intervals.
My teacher told me that if the file is edited while the "analyzer" is... (4 Replies)
Discussion started by: hurricane
4 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. Shell Programming and Scripting
Hello,
I have an xml file whose contacts are like below:
<Node>Apple
<B>Value1</B>
<B>Value2</B>
<B>Value3</B>
</Node>
<Node>Mango
<B>Value1</B>
<B>Value2</B>
<B>Value3</B>
</Node>
<Node>Apple
<B>Value1</B>
<B>Value2</B>
<B>Value3</B>
</Node>
<Node>Bannana (3 Replies)
Discussion started by: umarsatti
3 Replies
6. Programming
Hi, I'm pretty new to kernel coding and I'm working on a device driver that works with an existing framework.
Basically my module will be loaded/unloaded multiple times and I'd like to create a register a class, driver, and create a /dev node on the first load only. The existing framework... (0 Replies)
Discussion started by: ThomasBrez
0 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I wanted to zip some files (very large files) on our cluster (centOS). I am told that I should use the head node for this as it would tie down the CPU. How can I do this using one of the other nodes in the cluster?
For small files, I would just log into the cluster using ssh (ie. ssh... (1 Reply)
Discussion started by: pc2001
1 Replies
8. 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
9. Shell Programming and Scripting
Dear members, The following expect script connects to remote node and check for the file "authorized_keys" in directory /root/.ssh in remote node. However the result is always found even if the file exist or doesn't exist.
expect {
"$fname" {
send_user "found\n"
}
Any idea what is... (4 Replies)
Discussion started by: Sudhakar333
4 Replies
10. Shell Programming and Scripting
<?xml version="1.0" encoding="UTF-8"?>
<Document>
<FIToFICstmrCdtTrf>
<GrpHdr>
<MsgId>10001</MsgId>
<NbOfTxs>1</NbOfTxs>
<IntrBkSttlmDt>2015-05-06</IntrBkSttlmDt>
<SttlmInf>
<SttlmMtd>CLRG</SttlmMtd>
</SttlmInf>
<PmtTpInf>
... (2 Replies)
Discussion started by: harish2015
2 Replies
LEARN ABOUT HPUX
cmhaltpkg
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)