HP P2000 HP P2000 G3 1GbE iSCSI MSA and 10GbE iSCSI MSA Controller Firmware TS - Page 14

P2000 G3 QuickSpecs on the P2000 G3 product Maximum IQN Character Length

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

Page 14 highlights

will be recorded in the event logs: "An unsupported cable or SFP was inserted". At the same time, the host port will not show a status of "Down". Workaround: Do the following: 1. Verify that the SFP+, Copper Cable, or Direct Attach Cable is a supported component. For support information, see the P2000 G3 QuickSpecs on the P2000 G3 product page: http://www.hp.com/go/p2000. 2. If the components are indeed listed as supported models, remove and reinsert the SFP+, Copper Cable, or Direct Attach cable. 3. If this does not correct the issue with the SFP+, Copper Cable, or Direct Attach Cable connected to the controller, either remove and reinsert the controller or power down and reapply power to the array. Issue: RHEL 5 Update 5 will not shutdown properly when using the iSCSI initiator utilities shipped in RHEL 5 Update 5 to access the array. Workaround: See issue 583218 on the Red Hat Bugzilla bug-tracking system https://bugzilla.redhat.com/show_bug.cgi? id=583218 for the current status of the issue and possible workarounds. Issue: When using explicit LUN mapping, using long IQN names for the iSCSI Initiator can cause the array to map the LUN incorrectly. A predefined area is used to store explicit LUN mapping information per LUN and, with longer IQN names, this area can be exhausted. This issue is not dependent on the number of paths to the LUN. Workaround: Shorten the IQN name on the nodes. The following formula is used to calculate the maximum IQN name length based on the number of hosts being explicitly mapped to a LUN on the array: Maximum IQN Character Length = (4083 / n) - 7 (Where n = number of hosts nodes explicitly mapped to a LUN on the array.) NOTE: By specification, 223 is the maximum IQN length allowed. The following table provides the calculated values based on the number of hosts being explicitly mapped to a LUN on the array: Number of hosts explicitly mapped to a LUN and the Maximum IQN character length 1-17 223 18 219 19 207 20 197 21 187 22 178 23 170 24 163 25 156 26 150 27 144 28 138 29 133 30 129 31 124 32 120 Number of hosts explicitly mapped to a LUN and the Maximum IQN character length 33 116 34 113 35 109 36 106 37 103 38 100 39 97 40 95 41 92 42 90 43 87 44 85 45 83 46 81 47 79 48 78 Number of hosts explicitly mapped to a LUN and the Maximum IQN character length 49 76 50 74 51 73 52 71 53 70 54 68 55 67 56 65 57 64 58 63 59 62 60 61 61 59 62 58 63 57 64 56 Issue: USB CLI becomes unusable after a Management Controller reboot in Windows environments. 14 Known issues and workarounds

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
will be recorded in the event logs: “An unsupported cable or SFP was inserted". At the same time, the host port will not
show a status of "Down".
Workaround:
Do the following:
1.
Verify that the SFP+, Copper Cable, or Direct Attach Cable is a supported component. For support information, see the
P2000 G3 QuickSpecs on the P2000 G3 product page:
h
t
tp://w
w
w
.hp
.co
m/go/p2000
.
2.
If the components are indeed listed as supported models, remove and reinsert the SFP+, Copper Cable, or Direct Attach
cable.
3.
If this does not correct the issue with the SFP+, Copper Cable, or Direct Attach Cable connected to the controller, either
remove and reinsert the controller or power down and reapply power to the array.
Issue:
RHEL 5 Update 5 will not shutdown properly when using the iSCSI initiator utilities shipped in RHEL 5 Update 5 to
access the array.
Workaround:
See issue 583218 on the Red Hat Bugzilla bug-tracking system
h
t
tp
s://bugzilla
.r
edhat
.co
m/sh
o
w_bug
.cgi?
i
d=5
8
3
2
1
8
for the current status of the issue and possible workarounds.
Issue:
When using explicit LUN mapping, using long IQN names for the iSCSI Initiator can cause the array to map the
LUN incorrectly. A predefined area is used to store explicit LUN mapping information per LUN and, with longer IQN
names, this area can be exhausted. This issue is not dependent on the number of paths to the LUN.
Workaround:
Shorten the IQN name on the nodes.
The following formula is used to calculate the maximum IQN name length based on the number of hosts being explicitly
mapped to a LUN on the array:
Maximum IQN Character Length =
(4083 / n)
–
7
(Where n = number of hosts nodes explicitly mapped to
a LUN on the array.)
NOTE: By specification, 223 is the maximum IQN length allowed.
The following table provides the calculated values based on the number of hosts being explicitly mapped to a LUN on the
array:
Number of hosts explicitly mapped
to a LUN and the Maximum IQN
character length
Number of hosts explicitly mapped
to a LUN and the Maximum IQN
character length
Number of hosts explicitly mapped
to a LUN and the Maximum IQN
character length
76
49
116
33
223
1–17
74
50
113
34
219
18
73
51
109
35
207
19
71
52
106
36
197
20
70
53
103
37
187
21
68
54
100
38
178
22
67
55
97
39
170
23
65
56
95
40
163
24
64
57
92
41
156
25
63
58
90
42
150
26
62
59
87
43
144
27
61
60
85
44
138
28
59
61
83
45
133
29
58
62
81
46
129
30
57
63
79
47
124
31
56
64
78
48
120
32
Issue:
USB CLI becomes unusable after a Management Controller reboot in Windows environments.
14
Known issues and workarounds