01-03-2012
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 unplug the en0 cable (i.e. unplug the corresponding VIO ethernet cable), persistent and service will not failover to en1.
I tried the case for dedicated machine, when en0 is unplugged, in error report it will show a failure of ethernet, and the persistent and service IP will failover to en1. This will not happen at VIO LPAR since it is logical LAN and it will not detect a failure.
I found a solution from IBM to add !REQD <source IP> <destination IP> in the netmon.cf file, but not successful. I also added the IPs for the variable ping_client_list in clrginfo.rc file, but still failed.
Please kindly help how to make the LPAR know there is a failure in adapter, and will failover the persistent and service IP to the other interface.
Thank you very much!!
10 More Discussions You Might Find Interesting
1. AIX
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 (0 Replies)
Discussion started by: aix_53
0 Replies
2. AIX
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. AIX
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 (2 Replies)
Discussion started by: itik
2 Replies
4. AIX
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. AIX
Hello,
Can someone point to me document or the method to make failover for VIO Servers ?
I have one VIO_Server1 which has 4 AIX LPARS
- From the VIO_SERVER1 I have assigned virtual SCSI DISK to the four LPARS
- For Ethernet I have used LHEA
So, if my VIO Server1 crashes all the LPARS... (17 Replies)
Discussion started by: filosophizer
17 Replies
6. AIX
Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies
7. AIX
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
8. AIX
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
9. AIX
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
10. AIX
Hi all,
How can I close ftp port 21 on VIO server.
Best regards,
---------- Post updated at 10:06 AM ---------- Previous update was at 08:45 AM ----------
I resoved with switch to OS mode.
$ oem_setup_env (0 Replies)
Discussion started by: getrue
0 Replies
LEARN ABOUT HPUX
vtdaemon
vtdaemon(1M) vtdaemon(1M)
NAME
vtdaemon - respond to vt requests
SYNOPSIS
lan_device lan_device ...
DESCRIPTION
responds to requests from other systems (via local area network) made by (see vt(1)). spawns a server to respond to each request that it
receives.
Options
recognizes the following command-line options and arguments:
Causes to rebroadcast all requests received on one lan device to all other lan devices specified on the command line. The
optional parameter ngateway specifies the maximum number of vtgateway servers that can be in operation concurrently. If
ngateway is not specified, there is no limit on the number of vtgateway servers that can be in operation concurrently.
Causes vtdaemon to ignore all requests that have come through a gateway.
The remaining arguments are the full path names of lan devices that vtdaemon looks for requests on. If no lan devices are specified, the
default lan device is used.
The major number for this device must correspond to a IEEE 802.3 local area network device.
Another function of is to create portals and service portal requests. A portal is a callout device that can be used by to communicate to
another machine via local area network (see uucico(1M)). Portals are created by according to the configuration information found in the
file Each line in has the format:
<calldev>[,<lan device>] <nodename>
For each line, creates a portal named calldev in Whenever this device is opened, spawns a server that creates a connection to the system
specified by nodename via the lan device specified. If no lan device is specified, the first one specified on the command line when was
started is used (or the default lan device is used if no lan devices were specified on the command line).
should be terminated by sending signal to it. When receives this signal it removes all of the portals it created in before exiting.
DIAGNOSTICS
Diagnostics messages produced by are written to
WARNINGS
uses the Hewlett-Packard (Link Level Access) direct interface to the HP network drivers. uses the multicast address It should not be used
or deleted by other applications accessing the network. uses the following IEEE 802.3 sap (service access point) values: and They should
not be used by other applications accessing the network.
Desktop HP-UX
If your system has been installed with the Desktop HP-UX product, then both and will not be started by default. In order to start these
daemons, change PTYDAEMON_START and VTDAEMON_START from a "0" to a "1" in the and files, respectively. The system must either be rebooted
for these changes to take effect, or you can manually start both daemons by typing :
where /dev/lan0 is the character special device file corresponding to the IEEE802.3 local area network device.
FILES
logfile used by vtdaemon.
default lan device name.
SEE ALSO
vt(1), uucico(1M).
vtdaemon(1M)