What Are the Inherent Defects of iSCSI Initiators?

Hi team!

Here is a case about what are inherent defects of iSCSI initiators.

I hope it can be helpful when you learn about it :)

Symptom

What are inherent defects of iSCSI initiators?

Answer

1. In Windows Server 2003, iSCSI initiator 2.08 in check version is not compatible with UltraPath.

   For details, see section 1.1.7.4 How Can I Solve the Problem if UltraPath Is Not Compatible with an iSCSI Initiator in Check Version on Windows Server 2003?

2. In Windows Server 2003, Microsoft MPIO Multipathing Support for iSCSI is selected during iSCSI initiator installation and is used to manage Huawei storage.

   In this situation, a message is displayed indicating that MPIO has taken over Huawei storage and UltraPath cannot be installed if you want to install the UltraPath.

   For details, see section During UltraPath Installation, "The MPIO coming with Windows is managing Huawei storage devices. Delete related configurations and retry." Is Displayed.

3. In Windows Server 2003, iSCSI initiators do not support dynamic disks.

   For details, see section 1.1.8.2 What Can I Do if Windows Server 2003 iSCSI Initiators Do Not Support Dynamic Disks?

4. In Windows 7 and Windows Server 2008 R2, a blue screen of death (BSOD) error occurs when I/Os are delivered during link switchover. Error code 0x0000000a.

   For details, see section In an iSCSI Networking Environment, BSOD Occasionally Occurs in Windows 7 or Windows Server 2008 R2 and the Error Code Is 0x0000000a.

5. In Windows Server 2012 R2, the initiator target does not respond for a long time or stops responding.

6. In iSCSI initiators, the status of one target is inactive.

   The target has already been logged in via an iSCSI session dialog box is displayed during manual logon.

   For details, see section 1.1.8.19 How Can I Solve the Problem When a Message Is Displayed Indicating that the iSCSI Initiator Has Been Connected Although It Is Inactive?

7. When multiple LUN mappings exist, UltraPath link status is incorrect because the LUN reporting and deletion process takes a time or does not respond.

8. When a Target of the iSCSI initiator is in Reconnection status, UltraPath cannot be uninstalled. For details, see section 1.3.12-What Can I Do When UltraPath Uninstallation Gets Stuck? Error 10054 is displayed in IOmeter when network cables of service ports are removed.

   For details, see section In an iSCSI Environment, After a Network Cable Is Removed from a Service Network Port, Iometer Displays the 10054 Error.

9. I/O switchover time exceeds 30 seconds. For details, see section 1.1.4.3 What Can I Do If the I/O Switchover Time Exceeds 30 Seconds?

10. In the I/O delivery process, services on the peer end are interrupted when connection cables on one controller are removed. Services cannot be restored after cables are reconnected.

    For details, see section 1.1.4.5 How Can I Solve the Problem when I/Os on All Paths Occasionally Return to Zero During a LUN Switchover and Failover (Failback)?