03-07-2013
i have done it with iscsi. and, yes, i assume the no_resdrve setting is also needed. been nearly 18 months since i have played with ha.
have fun.
ps, if working with systemmirror 7.x remember that the ha interfaces will multicast for caa. if you have a lot of systems in a vlan they may be affected..
10 More Discussions You Might Find Interesting
1. AIX
Hello,
I would like to know if anyone has faced this problem. Whenever there is a duplicate IP address, HACMP goes down infact HACMP ( PowerHA ) takes the whole system down.
Does anyone know how to solve this problem ? (3 Replies)
Discussion started by: filosophizer
3 Replies
2. 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
3. AIX
I am planning for building a new database server using AIX 6.1 and Oracle 11.2 using ASM.
As i have learned starting with Oracle 11.2 ASM can only be used in conjunction with Clusterware, which is Oracles HA-software. As is the companies policy we do intend to use PowerHA as HA-solution instead... (1 Reply)
Discussion started by: bakunin
1 Replies
4. AIX
Hello!
I have this infraestructure:
- 1 POWER7 with single VIOS on Site A.
- 1 POWER6 with single VIOS on Site B.
- 1 LPAR called NodeA as primary node for PowerHA 6.1 on Site A.
- 1 LPAR called NodeB as secondary (cold) node for PowerHA 6.1 on SiteB.
- 1 Storage DS4700 on Site A.
- 1... (8 Replies)
Discussion started by: enzote
8 Replies
5. AIX
Hello AIX GURU's
Can anybody tell me the steps to crate shared VG (enhanced concurent) for my Lpars from VIO server?
my questions are:
1.
Should I crate Enhanced Concurent VG in VIO and map it using virtual Scsi to Lpar?
or
2. Can I just create virtual SCSI in VIO and map to Lpar and... (1 Reply)
Discussion started by: Vit0_Corleone
1 Replies
6. AIX
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies
7. AIX
Hello,
AIX 6.1 TL7 SP6
POwerHA 6.1 SP10
I was experimenting with new hacmp build. It's 3-node cluster build on AIX 6.1 lpars. It contains Ethernet and diskhb networks. Shared vg disk is SAN disk. Two nodes see disk using vscsi, third node sees disk using npiv. Application is db2 server.
... (4 Replies)
Discussion started by: vilius
4 Replies
8. AIX
hello
ive installed powerha 7.1.3 on two servers aix 6.1.9 6100-09-03-1415
work with dmx4 EMC storgae.
after sync cluster ( terminate with OK ) ive see that the repository disk upper only in one machine :
hdiskpower60 00c7f6b59fc60d9d caavg_private active... (1 Reply)
Discussion started by: ariec
1 Replies
9. AIX
I have created a VxVM disk group in AIX7.1. I have tried to added this VxVM disk group in powerHA 6.1. But in cluster VxVM DGs are not listing. Is there any other procedure to add vxvm diskgroup to hacmp.
Please share me steps for adding vxvm diskgroup to hacmp. (6 Replies)
Discussion started by: sunnybee
6 Replies
10. AIX
Hi All,
As per the IBM upgrade/support matrix
IBM Techdocs Technote: PowerHA for AIX Version Compatibility Matrix
we can't do online upgrade or rolling migration from powerha v7.1.0 to v7.1.3. on AIX61_TL9_SP4, So we are following the steps as below ...
1 ) Bring down the cluster
2 )... (2 Replies)
Discussion started by: linux.amrit
2 Replies
LEARN ABOUT FREEBSD
iscsi
ISCSI(4) BSD Kernel Interfaces Manual ISCSI(4)
NAME
iscsi -- iSCSI initiator
SYNOPSIS
To compile this driver into the kernel, place the following line in the kernel configuration file:
device iscsi
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
iscsi_load="YES"
DESCRIPTION
The iscsi subsystem provides the kernel component of an iSCSI initiator. The initiator is the iSCSI client, which connects to an iSCSI tar-
get, providing local access to a remote block device. The userland component is provided by iscsid(8) and both the kernel and userland are
configured using iscsictl(8). The iscsi subsystem is responsible for implementing the "Full Feature Phase" of the iSCSI protocol.
SYSCTL VARIABLES
The following variables are available as both sysctl(8) variables and loader(8) tunables:
kern.iscsi.ping_timeout
The number of seconds to wait for the target to respond to a NOP-Out PDU. In the event that there is no response within that time
the session gets forcibly restarted.
kern.iscsi.iscsid_timeout
The number of seconds to wait for ctld(8) to establish a session. After that time iscsi will abort and retry.
kern.iscsi.login_timeout
The number of seconds to wait for a login attempt to succeed. After that time iscsi will abort and retry.
kern.iscsi.maxtags
The maximum number of outstanding IO requests.
kern.iscsi.fail_on_disconnection
Controls the behavior after an iSCSI connection has been dropped due to network problems. When set to 1, a dropped connection causes
the iSCSI device nodes to be destroyed. After reconnecting, they will be created again. By default, the device nodes are left
intact. While the connection is down all input/output operations are suspended, to be retried after the connection is reestablished.
SEE ALSO
iscsi.conf(5), iscsictl(8), iscsid(8)
HISTORY
The iscsi subsystem first appeared in FreeBSD 10.0.
AUTHORS
The iscsi subsystem was developed by Edward Tomasz Napierala <trasz@FreeBSD.org> under sponsorship from the FreeBSD Foundation.
BSD
September 11, 2014 BSD