Sponsored Content
Full Discussion: failover on 4.5 hacmp
Operating Systems AIX failover on 4.5 hacmp Post 302208704 by itik on Tuesday 24th of June 2008 03:23:21 PM
Old 06-24-2008
failover on 4.5 hacmp

Hi All,

How do I trigger the failover on the second hacmp server?

Please give me idea and I will do the rest.

Thanks,
itik
 

10 More Discussions You Might Find Interesting

1. Solaris

Interfaces do not failover

Would anyone know why a V440 Solaris 9 machine's interfaces (ce0 and ce1) will not failover? Both interfaces are on the same subnet, but different IPs. I can pull the plug on once interface (ce0) and ce1 will be accessible. I can reverse it and pull ce1, and ce0 will NOT be accessible. ... (5 Replies)
Discussion started by: StorageGuy
5 Replies

2. AIX

Can anyone shed some light on this HACMP failover?

Hello All, Here is a snipet from our cluster.log, I was wondering if anyone could shed some light on what may have caused the failover. The first two lines indicate a possible memory issue which I am currently looking into. Thanks. (0 Replies)
Discussion started by: Wez
0 Replies

3. UNIX for Advanced & Expert Users

directories failover

Hi, I have 3 directories (/1 /2 and /3) with same contents and want to achieve fail over among them. The Solution i thought of: 1. link /data to /1 (and provide users with /data to access) 2. CRON a script (to run every minute) to verify if /1 exist or not, if it does not exist (or its... (3 Replies)
Discussion started by: prvnrk
3 Replies

4. AIX

hacmp ip load balancer failover

Hi All, How do I failover on the ip load balancer (back and forth)? It involves first to load a new config on the passive ip. If success, load the new config on the ip active (which is now passive). Any idea, please. Thanks in advance. (0 Replies)
Discussion started by: itik
0 Replies

5. Solaris

IPMP failover: Why is it occurring?

The active NIC has been failing back and forth on two of our T2000s. I don't know when the problem originally began, but I can see failovers in the messages.* files. The network guy says the switches are clean (no errors) so I'm left looking at the configuration or any other issue that may be... (5 Replies)
Discussion started by: dangral
5 Replies

6. Solaris

EMC Failover

Hi guys, I'm running vxdmp and powerpath at the same time. Vxdmp for internal disks and powerpath for external. The problem is that, on the failover tests which a fiber cable should be removed, the system cannot recognize the disks. Any hints on how to configure powerpath in order to... (4 Replies)
Discussion started by: glenioborges
4 Replies

7. IP Networking

IP failover needed

All, I am looking to setup a simple IP failover setup, but it seems every place i look has some difficult setup like pacemaker or LVS. I only want to handle the IP piece to failover a VIP. Any suggestions? I checked out keepalived and that my work for me. (4 Replies)
Discussion started by: markdjones82
4 Replies

8. Gentoo

How to failover the cluster ?

How to failover the cluster ? GNU/Linux By which command, My Linux version 2008 x86_64 x86_64 x86_64 GNU/Linux What are the prerequisites we need to take while failover ? if any Regards (3 Replies)
Discussion started by: sidharthmellam
3 Replies

9. 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

10. 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
MEMCACHE.ADDSERVER(3)							 1						     MEMCACHE.ADDSERVER(3)

Memcache::addServer - Add a memcached server to connection pool

SYNOPSIS
bool Memcache::addServer (string $host, [int $port = 11211], [bool $persistent], [int $weight], [int $timeout], [int $retry_inter- val], [bool $status], [callable $failure_callback], [int $timeoutms]) DESCRIPTION
Memcache.addServer(3) adds a server to the connection pool. You can also use the memcache_add_server(3) function. When using this method (as opposed to Memcache.connect(3) and Memcache.pconnect(3)) the network connection is not established until actu- ally needed. Thus there is no overhead in adding a large number of servers to the pool, even though they might not all be used. Failover may occur at any stage in any of the methods, as long as other servers are available the request the user won't notice. Any kind of socket or Memcached server level errors (except out-of-memory) may trigger the failover. Normal client errors such as adding an existing key will not trigger a failover. Note This function has been added to Memcache version 2.0.0. PARAMETERS
o $host - Point to the host where memcached is listening for connections. This parameter may also specify other transports like unix:///path/to/memcached.sock to use UNIX domain sockets, in this case $port must also be set to 0. o $port - Point to the port where memcached is listening for connections. Set this parameter to 0 when using UNIX domain sockets. Please note: $port defaults to memcache.default_port if not specified. For this reason it is wise to specify the port explicitly in this method call. o $persistent - Controls the use of a persistent connection. Default to TRUE. o $weight - Number of buckets to create for this server which in turn control its probability of it being selected. The probability is rela- tive to the total weight of all servers. o $timeout - Value in seconds which will be used for connecting to the daemon. Think twice before changing the default value of 1 second - you can lose all the advantages of caching if your connection is too slow. o $retry_interval - Controls how often a failed server will be retried, the default value is 15 seconds. Setting this parameter to -1 disables auto- matic retry. Neither this nor the $persistent parameter has any effect when the extension is loaded dynamically via dl(3). Each failed connection struct has its own timeout and before it has expired the struct will be skipped when selecting backends to serve a request. Once expired the connection will be successfully reconnected or marked as failed for another $retry_interval seconds. The typical effect is that each web server child will retry the connection about every $retry_interval seconds when serving a page. o $status - Controls if the server should be flagged as online. Setting this parameter to FALSE and $retry_interval to -1 allows a failed server to be kept in the pool so as not to affect the key distribution algorithm. Requests for this server will then failover or fail immediately depending on the $memcache.allow_failover setting. Default to TRUE, meaning the server should be considered online. o $failure_callback - Allows the user to specify a callback function to run upon encountering an error. The callback is run before failover is attempted. The function takes two parameters, the hostname and port of the failed server. o $timeoutms - NOTES
Warning When the $port is unspecified, this method defaults to the value set of the PHP ini directive memcache.default_port If this value was changed elsewhere in your application it might lead to unexpected results: for this reason it is wise to always specify the port explicitly in this method call. RETURN VALUES
Returns TRUE on success or FALSE on failure. EXAMPLES
Example #1 Memcache.addServer(3) example <?php /* OO API */ $memcache = new Memcache; $memcache->addServer('memcache_host', 11211); $memcache->addServer('memcache_host2', 11211); /* procedural API */ $memcache_obj = memcache_connect('memcache_host', 11211); memcache_add_server($memcache_obj, 'memcache_host2', 11211); ?> SEE ALSO
Memcache.connect(3), Memcache.pconnect(3), Memcache.close(3), Memcache.setServerParams(3), Memcache.getServerStatus(3). PHP Documentation Group MEMCACHE.ADDSERVER(3)
All times are GMT -4. The time now is 07:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy