The transition to NetApp MS Azure AD B2C is complete. If you missed the pre-registration, you will be invited to reigister at next log in.
Please note that access to your NetApp data may take up to 1 hour.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

Active IQ Unified Manager Discussions

OCI 6.3.2 HMC Inventory Issue

gmilazzoitag

On a OCI 6.3.2 installation I can acquire data from several HMC consoles except one that gives me an undocumented error. The only difference respect the other

Starting the accquisition after few secs I got this error on OCI:

An unexpected internal runtime error occurred during acquisition of this DataSource.

Details (if any): java.lang.NumberFormatException - For input string: ""

Further information may be available in the acquisition unit log file.

The acq.log states:

2013-01-24 14:55:02,604 FATAL [pool-2-thread-9] com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource (BaseDataSource.java:259) - [foundation] HMC_P5_RAC - Runtime exception: For input string: ""

java.lang.NumberFormatException: For input string: ""

          at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)

          at java.lang.Integer.parseInt(Integer.java:470)

          at com.onaro.sanscreen.acquisition.datasource.ibm_power_vm.builders.BuilderUtils.covertPowerVMLunToDecimal(BuilderUtils.java:41)

          at com.onaro.sanscreen.acquisition.datasource.ibm_power_vm.builders.PhysicalVolumeBuilder.buildPhysicalVolumeDetails(PhysicalVolumeBuilder.java:248)

          at com.onaro.sanscreen.acquisition.datasource.ibm_power_vm.builders.PhysicalVolumeBuilder.buildComponent(PhysicalVolumeBuilder.java:50)

          at com.onaro.sanscreen.acquisition.datasource.ibm_power_vm.builders.VIOServerBuilder.buildComponent(VIOServerBuilder.java:72)

          at com.onaro.sanscreen.acquisition.datasource.ibm_power_vm.builders.PowerVMModelRootBuilder.buildModel(PowerVMModelRootBuilder.java:71)

          at com.onaro.sanscreen.acquisition.datasource.ibm_power_vm.PowerVMFoundationPackage.doFoundation(PowerVMFoundationPackage.java:71)

          at com.onaro.sanscreen.acquisition.foundation.datasource.BaseFoundationPackage.pollNow(BaseFoundationPackage.java:185)

          at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.run(BaseDataSource.java:247)

          at com.onaro.sanscreen.acquisition.framework.mgmt.DataSourceManager$PollLogic.run(DataSourceManager.java:612)

          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

          at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

          at java.util.concurrent.FutureTask.run(FutureTask.java:138)

          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

          at java.lang.Thread.run(Thread.java:662)

2013-01-24 14:55:02,604 ERROR [pool-2-thread-9] com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource (DataSourceErrorException.java:224) - HMC_P5_RAC [Internal error] - For input string: "" ([Device name HMC_P5_RAC]: For input string: "")

com.onaro.sanscreen.acquisition.framework.datasource.DataSourceErrorException: For input string: ""

          at com.onaro.sanscreen.acquisition.framework.datasource.DataSourceErrorException.createWithEnhanced(DataSourceErrorException.java:70)

          at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.run(BaseDataSource.java:262)

          at com.onaro.sanscreen.acquisition.framework.mgmt.DataSourceManager$PollLogic.run(DataSourceManager.java:612)

          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

          at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

          at java.util.concurrent.FutureTask.run(FutureTask.java:138)

          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

          at java.lang.Thread.run(Thread.java:662)

Caused by: java.lang.NumberFormatException: For input string: ""

          at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)

          at java.lang.Integer.parseInt(Integer.java:470)

          at com.onaro.sanscreen.acquisition.datasource.ibm_power_vm.builders.BuilderUtils.covertPowerVMLunToDecimal(BuilderUtils.java:41)

          at com.onaro.sanscreen.acquisition.datasource.ibm_power_vm.builders.PhysicalVolumeBuilder.buildPhysicalVolumeDetails(PhysicalVolumeBuilder.java:248)

          at com.onaro.sanscreen.acquisition.datasource.ibm_power_vm.builders.PhysicalVolumeBuilder.buildComponent(PhysicalVolumeBuilder.java:50)

          at com.onaro.sanscreen.acquisition.datasource.ibm_power_vm.builders.VIOServerBuilder.buildComponent(VIOServerBuilder.java:72)

          at com.onaro.sanscreen.acquisition.datasource.ibm_power_vm.builders.PowerVMModelRootBuilder.buildModel(PowerVMModelRootBuilder.java:71)

          at com.onaro.sanscreen.acquisition.datasource.ibm_power_vm.PowerVMFoundationPackage.doFoundation(PowerVMFoundationPackage.java:71)

          at com.onaro.sanscreen.acquisition.foundation.datasource.BaseFoundationPackage.pollNow(BaseFoundationPackage.java:185)

          at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.run(BaseDataSource.java:247)

          ... 7 more

The event viewer in HMC reports me a list of command issued all regularly performed. User 'monuser' is 'hmcsuperadmin' with all roles.

24/01/2013 14.46.34.970 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsdev -dev hdisk2 -attr correctly executed.

24/01/2013 14.46.34.250 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsdev -dev hdisk19 -attr correctly executed.

24/01/2013 14.46.34.020 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsdev -dev hdisk16 -attr correctly executed.

24/01/2013 14.46.33.590 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsdev -dev hdisk15 -attr correctly executed.

24/01/2013 14.46.33.360 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsdev -dev hdisk14 -attr correctly executed.

24/01/2013 14.46.33.130 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsdev -dev hdisk13 -attr correctly executed.

24/01/2013 14.46.32.880 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsdev -dev hdisk12 -attr correctly executed.

24/01/2013 14.46.32.620 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsdev -dev hdisk11 -attr correctly executed.

24/01/2013 14.46.32.380 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsdev -dev hdisk10 -attr correctly executed.

24/01/2013 14.46.31.940 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsdev -dev hdisk0 -attr correctly executed.

24/01/2013 14.46.31.680 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lspv -fmt , correctly executed.

24/01/2013 14.46.31.250 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsvg -lv rootvg -fmt , correctly executed.

24/01/2013 14.46.30.750 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsvg rootvg -fmt , correctly executed.

24/01/2013 14.46.30.240 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsvg correctly executed.

24/01/2013 14.46.30.000 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsdev -dev fcs* -vpd correctly executed.

24/01/2013 14.46.29.650 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c lsmap -all correctly executed.

24/01/2013 14.46.27.940 HSCE2123 Username monuser: Command viosvrcmd -m 9117-570*101FF42 --id 2 -c ioslevel correctly executed.


3 REPLIES 3

ostiguy

Just to close out the loop - engineering came up with a workaround for the old VIOS version on P5 hardware we encountered. This datasource patch is available from NGS, and will ship in a future Data Source service pack for 6.3.x.

ostiguy

"covertPowerVMLunToDecimal" doesn't appear in any of our bug history. I'd recommend getting a support case open. For your support case, you will want to supply the datasource "recording" zip file for the failing datasource

It is worth mentioning that Data Source Service Pack 4 has been released - this is a way of upgrading your OCI 6.3.2's data source code to the latest and greatest, which happens to be the same level as OCI 6.3.3 . I don't believe installing SP4 will actually solve this issue.

gmilazzoitag

I'll think about it. But this is a POC and after all opening a case will require time and effort to follow it.

I agree with you about patching. I don't think this could solve this particular error.

PS) covert? Maybe they want to write "convert" that makes sense

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public