This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
The customer found they can't add the virtual adapter last Friday.The HMC called out the HMC could not visit the VIOS database.We asked the customer collected the pedbg,iqyy and the VIOSs' snap.Then we opened a PMH 57449,141,672.The tsg thought the hardware is normal.RMC maybe the root cause and suggest we update the HMC version to the latest.If the problem still, tsg asked us to open a PMS, he thought it is not a hw problem or hmc problem.We found the RMC was active state at that time.Then the customer follow the action plan to update the HMC version from V9R1M911 to V9R1M920.But the problem still.But the customer is hurry to install the system this Tuesday.So we did the below action. 1.Try to reinstalled the VIOS system through HMC iso mapping.But the process hung. 2.Delete the VIOS profiles from the HMC. 3.Factory config the machine. 4.Reinstalled VIOS systems throught USB removable DVD.The action succeeded. Then we found we can config the virtual storage. Above is the situaton before we open this PMS.
Yesterday, the customer want to install another producure system on this machine.During the Tuesday to Thursday, the customer did nothing on this machine.They sured there was no network change these day.They found the problem happened again.RMC state are active.And ping from the VIOS to HMC, HMC to VIOS, were all normal.Then we did some test and found some bugs.
1.We tried to change the IP of VIOS which used to connect with the HMC.We used the padmin and the cfgassist commond to change it.The output is OK.But we found the IP not be changed.Because we used ping commond ,we found the server itself is used the old IP.Then we enter the oem enviroment used the oem_setup_env commond.The smit tcpip can change the IP.But from the HMC side we can found the ip info was not overwrite. 2.We tried to changed the hostname, nor the padmin or the root could not change it.We only can use the commond to change it. 3.After some time the state of RMC of VIOS actived(because we changed the IP),but the virtual storage still can't use.The HMC called out the HMC could not visit the VIOS database. 4.We rebooted the VIOS.We found the HMC info changed.But from the VIOS side, we found the ping HMC, the VIOS IP still the old.We outputed the /etc/hosts file.We found the old and the new IP were all there.Then we did more test.We pinged VIOS itself after we changed the ip through root.The ping will failed.The only way we changed the IP is to delete the old ip from the /etc/hosts. 5.The virtual storage can use after setup4. 6.We found another bug.The virtual storage only can discover 3 hdisk which are the inside disks of machine.VIOS2's hdisk3 can't be discovered.We found we can use the commond mkvdev to mapping this disk to VIOC.But we still can't find this disk in INUSE table.INUSE table only output four rootvg disk of VIOSs. 7.We delete the mapping of VIOS2's hdisk3,then we can find this disk appeared in the list.We reboot the system.Then the disk missed again. 8.We used created a new partition from the HMC side.We found the VIOS didn't add a new vhost before we mapped the virtual storage to it.Then we did the setup7 again.The situation is still.
Do not place IBM confidential, company confidential, or personal information into any field.