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

• Enter a portion of the data between page refreshes, and click Save to store the information. Enter

the rest of the data and click Save.

• Chang e the refresh interval for the entire GUI to a larger value in Ag ent Options > User Interface.

Thedefaultvalueforthecontentpaneis60seconds.

iSCSI host entry in Command View EVA 5.0 and 6.0 must be refreshed with new WWPNs

after an mpx100 FRU replacement

Thempx100FCportWWPNsarepresentedLUNs,muchlikeanyotherFChost,byCommandViewvia

the iSCSI hos

t entry under the Command View EVA hosts folder. If an mpx100 is replaced, the iSCSI host

entry must contain the WWPNs of the replacement to continue LU N presentation.

Workaround

Once a new mpx100 has been installed and restored with the full c onﬁguration of the replaced mpx100,

start Command View and click the Refresh button in the properties page of the iSCSI Controller under

iSCSI devices. This adds the new mpx100 Fibre Channel port’s WWPNs to the existing iSCSI host entr y.

IMPORTANT:

This workaround is no longer necessary with 6.02 or greater.

Command View 5.0 and 6.0, iSCSI host objects Fibre Channel ports are not updated during

mpx100 FRU replacement

Command View presents LUNs to the mpx100 Fibre Channel port W WPNs through the iSCSI host entry

in the Command View EVA hosts folder. If an mpx100 is replaced, the iSCSI host entry must contain the

WW PNs of the replacement to continue LUN presentation.

Workaround

If the replaced mpx100 loses communication after restoring the conﬁguration ﬁle, update the iSCSI

controller object WWN:

1. Open the Command View GUI.

2. Check the iSCSI host object in the host folder to verify the Fibre Channel por t WWN.

3. If the Fibre Channel ports are not updated with the new hardware's Fibre Channel port WWN,

manually delete the old Fibre Channel port W W N.

4. Use add host to add the new Fibre Channel port WWN.

5. Verify the new Fibre Channel WWN is displayed.

IMPORTANT:

This workaround is no longer necessary with 6.02 or greater.

Creating a LUN on an EVA GL running VCS 3.028 to present to an iSCSI initiator

When creating a LUN on an EVA GL running VCS 3.028 to present to an iSCSI initiator, the LUN’s

preferred path properties must be set to either Path (controller) A or Path (controller) B.

When an EVA GL is running VCS 3.028 ﬁrmware, the controllers are conﬁgured in Active/Passive m ode.

Because a LUN is not presented out of all EVA ports, you need to set a preferred path to ensure that the

LUN is available from a speciﬁc controller or from a known iSCSI EVA target port.

If the LUN is created with no preferences and if the initiator logs into the wrong EVA target port, the LUN

may not be available to the initiator. The initiator must log into the EVA target p ort that is presenting the

LUN.