Target information not updated by iSCSI array

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Summary

When you attempt to rescan the iSCSI storage after changing the configuration or rebooting, the iSCSI array denies ESXi to update with target information.

This error usually occurs after a user misconfigures a new discovery address.

Example

The following is an example of an error event:

iSCSI discovery to 10.115.178.29 on vmhba40 failed. The Discovery target returned a login error of: 0201.

Impact

If ESXi cannot retrieve iSCSI target information from the array, the expected user storage is not mounted.

Expected iSCSI storage volumes are not automatically discovered.

Environment

VMware vCenter Server 5.0.x
VMware vSphere ESXi 5.0

Resolution

The following solutions correspond to each reason (returned with a specific reason code).

• Requested ITN has moved temporarily to the address provided (0101)
  Requested ITN has moved permanently to the address provided (0102)

The ESXi iSCSI initiator logged in to the configured target. The target indicates that it moved to a different network address, and attempts to contact the target on the new address failed.

Solution: Verify the iSCSI array configuration.

• Miscellaneous iSCSI initiator errors (0200)

This error implies a configuration mismatch. The iSCSI initiator tries to log in with parameter settings that the target array does not support. The cause is most likely some changes in iSCSI advanced options to values that are not supported by this array.

Solution: Change the advanced options back to the default options.

• Initiator could not be successfully authenticated (0201)

The CHAP and mutual CHAP credentials configured on the ESXi initiator and on the iSCSI array do not match.

Solution: Verify that the correct CHAP parameters are set on the initiator and target.

• Initiator is not allowed access to the given target (0202)

The array refuses the login request because the iSCSI initiator IQN or IP address is not in the array's ACL list.

Solution: Change the array configuration to allow access by the iSCSI initiator.

• Requested ITN does not exist at this address (0203)

The iSCSI array indicates that the target does not exist. This might be caused if a static iSCSI target that does not exist entered, or the target is removed, deleted, or unprovisioned for this iSCSI initiator on the array configuration.

Solution: Verify that the target IQN is correct and that the target does exist.

• Requested ITN has been removed and no forwarding address is provided (0204)

The iSCSI array indicates that the target has been removed from the array by the administrator.

Solution: Remove the target's static target configuration from the iSCSI initiator.

• Requested iSCSI version range is not supported by the target (0205)

The array version is not supported.

Solution: Update the array firmware.

• No more connections can be accepted on this Session ID (SSID) (0206)

The array is out of resources. This might be caused if the array is over-provisioned by exporting too many targets or having too many initiators connecting to a single array.

Solution: Re-evaluate how the array is provisioned.

• Missing parameters (e.g., iSCSI initiator and/or target name) (0207)

Call support. This error should not occur.

• Target does not support session spanning to this connection (address) (0208)

Call support. This error should not occur.

• Target does not support this type of session or not from this initiator (0209)

A discovery session was attempted to a full session only target, or a full session was attempted to a discovery only target.

Solution: Verify that your discovery and static target configuration is correct for the array you are using.

• Attempt to add a connection to a nonexistent session (020A)

Call support. This error should not occur.

• Invalid request type during login (020B)

Call support. This is likely an initiator-target compatibility problem.

• Target hardware or software error (0300)

This is a target-side firmware error.

Solution: Check your array logs for more information and contact your array vendor.

• iSCSI service or target is not currently operational (0301)

The array reports that the iSCSI target or port is offline. This might be caused by an array controller failover that is in progress. The array port is being disabled by the array.

• Target has insufficient session, connection or other resources (0302)

The array is out of resources. This is typically caused when the array is over-provisioned.