06-04-2013
Hicksd8 thanks a lot i think that the solution are on the cluster chapitres
i will post some informations when i resolve this issue
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hi,
i have a volume on a LUN of an EMC-storage and i need to increase the
size.
i could increase the size of the LUN on the EMC, i could increase the
size of the disk for solaris, but how can i tell the veritas volume
manager that the disk is larger now?
what i've done:
1. LUN on EMC
2.... (3 Replies)
Discussion started by: pressy
3 Replies
2. Solaris
Hi,
I have a nasty little problem with my disks on my system
My system configuration is as follows
Sunv890 with sunos 9 connected tot a IBM6800 SAN using a 2port 2 GB qla2342 adapter.
We have bought a EMC SAN. The company who sold us the san, said that it would be no problem connecting the... (10 Replies)
Discussion started by: orac
10 Replies
3. Solaris
Hi,
Quick question if anyone knows this. Is there a command I can use in Veritas Volume manager on Solaris that will tell me what the name of the SAN I am connected to? We have a number of SANs so I am unsure which one my servers are connected to. Thanks. (13 Replies)
Discussion started by: gwhelan
13 Replies
4. Solaris
Hi
Can anyone suggest me some documents for EMC clarion documents which I am going to use in the servers with solaris environments. (1 Reply)
Discussion started by: ningy
1 Replies
5. UNIX for Advanced & Expert Users
I have seen a few threads / posts on the forum's but nothing specific to what Iam after. So Iam hoping you can help.
Issue : Iam hoping to remove unused emc luns from my solaris servers , T2000 (5.10 Generic_142900-02). I have a list of the process I have followed for the removal of the luns.... (3 Replies)
Discussion started by: furby
3 Replies
6. Linux
Hello guys, I'm going crazy over here with a problem with a LUN created on a EMC CX3.
I did sucessfully managed to create the LUN on the Storage (the LUN is named DBLNX25EC_TST), after doing the following process:
echo "1" > /sys/class/fc_host/host<n>/issue_lip
and
echo "- - -" >... (10 Replies)
Discussion started by: Zarnick
10 Replies
7. Solaris
The Storage Admin presents a clone of a LUN, on the source side the device is under VxVM control, assuming that on the target side we have scanned the new cloned LUN at the OS level (solairs), from there on how do we initialize and mount the new volume.
Please give some guidence on this or a... (1 Reply)
Discussion started by: Tirmazi
1 Replies
8. Solaris
Hi All,
I have server : Sun-Fire-V490 configured with Solaris 10 zfs
..
and I have configured three mirror the third one from EMC
storage.
root@server # zpool status -v
pool: rpool
state: ONLINE
status: The pool is formatted using an older on-disk format. The pool can
... (8 Replies)
Discussion started by: top.level
8 Replies
9. AIX
we have an old AIX system with important data on an EMC LUN. the AIX server crashed and we had to rebuild it with the old AIX os 5.8. how do we reconnect the EMC LUN without losing the data? (15 Replies)
Discussion started by: jhudson12
15 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)