AMS/WMS

MICROCODE VERSION 0750/A

RELEASED 06/28/2006

Newly supported features and functions for Version 0750/A

1) LAN Negotiation Mode support
Item Description
Contents The microcode supports LAN Negotiation Mode. It can be selected from the following modes:
A) Auto (default)
B) 100Mbps Full
C) 100Mbps Half
D) 10Mbps Full
E) 10Mbps Half

2) ISCSI initiator support

Item Description
Contents The microcode supports 255-initiator connection on ISCSI platform.
A) Target count: 128 to 255
B) CHAP user count: 256 to 512
C) Initiator count: 128 to 255

Improvements for Version 0750/A

1) Random Read performance improvement in RAID1
Item Description
Contents ) The microcode modified to improve the performance of random Read in RAID1 by improving
the process of disk access.

2) SATA 500GB HDD “720 hours per month use” support

Item Description
Contents The microcode executes Online Verify for SATA 500GB HDD as frequently as the FC HDD
(full time online verify execution.

3) Improvement of both Loop obstacles processing during the subsystem boot

Item Description
Contents The microcode improved to prevent hang- up of both Loop obstacles during subsystem boot.

4) Improvement of the Backend automatic diagnosis for Controller unit in DF700H

Item Description
Contents The microcode improved to check the controller with an obstacle using the Backend automatic
diagnosis.

5) Improvement for repetitive blocks by LA/LRC error in the Dual controller configuration
Item Description
Contents To avoid the repetitive controller blocks, the microcode modified not to block the controller
when the LA/LRC error detected in the same area after controller exchange.

HDS Confidential 1 of 6
6) Web indication of NAS PP Version
Item Description
Contents The microcode improved to display a version of installed NAS PP.

7) Modification of LU size check Web indication of NAS PP Version

Item Description
Contents The microcode modified to check the LU too small for NAS system LU.

8) Web message change in “NNC Boot time-out”

Item Description
Contents The microcode modified to clarify the factors of “NNC Boot time-out”. The following messages
will be displayed by this change:
A) NNC Boot time-out[post xxxx,yyyy](NNC-z)
B) NNC Boot time-out[PXE][post xxxx,yyyy](NNC-z)
C) NNC Boot time-out[BIOS][post xxxx,yyyy](NNC-z)
D) NNC Boot time-out[TUR][post xxxx,yyyy](NNC-z)
E) NNC Boot time-out[BIOS_LOAD][post xxxx,yyyy](NNC-z)
F) NNC BIOS firmware installation time-out[post xxxx,yyyy](NNC-z)

9) Backend Auto Diagnosis Threshold setting support

Item Description
Contents The microcode supports a function to change the maximum retry count of Backend auto
diagnosis. A default value of the maximum retries count of Backend auto diagnosis is 10.

10) Improvement of Backend Auto Diagnosis

Item Description
Contents The microcode improved to prevent an incorrect judgment of an obstacle part by an intermittent
obstacle in the backend Loop.

11) Improvement of Multiple LBA command processing in the NAS system

Item Description
Contents When a multi-LBA command received in the NAS system, a command time-out may occur. The
microcode improves the processing of the multi-LBA command.

12) Improvement of User IP address change

Item Description
Contents The microcode improves the following items for User IP address change in the Storage
Navigator Modular GUI window.
A) The microcode maintains a chosen value (set with reboot) or (set now without reboot).
B) The microcode modified to set the default value of setting timing to (set now without reboot).

13) Improvements in NNC voltage obstacle

Item Description
Contents When a voltage obstacle occurs in the NNC, the microcode improved to fail over the NNC, and
the microcode improves the detection process for voltage obstacle.

14) Improvement of COW – Snapshot Pool

Item Description
Contents When COW – Snapshot Pool LU is made with a large segment (256KB, 512KB), the microcode
modified to improve the process to get Pool resource to reduce the internal processing time.

