hacmp service ip


 
Thread Tools Search this Thread
Operating Systems AIX hacmp service ip
# 1  
Old 08-22-2006
hacmp service ip

Hi,

I have two resource grps in hacmp 5.2 cluster.One is cascading and other is concurrent.

I have apply one svc_ip to cascading rg but not able to apply any svc ip with node bound option for concurrent rg.

Can any one guide me with the step to apply svc ip .

thanks in advance
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Run one service after another service has finished - systemd

Hi all I would like to know how to run task2.service after task1.service has finished. task1.service has a timer (task1.timer), that makes it run every 5 minutes OnCalendar=*:0/5task2.service is basically a script, that has to work on the files created after task1 has finished. This is what I... (2 Replies)
Discussion started by: guilliber
2 Replies

2. AIX

HACMP with VIO, service IP failover

Would anyone please kindly help to solve this problem... An LPAR with the below network configuration. ent0 and ent1 are logical lan (virtual ethernet) from VIO SEA. en0 1.2.3.4 <- boot ip 192.168.1.1 <- persistent ip 192.168.1.10 <- service ip en1 11.22.33.44 <- boot ip When I... (6 Replies)
Discussion started by: skeyeung
6 Replies

3. AIX

Service IP issue in HACMP, Working with only one node

Hi, I have a running HACMP Cluster with two nodes. Its working in active/passive mode. (i.e Out of the two nodes in the cluster one will be active and the other one will be on standby. If first node fails the other takes over) 1. There is a Service IP associated with the cluster. Now the... (2 Replies)
Discussion started by: aixromeo
2 Replies

4. AIX

HACMP does not start db2 after failover (db2nodes not getting modified by hacmp)

hi, when I do a failover, hacmp always starts db2 but recently it fails to start db2..noticed the issue is db2nodes.cfg is not modified by hacmp and is still showing primary node..manually changed the node name to secondary after which db2 started immediately..unable to figure out why hacmp is... (4 Replies)
Discussion started by: gkr747
4 Replies

5. AIX

HACMP: set preferred adapter for service ip

Hi, lets say we have two boot interfaces en0 en1 and two resource groups, with two service ips, sip1 and sip2, one persistent ip pers1 both persistend and service ips are applied as ip-alias when I start the cluster, and bring the resource groups up, it looks like en0: sip1 and sip2 ... (4 Replies)
Discussion started by: funksen
4 Replies
Login or Register to Ask a Question
PACEMAKER(8)						  System Administration Utilities					      PACEMAKER(8)

NAME
Pacemaker - Part of the Pacemaker cluster resource manager SYNOPSIS
crm_attribute command -n attribute [options] DESCRIPTION
crm_attribute - Manage node's attributes and cluster options. Allows node attributes and cluster options to be queried, modified and deleted. OPTIONS
-?, --help This text -$, --version Version information -V, --verbose Increase debug output -q, --quiet Print only the value on stdout -n, --name=value Name of the attribute/option to operate on Commands: -G, --query Query the current value of the attribute/option -v, --update=value Update the value of the attribute/option -D, --delete Delete the attribute/option Additional Options: -N, --node=value Set an attribute for the named node (instead of a cluster option). See also: -l -t, --type=value Which part of the configuration to update/delete/query the option in. Valid values: crm_config, rsc_defaults, op_defaults, tickets -l, --lifetime=value Lifetime of the node attribute. Valid values: reboot, forever -z, --utilization Set an utilization attribute for the node. -s, --set-name=value (Advanced) The attribute set in which to place the value -i, --id=value (Advanced) The ID used to identify the attribute -d, --default=value (Advanced) The default value to display if none is found in the configuration EXAMPLES
Add a new attribute called 'location' with the value of 'office' for host 'myhost': # crm_attribute --node myhost --name location --update office Query the value of the 'location' node attribute for host myhost: # crm_attribute --node myhost --name location --query Change the value of the 'location' node attribute for host myhost: # crm_attribute --node myhost --name location --update backoffice Delete the 'location' node attribute for the host myhost: # crm_attribute --node myhost --name location --delete Query the value of the cluster-delay cluster option: # crm_attribute --type crm_config --name cluster-delay --query Query the value of the cluster-delay cluster option. Only print the value: # crm_attribute --type crm_config --name cluster-delay --query --quiet AUTHOR
Written by Andrew Beekhof REPORTING BUGS
Report bugs to pacemaker@oss.clusterlabs.org Pacemaker 1.1.10-29.el7 June 2014 PACEMAKER(8)