I have a scenario where I use iSCSI Target 3.3 (windows 2012 native iSCSI Target), where while I power off my Cluster and iSCSI Target and move the POD of equipment to another venue, as I boot my Cluster it is failing to see LUNs.
The order I boot the equipment is:
- Boot iSCSI Target Server - Allow it to come up fully
- Boot First Node on Cluster where the Disks were last active and all the Virtual Machines currently reside
Now after a little troubleshooting, I was going through the iSCSI Initiator and saw it couldn't reach the iSCSI Target. While looking at the iSCSI Target Settings the IP Address for the link (Which was down at boot time, Directly connected to the Cluster-Node) is not listed as an available Portal. It says at the bottom that new IP addresses will be added to the list, but unless I restart the iSCSI Target Service it doesn't repopulate with the Links as they come online.
Anyone else seen this issue? It's a pain in the neck, any other iSCSI Target Vendor out there would allow you to create portals that are specifc to a port and stay online regardless of their link state.
Thanks for your help!