locked
HP EVA Management Pack 2.0.1.11 - Generic Performance Mapper Module Failed Execution RRS feed

  • Question

  • Hi,

     

    I have installed the "HP EVA Management Pack 2.0.1.11" management pack in our System Center Operations Manager 2007 R2 version 6.1.7221.0.

     

    But I get some alerts that I do not understand why I get the following errors: 

     

     

    1 Module was unable to convert parameter to a double value Original parameter: '$Data/Property[@Name='Value']$' Parameter after $Data replacement: 'maxAge::2Time' Error: 0x80020005 Details: Type mismatch. One or more workflows were affected by this.  Workflow name: EVA.Controller.Processor.Data Instance name: Evaperf Instance ID: {2CA2AA56-9528-6245-A1A9-32FA967BD87C} Management group: SilkSystemCenter
    2 Module was unable to convert parameter to a double value Original parameter: '$Data/Property[@Name='Value']$' Parameter after $Data replacement: 'Total Write Req/s' Error: 0x80020005 Details: Type mismatch. One or more workflows were affected by this.  Workflow name: EVA.Disk.Group.Write.Latency Instance name: Evaperf Instance ID: {2CA2AA56-9528-6245-A1A9-32FA967BD87C} Management group: SilkSystemCenter
    3 Module was unable to convert parameter to a double value Original parameter: '$Data/Property[@Name='Value']$' Parameter after $Data replacement: 'Average Read Hit Latency (ms)' Error: 0x80020005 Details: Type mismatch. One or more workflows were affected by this.  Workflow name: EVA.Disk.Group.Read.Miss.MBs Instance name: Evaperf Instance ID: {2CA2AA56-9528-6245-A1A9-32FA967BD87C} Management group: SilkSystemCenter
    4 Module was unable to convert parameter to a double value Original parameter: '$Data/Property[@Name='Value']$' Parameter after $Data replacement: 'Average Read Miss Latency (ms)' Error: 0x80020005 Details: Type mismatch. One or more workflows were affected by this.  Workflow name: EVA.Disk.Group.Write.MBs Instance name: Evaperf Instance ID: {2CA2AA56-9528-6245-A1A9-32FA967BD87C} Management group: SilkSystemCenter
    5 Module was unable to convert parameter to a double value Original parameter: '$Data/Property[@Name='Value']$' Parameter after $Data replacement: 'Write MB/s' Error: 0x80020005 Details: Type mismatch. One or more workflows were affected by this.  Workflow name: EVA.Virtual.Disk.Write.MBs Instance name: Evaperf Instance ID: {2CA2AA56-9528-6245-A1A9-32FA967BD87C} Management group: SilkSystemCenter
    6 Module was unable to convert parameter to a double value Original parameter: '$Data/Property[@Name='Value']$' Parameter after $Data replacement: 'Total Read Miss Req/s' Error: 0x80020005 Details: Type mismatch. One or more workflows were affected by this.  Workflow name: EVA.Disk.Group.Read.Miss.Latency Instance name: Evaperf Instance ID: {2CA2AA56-9528-6245-A1A9-32FA967BD87C} Management group: SilkSystemCenter
    7 Module was unable to convert parameter to a double value Original parameter: '$Data/Property[@Name='Value']$' Parameter after $Data replacement: 'Disk Group' Error: 0x80020005 Details: Type mismatch. One or more workflows were affected by this.  Workflow name: EVA.Disk.Group.Read.Hit.MBs Instance name: Evaperf Instance ID: {2CA2AA56-9528-6245-A1A9-32FA967BD87C} Management group: SilkSystemCenter
    8 Module was unable to convert parameter to a double value Original parameter: '$Data/Property[@Name='Value']$' Parameter after $Data replacement: 'Total Read Miss MB/s' Error: 0x80020005 Details: Type mismatch. One or more workflows were affected by this.  Workflow name: EVA.Disk.Group.Write.Reqs Instance name: Evaperf Instance ID: {2CA2AA56-9528-6245-A1A9-32FA967BD87C} Management group: SilkSystemCenter
    9 Module was unable to convert parameter to a double value Original parameter: '$Data/Property[@Name='Value']$' Parameter after $Data replacement: 'Write Latency (ms)' Error: 0x80020005 Details: Type mismatch. One or more workflows were affected by this.  Workflow name: EVA.Virtual.Disk.Write.Latency Instance name: Evaperf Instance ID: {2CA2AA56-9528-6245-A1A9-32FA967BD87C} Management group: SilkSystemCenter
    10 Module was unable to convert parameter to a double value Original parameter: '$Data/Property[@Name='Value']$' Parameter after $Data replacement: 'maxAge::2Time' Error: 0x80020005 Details: Type mismatch. One or more workflows were affected by this.  Workflow name: EVA.Disk.Group.Read.Hit.Reqs Instance name: Evaperf Instance ID: {2CA2AA56-9528-6245-A1A9-32FA967BD87C} Management group: SilkSystemCenter
    11 Module was unable to convert parameter to a double value Original parameter: '$Data/Property[@Name='Value']$' Parameter after $Data replacement: 'Total Read Hit MB/s' Error: 0x80020005 Details: Type mismatch. One or more workflows were affected by this.  Workflow name: EVA.Disk.Group.Read.Miss.Reqs Instance name: Evaperf Instance ID: {2CA2AA56-9528-6245-A1A9-32FA967BD87C} Management group: SilkSystemCenter
    12 Module was unable to convert parameter to a double value Original parameter: '$Data/Property[@Name='Value']$' Parameter after $Data replacement: 'Total Read Hit Req/s' Error: 0x80020005 Details: Type mismatch. One or more workflows were affected by this.  Workflow name: EVA.Disk.Group.Read.Hit.Latency Instance name: Evaperf Instance ID: {2CA2AA56-9528-6245-A1A9-32FA967BD87C} Management group: SilkSystemCenter

     

    I have not been able to find any information about if the language error in the DHCP Management Pack (http://social.technet.microsoft.com/Forums/en-US/operationsmanagermgmtpacks/thread/76bce6c3-9aa4-49f7-9290-f7ad16bfadf4) is the same in the "HP EVA Management" management pack.

     

    I have just tried to change the language to American from Danish and restarted the "System Center Management" service on the server, but the alerts have not been closed by SCOM so far yet.

     

    It is not possible to file the error to Microsoft in the http://connect.microsoft.com/directory/accepting-bugs/servers/ because the System Center Operation Manager is not listed in there :-(

     

    Do you have any experience on this?

     

    Kind regards,

    Carl-Marius

    Friday, June 10, 2011 7:24 AM

Answers

  • Hi,

    It looks like some files in c:\temp contain only headers, no data...

    > but the alerts have not been closed by SCOM so far yet.

    THis alerts will not be closed by OpsMgr because this alerts are generated by a rule. You need to close it manually. 

    BTW, you can try the v3: HP EVA Performance Management Pack v3


    http://OpsMgr.ru/
    • Marked as answer by Yog Li Wednesday, June 22, 2011 11:48 AM
    Friday, June 10, 2011 7:47 AM

All replies

  • Hi,

    It looks like some files in c:\temp contain only headers, no data...

    > but the alerts have not been closed by SCOM so far yet.

    THis alerts will not be closed by OpsMgr because this alerts are generated by a rule. You need to close it manually. 

    BTW, you can try the v3: HP EVA Performance Management Pack v3


    http://OpsMgr.ru/
    • Marked as answer by Yog Li Wednesday, June 22, 2011 11:48 AM
    Friday, June 10, 2011 7:47 AM
  • Hi Alexey,

    I have just looked through the files in the C:\temp on the server, and it does seem like all the files contains data.

     

    I have the following files in the c:\temp folder:

    EVAPERF_cs.csv

    EVAPERF_drt.csv

    EVAPERF_EVA_Discovery.csv

    EVAPERF_EVA_Disk_Group_Discovery_SK-EVA01.csv

    EVAPERF_EVA_Disk_Group_Discovery_SK-EVA02.csv

    EVAPERF_hps.csv

    EVAPERF_pd.csv

    EVAPERF_vd.csv

    EVAPERF_vd_top_diag.csv

    EVAPERF_vdg.csv

     

     

    The file "EVAPERF_cs.csv" has the following content:

    Time,CPU %,Data %,Ctlr,Serial,Node
    10/Jun/2011 10:02:04,6,5,5015,PBA23F19SV5015,SK-EVA02
    10/Jun/2011 10:02:04,8,8,I0BK,PBA23F29SWI0BK,SK-EVA02
    10/Jun/2011 10:02:04,0,0,I08E,P5849D3AAOI08E,SK-EVA01
    10/Jun/2011 10:02:04,0,0,I08B,P5849D3AAOI08B,SK-EVA01

     

     

    The file "EVAPERF_EVA_Disk_Group_Discovery_SK-EVA02.csv" has the following content:

    Time,Disk Group,Total Read Hit Req/s,Total Read Hit MB/s,Average Read Hit Latency (ms),Total Read Miss Req/s,Total Read Miss MB/s,Average Read Miss Latency (ms),Total Write Req/s,Total Write MB/s,Average Write Latency (ms),Total Flush MB/s,Total Mirror MB/s,Total Prefetch MB/s,Ctlr,Node
    10/Jun/2011 09:08:01,01,0,0.00,0.0,0,0.00,0.0,22,0.14,0.2,0.00,0.14,0.00,I08B,SK-EVA01
    10/Jun/2011 09:08:01,01,0,0.00,0.0,0,0.00,0.0,0,0.00,0.0,0.00,0.00,0.00,I08E,SK-EVA01
    10/Jun/2011 09:08:01,HP1TBFATA,0,0.00,0.0,40,15.53,13.8,8,3.35,174.2,0.00,3.35,0.00,5015,SK-EVA02
    10/Jun/2011 09:08:01,HP1TBFATA,0,0.00,0.0,40,15.66,11.2,24,7.75,157.1,11.17,34.50,0.00,I0BK,SK-EVA02
    10/Jun/2011 09:08:01,HP300GB10K,73,2.72,10.0,240,3.23,10.2,224,1.98,0.4,1.82,3.63,3.35,5015,SK-EVA02
    10/Jun/2011 09:08:01,HP300GB10K,72,2.20,3.8,453,6.44,7.8,491,5.54,0.5,5.47,10.28,3.42,I0BK,SK-EVA02
    10/Jun/2011 09:08:01,HP300GB15K,8,0.14,0.1,28,0.48,3.7,61,0.54,0.6,0.46,1.00,0.03,5015,SK-EVA02
    10/Jun/2011 09:08:01,HP300GB15K,43,1.76,0.2,86,1.35,4.9,199,3.11,0.6,3.15,6.28,0.06,I0BK,SK-EVA02

     

    Thank you for the link to v3, I will give it a try if I cannot remove this error in v2 :)

    Kind regards,

    Carl-Marius

    Friday, June 10, 2011 8:02 AM
  • Hi Carl,

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios.

    In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

    Thanks,


    Yog Li -- Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, June 22, 2011 11:48 AM
  • Hi Yog Li,

     

    I have not found a solution yet on this issue, but I am sure that the solution is in Alexey Zhuravlev response above, I have just not had the time to test it :)

     

    I will post my result when I get so far :).

     

    Kind regards,

    Carl-Marius


    Thursday, June 23, 2011 12:40 PM
  • Hi,

    Just to complete this thread, I have not had the time to test v3 of this management pack, so I have just disabled all these errors.

     

    Kind regards,

    Carl-Marius

    Thursday, June 30, 2011 5:54 AM