HP StorageWorks MSA1510i HP StorageWorks 1510i Modular Smart Array installatio - Page 69

new pi, In multipathing environments only

Get HP StorageWorks MSA1510i PDF manuals and user guides View all HP StorageWorks MSA1510i manuals
Add to My Manuals
Save this manual to your list of manuals

Page 69 highlights

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 Possible cause / solution 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 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. Microsoft iSCSI initiator • Check the Access Control List for the iSCSI target. logs into iSCSI targets but does not see any LUNs • No LUNs configured for the iSCSI target in the MSA1510i. iSCSI configuration was lost during a MSA1510i chassis swap out • All iSCSI information is tied to the serial number of the device. Swapping chassis results in a change in the serial number. newpage pi 1510i Modular Smart Array installation and user guide 69

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
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
Possible cause / solution
Microsoft iSCSI initiator
cannot add a discovery
portal
The initiator name in the Microsoft iSCSI initiator software does not match the
name entered for the initiator in the MSA1510i SMU or CLI.
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 MSA1510itarget 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.
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 targets are con
fi
gured 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.
Microsoft iSCSI initiator
fi
nds iSCSI targets but
can not login
•
Examine the target statistics for failed logins in the Storage Management
Utility.
•
CHAP logon information improperly con
fi
gured in the iSCSI initiator advanced
login options.
•
IP-SEC incorrectly enabled on the iSCSI initiator advanced login options.
•
Targets may be con
fi
gured 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.
Microsoft iSCSI initiator
logs into iSCSI targets but
does not see any LUNs
•
Check the Access Control List for the iSCSI target.
•
No LUNs con
fi
gured for the iSCSI target in the MSA1510i.
iSCSI con
fi
guration was
lost during a MSA1510i
chassis swap out
•
All iSCSI information is tied to the serial number of the device. Swapping
chassis results in a change in the serial number.
newpage pi
1510i Modular Smart Array installation and user guide
69