SMS

MICROCODE VERSION 1885/A

RELEASED 01/19/2010

Newly supported features and functions for Version 1885/A

NONE

Improvements for Version 1885/A

1 2 Improvements
Contents 1. Improvement of the check process of the firmware update.
2. Improvement of failure search accuracy of backend diagnosis.
3. Improvement for the capturing dump data of ISCSI interface.
4. Improvement of the response time when Queue full occurs frequently on FC interface.
5. Improvement of failure search accuracy of SAS controller firmware.
6. “SATA Write & Compare” check (or SATA RAW) can be disabled/enabled by HSNM2

The change of contents for Version 1885/A

1 Plural ENC failures during Online Firmware upgrading process

Phenomena While in Online Firmware Upgrading, when one ENC is failed, then the other ENC in
the same path may be also failed. (Firmware inappropriately blocks the other ENC.)
Severity High
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) ENC Firmware Upgrading process is executed on plural ENC in the same path.
(Online Firmware Upgrading, or installing plural ENC at the same time.)
(2) While ENC reboot process in above (1), a certain link failure occurs.
(3) Within 15ms from above (2), internal failure transaction works.
Cause Because of inappropriate transaction for link failure in ENC, the Firmware detects the
normal ENC as failure.
Affected Products/Version DF800H/M/S, V3.2/A(0832/A) or later
SA8x0, All version
Fixed Product/Version Version: 0885/A or later
Category Backend
Changed Part MICRO-Disk

HDS Confidential 1 of 5
2 HDD failure caused by LA/LRC errors
Phenomena In case that DF800 receives the read/write command from hosts, blockading multiple
HDU may occur with following messages.
IY0F00 LA error (errcode:LUN) (Unit-x, HDU-y)
IY0G00 LA error (errcode:LBA) (Unit-x, HDU-y)
IY0H00 LRC error (Unit-x, HDU-y)
x: Unit number, y: HDU number

When DF800/SA8x0 is managed by Hitachi Device Manager (HDvM) and this

phenomenon occurs on this DF800/SA8x0, following alert message will be shown in
HDvM. Serious error reported for Disk Drive #n.
In addition, following log message will be shown in Event Log (Windows) and/or
System Log (Other OS) where HDvM has been installed.
KAID11010-E Serious error reported for Disk Drive #n.
Severity High
Conditions of Occurrence The problem may occur when all following conditions are met.
A. In the case of DF800>
- Firmware version: 0862/A or 0865/A to 0865/H
<In the case of SA8x0>
- Firmware version: 1850/A to 1850/E
B. <In the case of DF800>
- The quick format command is ordered to a LU of more than 48TB (This applies to
multiple LU of more than 48TB specified, too.)
<In the case of SA8x0>
- The quick format command is ordered to a LU of more than 4.8TB (This applies to
multiple LU of more than 4.8TB specified, too.)
C. Executing the quick format to the first 64GB area where 48TB (DF800H) or 4.8TB
(SA8x0) is exceeded.
D. SNM2/Hicommand is available with the array.
Cause When the subsystem receives a sense command through the LAN while formatting LU
in the quick mode, an error relating to the sense command occurs and some spaces
become unformatted.(transfer information that is supposed to be held in the local
memory is mistakenly held in the quick format managing table in the cache memory. )As
a result, when read/write come to the unformatted spaces, several HDD failures are
falsely detected by LA/LRC errors.
Affected Products/Version DF800H, V6.2/A(0862/A) or V6.5/A to V6.5/H(0865/A to 0865/H)
SA8x0, V5.0/A to V5.0/E(1850/A to 1850/E)
Fixed Product/Version Version: x885/A or later
Category Common
Changed Part MICRO-Disk

HDS Confidential 2 of 5
3 Controller blockade with failure in the Local Memory
Phenomena Controller blockade with failure in the Local Memory caused by Firmware logical
contradiction. One of the following messages is issued at that time. [CSDS]The
uncorrectable error on the write was detected[0xYYYYYYYY](CTL-X)
[CSDS]The uncorrectable read memory error was detected[0xYYYYYYYY](CTL-X)
The processor system bus error was detected[0xYYYYYYYY](CTL-X)
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) 1bit error (ECC correctable error) in the Local Memory occurs.
(2) 2bit error (ECC uncorrectable error) in the Local Memory occurs.
Cause Logical contradiction occurs when 1bit error (ECC correctable error) in the Local
Memory occurs, then 2bit error (ECC uncorrectable error) in the Local Memory occurs.
Affected Products/Version DF800S/M/H,SA8x0 Version: All version
Fixed Product/Version Version: 0885/A or later
Category Common
Changed Part MICRO-Disk

4 Host I/O and reserve command error

