Sponsored Content
Full Discussion: failover on 4.5 hacmp
Operating Systems AIX failover on 4.5 hacmp Post 302208809 by encrypted on Wednesday 25th of June 2008 03:22:51 AM
Old 06-25-2008
Failover can be triggered by anything as unplugging a network interface cable to one of the nodes. Smilie
 

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
DE(4)							     Kernel Interfaces Manual							     DE(4)

NAME
de - DEC DEUNA 10 Mb/s Ethernet interface SYNOPSIS
/sys/conf/SYSTEM: NDE de_controllers # DEUNA DESCRIPTION
The de interface provides access to a 10 Mb/s Ethernet network through a Digital Equipment UNIBUS Network Adapter (DEUNA). Each of the host's network addresses is specified at boot time with an SIOCSIFADDR ioctl. The de interface employs the address resolution protocol described in arp(4P) to dynamically map between Internet and Ethernet addresses on the local network. The interface normally tries to use a ``trailer'' encapsulation to minimize copying data on input and output. The use of trailers is nego- tiated with ARP. This negotiation may be disabled, on a per-interface basis, by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl. DIAGNOSTICS
de%d: hardware address %s. This is a normal autoconfiguration message noting the 6 byte physical ethernet address of the adapter. de%d: oerror, flags=%b tdrerr=%b (len=%d). The hardware indicated an error in transmitting a packet to the cable. The status and error flags are reported. de%d: ierror, flags=%b lenerr=%b (len=%d). The hardware indicated an error in reading a packet from the cable. The status and error flags are reported. de%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was dropped. de%d: buffer unavailable. The interface received more packets than it had buffers allocated to receive them. de%d: address change failed, csr0=%b csr1=%b. The interface was unable to reprogram its physical ethernet address. This may happen with very early models of the interface. This facility is used only when the controller is not the first network interface configured for XNS. The following messages indicate a probable hardware error performing the indicated operation during autoconfiguration or initialization. The two control and status registers should indicate the nature of the failure. See the hardware manual for details. de%d: reset failed, csr0=%b csr1=%b. de%d: ppcb failed, csr0=%b csr1=%b. de%d: read addr failed, csr0=%b csr1=%b. de%d: wtring failed, csr0=%b csr1=%b. de%d: wtmode failed, csr0=%b csr1=%b. SEE ALSO
intro(4N), inet(4F), arp(4P) 3rd Berkeley Distribution August 20, 1987 DE(4)
All times are GMT -4. The time now is 07:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy