Hi Manjunath & the HMC developement team!

It seems that the upgrade vios function is "hardcoded" to use dvdimage.v1.iso & dvdimage.v2.iso as media files, but actually we tend to use the Flash image like Virtual_IO_Server_Base_Install_4.1.0.10_Flash_112023_LCD8292400.iso when upgrading.

I was able to upload the image during the process and upon a rerun (due to efixes not getting uninstalled) it showed up as an imgaefile on the HMC, so I selected it. But the upgrade still failed with an error message indicating that the file "dvdimage.v1.iso" couldn't be found in /home/padmin.

So I think the procedure should be rewritten to accept any given name of the image and also it shouldn't be mandatory to provide a filename for the second image as there is none when using flash images.

Hi Manjunath & the HMC developement team!

It seems that the upgrade vios function is "hardcoded" to use dvdimage.v1.iso & dvdimage.v2.iso as media files, but actually we tend to use the Flash image like Virtual_IO_Server_Base_Install_4.1.0.10_Flash_112023_LCD8292400.iso when upgrading.

I was able to upload the image during the process and upon a rerun (due to efixes not getting uninstalled) it showed up as an imgaefile on the HMC, so I selected it. But the upgrade still failed with an error message indicating that the file "dvdimage.v1.iso" couldn't be found in /home/padmin.

So I think the procedure should be rewritten to accept any given name of the image and also it shouldn't be mandatory to provide a filename for the second image as there is none when using flash images.

Hi Henrik,

HMC do not mandate specifying the VIOS image name to be dvdimage.v1.iso/dvdimage.v2.iso. You can specify the name as you wish. If there are 2 images for the VIOS upgrade, then we consider first image that you specified as DVD1 image and second one as DVD2 image.

I am not sure how you imported the VIOS image into HMC. But if you have used VIOS upgrade task and specified "Virtual_IO_Server_Base_Install_4.1.0.10_Flash_112023_LCD8292400.iso" to be imported from remote SFTP/NFS server, then as first step HMC will import the image into its file system and rename it as dvdimage.v1.iso. And then it copies the image into VIOS and perform the upgrade task. 

So the procedure do accept any file name of the image. And it accept one or 2 ISO image as part of the upgrade. If you still see failure, i would request you to open a case to debug the issue further. Thanks!

-Manju

Hi Manjunath & the HMC developement team!

It seems that the upgrade vios function is "hardcoded" to use dvdimage.v1.iso & dvdimage.v2.iso as media files, but actually we tend to use the Flash image like Virtual_IO_Server_Base_Install_4.1.0.10_Flash_112023_LCD8292400.iso when upgrading.

I was able to upload the image during the process and upon a rerun (due to efixes not getting uninstalled) it showed up as an imgaefile on the HMC, so I selected it. But the upgrade still failed with an error message indicating that the file "dvdimage.v1.iso" couldn't be found in /home/padmin.

So I think the procedure should be rewritten to accept any given name of the image and also it shouldn't be mandatory to provide a filename for the second image as there is none when using flash images.

Dear Team,

Regarding the image file, I have questions.
What is possible if you don't have the option to use nfs/sftp/usb to copy the image file to the HMC?
Can I place the image file from a Windows dfs share directly  in /home/hscroot? I tried the latter but the upgrade procedure on the HMC does not "see" the image file. Even though I named it dvdimage.v1.iso. For your information. I downloaded the 4.1.2 iso directly from ESS.

Kind regards,

Philip.

Hi Henrik,

HMC do not mandate specifying the VIOS image name to be dvdimage.v1.iso/dvdimage.v2.iso. You can specify the name as you wish. If there are 2 images for the VIOS upgrade, then we consider first image that you specified as DVD1 image and second one as DVD2 image.

I am not sure how you imported the VIOS image into HMC. But if you have used VIOS upgrade task and specified "Virtual_IO_Server_Base_Install_4.1.0.10_Flash_112023_LCD8292400.iso" to be imported from remote SFTP/NFS server, then as first step HMC will import the image into its file system and rename it as dvdimage.v1.iso. And then it copies the image into VIOS and perform the upgrade task. 

So the procedure do accept any file name of the image. And it accept one or 2 ISO image as part of the upgrade. If you still see failure, i would request you to open a case to debug the issue further. Thanks!

-Manju

Hi Manjunath & the HMC developement team!

It seems that the upgrade vios function is "hardcoded" to use dvdimage.v1.iso & dvdimage.v2.iso as media files, but actually we tend to use the Flash image like Virtual_IO_Server_Base_Install_4.1.0.10_Flash_112023_LCD8292400.iso when upgrading.

I was able to upload the image during the process and upon a rerun (due to efixes not getting uninstalled) it showed up as an imgaefile on the HMC, so I selected it. But the upgrade still failed with an error message indicating that the file "dvdimage.v1.iso" couldn't be found in /home/padmin.

So I think the procedure should be rewritten to accept any given name of the image and also it shouldn't be mandatory to provide a filename for the second image as there is none when using flash images.

Yes, you can upload your *.iso file to homedirectory and then import over cli. 

cpviosimg -r disk -n VIOS4 -f VIOSV4120.iso -d /home/hscroot/

