Edit: I still enjoy the new interfaces. Some links no longer work.
Originally posted October 14, 2014 on AIXchange
After writing about the HMC’s new look, I found that one of my options wasn’t working as expected. When I clicked on Manage PowerVM, I got this error.
I opened a ticket with IBM Support, which sent me to this link to run this procedure:
The apply of V8R8.1.0 Service Pack 1 may cause some VIOS related tasks to fail. Impacted HMC tasks include Manage PowerVM and Manage partitions task in the new “enhanced GUI” as well as the Performance and Capacity Monitor (PCM). External applications using the HMC REST API such as IBM PowerVC are also impacted. The error text will typically include the error message “3003c 2610-366 The action array contains an undefined action name at index 0: VioService.
Contact IBM support for the circumvention until a fix is available.
Symptom: The apply of V8R8.1.0 Service Pack 1 may cause some VIOS RMC related tasks to fail. Impacted HMC tasks include Manage PowerVM and Manage partitions task in the new “enhanced GUI” as well as the Performance and Capacity Monitor (PCM). External applications using the HMC REST API such as IBM PowerVC are also impacted.
For example, the Manage PowerVM task fails with the error:
Exception occurred in Querying for Media Repositories from vios P8TVIO1 with ID 1 in CEC 8286-41A*TU20305 – Network interruption occurs while RMC is waiting for the command execution on the partition to finish. The operation might have caused CPU starvation or network disruption. The operation could have completed successfully. (3003c 2610-366 The action array contains an undefined action name at index 0: VioService. )
This procedure requires you to get a root shell on the HMC, which usually requires the assistance of IBM Support.
However, right around the time of this error, I saw a post on IBM developerWorks that notes another way to become root using the ‘shellshock’ bash security bug. (That post has since been removed, though HMC fixes to fix bash are available from IBM’s Fix Central.)
At the end of the instructions, you’re told to wait for the RMC connections to restart. In my case, nothing happened. I rebooted the HMC, and found this new error:
Support pointed me to this procedure,but then recommended I apply the fix:
“Querying VIOS using the HMC REST API fails with “Exception occurred in Querying for Media Repositories from vios <vios name> with ID <vios lpar id> in CEC <server MTMS> – Unable to connect to Database”. This error usually indicates that the VIOS database is corrupt and needs rebuilt.”
“At VIOS level 2.2.3.1, the resolution is to apply fix VIOS_2.2.3.1-IV52899m1a. No further recovery is needed.”
Seeing as I was at 2.2.3.3, I thought it was an odd suggestion, as 2.2.3.3 already had the fix. However, in the interest of completeness, I wanted to mention the procedure itself. Perhaps it will help with any issues you might encounter.
I decided to update the firmware on the server and reboot all of the LPARs. The Manage PowerVM option started working. Here are some screen shots.
Right-clicking on the active VIO server brought me to a view that looked pretty similar to what I was used to:
When I went to adapter view, it appeared something was missing:
I’ve been able to use the GUI to set up server templates and shared Ethernet adapters — all without needing to login as padmin to the VIO servers. Keep in mind that the “classic” mode still works exactly as you’re used to. The same is true for all of the VIO commands you’re used to.
As I continue to learn about this HMC code, I’ll pass along more information.