07-06-2014
First off, i wouldn't want to run HACMP 7.1.3 off an 6.1 LPAR. I strongly suggest to update to 7.1.3 SP3 from May. Do not forget the two necessary efixes.
Two probable causes for your problem come to mind: have you zoned the LUN for concurrent access? Second, Repository disks are supported via NPIV only if the storage is IBM (yes, thanks a lot, IBM, for that open system). As you use EMC storage (like me) you have to provide the disk via iSCSI, which means via the VIOS.
Please tell us how the Repo-disk is connected to the system, which driver suite you use for your FC adapters - in short, describe your system better.
Moderator's Comments:
|
|
by the way: we have an AIX board, so please write your AIX-related questions there. I move this thread over.
|
|
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. AIX
I was wondering if any one have any guides or documention regarding Oracle and SAP on AIX 6.1 + PowerHA setups in one guide step by step
Thanks (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies
2. AIX
I've configured multiple clusters using PowerHA 5.5, but never using the 'Two-node cluster configuration assistant'. I removed all the clusters, clean setup, and gave the assistant a try. I've filled in all the necessary options:
Communication Path to Takeover Node
Application Server
... (11 Replies)
Discussion started by: Koen87
11 Replies
3. AIX
I am new in AIX and please forgive my poor english.
I know that AIX allow same subnet IPs for different interfaces, which result in multipath routing / route striping.
My question is,
is there any best practice for the persistent and service IP with same subnet to stay on same interface, or... (5 Replies)
Discussion started by: skeyeung
5 Replies
4. 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
5. AIX
Looking to find PowerHA with 3rd node used for communication (voting node) only. Does anyone use such configuration with IBM products? (2 Replies)
Discussion started by: gogogo
2 Replies
6. AIX
Few questions regarding Power HA ( previously known as HACMP) and VIOS POWERVM IVM ( IBM Virtualization I/O Server )
Is it possible to create HACMP cluster between two VIOS servers
Physical Machine_1
VIOS_SERVER_1
LPAR_1
SHARED_DISK_XX
VIOS_SERVER_2
Physical Machine_2
LPAR_2... (6 Replies)
Discussion started by: filosophizer
6 Replies
7. AIX
Hi all,
I want to upgrade a clustered AIX 5.3 TL10 with PowerHA 5.5.0.4.
To both AIX 6.1 and PowerHA 6.1 in an wasy way.
Any guidelines or procedures in an easy way to accomplish this task safely?
Note : fdown time is an acceptable option. (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies
8. 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
9. AIX
Hello Guys,
I was trying to upgrade the PowerHA from 6.1.0.9 to 7.1.3 in prod cluster. Have snapshot migration and run climgcheck.
1. Run climgcheck on node1(kul1pqcmur01) and it success
2. Upgrade the cluster sw
3. Run climgcheck on node2(kul1pqcmur02) and it failed with below errors
... (6 Replies)
Discussion started by: novaothers
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
SCSI(4) Kernel Interfaces Manual SCSI(4)
Name
SCSI - Small Computer System Interconnect
Description
The ULTRIX system interfaces to disk and tape devices through the Small Computer System Interconnect (SCSI). Initial ULTRIX SCSI support
is limited to the Digital-supplied mass storage devices. The following devices are fully supported on the ULTRIX system:
o Winchester disks: RZ22, RZ23, RZ23L, RZ24, RZ55, RZ56, RZ57, RX23, RX26, RX33
o Magnetic tapes: TZ30, TZK50, TLZ04, TSZ05, TKZ08, TZK10
o Optical disks: RRD40, RRD42
Under the ULTRIX operating system, a SCSI device is referred to by its logical name. Logical names take the following form:
nn#
The nn argument is the two-character name; the number sign (#) represents the unit number. The two character names for SCSI devices are:
rz - RZ22, RZ23, RZ23L, RZ24, RZ55, RZ56, RZ57, RX23, RX26, RX33, RRD40, RRD42 disks
tz - TZ30, TZK50, TLZ04, TSZ05, TKZ08, and TZK10 tapes
The unit number is a combination of the SCSI bus number, either 0, 1, ... and the device's target ID number. The unit number is eight
times the bus number plus the target ID. For example, an RZ23 disk at target ID 3 on bus 0 would be referred to as rz3; a TZK50 tape at
target ID 5 on the second SCSI bus would be referred to as 13.
The SCSI bus has eight possible target device IDs. By default, one is allocated to the system. This allows for a maximum of seven target
devices connected to a SCSI bus.
Restrictions
The ULTRIX SCSI device driver does not operate with optical disks, other than the Digital-supplied devices.
The SCSI driver attempts to support on a best effort basis, non-Digital-supplied winchester disks and magnetic tapes.
The following notes apply to the driver's handling of non-Digital-supplied disks:
o These disks are assigned a device type of RZxx, instead of RZ22, RZ23, RZ23L, RZ55, RZ56, RZ57, RX23, RX26, or RX33. The RZxx disks
follow the same logical device naming scheme as the Digital-supplied disks.
o During the autoconfigure phase of the system startup, the driver prints the contents of the SCSI vendor ID, product ID, and the
revision level fields of the inquiry data return by the SCSI device.
o RZxx disks are assigned a default partition table. The default table can be modified by editing the sz_rzxx_sizes[8] entry in the
file The utility can also be used to modify the partition table on a RZxx disk.
o The only logical unit number (LUN) supported for each target ID is 0.
See Also
rz(4), tz(4), chpt(8)
SCSI(4)