AMS/WMS

MICROCODE VERSION 0783/G

RELEASED 03/08/2010
Newly supported features and functions for Version 0783/G
NONE

Improvements for Version 0783/G

1 2 Improvements
Content 1. The addition of “NNC Fail-over Information” to “Mode Sense Page 33H”
“NNC Fail-over Information” field is added to “Mode Sense Page 33H” to get more information
about the failure of NNC Type-1/2 (RKNAS/CNAS).
2) Improvement of the NNC failure recovery in the network failure.
The new microcode 0783/G executes the reboot of the NNC, when too many network packets keep
being issued to the NNC, caused by the network failure etc.

The change of contents for Version 0783/G

1 Both controllers may be blockaded when System Copy starts.
Phenomena Both controllers may be blockaded with the following WEB information message,
when System Copy (*) starts.
WEB information message: "HZ0L31 DSC detected IOLIST error"
(*): System Copy means a recovery process for a system area in a system drive.
System drives mean HDU-0 - HDU-4 in Unit-0. Each system drive has the
microcode, the system parameter and the transmission information.
Severity High
Conditions of Occurrence When all of the following conditions are met, the phenomenon occurs.
(a) Setting "Processing Unit Size" in "Configuration Settings"-"Restore Options" of
Storage Navigator Modular to 16 x 128 Blocks or 32 x 128 Blocks or 48 x 128
Blocks.
(Default setting: 1 x 128 Blocks)
(b) System Copy starts with the following WEB information message, when
- a failed system drive is replaced (including dummy replacement)
- a blockade of the system area is detected during a booting process.
WEB information message: "I1400x System copy started (Unit-00, HDU-x)"
(c) System drives consist of Fibre channel models of HDD.
Cause Due to the microcode bug in System Copy process.
In case that "Processing Unit Size" has been set to a specified value, a controller is
blockaded when System Copy starts, because an internal recovery parameter
becomes an invalid value.
After a controller has been blockaded, another one is blockaded too caused by the
same reason.
Affected Products/Version Products: DF700S/M/H/HE (excluding XS model) Version: All microcode version
Fixed Product/Version Products: DF700S/M/H/HE (excluding XS model) Version: 0783/G
Category System copy
Changed Part MICRO-Disk

HDS Confidential 1 of 3
 2 Blockade with SATA HDD login time-out errors
Phenomena The unexpected blockade (*1), not the failure SENC may occur with the following
WEB information message 1, when the error counter of the SENC/ENC (or the
SENC/ENC module on the controller) or LOOP exceeds the threshold caused by the
login time-out errors of SATA HDDs. Finally, the subsystem-down may occur with
the following WEB information message 2, when the unexpected blockade (*1) has
occurred in the backend loop which is different from the failure SENC.
(*1)
The part of the unexpected blockade is different in the product models.
DF700H/M : SENC, ENC, Controller
DF700S : SENC, ENC, Controller, LOOP
DF700XS : SENC, Controller, LOOP
WEB information message 1: "SENC alarm" or "ENC alarm" or " CTL alarm" or
"Loop alarm" etc.
WEB information message 2 : "HE0710 Backend loop change error[OWN]" etc.
Severity High
Conditions of Occurrence When all of the following conditions are met, the phenomenon may occur.
(a) RKAJAT is connected or the basic unit is DF700XS.
(b) The login time-out errors of the SATA HDDs occur frequently.
(c) The error counter of the SENC/ENC (or the SENC/ENC module on the
controller) or LOOP exceeds the threshold caused by the error of (b).
Cause Due to the microcode bug in the SENC blockade process, when the login time-out
error has occurred in a SATA HDD.
Affected Products/Version Products : DF700XS/S/M/H/HE Version : All microcode version
Category SENC failure
Changed Part MICRO-Disk

3 Access lost to the LU

Phenomena The following phenomenon may occur at MCU, when the pair operation of True
Copy remote replication / True Copy Extended Distance has been executed during
the remote path blockade.
1. Access lost to the LU may occur, which is executed pair operation command.
2. Pair operations may fail to the True Copy remote replication / True Copy
Extended Distance pair by Storage Navigator Modular.
3. Pair operations may fail to the True Copy remote replication / True Copy
Extended Distance pair by RAID Manager.
4. Reverse operation commands may fail to the True Copy remote replication / True
Copy Extended Distance pair from RCU.
5. Shutdown operation may not complete.
Severity Medium
Conditions of Occurrence When all of the following conditions are met, the phenomenon may occur.
(a) True Copy remote replication or True Copy Extended Distance is enabled.
(b) A remote path for the program product of (a) is blockaded.
(c) The pair operation for the program product of (a) is performed to the controller,
which has the blockaded remote path of (b), by Storage Navigator Modular or RAID
Manager.
Cause Due to the microcode bug in the path alternation process for the pair operation
command of Storage Navigator Modular or RAID Manager, when the pair operation
command of True Copy remote replication / True Copy Extended Distance has been
executed during the remote path blockade.
Affected Products/Version Products : DF700XS/S/M/H/HE Version : All microcode version (DF700M/H/HE),
0760/A and later (DF700XS/S)
Fixed Product/Version Products : DF700XS/S/M/H/HE
Category True Copy remote replication, True Copy Extended Distance
Changed Part MICRO-Disk

HDS Confidential 2 of 3
 4 Improvement of the trace data
Phenomena The HDU replacement has failed with the following WEB information message.
WEB information message: “I303xy HDU read capacity failed”
Severity Medium
Conditions of Occurrence When the following condition is met, the phenomenon may occur.
(a) The HDU replacement has failed with the WEB information message: “I303xy
HDU read capacity failed”
Cause Cause under investigation
Affected Products/Version Products : DF700XS/S/M/H/HE Version : All microcode version
Category HDU
Changed Part MICRO-Disk

5 The shadow Image copy of LUN#0 may fail

Phenomena The invalid shadow Image copy (P-VOL: LUN#0, S-VOL: LUN#0) may start,
and the shadow Image copy may fail in the shadow Image pair of LUN#0 with the
following WEB information message, and the pair status may become "SMPL" in the
S-VOL of this pair. And then, the following pair operation (*1) cannot be executed in
this pair.
(*1)
"pair create" command with the same MU#,
"pair split" command,
"pair resync" command,
"pair restore" command,
"pair delete" command

WEB information message: ID0000 Resync started(LU-0000/0000),

IE0000 Resync completed(LU-0000/0000),
IF0000 Resync failed(LU-0000/xxxx)
Severity Medium
Conditions of Occurrence When all of the following conditions are met, the phenomenon occurs.
(a) Dual controller
(b) Shadow Image in-system replication is enabled.
(C) The shadow Image pair is created with the LU which the LU number is "0".
(d) The pair status of (c) is "COPY" or "PAIR" and shadow Image copy is executed
in this pair.
(e) A shadow Image copy is completed in the controller which does not have LU
ownership of LUN#0.
(f) The ownership change process for the shadow Image copy is executed in the
controller which has LU ownership of LUN#0 at the same time as (e).
Cause Due to the microcode bug in the exclusion control between the controllers in the
ownership change process for the shadow Image copy.
Affected Products/Version Products : DF700XS/S/M/H/HE Version : All microcode version
Category Shadow Image in-system replication
Changed Part MICRO-Disk

HDS Confidential 3 of 3