Unable to initialize BlackArmor after running iSCSI Manager and Windows 7 iSCSI Initiator

The trick is set the "port number" parameter in the AddTargetPortal command in iscsicli.

However, the only way I was able to associate this port number with an actual IP address is using WMI. In order to figure this out, I used PowerShell

Function Get-IscsiPortNumber {

$query = "select portalinformation from msIsci_portalinfoclass"                                       
$portalInfo = get-wmiobject -namespace root\wmi -query $query
$eScriptBlock ={([Net.IPAddress]$_.ipaddr.IPV4Address).IPAddressToString}
$customLabel = @{Label="IpAddress"; expression = $eScriptBlock}
$portalInfo.portalInformation | select port,$customlabel

}

Once you track down the port number (let's say 2) you can use the following to add the target portal assuming the target has an ip of 10.10.10.10. The port number comes after the initiator name, ROOT\ISCSIPRT\0000_0

iscsicli addtargetportal 10.10.10.10 3260 ROOT\ISCSIPRT\0000_0 2 * * * * * * * * * *

Looks like I've already answered this one on ru_root, but for the record:

• disable tcp offloading. and generally go over ProSet's options, might be something worthwhile in there
• check the initiator for a persistent connection option, I remember something of the sort in there
• If MPIO is used, it is possible that you're losing a path and not the connection
• If everything else fails, I'd get a tcpdump and analyse it for iSCSI related traffic issues.

BTW, if you're using a team, it will not work with MPIO apparently: http://technet.microsoft.com/en-us/library/ee338480(WS.10).aspx