9500V

MICROCODE VERSION 065C/R & 165C/R

RELEASED 11/10/2006

Newly supported features and functions for Version 065C/R & 165C/R

NONE
Improvements for Version 065C/R & 165C/R

(1) Improvement of trace information “HJ11D2 Micro program error [RCH]”

Item Description
Contents Microcode improved to collect more information in “simple trace” so “full dump” not required.

(2) Web indication of backend diagnostic pattern

Item Description
Contents The microcode is improved to indicate backend diagnostic pattern as follows.
- I5FF00 Obstacle HDU search end
- I5FF01 Obstacle HDU search end
- I5FF02 Obstacle HDU search end
- I5FF03 Obstacle HDU search end
- I5FF04 Obstacle HDU search end

The change of contents for Version 065C/R &165C/R

(1) Subsystem down by “HH4E00 Backend down [SES access error BKW]”
Item Description
Contents In configurations with FC units and SATA units, subsystem down may occur caused by an FC
HDD obstacle. When all of the following conditions are met, the problem may occur:
A) FC units 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) Online Verify and SATA unload function failure

Item Description
Contents After a microcode exchange, online verify and SATA unload may not execute normally. This is
due to a bug in the management of a flag used to operate the online verifying.
When all of the following conditions are met, the problem may occur:
A) Microcode update to x65A/N or higher
B) Online verify executes the first iteration
C) Start timing of online verify conflicts with both controllers by exclusive processing
For example,
- LU ownership change
- Configuration setting by DAMP/SNM

HDS Confidential 1 of 2
(3) True Copy Path failure occurred with “Path login failed”
Item Description
Contents In the True Copy configuration via FC switch, when one of the subsystems is rebooted, “Path
login failed” occurs and the path does not recover automatically. Due to a microcode bug in the
path login/logout process.
DF------FC Switch(no zoning)-------DF
When all of the following conditions are met, the problem may occur:
A) True Copy configuration with FC switch
B) Zoning is not configured in the switch
C) One of the subsystem is rebooted

(4) Controller failure by “Micro program error [RVM]

Item Description
Contents 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 bug in the recovery
process of S-VOL.
When all of the following conditions are met, the problem may occur:
A) COPY or PAIR status on True Copy
B) During host I/O
C) Power failure or CHK1 occurs -> The pair status changes to PSUE
D) Recover the subsystem
E) Remote path of controller #0 is blocked, and remote path of controller #1 is normal

(5) Wrong quick format status / wrong waiting list in LUN expansion
Item Description
Contents When quick format is executed in the expanded LU, the wrong status is displayed in
DAMP/SNM and the LU is not displayed. This is due to a microcode bug in the displaying for
status with LUN Expansion.
When all of the following conditions are met, the problem may occur:
A) LUN Expansion is used
B) Quick format is executed for more than (7) internal LU including expanded LU

(6) Issue with number of simultaneous copy operations for Shadow Image
Item Description
Contents When the copy operations are performed for more than 4 copies. In this case actually less than
(4) copy operations may be simultaneous. This phenomenon may occur by LU ownership
change or controller failure during the copy operations.

HDS Confidential 2 of 2