In using the advanced options when introducing an iSCSI session for a host, I am able to provide valid target portal and initiator IPs. However when viewing the iSCSI connection on the host, the initiator IP always registers as 0.0.0.0 instead of the provided initiator IP from VMM. As a result, I cannot create multiple iSCSI sessions through VMM, and therefore, have to manage my iSCSI sessions through Windows.
The create iSCSI session action uses the Set-SCInternetSCSIHba cmdlet. However, I haven't been able to find out how to pass the right objects in this command to get it to work properly.
The 0.0.0.0 address seems like it's a bug. Have any of you experienced this problem before?
MCITP Windows 7 MCTS Windows Server 2008