Verifying the Migration
This topic discusses the steps that you can use to verify that the migration successfully completed.
Verifying the destination server configuration
To verify that the destination server has been properly configured after migration, you can verify the listening endpoints and connectivity and run a scan with the Best Practices Analyzer.
Verify the listening endpoints
On the iSCSI Software Target server, you can validate that the target portals have been configured as desired by using the following Windows PowerShell command:
PS > & netstat.exe -nao | findstr 3260 | findstr LISTENING TCP 10.121.26.107:3260 0.0.0.0:0 LISTENING 1560 TCP 10.121.26.126:3260 0.0.0.0:0 LISTENING 1560 TCP [2001:4898:0:fff:0:5efe:10.121.26.126]:3260 [::]:0 LISTENING 1560 TCP [2001:4898:f0:1001:f063:8fc5:52e6:2310]:3260 [::]:0 LISTENING 1560
The list of IP addresses and port pairs in the listening state needs to match the desired set of target portals.
|If ports other than the default 3260 are being used, the command needs to be altered to reflect the alternate IP ports.|
Verify the basic connectivity
To validate that the iSCSI Software Target server is reachable from other computers on the network, from a computer that has the Telnet Client feature installed, use the following Windows PowerShell command:
PS > telnet.exe <iSCSI Software Target machine name or IP> 3260
If there is a successful connection, Telnet Client will show a blinking cursor at the top of the window. Press any key to close Telnet Client.
Perform a Best Practices Analyzer scan
To verify that Microsoft iSCSI Software Target 3.3 is optimally configured on Windows Server 2008 R2 after migration, we recommend that you run a Best Practices Analyzer (BPA) scan on the role.
BPA is a server management tool that is available in Windows Server 2008 R2. After the migration of Microsoft iSCSI Software Target 3.3 to Windows Server 2008 R2 is complete, BPA can help you ensure that your server is configured according to best practices. You can use the Server Manager console UI or Windows PowerShell to perform BPA scans and view results. For detailed information about how to scan your role and view results, see the Best Practices Analyzer Help (http://go.microsoft.com/fwlink/?LinkId=122786).
Verifying the configuration of other computers in the enterprise
Validating the migration of Microsoft iSCSI Software Target 3.3 to the destination server includes ensuring that the iSCSI initiators can discover and fully access all features of the iSCSI protocol.
Verify that the iSCSI initiators can discover iSCSI Software Target
To verify that Microsoft iSCSI Software Target 3.3 is able to discover the iSCSI targets that are exposed by the server to the initiators, use the following Windows PowerShell commands:
PS > & iscsicli AddTargetPortal <ip-address> 3260 PS > & iscsicli.exe ListTargets
If the commands execute without errors, the initiator is capable of discovering the targets that are offered by the server.
Verify that the iSCSI initiators can log on
The second step is to verify that the iSCSI initiators are able to log on to the iSCSI targets that are exposed by the server. This can be accomplished by using the following Windows PowerShell command:
PS > & iscsicli.exe LoginTarget <target IQN> T <ip address> 3260 Root\ISCSIPRT\0000_0 * * * * * * * * * * * * *
|If you are using CHAP and Reverse CHAP authentication, you may need to specify more parameters. For more information, consult the documentation in the iscsicli.exe.|
If the command executes without errors, the iSCSI initiator has successfully logged on to the target, and the disks are exposed to the iSCSI Software Target server.