Troubleshooting - HP StorageWorks 1510i - Modular Smart Array User Manual

6.
In multipathing environments only, test the redundancy by forcing a controller failover. (One
method of forcing a failover is to disable the switch port associated with the active MSA
controller path.)

Troubleshooting

Problem
Microsoft iSCSI initiator
cannot add a discovery
portal
Microsoft iSCSI initiator
cannot connect to target
portal
Microsoft iSCSI initiator
connects to target portal
but does not report any
targets
Microsoft iSCSI initiator
finds iSCSI targets but
can not login
Microsoft iSCSI initiator
logs into iSCSI targets but
does not see any LUNs
iSCSI configuration was
lost during a MSA1510i
chassis swap out
newpage pi
Possible cause / solution
The initiator name in the Microsoft iSCSI initiator software does not match the
name entered for the initiator in the MSA1510i SMU or CLI.
• Storage port with target portal is not connected to the network.
• Wrong IP address or TCP port number.
• No IP route from the initiator to the MSA1510i target portal.
• No IP route from the MSA1510i target portal back to the initiator.
• Initiator is on a different VLAN than the MSA1510i target portal.
• Bad cable connected to the network.
• Other network problem; verify connectivity to the management port with
ping command.
• MSA hardware problem – check status LEDs and front panel messages.
• Initiator is not on the access control list for any targets.
• No targets are configured on the MSA1510i.
• Portal is not bound to a target portal group in an iSCSI target.
• Add at least one, preferably all target portals into the Discovery list in the
Microsoft iSCSI initiator software, and then click Refresh to update the target
list.
• Examine the target statistics for failed logins in the Storage Management
Utility.
• CHAP logon information improperly configured in the iSCSI initiator advanced
login options.
• IP-SEC incorrectly enabled on the iSCSI initiator advanced login options.
• Targets may be configured for the second port on the controller. Be sure that
both ports are connected to the proper IP subnet with access to initiator.
• The MSA controller maximum session count may have been exceeded. The
controller supports a maximum of 32 sessions per controller. Log out of targets
on any non-essential servers to free some sessions.
• Check the Access Control List for the iSCSI target.
• No LUNs configured for the iSCSI target in the MSA1510i.
• All iSCSI information is tied to the serial number of the device. Swapping
chassis results in a change in the serial number.
1510i Modular Smart Array installation and user guide
69