locked
HPC R2 (Beta-2) iSCSI compute node deployment - missing cluster manager iSCSI Deployment Task list? RRS feed

  • Question

  • In HPC Cluster Manager, Configuration, iSCSI Deployment, the iSCSI deployment task list is missing?

    HPC head-node iSCSI provider can see/acess mounted WSS vdisks. Missing iSCSI deployment task list in order to add iSCSI target portals per HPC-R2_SxSiSCSI.doc.

    Suggestions?

    TIA.

    Stan.

    Tuesday, April 6, 2010 8:49 PM

Answers

  • you need to get the beta2 iscsi provider for this, you are seeing a version mismatch issue.

    thanks


    pm
    • Marked as answer by parmita mehta Monday, April 12, 2010 6:52 PM
    Monday, April 12, 2010 6:52 PM

All replies

  • Stan,

    it seems like you have the wss iscsi provider installed on the head node, could you tell me where you got this provider from ( and the version number?). Also,  can you tell me what you see on the Configuration pane ->iscsi Deployment page?

    thanks

     

     


    pm
    Wednesday, April 7, 2010 6:09 PM
  • Hello,

    WSS iSCSI Software target Client 3.2.0 per TechNet article.

    Should this be uninstalled? This provider works fine with the WSS target in that iSCSI vdisks are located, mounted and usable.

    Storage Explore also finds WSS based iSCSI vdisks.

    After installing HPC Beta-2 hpc_wintarget_provider.msi on the HPC head-node, we now have task list entries in the Configuration pane ->iscsi Deployment.

    Thanks for the updated HPC step-by-step guide @ http://technet.microsoft.com/en-us/library/ee918811(WS.10).aspx

    The 1st HPC head-node configuration pane --> iSCSI Deployment task 'Add iSCSI Storage Arrays' failed in validating an existing iSCSI target via IPv4 address with the following error message:

    Method 'MapLun' in type 'MsIScsiProvider.MsIScsiProvider' from assembly 'MsIScsiProvider, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null' does not have an implementation.

     The iSCSI storage explorer and/or iSCSI initiator properties both locate/access the iSCSI target @ correct IPv4 address.

    Suggestions?

     

    Thursday, April 8, 2010 5:22 PM
  • you need to get the beta2 iscsi provider for this, you are seeing a version mismatch issue.

    thanks


    pm
    • Marked as answer by parmita mehta Monday, April 12, 2010 6:52 PM
    Monday, April 12, 2010 6:52 PM
  • What is hpc_wintarget_provider.msi? Is it provider lib to communicate HPC Cluster Manager and iSCSI Software target Client 3.2.0? If yes where can i get it?
    • Proposed as answer by Chubij Daniil Tuesday, May 18, 2010 5:45 PM
    Monday, May 17, 2010 9:00 PM