Phenomena When LU ownerships are changed like during load balancing while commands are being
executed, a command error is detected, I/O operations cannot be executed or a reserve
LU cannot be set.
(a)Copy pair operations or a reserve command cannot be executed.
(b)LU becomes inaccessible to hosts for I/O. When a True Copy pare is created, the
status of another LU at a remote site is changed to COPY status by mistake, so the host
at the remote site becomes inaccessible for read/write.
(c)A reserve LU cannot be set. Because another LU is reserved by mistake by Persistent
Reserve OUT command, the specified LU cannot be reserved.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
[(a)A command error occurs]
(1)A copy pair command is executed.
(2)the ownership of the specified LU is changed. (like when load balancing occurs)
(3)After the LU ownership has been changed, the LU receives a PIO related
command(other than RD/WR).
[(b)The host is inaccessible, (a)A command error occurs]
(1)A True Copy pair command is executed
(2)The ownership of the specified LU as the S-VOL by the command at the remote site
is changed. (like when load balancing occurs)
(3)After the LU ownership has been changed, the LU receives a PIO related
command(other than RD/WR).
[(c)The reserve information is wrong, (a) A command error occurs]
(1)Persistent Reserve OUT command is executed
(2)The ownership of the reserve LU is changed. (like when load balancing occurs)
(3)After the LU ownership has been changed, the LU receives a PIO related
command(other than RD/WR).
Cause There is a short period of time when changing a LU ownership is not prohibited, when a
command has not been completed yet. When the ownership of a LU is changed during
that short period of time, the buffer needed to execute the command is rewritten by the
information of another command.
Affected Products/Version DF800H/M/S, All version
SA800, All version
Fixed Product/Version Version: 0885/A or later
Category Common
Changed Part MICRO-Disk

HDS Confidential 3 of 5
5 A controller failure occurs after a host transfer
Phenomena A controller failure may occur due to a DMA DCTL failure during write operations.
The message that is displayed when a controller is blockaded: Host transfer DMA error
was detected(CTL-X,DMA-XX)
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1)ISCSI interface is used.
(2)More than two write operations are issued with no read operations.
(3)DCTL error by host write transfer occurs.
Cause When a host transfer DMA DCTL failure occurs during write operations, the ISCSI chip
is not halted. So even when the DCTL has been recovered, the ISCSI chip still has been
sending data to the DCTL and a data transmission error occurs.
Affected Products/Version DF800H/M/S, All version
SA800, All version
Fixed Product/Version Version: 0885/A or later
Category Common
Changed Part MICRO-Disk

6 Controller blockade when controller executes internal retry

Phenomena Controller is blockaded because of a factor “The read data parity error was detected in
the register interface” when controller executes internal retry (CHK1 reset) in case that
controller failure occurs.
Severity Medium
C: Critical Low
Conditions of Occurrence The problem may occur when all following conditions are met.
- Intermittent failure about CPU occurs in the controller.
Cause There is a bug about illegal detection of transfer error because data transfer doesn’t abort
unexpectedly when controller executes internal retry (CHK1 reset), in case that
controller failure occurs.
Affected Products/Version DF800H/M/S, All version
SA8x0, All version
Fixed Product/Version Version: 0885/A or later
Category Common
Changed Part MICRO-Disk

7 SNMP error and the device (subsystem) warning occur

Phenomena The SNMP error and the device (subsystem) warning state might occur after updating
the firmware. The firmware update itself completes normally. IB1700 SNMP RAM
Device allocation error for SNMP :controller /STRC
W3Q001 SNMP error occurred in the SNMP function(controller-1) :MANUAL/STRC
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) Enable SNMP Program Product
(2) Enable DHCP function
(3) Update the firmware
Cause Because the SNMP information is checked unjustified when the DHCP function is used,
and logical error has been detected.
Affected Products/Version DF800H/M/S, All version
SA8x0, All version
Fixed Product/Version Version: 0885/A or later
Category SNMP
Changed Part MICRO-Disk

HDS Confidential 4 of 5
8 Subsystem can not be booted up
Phenomena Subsystem can not be booted up because both controllers are blockaded. Or I/O
operation can not be executed because PIN is over when firmware exchange is executed
or controller replacement(insertion) is executed in case that the system has a SATA HDD
as system HDD.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
[Not booted up]
(1) Both device discover process (discover) on one backend path and request for device
discover process on another backend path occur.
[I/O operation cannot be executed.]
(1) The system has a SATA HDD as system HDD.
(2) Both device discover process (discover) on one backend path and request for device
discover process on another backend path occur.
Cause Exclusive process about common flag doesn't be executed between controllers. So
device discover process doesn't complete for illegal update.
Affected Products/Version DF800H/M/S, SA800/810 First version or later
Fixed Product/Version Version: 1883/B or later
Category Backend (SAS I/F)
Changed Part MICRO-Disk

9 Array can not respond due to wrong port setting

Phenomena Due to the wrong port setting for HSNM2/HiCommand Secure communication, the
array can not respond.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) Set the number of the Secure communication port of the array (default: 28355) to the
Non Secure communication port from HSNM2 or HiCommand.
(2) Packet lost occurs on the LAN between the HSNM2/HiCommand and the array.
Cause The start procedure of Secure communication has a bug such that the procedure cannot
deal with the Non Secure communication request and the communication does not start.
If such status holds several minutes, a packet with the timeout notice is sent from
HSNM2/HiCommand to recover the procedure. However, if the packet is lost, the
recovery will not be held.
Affected Products/Version DF800H/M/S, All version
SA8x0, All version
Fixed Product/Version Version: 0885/A or later
Category Common
Changed Part MICRO-Disk

HDS Confidential 5 of 5