SMS

MICROCODE VERSION 1885/D

RELEASED 03/08/2010
Newly supported features and functions for Version 1885/D
NONE

Improvements for Version 1885/D

NONE

The change of contents for Version 1885/D

1 Invalid response from Controller 1 for Inquiry Page83h
Phenomena Controller 1 responses a wrong value for Inquiry Page83h to a host when CHK1 occurs on
Controller 1 after completed Auto Migration (AM2). As a result, some applications such
as multi-path software may not be able to identify LU correctly via Controller 1.
Severity High
Conditions of Occurrence The phenomenon occurs when all of the following conditions are met.
(1) AM2 is done. (Problem does not occur if AM2 is offline array replacement)
(2) Then CHK1 occurs on Controller 1 on a new array.
(3) And then Inquiry Page83h is received to Controller 1 of the new array.
Does not occur if power cycle (PS-OFF/ON) or reboot is done after execution of AM2
Cause There is a microcode bug in “Node Name” re-creation process at CHK1.
When Inquiry Page83h is received from a host, “Node Name” is responded, which is
based on a unit serial number. “Node Name” of new array is copied from an original array
when AM2 has completed, and each Controller has an original unit serial number of the
new array and an original array in the internal table on the new array after AM2 has
completed. When CHK1 occurs on Controller 1 of the new array after AM2 has
completed, “Node Name” is re-created from the original unit serial number of the new
array wrongly, and then invalid “Node Name” is responded for Inquiry Page83h.
This problem occurs on Controller 1 only because there are some differences between
Controller 0 and Controller1 about “Node Name” re-creation process at CHK1.
Affected Products/Version SA800, V6.5/A(1865/A) or later
Category Auto Migration
Changed Part MICRO-Disk

2 Firmware update fails when Session-timeout length disabled.

Phenomena Non-stop firmware update fails with the following message. Even if you retry in
accordance with the message, firmware update fails again.
Low
Conditions of Occurrence The problem occurs when all following conditions are met.
(1) Account Authentication is enabled.
(2) Session-timeout length for Account Authentication is disabled.
(3) Updating firmware as non-stop firmware update.
Cause When Session-timeout length for Account Authentication is disabled, some sessions are
terminated in the reboot-process for updating firmware. As a result, session-timeout
occurs on HSNM2, and firmware update fails.
Affected Products/Version DF800H/M/S, SA8x0 V6.2/A(x862/A) or later
Category Account Authentication
Changed Part MICRO-Disk

HDS Confidential 1 of 2
3 Auto Migration Fails
Phenomena Auto Migration (online array replacement)(Abbreviated as AM2, hereafter) fails when
creating copy due to the error, communication with the new array has abnormally ended if
AM2 is executed under the environment that SNM2 is connected to the new array.
Severity Medium
Conditions of Occurrence The phenomenon occurs when all of the following conditions are met.
(1) AM2 is running
(2) SNM2 is connected to the new array
(3) Operation or viewing from SNM2 to the new array is executed while AM2 is running
Cause AM2 uses True Copy engine internally. When SNM2 communicates to the new array,
communication with SNM2 and communication between the original array and the new
array are excluded mutually in True Copy process. On firmware V8.0/A, there was
modification to make this mutual exclusion work only when True Copy PP key is
unlocked for Read/Write performance improvement. But although the mutual exclusion
was required when AM2 was running, because it didn’t work since True Copy PP key was
locked, AM2 failed due to communication timeout between original array and new array.
Affected Products/Version SA800, V8.0/A(1880/A) or later
Category Auto Migration
Changed Part MICRO-Disk

4 Auto Migration Fails cont.

Phenomena After the AM2 failure of #2("Auto Migration (online array replacement) fails because
communication with the new array has abnormally ended.") or network error, when user
re-executes AM2 after resetting failure status by “Reset Migration Status” and “Release
Migration Status”, then the new array goes subsystem down and the error “DMEA000006:
Failed to connect with the subsystem. Confirm the subsystem status and the LAN
environment, and then try again” will be displayed and the re-execution of AM2 will fail.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) When AM2 is re-executed after previously executed AM2 fails.
Cause After the AM2 failure, uncompleted migration data remains in the new array. The
implementation of AM2 re-execution is supposed to remove the uncompleted migration
data which was created by the last AM2 execution. However, because there is a firmware
bug in V8.5/A enhancement regarding reboot process, the new array goes subsystem down
due to the uncompleted migration data created by last AM2 execution.
Affected Products/Version SA800, V8.5/A(1885/A) or later
Category Auto Migration
Changed Part MICRO-Disk

5 Uncorrectable error occurs in a SAS HDU and HDU is blocked.

Phenomena Uncorrectable error occurs in block of SAS HDU with Write operations to block, the
reassignment of the block is not done and the HDU is blockaded with Write failure error.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) SAS HDU
(2) Uncorrectable error occurs in a block of (1)
(3) Write operations (host I/O, HDD recovery, etc.) are executed to the block of (2).
Cause When uncorrectable error occurs in a block of a SAS HDU, the reassignment to the block
is executed by the firmware. In some cases, write command (e.g. host I/O, HDD recovery,
etc.) is issued to the block before the reassignment is done and a write failure response
(03/0C03) is sent from the HDU. This write failure is managed by the threshold check of
the write failure itself and the HDU will blockaded as results.
Affected Products/Version DF800H/M/S, SA8x0, All versions
Category Common
Changed Part MICRO-Disk

HDS Confidential 2 of 2