メインコンテンツへスキップ

Active IQ Unified Manager仮想マシンのパフォーマンスデータが表示されない

Views:
48
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

環境

Active IQ Unified Manager 9.7+(AIQUM)

問題

  • 仮想マシン(VM)/仮想ホスト(ゲストなど)のパフォーマンスデータは表示されません
  • vCenter のパフォーマンスデータはまったく収集されていません
  • vCenter のパフォーマンス記録がありません
  • インベントリ > 仮想マシンページに次のエラーが表示されます:
    • Metrics data for this vCenter is not yet available. Data collection may take up to an hour after vCenter discovery
  • vCenter の取得が SOAP エラーで失敗する
UIにおける動作:
vcenter_UM97+_error_UI.jpg
 
au.logのエラー
2022-02-15 11:57:10,375 ERROR [common-pool-9526] c.o.s.a.d.v.VCOCIEPerformancePackage (VCOCIEPerformancePackage.java:191) - Got exception... com.sun.xml.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: A specified parameter was not correct: querySpec.interval Please see the server log to find more detail regarding exact cause of the failure.
         at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:193) ~[jaxws-rt.jar:2.3.0]
         at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:136) ~[jaxws-rt.jar:2.3.0]
         at com.sun.xml.ws.client.sei.StubHandler.readResponse(StubHandler.java:253) ~[jaxws-rt.jar:2.3.0]
         at com.sun.xml.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:206) ~[jaxws-rt.jar:2.3.0]
         at com.sun.xml.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:293) ~[jaxws-rt.jar:2.3.0]
         at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119) ~[jaxws-rt.jar:2.3.0]
         at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:92) ~[jaxws-rt.jar:2.3.0]
         at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:161) ~[jaxws-rt.jar:2.3.0]
         at com.sun.proxy.$Proxy7706.queryPerf(Unknown Source) ~[?:?]
         at com.netapp.collectors.vmware.util.VMWareDataFetcher.retrievePerfData(VMWareDataFetcher.java:265) ~[vmware.jar:9.10.0-2022.01.J127]
         at com.netapp.collectors.vmware.util.VMWareDataFetcher.retrievePerfData(VMWareDataFetcher.java:248) ~[vmware.jar:9.10.0-2022.01.J127]
         at com.onaro.sanscreen.acquisition.datasource.vcocie.VCOCIEPerformancePackage.getStatsForMor(VCOCIEPerformancePackage.java:630) ~[au-datasource-vcperformance.jar:9.10.0-2022.01.J127]
         at com.onaro.sanscreen.acquisition.datasource.vcocie.VCOCIEPerformancePackage.getAndReportStatsForVmVirtualDisks(VCOCIEPerformancePackage.java:275) ~[au-datasource-vcperformance.jar:9.10.0-2022.01.J127]
         at com.onaro.sanscreen.acquisition.datasource.vcocie.VCOCIEPerformancePackage.getAndReportPerformanceMetrics(VCOCIEPerformancePackage.java:242) ~[au-datasource-vcperformance.jar:9.10.0-2022.01.J127]
         at com.onaro.sanscreen.acquisition.datasource.vcocie.VCOCIEPerformancePackage.doVCenterPerformance(VCOCIEPerformancePackage.java:174) ~[au-datasource-vcperformance.jar:9.10.0-2022.01.J127]
         at com.onaro.sanscreen.acquisition.vcperformance.datasource.VCPerformancePackage.doFoundationDependantPollNow(VCPerformancePackage.java:206) ~[au-package-vcperformance.jar:9.10.0-2022.01.J127]
         at com.onaro.sanscreen.acquisition.vcfoundation.datasource.dependant.VCFoundationDependantPackage.pollNow(VCFoundationDependantPackage.java:390) ~[au-package-vcfoundation.jar:9.10.0-2022.01.J127]
         at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.run(BaseDataSource.java:269) ~[au-framework.jar:9.10.0-2022.01.J127]
         at com.onaro.sanscreen.acquisition.framework.mgmt.DataSourceManager$PollLogic.run(DataSourceManager.java:756) ~[au-framework.jar:9.10.0-2022.01.J127]
         at com.onaro.sanscreen.acquisition.framework.mgmt.scheduler.SchedulerTask.runLogic(SchedulerTask.java:102) ~[au-framework.jar:9.10.0-2022.01.J127]
         at com.onaro.sanscreen.acquisition.framework.mgmt.scheduler.Scheduler$LogicWrapper.run(Scheduler.java:271) ~[au-framework.jar:9.10.0-2022.01.J127]
         at com.onaro.commons.metrics.executor.ThreadPoolMonitorExecutor.lambda$submit$1(ThreadPoolMonitorExecutor.java:178) ~[commons-commons.jar:9.10.0-2022.01.J127]
         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
         at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
         at com.onaro.commons.metrics.executor.ThreadPoolMonitorExecutor.lambda$execute$0(ThreadPoolMonitorExecutor.java:164) ~[commons-commons.jar:9.10.0-2022.01.J127]
         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
         at java.lang.Thread.run(Thread.java:829) [?:?]
 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.