HP StorageWorks 1510i Modular Smart Array iSCSI concepts and deployment guide (431338-002, July 2008)

Microsoft iSCSI initiator
cannot connect to target
portal
• 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.
• Badcableconnectedtothenetwork.
• Other network problem; verify connectivity to the management port with
ping command.
• MSA hardware problem – check status LEDs and front panel messages.
Microsoft iSCSI initiator
connects to target portal
but does not report any
targets
• Initiator
is not on the access control list for any targets.
• No target
sareconfig u re d o n t h e M SA 1510 i .
• Portal is
not bound to a target portal group in an iSCSI target.
• Add at le
ast one, preferably all target portals into the Discovery list in the
Microsoft iSCSI Initiator software, and then click Refresh to update the target
list.
Microsoft iSCSI initiator
finds iSCSI targets but
can not login
• 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 configuredforthesecondportonthecontroller.Besurethat
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.
Microsoft iSCSI initiator
logs into iSCSI targets but
does not see any LUNs
• Check the Access Control List for the iSCSI target.
• No LUNs configured for the iSCSI target in the MSA1510i.
Persistent binding fails
• T
arget Login failed.
• T
arget Login must have a persistent login for Persistent bindings to function.
• D
rive letter may already be in use by another device.
• See Microsoft iSCSI Initiator troubleshooting in this section.
Persistent login fails
• See Microsoft iSCSI Initiator troubleshooting in this section.
Controller did not failover
• Redundant paths were not established by the host. Follow the procedures for
establishing redundant paths.
• A redundant path has failed and failover can not occur.
• The HP DSM is not loaded.
• Path may have failed over and failed back to the original path due to a path
problem on the redundant controller.
• See Microsoft iSCSI Initiator troubleshooting information in this section.
HP-Systems Insight
Manager (HP-SIM) did
not see SNMP trap
• Wrong IP address entered for trap destination.
• Wrong community string.
• No network connectivity between trap destination and the MSA1510i
management port; verify with ping command.
HP-SIM cannot read
SNMP status
• Using incorrect IP address of management port.
• Community string of the MSA1510i does not match the one being used by
HP-SIM.
• No network connectivity between HP-SIM and the MSA1510i management
port; check with ping command.
• SNMP disabled on the MSA1510i.
48
Troubleshooting