• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (11)

1 JP91_Maurizio_Pagani commented Permalink

Hi, <div>&nbsp;</div> I have two node with AIX 6.1 TL08 SP2, i want configure powerha 7.1.1, but unfortunatly when i must create the “repository disk”, the mkcluster command failed with this message: <div>&nbsp;</div> mkcluster: Cluster product not licensed <div>&nbsp;</div> do you know, why? <div>&nbsp;</div> Thanks in Advance

2 cggibbo commented Permalink

Make sure PowerHA is installed.

3 JP91_Maurizio_Pagani commented Permalink

sure, i have installed yet the POWERHA 7.1.1: <div>&nbsp;</div> [dmv02trnx:root:/home/root:] halevel -s <br /> 7.1.1 GA <br /> [dmv02trnx:root:/home/root:] mkcluster -r hdisk300 -d hdisk302 -m dmv02trnx,dmv03trnx -v <br /> INFO: START <br /> mkcluster: Cluster product not licensed. <br /> [dmv02trnx:root:/home/root:] <div>&nbsp;</div> someone know, why i have this problem? <div>&nbsp;</div> Thanks in advance

4 JP91_Maurizio_Pagani commented Permalink

yes, i have installed yet. <div>&nbsp;</div> My realease is "PowerHA 7.1.1" <div>&nbsp;</div> do you have any idea?

5 cggibbo commented Permalink

I have not come across this error before. I would recommend installing the latest updates for PowerHA 7.1 and then try again.

6 cggibbo commented Permalink

I asked my PowerHA guru about this and his advice was: <div>&nbsp;</div> "when testing labs for...class, I ran into it ....what I did to get it to work was create a bare PowerHA cluster, sync, let it create the CAA cluster like normal. Then go back and remove/delete the cluster definition and then I could do mkcluster manually after that. <div>&nbsp;</div> Another thing I discovered (searching PMRs when I hit it) might be a cause, is AIX Express edition does not include CAA support. So there is a chance IF they had Express edition that CAA would not be able to be used to." <div>&nbsp;</div> Of course, if none of this helps, you should open a new PMR with IBM support.

7 PrabhanjanG commented Permalink

We have often seen this message and is resolved by unlocking CAA

8 JP91_Maurizio_Pagani commented Permalink

Thanks, <div>&nbsp;</div> but i have latest SP of PowerHA yet, and i have opened a PMR for this problem. Today i have also upload "snap" files. <div>&nbsp;</div> When i'll solve this problem, i can write here the solution for traceability, ok? <div>&nbsp;</div> Thanks in advance, Bye Bye

9 JP91_Maurizio_Pagani commented Permalink

However, i don't have AIX Express Edition, because my servers are on Production Environment, and I'm working at IBM italy (Rome).

10 ashishnain commented Permalink

I read in an IBM document that size of Cluster repo disk should be greater than 512MB and less than 460GB. Please confirm <br /> Also I have a related question. Can we have multiple repo disks, (mirrored or unmirrored ) as cluster repository disks to avoid single disk as a SPOF. I am aware that we can replace the repo disk.

11 cggibbo commented Permalink

The online CAA documentation appears to be out dated. <div>&nbsp;</div> Basically CAA needs 256MB and PowerHA needs a 512MB disk. The initial 7.1.0 release did have a 10GB lun requirement documented, which later changed to 1GB, but going forward with the new usage of CAA with HA versions 7.1.1 and 7.1.2 they only need 512MB. Thus the smallest size is 512MB the largest if 460GB. The size requirements should not change even for a 16 node cluster, so we typically advise clients to use their standard lun size if they don't want to jump through hoops with their storage team, or assign it as small as possible w/the 512MB min size since anything beyond that would be wasted space. <div>&nbsp;</div> Note that in the first release we would create a database w/the Solid DB fileset and we no longer exploit it in V7.1.1 or 7.1.2. So you basically only see raw lvs in the private VG that gets created, you no longer see the filesystems that we had in V7.1.0. <div>&nbsp;</div> At this stage, it's not possible to have multiple repos disks. Only the backup disk (for hot replacement).

Add a Comment Add a Comment