Troubleshooting eva or lun fc port connections – HP EVA Array iSCSI Connectivity Option User Manual

Page 176

Advertising
background image

Presenting an EVA LUN to an iSCSI Initiator is a two-step process in HP Command View:

1.

Presenting the LUN to the iSCSI host entry. This communication presents the LUN from the

EVA FC ports to the mpx100/100b FC ports.

2.

Presenting the LUN to the iSCSI Initiator. This communication presents the LUN from the

mpx100/100b Gigabit Ethernet ports to the iSCSI Initiator.

Troubleshooting EVA communication with the mpx100/100b

If there is a problem with HP Command View EVA communicating with the mpx100/100b or not

discovering LUNs, verify that:

The mpx100/100b is powered on.

The mpx100/100b management port is cabled to the IP network.

The mpx100/100b management port IP address, subnet mask, and gateway are set properly.

The HP Command View application server NIC IP address, subnet mask, and gateway are

set properly.

The mpx100/100b management port is on the same IP network as the HP Command View

EVA application server.

The iSCSI controller’s management port connection status is online in HP Command View EVA.

Troubleshooting EVA or LUN FC port connections

If the mpx100/100b does not see EVA ports or LUNs connected to the FC ports:

Verify that the mpx100/100b is powered on.

Verify that the Fibre Channel link light is green.

If your configuration is fabric connect mode, check to see if the mpx100/100b FC ports are

zoned with the EVA FC ports.

If your configuration is direct connect mode, check to see if EVA ports connected to the

mpx100/100b FC ports are set to direct connect.

Verify that the EVA ports and LUNs are discovered and online to the mpx100/100b are using the

mpx Manager GUI or CLI.

In HP Command View EVA , verify that the Vdisk is uses FC ports to present the Vdisk to the

iSCSI host entry.

Troubleshooting iSCSI Initiator connections to the EVA iSCSI targets

If the iSCSI Initiator cannot connect to the EVA iSCSI targets presented by the mpx100/100b:

For a Windows Initiator:
• Verify that the iSCSI driver is installed.
• Ping the mpx100/100b iSCSI port from the iSCSI Initiator.
• Select General > Secret and check the security setting on the initiator.
• Verify that the iSCSI Initiator’s iqn name changed in the General tab.
• Verify that the iSCSI Port IP address is added to Target Portals on the Discovery tab.
• Verify that the iSCSI Target status is connected on the Targets tab.

For a Linux Initiator:
• Verify that the iSCSI driver is installed.
• Ping the mpx100/100b iSCSI Port from the iSCSI Initiator.
• Check for security settings, if any, in authentication settings in the /etc/iscsi.conf file.
• Verify that the iSCSI IP port address is added to the Discovery Address setting in

/etc/iscsi.conf

file.

• Verify that the iSCSI Target name is added to the TargetName setting in the

/etc/iscsi.conf

file.

176

Diagnostics and troubleshooting

Advertising