HP MSA 1040 HP MSA 1040/2040 Controller GL 105 Firmware Release Notes - Page 17

Issue: When the system has an unwriteable cache, components of a firmware upgrade fail. Workaround: Ensure that there is no unwriteable cache, and reload the firmware bundle. Issue: Online help text for a replication volume status of Offline indicates that the volume can be accessed. Workaround: Online help should read, Offline: the volume cannot be accessed and is unusable due to an error. Issue: When you are logged in to WBI with Japanese locale, the Table of Contents for help text is not valid. Workaround: None. Issue: When a system is configured as single-controller, controller B ports are also displayed in the output of CLI command show ports. Workaround: None. Issue: Online LUN addition is not seen by clients using the P711m, P712m, or P721m controllers and the HP cciss driver in RHEL 5 operating systems. Workaround: Use the rescan volumes command on the /proc subsystem of the cciss driver to force a rescan of the cciss driver, and then update multipath. For example: echo "rescan volumes" > /proc/driver/cciss/cciss1 multipath -v 0 Issue: Online LUN addition is not seen by clients using the P711m, P712m, or P721m controllers and the HP cciss driver in SLES 11 SP2 and SP3 operating systems. Workaround: Use the hpacucli or hpssacli utility to force the SmartArray to rescan for LUNs. Do this by issuing a command for the utility to list the logical drives from the SmartArray that is connected to the MSA storage. NOTE: There will be no logical drives found in the utility, but the LUNs will now be discovered in the operating system. Use the following commands in the utility: ctrl slot=X ld all show, where X is the slot number for the SmartArray connected to the MSA. Then force multipath to create to devices by running multipath -v 0. Issue: When you use explicit LUN mapping, 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; 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 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 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 Known issues and workarounds 17