9500V

MICROCODE VERSION 065C/E & 165C/E

RELEASED 08/16/2006

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

NONE

Improvements for Version 065C/E & 165C/E

(1) Backend Auto Diagnosis improvement during ENC/SENC firmware exchange process
Item Description
Contents Microcode modified to improve the diagnostic logic when an ENC/SENC obstacle occurs
during the ENC/SENC firmware exchange.

(2) Backend Auto Diagnosis improvement (Phase II)

Item Description
Contents Microcode modified to improve the ability to isolate an intermittent failing part from backend
loop by increasing the number of diagnostic frames to max. 30 times to check the backend loop.

(3) Improvement of subsystem down by memory failure in an ENC

Item Description
Contents When a memory failure in an ENC occurs, subsystem down may occur by deciding that both
ENC are failing. Microcode modified to improve check process of ENC memory in this case.

(4) Improvement of the subsystem down by an obstacle of ENC and controller

Item Description
Contents When a controller blocks by a cache correctable error during an ENC block, the Subsystem
down occurs. The microcode modified so controller does not block with a correctable cache
error when there is no redundancy in the Loop.

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

(1) Subsystem down by a Loop obstacle during online microcode exchange

Item Description
Contents When a Loop obstacle occurs during online microcode exchange, the subsystem may go down.
When all of the following conditions are met, the problem may occur:
1. Online microcode exchange
2. Backend loop obstacle

(2) Subsystem does not become ready with “BKW job time-out”
Item Description
Contents When an ENC in the controller fails during the Subsystem booting, the Subsystem may not
come Ready. When all of the following conditions are met, the problem may occur:
A) During the subsystem booting
B) ENC in the controller has a failure
C) The controller #0 cannot access all SES HDD (HDD #0, 1, 2, 3 in the Unit #0 by (B)
HDS Confidential 1 of 2
(3) HDD block by “Drive Response DIAG NG” in RAID1, RAID5
Item Description
Contents HDD block may occur due to a drive response diagnosis function with “I6DY00 Drive
Response DIAG NG (Unit-XX, HDU-YY)” message. This is due to a microcode bug in the
calculation processing of the average response time during Drive Response Diagnosis.
When all of the following conditions are met, the problem may occur:
Case #1
A) RAID1/FC HDD
B) Average response time more than 20msec continues for more than 10min.
Case #2
A) RAID1/SATA HDD
B) Average response time more than 40msec continues for more than 10min.
Case#3
A) RAID5/FC HDD
B) The HDD response time is more than 2 times longer than the other HDD
C) The average response time more than 20msec continues for more than 10min.
Case #4
A) RAID5/SATA HDD
B) The HDD response time is more than 2 times longer than the other HDD
C) The average response time more than 40msec continues for more than 10min.

(4) Write command error for PVOL in Shadow Image

Item Description
Contents When a PVOL and SVOL switch, caused by a PVOL obstacle a Write command error may
occur.
When all of the following conditions are met, the problem may occur:
A) Shadow Image
B) SI pair status: PAIR or COPY
C) SI “I/O switch mode” is enabled
D) Receive Write command for PVOL
E) After a response to (D) multiple HDD obstacle in PVOL occurs.
F) The data copy from PVOL to SVOL fail

(5) Controller isolation failure by Backend Auto Diagnosis

Item Description
Contents When both Loops block occurs in the controller, controller isolation failure may occur.
When all of the following conditions are met, the problem may occur:
A) DF600H(9580) DF600HE(9585)
B) Connection SATA unit, path #2 and path #3
C) Both Loop block by controller failure

(6) Incorrect IP Address indication in DHCP mode

Item Description
Contents Displayed IP address may be different from the correct IP address.
When all of the following conditions are met, the problem may occur:
A) DHCP mode
B) Failed acquisition of the IP address from DHCP server during the Subsystem booting
C) Success in acquisition of IP address from DHCP server after the Subsystem comes Ready

HDS Confidential 2 of 2