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_resource (query|command) [options] DESCRIPTION
crm_resource - Perform tasks related to cluster resources. Allows resources to be queried (definition and location), modified, and moved around the cluster. OPTIONS
-?, --help This text -$, --version Version information -V, --verbose Increase debug output -Q, --quiet Print only the value on stdout -r, --resource=value Resource ID Queries: -L, --list List all resources -l, --list-raw List the IDs of all instantiated resources (no groups/clones/...) -O, --list-operations List active resource operations. Optionally filtered by resource (-r) and/or node (-N) -o, --list-all-operations List all resource operations. Optionally filtered by resource (-r) and/or node (-N) -q, --query-xml Query the definition of a resource (template expanded) -w, --query-xml-raw Query the definition of a resource (raw xml) -W, --locate Display the current location(s) of a resource -A, --stack Display the prerequisites and dependents of a resource -a, --constraints Display the (co)location constraints that apply to a resource Commands: -p, --set-parameter=value Set the named parameter for a resource. See also -m, --meta -g, --get-parameter=value Display the named parameter for a resource. See also -m, --meta -d, --delete-parameter=value Delete the named parameter for a resource. See also -m, --meta -M, --move Move a resource from its current location, optionally specifying a destination (-N) and/or a period for which it should take effect (-u) If -N is not specified, the cluster will force the resource to move by creating a rule for the current location and a score of -INFINITY NOTE: This will prevent the resource from running on this node until the constraint is removed with -U -U, --un-move Remove all constraints created by a move command Advanced Commands: -D, --delete Delete a resource from the CIB -F, --fail Tell the cluster this resource has failed -R, --refresh (Advanced) Refresh the CIB from the LRM -C, --cleanup (Advanced) Delete a resource from the LRM -P, --reprobe (Advanced) Re-check for resources started outside of the CRM Additional Options: -N, --node=value Host uname -t, --resource-type=value Resource type (primitive, clone, group, ...) -v, --parameter-value=value Value to use with -p, -g or -d -u, --lifetime=value Lifespan of migration constraints -m, --meta Modify a resource's configuration option rather than one which is passed to the resource agent script. For use with -p, -g, -d -z, --utilization Modify a resource's utilization attribute. For use with -p, -g, -d -s, --set-name=value (Advanced) ID of the instance_attributes object to change -i, --nvpair=value (Advanced) ID of the nvpair object to change/delete -f, --force EXAMPLES
List the configured resources: # crm_resource --list Display the current location of 'myResource': # crm_resource --resource myResource --locate Move 'myResource' to another machine: # crm_resource --resource myResource --move Move 'myResource' to a specific machine: # crm_resource --resource myResource --move --node altNode Allow (but not force) 'myResource' to move back to its original location: # crm_resource --resource myResource --un-move Tell the cluster that 'myResource' failed: # crm_resource --resource myResource --fail Stop a 'myResource' (and anything that depends on it): # crm_resource --resource myResource --set-parameter target-role --meta --parameter-value Stopped Tell the cluster not to manage 'myResource': The cluster will not attempt to start or stop the resource under any circumstances. Useful when performing maintenance tasks on a resource. # crm_resource --resource myResource --set-parameter is-managed --meta --parameter-value false Erase the operation history of 'myResource' on 'aNode': The cluster will 'forget' the existing resource state (including any errors) and attempt to recover the resource. Useful when a resource had failed permanently and has been repaired by an administrator. # crm_resource --resource myResource --cleanup --node aNode AUTHOR
Written by Andrew Beekhof REPORTING BUGS
Report bugs to pacemaker@oss.clusterlabs.org Pacemaker 1.1.7 April 2012 PACEMAKER(8)