In this article I'm going to cover what you need to do to setup Infiniband on IBM Power for Linux, in the example here it will be on Redhat, but when I get the time I will cover SUSE too. Simply I had a system that a customer wants to test on and Redhat was their choice. Now in my previous article I covered how the various GX++ adapters can be shared between the virtual machines in the system for AIX and this part is the same for Linux (see here). But I will cover those bits so you don't have to look in a different place:
POWER me up
Daniel Martin-Corben 270004CY29 Tags:  power powerlinux network networking linux infiniband 13,352 Views
Re-installing a VIOS today to the latest version I hit a issue, it was that my HMC was complaining a server with the same name was already installing. The message was 'Install Virtual I/O Server Failed - <name> Error reading nimol configuration. The client "<name.domain>" already exists.' As you can see from the image below:
It would seem that this is a bug with HMC 188.8.131.52, in that if you have ended a install before it completes, some of the clean up doesn't get done. Fortunately there is a way you can resolve this by login onto your HMC and examining the nimol.conf file for information:
hscroot@hmc:~> cat /etc/nimol.conf
As you can see I still have a install against default 3 for my VIOS, so I just needed to remove it using the installios command:
hscroot@hmc:~> installios -F -e -R default3
After which I just got back on with my VIOS install:
Daniel Martin-Corben 270004CY29 Tags:  powerlinux power vios powervc linux hmc error 11,987 Views
If you see the following error, then like me you might be wondering what the issue is -
Unable to connect to HMC <hmc-name>.
Explanation: Connection failed to the Hardware Management Console.
Response: Review the explanation and try the request again.
It would seem that PowerVC has performed more stringent checking then I have, and in this case it doesn't like my HMC, its a model 7042C06. If you have been paying attention and looking at my previous blogs you will see that the supported models are CR5/C08 or later.. So if you see AEVCOM021E too, take a look at your HMC model, switching to a spare CR6 model I had resolved my problem.
Note: I would like to point out that this is only one example of the issues that the AEV code covers. I have seen it reproduced in the event of a network failure, in that case it had slightly different explanation and response text. Looking at the '/var/log/nova/api.log' should give you more information.
More about Interpreting messages in IBM PowerVC (taken from the installation and user's guide):
You can use IBM PowerVC messages to help you troubleshoot problems. This describes how to interpret the message information you see in order to help understand the source of problems you may be seeing in the product.
Messages have unique message identifiers that are a minimum of seven characters and a maximum of ten characters in length. The format of the message identifiers is AEVXXX######Z, and is structured as follows:
E - Indicates that the message is an error message.
I - Indicates that the message is an information message.
S - Indicates that a process completed successfully.
W - Indicates that the message is a warning message.
Most messages include a description of the problem that has occurred as well as information on what you can do to resolve the problem. In some cases, additional information may be provided that refers to what is happening within the program itself. This information is intended to give you a better idea of what is causing the problem in order to assist with troubleshooting. You may see some of this internal information as the Explanation in an error message; you may also see some of this information in the Health field if you look at the properties of a resource.
Daniel Martin-Corben 270004CY29 Tags:  hmc install vios power powervc 7 Comments 19,978 Views
As part of the IBM PowerVC work I've been doing there is something extra preperation work that needs to be done, namely the update of the Hardware Management Console and VIO Server.
When the code is released you will need to be at:
So when you update your HMC, I recommend you take a look at this article as it will give you some tips on what you need to do:
Once that update is complete, you can move onto the VIO Server, of which there are a number of ways you can update them. In my case I have the iso mounted through a loop and that filesystem is then NFS served out:
[root] # loopmount -i /sharefs/2230vios.v1.iso -o "-V cdrfs -o ro" -m /cdrom
Login to you VIOS and mount the NFS and start the install:
[padmin] $ mount <nfs-server>:/cdrom /mnt
[padmin] $ updateios -commit
All updates have been committed.
[padmin] $ updateios -dev /mnt -install -accept
Once complete perform a reboot and when its back up, just do your normal checks to ensure all the packages are applied
[padmin] $ ioslevel
[padmin] $ oem_setup_env
# instfix -i |grep ML
All filesets for 184.108.40.206_AIX_ML were found.
All filesets for 6100-00_AIX_ML were found.
All filesets for 6100-01_AIX_ML were found.
All filesets for 6100-02_AIX_ML were found.
All filesets for 6100-03_AIX_ML were found.
All filesets for 6100-04_AIX_ML were found.
All filesets for 6100-05_AIX_ML were found.
All filesets for 6100-06_AIX_ML were found.
All filesets for 6100-07_AIX_ML were found.
All filesets for 6100-08_AIX_ML were found.
All filesets for 6100-09_AIX_ML were found.
All done, now enjoy.
So I've done the first part of my PowerVC set-up, in this case install of the base code onto the Redhat 6.4 system I prepared. If you're not sure how to do this then I have a number of related articles that cover setting up the repositories, IBM Power Tool, and the networking. So be sure to have a look at those before you get started then you know you have the right packages on the image:
First you need to put the base code on the system, so find the package: gzip -d powervc-install-ppc-rhel-220.127.116.11.tgz and get it copied over:
[root@scend227]# cp gzip -d powervc-install-ppc-rhel-18.104.22.168.tgz /tmp/powervc
[root@scend227]# gzip -d powervc-install-ppc-rhel-22.214.171.124.tgz
[root@scend227]# tar xvf powervc-install-ppc-rhel-126.96.36.199.tar
Not forgetting to unzip and then untar the file, after which just run the install file:
The system then should work its way through its checks, updating the screen:
Before finally finishing, I think it took between 10-15 minutes to install on my 0.5 (12ent) core, 8GB ram system:
I did hit a few issues on my first attempt, the new server was not in DNS so the installer was unable to look it up. As you can imagine it bombed out at that point; also be sure that there is at least 4GB in the related filesystem.
Overall it was very easy to setup, once the install is complete you can access the login page and perform the configuration to talk to your other systems:
As you can see below we are presented with a much cleaner welcome page;
In my next article I'll cover the setting up of PowerVC, including the adding of hosts, storage and networking. But while you wait for that, here are some important details about IBM PowerVC:
IBM PowerVC Requisites – Standard Edition
Standard Edition-specific requisites:
License for PowerVC Standard Edition is no-charge for current SWMA users of:
PowerVC is bundled with the above, so new customers get it too.
Licensing is done per managed host
Express Edition-specific requisites
General requisites (apply to both Express and Standard Edition):
And Finally, some cake: