HP StorageWorks EVA iSCSI Connectivity Option 9.0 Release Notes (5697-0510, June 2010)

iqn.1991-05.com.microsoft:imthe.firstone.net

This designator type consists of the following parameters:

• The string iqn followed by a dot (.)

• A date code, in yyyy-mm format, followed by another dot (.)

• A reverse domain name

• An optional colon (:) prefixed by a string

If you are using only ASCII characters (U+0000 to U+007F), the following characters are allowed:

• ASCII dash character (’-’ = U+002d)

• ASCII dot character (’.’ = U+002e)

• ASCII colon character (’:’ = U+003a)

• ASCII lowercase characters (’a’..’z’ = U+0061..U+007a)

• ASCII numeric characters (’0’..’9’ = U+0030..U+0039)

NOTE:

See section 3.2.6 of Request for Comments (RFC) 3720 (iSCSI) for a description of the iSCSI name

string profile. You can access RFC 3720 at ftp://ftp.rfc-editor.org/in-notes/

rfc3720.txt.

Workaround

Use the correct IQN syntax, as described in section 3.2.6 of RFC 3720.

• For Windows—In the initiator GUI, click Reset under Change in the General tab to reset the IQN

to the original name that was created when you installed the initiator.

• For Linux—Edit the InitiatorName setting in the initiatorname.iscsi file using the correct

syntax.

• For Linux and Windows—Reinstall the initiator to create a valid IQN.

iSCSI initiator LUNs disappear after changing the initiator IQN

The mpx100 maintains a database of targets, initiators, and LUNs and the corresponding links between

them. When HP Command View EVA presents or removes a LUN from an iSCSI initiator, it updates

the mpx100 database. When a new IQN logs in to the mpx100, it is considered a new initiator and

no LUNs are assigned to it. All LUN assignments to the old IQN are maintained.

Workaround

Using HP Command View EVA, unpresent the LUN from the old initiator IQN and present it to the

new initiator IQN. Remove the old initiator from the mpx100 database with either the mpx100

Manager GUI or the CLI.

Windows iSCSI initiators must add Tcp1323Opts to registry

Timestamps enable TCP to measure the round-trip time (RTT) accurately to adjust retransmission timeouts.

The Timestamps option provides two timestamp fields of 4 bytes each in the TCP header: one to record

the time of the initial transmission, and one to record the time on the remote host.