HDS Confidential 2 of 6
15) Improvement of Backend Auto Diagnosis to ENC/SENC firmware exchange
Item Description
Contents The microcode modified to improve the diagnosis logic of obstacle part when an ENC/SENC
obstacle occurred during ENC/SENC firmware exchange.

16) ISCSI connection exchange

Item Description
Contents The microcode modified to change the ISCSI Login Response parameters to ISCSI driver logic.
A) HP-UX support
I. The microcode changes IFMARKER and OFMARKER parameter
B) Solaris support
II. The microcode changes the First-Burst-Length parameter

The change of contents for Version 0750/A

1) Subsystem Hang-up or Controller failure by “Data share job time-out” during recovery of 3
HDD blocked in RAID6
Item Description
Contents The following phenomenon may occur during recovery of 3 HDD blocked in RAID6.
A) Subsystem hang-up
B) Controller failure “Data share job time-out”
The problem may occur with all conditions met:
A) SATA configuration
B) RAID6
C) Write command
D) Block of more than 3 HDD, during the recovery of C
E) No use of “Drive Detach Mode”
F) Write through condition (battery block, PIN over etc.)

2) Subsystem down by both controllers with “Kernel processing error” subsystem

Item Description
Contents The subsystem may go down by both with web message “Kernel processing error” This is due
to a bug in the cache segment acquisition process in a system copy.
The problem may occur with all conditions met:
A) LU0 is not defined
B) Executing system copy by system HDD obstacle
C) One of the following conditions occurs:
1) LU change(all LU change pattern: Directory unit or LU unit)
2) CHK1(Controller hardware failure
Microcode improved to resolve this issue.

3) Controller failure during Subsystem boot process

Item Description
Contents A controller blocked with the following messages during the Subsystem boot process, with the
Web message: OTH CTL Response time-out [OFW]. This is due to a bug in the
Communications process between the two controllers.
The problem may occur with all conditions met
A) Subsystem boot process
B) System copy is executed by a system HDD block
C) Controller #1 process is delayed by interruptions during the system copy
Microcode improved to resolve this issue.

HDS Confidential 3 of 6
4) Host connection may fail - ISCSI
Item Description
Contents This is due to a microcode bug in the ISCSI port initialization
The problem may occur with all conditions met
A) ISCSI interface
B) Set LU mapping
C) Reserve command is received
D) Release or change LU mapping before releasing the reservation
Microcode improved to resolve this issue.

5) NNC failure caused by Subsystem cache memory obstacle

Item Description
Contents When the controller fails by a cache memory obstacle, NNC, connected to the controller, may
also fail. This is due to a microcode bug in the NNC check processing of controller failure.
The problem may occur when following all of the following conditions are met
A) AMS1000 (DF700H)
B) NAS system
C) Controller block caused by a cache obstacle.
Microcode improved to resolve this issue.

6) Write command error for PVOL in Shadow Image

Item Description
Contents When the PVOL and SVOL switch by a PVOL obstacle, a Write command error may occur.
This is due to a microcode bug in check processing of the Write command in data copy failure.
The problem may occur when following all of the following conditions are met:
A) Shadow Image
B) Shadow Image pair status: PAIR or COPY
C) Enable “Shadow Image I/O Switch Mode”
D) Receive Write command for PVOL
E) After a response of (D), multiple HDD blocks in PVOL occurs.
F) The data copy from PVOL to SVOL fails
Microcode improved to resolve this issue.

7) NAS PP install failure after NNC maintenance IP address change

Item Description
Contents In case that the NNC maintenance IP address has been changed before the microcode initial
setup, the installation of the NAS PP fails even though the installation of NAS OS completes.
This is due to a microcode bug in the setting process of the NNC maintenance IP address.
With all conditions met, the problem may occur.
A) NAS system
B) Change of maintenance IP address before (C)
C) Execute the microcode initial setup
D) Connect to a LAN network where another subsystem is connected
E) Install NAS OS
F) Install NAS PP after (E)
Microcode improved to resolve this issue.

