HP StorageWorks EVA iSCSI Connectivity Option 5.1 release notes (5697-7321, January 2008)

Workaround

To ensure that th

e iSCSI initiator logs into the correct EVA target port:

1. Present only th

at EVA target port to the initiator. If multiple EVA target por ts are presented,

only log into th

e active EVA target port. Select from one of the following operating systems to

set the iqn name:

• For Windows—log in to the correct active target iqn name.

•ForLinux—set

the TargetName in /etc/iscsi.conf to the active target iqn name.

2. Cross-refer

ence the preferred path EVA controller with the correct EVA target port by comparing

the preferre

d path controller’s Host Port WWPN with the last 16 characters of the EVA target

iqn name.

Rebooting the mpx100 to activate a new ﬁrm ware version may r esult in a lost

connection between a single-path iSCSI initiator and the mpx100 iSCSI port

Although the average mpx100 reboot time is under 50 seconds, the reboot can result in a lost connection

between a single-path iSCSI initiator and the mpx100 iSCSI por t.

NOTE:

In dual mpx100 multi-path conﬁ gurations,alostconnectiontotheupgradedmpx100doesnotdisrupt

I/O to a multi-path iSCSI initiator, because I/O fails over to the other mpx100 iSCSI ports.

Workaround

HP recommends that activity on the interfaces be suspended prior to activation of new ﬁrmware.

Ordered tagged c ommands

Ordered delivery of iSCSI commands c annot be guaranteed for applications running on iSCSI initiators

that use ordere d tagged command s.

Workaround

HP is investigating a ﬁx for a future release of mpx100 ﬁrmware.

Private iSCSI network for mpx100 GbE ports

HP recommends using a private Gigabit Ethernet network between the iSCSI initiators and the mpx10 0 in

any iSCSI con ﬁguration, to ensure adequate performance as well as data security.

The iSCSI technology is low cost, an d uses standardized network adapters and topology hardware.

However, existing networks must be evaluated for suitability regarding their capacity to support iSCSI

storage.

Workaround

If dedicated switches are not used, consider separate virtual LANs ( VLANs) .

Resolving an IP conﬂict on an mpx100 if the IP por t does not clear the LED

indication on the mpx100

When the mpx100 recognizes an IP con ﬂict with its management ports, the mpx100 indicates this

condition by blinking its fault LED four times, once per second and then off for two seconds. The

following error message is displayed:

EVA iSCSI Connectivity Option 5.1