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

Resolving an IP conflict on an mpx100 if the IP port does not clear the LED
indication on the mpx100
The HP Command View EVA refresh interval can affect controller property field information.
Workaround
• Enter a portion of the data between page refreshes, and then click Save to store the information.
Enter the rest of the data and then click Save.
• Select Agent Options > User Interface to increase the value of the refresh interval for the entire
GUI. The default value for the content pane is 60 seconds.
Rebooting the mpx100 to activate a new firmware version may result 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 port.
NOTE:
In dual mpx100 multipath configurations, a lost connection to the upgraded mpx100 does not disrupt
I/O to a multipath iSCSI initiator. The I/O fails over to the other mpx100 iSCSI ports.
Workaround
HP recommends that you suspend activity on the interfaces before activating the new firmware.
Ordered tagged commands
Ordered delivery of iSCSI commands is not guaranteed for applications running on iSCSI initiators
that use ordered tagged commands.
Workaround
HP is investigating a fix for a future release of the mpx100 firmware.
Using a private iSCSI network for mpx100 GbE ports
To ensure adequate performance and data security, HP recommends using a private Gigabit Ethernet
(GbE) network between the iSCSI initiators and the mpx100 in any iSCSI configuration.
The iSCSI technology is low cost and uses standardized network adapters and topology hardware.
However, existing networks must be evaluated for their capacity to support iSCSI storage.
Workaround
If you are not using dedicated switches, consider using separate virtual LANs (VLANs).
10