Dear Team,

Regarding the image file, I have questions.
What is possible if you don't have the option to use nfs/sftp/usb to copy the image file to the HMC?
Can I place the image file from a Windows dfs share directly  in /home/hscroot? I tried the latter but the upgrade procedure on the HMC does not "see" the image file. Even though I named it dvdimage.v1.iso. For your information. I downloaded the 4.1.2 iso directly from ESS.

Kind regards,

Philip.

Hi Henrik,

HMC do not mandate specifying the VIOS image name to be dvdimage.v1.iso/dvdimage.v2.iso. You can specify the name as you wish. If there are 2 images for the VIOS upgrade, then we consider first image that you specified as DVD1 image and second one as DVD2 image.

I am not sure how you imported the VIOS image into HMC. But if you have used VIOS upgrade task and specified "Virtual_IO_Server_Base_Install_4.1.0.10_Flash_112023_LCD8292400.iso" to be imported from remote SFTP/NFS server, then as first step HMC will import the image into its file system and rename it as dvdimage.v1.iso. And then it copies the image into VIOS and perform the upgrade task. 

So the procedure do accept any file name of the image. And it accept one or 2 ISO image as part of the upgrade. If you still see failure, i would request you to open a case to debug the issue further. Thanks!

-Manju

Hi Manjunath & the HMC developement team!

It seems that the upgrade vios function is "hardcoded" to use dvdimage.v1.iso & dvdimage.v2.iso as media files, but actually we tend to use the Flash image like Virtual_IO_Server_Base_Install_4.1.0.10_Flash_112023_LCD8292400.iso when upgrading.

I was able to upload the image during the process and upon a rerun (due to efixes not getting uninstalled) it showed up as an imgaefile on the HMC, so I selected it. But the upgrade still failed with an error message indicating that the file "dvdimage.v1.iso" couldn't be found in /home/padmin.

So I think the procedure should be rewritten to accept any given name of the image and also it shouldn't be mandatory to provide a filename for the second image as there is none when using flash images.

Respectfully sir, I disagree.   The -r flag is not an option for cpviosimg.

hscroot:~> cpviosimg -r disk -n LCD8298701_VIOS_4-1-1-00 -f LCD8298701_VIOS_4-1-1-00.iso -d /home/hscroot
An invalid parameter value was entered.  The parameter -r is empty or not valid.  Please check your entry and retry the command.

the man page for cpviosimg does not show a "disk" option for the -r flag.  Valid options are 
"-r {nfs | sftp | usb} "

I'm seeing this on a 7063-CR2 running RM V10R2 1031.0

I was very excited to see your post as this HMC is at a remote location and I did not want to have to make USBs and ship them and have support personnel put them in the HMCs for me.   I sincerely wish it worked, but thats not what I am seeing. 

I have tried using an "sftp loop" an pointing the command to the local host address, that appears to work, but then only creates an image that is 4k in size and quits. 

If anyone has a workaround, I would be thrilled to know about it, as I've been struggling with this for a week. 

Yes, you can upload your *.iso file to homedirectory and then import over cli. 

cpviosimg -r disk -n VIOS4 -f VIOSV4120.iso -d /home/hscroot/

Dear Team,

Regarding the image file, I have questions.
What is possible if you don't have the option to use nfs/sftp/usb to copy the image file to the HMC?
Can I place the image file from a Windows dfs share directly  in /home/hscroot? I tried the latter but the upgrade procedure on the HMC does not "see" the image file. Even though I named it dvdimage.v1.iso. For your information. I downloaded the 4.1.2 iso directly from ESS.

Kind regards,

Philip.

Hi Henrik,

HMC do not mandate specifying the VIOS image name to be dvdimage.v1.iso/dvdimage.v2.iso. You can specify the name as you wish. If there are 2 images for the VIOS upgrade, then we consider first image that you specified as DVD1 image and second one as DVD2 image.

I am not sure how you imported the VIOS image into HMC. But if you have used VIOS upgrade task and specified "Virtual_IO_Server_Base_Install_4.1.0.10_Flash_112023_LCD8292400.iso" to be imported from remote SFTP/NFS server, then as first step HMC will import the image into its file system and rename it as dvdimage.v1.iso. And then it copies the image into VIOS and perform the upgrade task. 

So the procedure do accept any file name of the image. And it accept one or 2 ISO image as part of the upgrade. If you still see failure, i would request you to open a case to debug the issue further. Thanks!

-Manju

Hi Manjunath & the HMC developement team!

It seems that the upgrade vios function is "hardcoded" to use dvdimage.v1.iso & dvdimage.v2.iso as media files, but actually we tend to use the Flash image like Virtual_IO_Server_Base_Install_4.1.0.10_Flash_112023_LCD8292400.iso when upgrading.

I was able to upload the image during the process and upon a rerun (due to efixes not getting uninstalled) it showed up as an imgaefile on the HMC, so I selected it. But the upgrade still failed with an error message indicating that the file "dvdimage.v1.iso" couldn't be found in /home/padmin.

So I think the procedure should be rewritten to accept any given name of the image and also it shouldn't be mandatory to provide a filename for the second image as there is none when using flash images.