HDS Confidential 4 of 6
8) Power off failure by NNC obstacle after pressing the PS off switch
Item Description
Contents When an NNC obstacle occurs after pressing the PS off switch, Power off failure may occur.
The problem may occur when all the following conditions are met
A) NAS system
B) Press PS off switch
C) After (B), NNC obstacle occurs

9) Controller failure “Micro program error [RSM]”

Item Description
Contents When a SATA HDD blocks by SMART a controller may fail with the following Web message.
This is due to a microcode bug in the internal resource release processing.
Web Message – SATA HDD blockade:
SATA HDU limit over[Self-monitoring]
Controller failure:
Micro program error[RSM]
The problem may occur when all the following conditions are met:
A) SATA configuration
B) SATA HDD error threshold over is detected by SMART processing
C) A case of the following conditions occurs:
1) Not setting spare SATA HDD
2) All spare SATA HDD are used
3) During forced parity correction
4) There are no LU on the SATA HDD (B)
Microcode improved to resolve this issue.

10) Controller failure by PS OFF failed [DSTG HUNG]

Item Description
Contents The controller failure with the following Web message may occur during PS OFF. This is due to
a microcode bug in the reference process of dirty data.
A) There is many dirty data in cache memory (it takes more than 20min to de-stage the dirty
data).
B) PS off or reboot using Storage Navigator Modular

11) Automatic True Copy path recovery failure

Item Description
Contents When Fibre obstacle occurs in the True Copy configuration using the Silkworm200E, the True
Copy path may fail to recover automatically. This is due to a microcode bug in the recovery
process of the True Copy path.
The problem may occur when all the following conditions are met:
A) Fibre configuration : 4Gbps
B) True Copy remote replication
C) True Copy configuration using Silkworm200E
D) The fibre link is down by a Fibre obstacle
Microcode improved to resolve this issue.

HDS Confidential 5 of 6
12) Controller failure by “Micro program error [JSD]”
Item Description
Contents When a spare HDD during the copy back was blocked, a controller failure with the following
Web message may occur. This is due to a microcode bug in processing for copy back failure.
The problem may occur when all the following conditions are met:
A) Executing copy back
B) A spare HDD of (A) is blocked
C) One of the following conditions occurs:
1) Received READ command to an LU of the RAID Group during copy back
2) Executing PVOL copy of Shadow Image/True Copy in the RAOD Group during copy back
3) Received Write command to a COW Snapshot PVOL in the RAID Group during copy back

13) Controller Failure by “Data share job time-out”

Item Description
Contents When a PS off an NNC executes, a controller failure with the following web message may
occur. This is due to a microcode bug in the processing to detect PS OFF of NNC
Web message: Data share job time-out
The problem may occur with all conditions met.
A) NAS system
B) During command processing by data share
C) NNC PS off
D) NNCPS off is detected by the microcode polling process before the interruption of NNC PS
off
Microcode improved to resolve this issue.

14) Incorrect IP address indication in DHCP mode

Item Description
Contents Displayed IP address may be different from the correct IP address.
The problem may occur when all following conditions are met:
A) DHCP mode
B) Failure in acquisition of IP address from the DHCP server during the subsystem boot
C) Success in acquisition of IP address from DHCP server after the subsystem is ready
Microcode improved to resolve this issue.

15) Pair operation during Parity Correction using Storage Navigator Modular
Item Description
Contents The microcode incorrectly executed the pair operation during the Forced Parity Correction using
Storage Navigator Modular. This is due to a microcode bug in the guard processing for pair
operation.
The problem may occur with all conditions met:
Shadow Image:
A) Shadow Image
B) Execute Forced Parity Correction for Shadow Image PVOL and SVOL
C) Parity Correction status: “parity correcting”, Waiting Parity Correction”
D) Execute “pair create” or pairresync”
Microcode improved to resolve this issue

HDS Confidential 6 of 6