How can I safely change iSCSI initiator properties on a two node Cluster

  • Got some iSCSI issues on my Cluster. After reviewing the case with Microsoft and apply a MS hotfix (see my other thread about it) ... a Microsoft Engineer suggest the following to us:

    iSCSI changes:

    -Under Discovery, select Discover Portal, and re-enter the iSCSI targets by manually typing them.

    -Go to Targets tab, select each target, hit Connect, then Advanced. Instead of Default, change local adapter to Microsoft iSCSI Initiator

    -Specify actual IP addresses on "Initiator IP" and "Target portal IP". Specify "Microsoft iSCSI initiator" on "Local Adapter"

    -Accept changes. Click ok and reboot.

    -Repeat on other node

    I guess that above changes should be applied like any other regular and normal Os change or patch, is that correct? Here the additional Cluster steps, to make it safe:

    -Remove passive node from list of owners

    -Perform iSCSI changes

    -Add removed node back to Cluster

    -Failover all resources to the node with new iSCSI changes

    -Check SQL

    -Remove other node from list of owners

    -Perform iSCSI changes

    -Add removed node back to Cluster

    -Check SQL

    Any comments or suggestions?

Viewing 0 posts

You must be logged in to reply to this topic. Login to reply