AMS/WMS

MICROCODE VERSION 0760/B

RELEASED 11/21/2006

Newly supported features and functions for Version 0760/B

NONE

Improvements for Version 0760/B

(1) Check function reinforcement for an attached LU in NAS system

Item Description
Contents The microcode is improved to check mapping operation for an attached LU in NAS system.

The change of contents for Version 0760/B

(1) Subsystem down by “HH4E00 Backend down [SES access error BKW]” (High priority)
Item Description
Contents In configurations with mixed FC and SATA units, subsystem down may occur caused by an FC
HDD block.
When all of the following conditions are met, the problem may occur:
A) FC and SATA intermix of units in the subsystem
B) FC HDD obstacles on both ports
C) SES polling for SATA units starts before bypassing the HDD from the Loop

(2) Subsystem down by “Micro program error [LUC] (High priority)

Item Description
Contents Subsystem outage may occur with “Micro program error [LUC].
The problem may occur when all of the following conditions are met:
A) Dual Active Mode
B) One of the following conditions occurs:
1) Change of the default controller
2) Expansion of an LU – using Storage Navigator Modular
3) Resync from CCI – Raid Manager
C) A controller fails during (B)
Microcode is improved to resolve this issue.

HDS Confidential 1 of 2
(3) Multiple HDD block occurred after automatic ENC/SENC firmware update (Medium priority)
Item Description
Contents SATA HDD failure does not recover because other SATA HDD in the Raid Group cannot be
accessed.
The problem may occur when one of the following conditions are met:
A) Micro program update
B) Automatic update of SENC firmware
Microcode is improved to resolve this issue.

(4) Controller block by watchdog timeout error (Medium priority)

Item Description
Contents This problem may occur when more than two clients try to connect to the LAN port of the
controller with Port #111(RPC) and transfer a large amount of data. In the case that CTL0 and
CTL01 are connected to the same LAN environment. If the problem occurs on both controllers,
subsystem down may occur. This is caused by a memory stack overflow by recursive calls of the
LAN handler function.
Microcode is improved to resolve this issue.

(5) Controller failure by “Micro program error [RVM]” (Medium priority)

Item Description
Contents A controller may fail with “Micro program error [RVM]” when rebooting the subsystem after a
power failure or CHK1 (controller hardware failure). This is due to a microcode bug in the
recovery process for S-VOL.
The problem may occur when all of the following conditions are met:
A) COPY or PAIR status of True Copy
B) During host I/O
C) Power failure or CHK1 occurs-> the pair status changes to PSUE
D) Recover the failure
Microcode is improved to resolve this issue.

(6) Controller failure by “Micro program error [FSM]” (Medium priority)

Item Description
Contents A controller may fail with “Micro program error [FSM]” during host I/O. This is due to a
microcode bug in the patch check mechanism for True Copy.
The problem may occur when all of the following conditions are met:
A) True Copy remote replication
B) During write commands to P-VOL
C) Health check command of remote path failed by microcode bug
Microcode is improved to resolve this issue.

(7) Addition of retry mechanism during NAS dump (Medium priority)

Item Description
Contents NAS dump may fail by NNC failure. This is due to lack of retry mechanism.
The problem may occur when all of the following conditions are met:
A) Execute NAS dump
B) Mate controller failure
C) Power failure or CHK1 occurs-> the pair status changes to PSUE
D) Recover the failure
Microcode is improved to resolve this issue.

HDS Confidential 2 of 2