The Virtual HMC Continues to Evolve
Rob McNelly shares updates on zero planned downtime and HMC problem determination, and reflects on how the online world sounded at its inception
There have been discussions around the virtual HMC lately. For starters, IBM Support has this explainer on upgrading:
“This document provides instructions to upgrade a vHMC for x86 from V10R2M1030 (or higher) to V11R1M1110. The V11 HMC product will support Power9, Power10 and Power11 systems, so if you have older Power systems such as Power8, then be advised those will not be managed post upgrade of the HMC. There are two methods such as upgrading using network images or using the HMC GUI and each will be detailed below. Once you complete the prerequisite steps, you can skip to the section of the document that details the upgrade method you want to use to complete the task.”
For more general information about the vHMC, I recommend this overview. It answered all my questions, including:
“Q: Are existing HMC customers entitled to vHMC?
A: No. vHMC is a separate offering and must be purchased separately. There is no conversion and no upgrade offering.
“Q: Can x86-based vHMC licenses (5765-HMV) be converted to POWER vHMC (5765-HMA)?
A: No. They are two different offerings.”
The document goes on to explain that the Power vHMC cannot manage (nor service) the server it is hosted on. Again, from the overview:
“For example, HMC virtual appliance A is running on server A and HMC virtual appliance B is running on server B. HMC virtual appliance A cannot manage server B and HMC virtual appliance B cannot manage server A at the same time. One of the HMC virtual appliance can manage the other server, but both HMC virtual appliance cannot manage each other at the same time.”
I wrote about testing a few years ago, and have since witnessed a pretty significant number of customers who find value in using the vHMC alongside the traditional HMC.
Where to Start With a Busy RMC Status Code
For PowerVM/VIOS users, this doc tells you what to do if the RMC has a status code of busy. Short answer: Your problem might stem from an incorrectly sized VIOS.
IBM Support says these steps should only be followed after checking:
* VIOS resources (Virtual I/O Server Performance Advisor)
* HMC RMC (Checking the status of RMC connections)
* PowerVC resources (Planning for performance)
After checking these links, there are instructions for refreshing cmdb. If that doesn’t work, there are instructions for more aggressive actions.
Zero Planned Downtime in Power11
IBM’s Artur Studzian explains:
“Zero Planned Downtime with Power11 means you can perform necessary system maintenance, updates, and upgrades without ever taking your critical applications offline. Through advanced technologies like live updates, rolling upgrades, and autonomous patching, this capability eliminates the impact of scheduled service interruptions, ensuring continuous operations and maximum staff productivity.”
A quick caveat: While I love that this capability exists and that more work is being done in this area, I will always have a plan for backing out and restoring if things don’t go as expected.
HMC Problem Determination: An Update
I previously cited this information on collecting PEDBG from the HMC, but it’s worth mentioning again because IBM now requires a Support ID if you plan to use Secure FTP to send your file. The process is quick and easy; I’ve done it. Just keep that in mind when you’re sending data to IBM Support:
“This document describes how to collect diagnostic data from the HMC for problem determination. This document references the HMC enhanced UI in the preparation section. Enhanced UI is available in HMC Version 8 and later.”
Step 1: Log in as user hscpe.
Step 2: Recreate the problem.
Step 3: Collect pedbg.
“Section 3. Getting the Data to IBM:There are many ways the data can be sent to IBM. The following is a list of preferred methods, starting with the quickest and easiest method. The method used varies depending on the type of network access available to the HMC and the availability of media.
“Secure FTP directly from HMC to IBM: IBM no longer allows unsecured FTP. Either the -S or -s flags must be used for secure file transfer.
“If the HMC has a network connection that allows Secure FTP (SFTP) to the Internet, type the following command to send the file directly to IBM Support via ECuRep:
sendfile -S -f /dump/HMClogsxxxxxxxx.zip -h sftp.ecurep.ibm.com -d /toibm/hw/ -n TSddddddddd.HMClogsxxxxxxxxx.zip -u Your_IBM_Support_File_Transfer_ID
“Upload to ECuRep requires an IBM Support File Transfer ID. The IBM Support File Transfer ID is valid until revoked. The password part of it is only displayed at creation time. If the password to a Transfer ID is lost, you must delete the Transfer ID and create a new one. Each IBM Support Transfer ID is linked an IBMid. If you do not already have an IBMid, you can obtain one here.”
Share Your Thoughts on AIX Automation
Register your thoughts on AIX automation by taking this brief survey. Feedback will be used to shape AIX plans for improvements and new automation use cases. All responses are anonymous.
Dial Up Modem Sounds, From 300 bps to 56K
For those of a certain age, here’s a blast from the past:
Recently I was talking to some teenagers, trying to describe a world that no longer exists, yet still feels like only yesterday.
Of course this was long before WiFi or cell phones. To even login to any system required proactive steps, which were accompanied by those distinct sounds that are baked into my memory.
Only a small subset of the population was even online in the 80s. We had landlines, dial-up, Gopher, Usenet and bulletin board systems. We dreamed of connecting to WOPR to play global thermonuclear war. Images were rare. I’d read the text that came across my screen just as fast as it came in.
I’m not sure I could effectively communicate what my life was like back when I relied on pagers and pay phones. It made me think of my grandparents trying to tell me about the times before the automobile or electricity.
Speaking to those kids was another reminder of the things I now take for granted. My internet provider recently doubled the speed I can get at home. I noticed this difference immediately, and yet it felt fleeting. Already I’m conditioned to those blazing speeds and am anticipating even more updates and enhancements in the near future.
These days, even when camping or hiking, it’s rare when I cannot get a signal. If I travel with devices that connect to satellites, I can go almost anywhere on earth and get online without much trouble.
So I listen to those long-ago sounds of modems connecting. I recall what I had—that jump to 56K was incredible when compared to the 300-baud acoustic coupler I started with—and how I once treasured it.
Then I’m reminded that time marches on.