AMS2000

MICROCODE VERSION 0890/B

RELEASED 05/05/2010
Newly supported features and functions for Version 0890/B
1 3 New Features
Contents 1) SAS HDD (AKH450X(S1) and AKH600X(S) are supported on RKAKX (Dense expansion unit)
2) Support Forced Reserve Reset with Hitachi Storage Navigator Modular 2 GUI
Unintentional LU reservation can be released using this function in Maintenance mode
3) Enhancement of Performance Monitor
Performance Monitor shows Sequential I/O performance numbers and Random I/O performance numbers

Improvements for Version 0890/B

1 6 Improvements
Contents 1) Detect function against unformatted areas caused by unexpected termination of the LU format. This
function runs either at startup/reboot of the subsystem (including microcode update). If an unformatted
area is detected, an information message will be issued: ‘I6H100 Unformatted area remains in the LU
(LU-XXXX). Please contact support for assistance’
2) Improvement for initialization of the SRAM in ENC in reboot sequence
Method for initializing the SRAM in ENC to fill complete with zero data
3) Improvement for capturing trace data when Write command response time out (B/C006) occurs
4) Improvement of E-mail message on E-mail Alert function
5) Improvement of subnet mask check function
The illegal subnet mask value in LAN configuration can be detected with this function
6) Year 2010 Compliance with NIST Minimum Security Strength

The change of contents for Version 0890/B

1 Recover from controller failure does not work
Phenomena If PS OFF without cache volatilization is performed or a controller failure occurs when
deleting arbitrary RAID groups, there are the cases where the RAID groups are deleted but
afterward LUs in a RAID group cannot be created. Or there is a possibility that Watchdog
Timeout can occur due to infinite loop during LU Ownership changing process.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1)Deleting RAID groups
(2) LUs are created in the specified RAID groups.
(3)During the RAID group deleting sequence, PS OFF without cache volatilization is
performed or the controller performing the sequence fails.
Cause If a failure occurs during decrementing the number of LUs in the RAID group deletion
process, the firmware inappropriately decrement the number of LUs again during the
failure recovery process.
Affected Products/Version DF800H/M/S, V3.1/A(0831/A) or later
DF800EH/EM/ES, V9.0/A(0890/A)
Fixed Product/Version Version: 0890/B or later
Category Common
Changed Part MICRO-Disk

HDS Confidential 1 of 11
 2 Controller Blocked
Phenomena The controller blockage is generated when AMS is used by USP_V/VM's Universal
Volume Manager function.
Severity High
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) DF800H
(2) Fibre Channel interface
(3)DF800H is used by USP_V/VM's Universal Volume Manager function
(4)I/O are executed
Cause When USP_V/VM's Universal Volume Manager is used, the I/O issues by the Round robin
method from USP_V/VM to two or more ports at DF800H. Because half the number of I/O
are processed by the controller on the side which have the LU owner, I/O load rises. The
hardware trouble is detected wrongly to depend on the access-timing of hardware.
Affected Products/Version DF800H, V4.0/A(0840/A) or later
Fixed Product/Version Version: 0885/F or later, except 0888/A and 0890/A
Category FC interface
Changed Part MICRO-Disk

3 Controller blockade by LA error

Phenomena The controller blockade may occur with the following WEB information message during
highly-loaded host I/O.
Severity High
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) High load
Cause When the processing that judges the end of the data transfer competes between controller's
CPU cores, when the data transfer to the cache memory has not completed, there is a case
to misjudge that the end of data transfer.
Affected Products/Version DF800H/M/S, V3.2/A(0832/A) or later
Fixed Product/Version Version: 0885/F or later, except 0888/A and 0890/A
Category FC interface
Changed Part MICRO-Disk

4 Performance degradation in sequential write on SATA

Phenomena I/O Performance degradation seen with sequential writes issued to LUs in SATA drives.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) Using SATA drives
(2) Sequential writes are issued
(3) There are more than 65 segments to skip the parity generation in each drive having
unprocessed middle dirty in the previous stripe.
Cause At DF800 V5.0, the firmware was enhanced so that in the process of searching segments to
execute collective writing, if sequential writes are issued to LUs in SATA drives and there
is unprocessed middle dirty in the previous stripe, the segments in the next stripe let skip
(wait) parity generation. In addition, the maximum number of segments to skip parity
generation is set and if the number of skipping exceeds the threshold (65), searching
segments in the specified RAID group would be stopped and performed in another drive.
However the firmware had problem with calculation of the number of skipping and did not
count up the number, so all segments in the drive were searched and the middle collective
writing took a long time and used a lot of CPU resources, which resulted in the
performance degradation.
Affected Products/Version DF800H/M/S, V5.0/A(0850/A) or later
DF800EH/EM/ES, V9.0/A(0890/A)
Fixed Product/Version Version: 0890/B or later
Category Common
Changed Part MICRO-Disk

HDS Confidential 2 of 11
 5 Controller blockade with message "Resource release time-out"
Phenomena The controller blockade is occurred with the message "Resource release time-out"
Severity Medium
Conditions of Occurrence The problem may occur when following conditions are met.
(1)Enabling Dynamic Provisioning
(2) Capacity of Dynamic Provisioning Pool is large. (more than 120TB / system)
(3)Dynamic Provisioning Pool is unused, or 4 or less than DP-VOL per Dynamic
Provisioning Pool defined or unused DP-VOL.
The problem may occur when any of the following conditions are met.
(4)Every 24 hours
(5) CPU boot (PS/ON, Firmware Exchange, Insert the Controller)
(6) Shrinking the DP-VOL
(7) Dynamic Provisioning Optimization
(8) Recovering the Dynamic Provisioning Pool.
(9)The write-same command to DP-VOL is received.
(10)The read command to non-allocation address in DP-VOL is received.
Cause At the case of the occurrence condition (4) ～ (10), after deleting an assigned page, the full
page in chunk might become unused. There is the procedure of garbage collection that
checks whether the relation with LU can be released. This processing is regularly done
during the constant time. When processing is not completed, it ends once. There is no
opportunity when processing is completed on the way for the chunk of non reclaimable.
Therefore, it takes time to check chunk when there are a lot of unused areas, and the watch-
dog error is generated.
Affected Products/Version DF800H/M/S, V7.0/A(0870/A) or later
Fixed Product/Version Version: 0885/F or later, except 0888/A and 0890/A
Category Hitachi Dynamic Provisioning
Changed Part MICRO-Disk

6 Loop State Timeout

Phenomena Controller failure occurs with following WEB message caused by data transfer check error
in 8Gbps Fibre Channel interface. HD2100 Host transfer DMA error was over the threshold
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) Using the 8Gbps Fibre Channel interface (DF800EH/H/EM/M/ES)
(2) Host I/Os which data length are less than 8KB.
(3) The Host stop the data transference without aborting process caused by hung-up, etc.
Cause Number of data transfer check error caused by inappropriate errata logic in 8Gbps Fibre
Channel interface exceeds the 6 which is the threshold, controller failure occurs.
Note: When the Loop State Timeout occurs during transferring two short length data, the
firmware inappropriately clear both two data although it should clear just the first
transferred data. Causing by this, there is a logic contradiction, and then the data transfer
check error is detected.
Affected Products/Version DF800H/M, V7.2/A(0872/A) or later
DF800EH/EM/ES, V9.0/A(0890/A)
Fixed Product/Version Version: 0890/B or later
Category FC interface
Changed Part MICRO-Disk

HDS Confidential 3 of 11
 7 Controller failure in boot up process in DF800H
Phenomena There might be the case that the controller failure occurs in boot up process in DF800H
with following WEB message. H0A500 PCI Configuration access error was
detected[Host0_PCI Express core, 0x00004000]
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) DF800H/EH (Multi Core configuration)
(2) I/F board #0 and #1 are same kind of interface.
(eg: I/F#0:iSCSI, I/F#1:iSCSI or IF#0:Fibre Channel, IF#1:Fibre Channel)
(3) Hardware reset is same between two cores on same controller in the boot up process.
Cause In the process of hardware reset for two cores on the same controller in boot up process,
caused by the firmware bug for exclusion logic of register access in host interface, the
firmware inappropriately releases reset status although the hardware reset process has not
been completed yet. Then, the hardware failure is detected illegally and controller is failed.
Affected Products/Version DF800H, V3.1/A(0831/A) or later
DF800EH, V9.0/A(0890/A)
Fixed Product/Version Version: 0890/B or later
Category Common
Changed Part MICRO-Disk

8 Illegal controller failure

Phenomena The controller failure might occur when many Link failures are detected in backend
diagnosis in array boot up process.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) Specific term for about 300ms in backend diagnosis in array boot up process.
(2) Many Link failures are detected caused by the failure of drive, ENC or controller.
Cause Value of progress for diagnosis becomes abnormal when a Link failure is detected
additionally in backend diagnosis, then controller failure occurs with timeout of diagnosis.
Affected Products/Version DF800H/M/S, V3.1/A(0831/A) or later
DF800EH/EM/ES, V9.0/A(0890/A)
Fixed Product/Version Version: 0890/B or later
Category Backend
Changed Part MICRO-Disk

9 Cannot issue the SNMP Trap

Phenomena If the config.txt is set with illegal contents at first after installing the SNMP PP key, then
SNMP can never be worked normally although the config.txt is fixed normally.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) Installing the SNMP PP key.
(2) The Default Gateway is set.
(3) The config.txt is set with illegal contents at first after installing the SNMP PP key, and
WEB message “IB1400 SNMP agent detected the error” is displayed.
Note: eg: IP address: MANAGER 123.45.67..89
Cause There is a firmware bug in the process of SNMP task generation for the case of illegal
config.txt, the SNMP task cannot be generated normally. Then it is never recovered
although the config.txt is fixed normally.
Affected Products/Version DF800H/M/S, V8.5/A(0885/A) or later
DF800EH/EM/ES, V9.0/A(0890/A)
Fixed Product/Version Version: 0890/B or later
Category SNMP
Changed Part MICRO-Disk

HDS Confidential 4 of 11
 10 Controller failure during Write and data length is more than 256KB.
Phenomena Controller failure might occur with following WEB message during executing the high-
loaded Write which data length is more than 256KB.
HD2400 DRR time-out
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) Executing the high-loaded Write I/Os.
(2) The data length is more than 256KB.
Cause There is a firmware bug in the process of parity generation for Host Write data. Cause by
the illegal logic, the firmware judges the first access as retry process, then detects the retry
failure illegally and fails the controller.
Affected Products/Version DF800H/M/S, V3.1/A(0831/A) or later
DF800EH/EM/ES, V9.0/A(0890/A)
Fixed Product/Version Version: 0890/B or later
Category Common
Changed Part MICRO-Disk

11 SAS HDD failure caused by the path failure between ENC and drive
Phenomena When path between ENC and drive fails, the HDD might fails with no-response status.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) Using SAS HDD.
(2) Path failure occurs between ENC and drive, and "Loss of Sync" is detected.
(3) The "Loss of Sync" is recovered within 500ms.
Cause When detecting the "Loss of Sync", the firmware illegally starts the Linkup watching timer,
and then judges it as Linkup failure with timeout, and the HDD becomes no-responding
status. However, the case that "Loss of Sync" status lasts more than 500ms, the firmware
can detect the failure as "Loss of Sync Timeout"; there is no problem at this case.
Affected Products/Version DF800H/M/S, V3.1/A(0831/A) or later
DF800EH/EM/ES, V9.0/A(0890/A)
Fixed Product/Version Version: 0890/B or later
Category Backend
Changed Part HDD Firmware

12 Subsystem-down for "HF0101 Data transfer check error"

Phenomena There might be the case of Subsystem-down caused by both CTLs failure for illegally
detecting the "Data transfer check error [WRNODTYBK]".
Severity High
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) DF800H
(2) Enabling Copy-on-write Snapshot, Shadow Image in-system replication, True Copy
remote replication, True Copy Modular Distributed, True Copy Extended Distance or
Dynamic Provisioning. Or, there are some dirty-data on the Cache.
(3) Executing planned shutdown
(4) Detecting the CTL failure
Cause Regarding the LU Ownership changing process during planned shutdown, it needs to be
worked after all job processes completed. However, because of the firmware bug, there is
the case to generate new job illegally during the LU Ownership changing process, then it
causes the CTL failure in the other side and Subsystem-down at last.
Affected Products/Version DF800H, V8.5/A(0885/A) or later
Fixed Product/Version Version: 0890/A or later
Category Common
Changed Part MICRO-Disk

HDS Confidential 5 of 11
 13 System-down with other CTL failure during DP Pool initializing
Phenomena There might be the case that Subsystem-down occurs caused by other side of CTL failure
which detects the "HJ4AC7 Micro program error was detected[HDP]" illegally if CTL
failure is occurs during DP Pool initializing process.
Severity High
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) Enabling Dynamic Provisioning
(2) Executing the DP Pool initialization
(3) Detecting the CTL failure
Cause Logical contradiction is detected when LU ownership changing process refers the internal
table illegally in the case of CTL failure during the DP Pool initializing process.
Affected Products/Version V7.0/A(0870/A) or later
Fixed Product/Version Version: 0890/A or later
Category HDP
Changed Part MICRO-Disk

14 Subsystem-down caused by route switching

Phenomena Subsystem-down occurred by switching (VRRP) of route of L3 Switch while I/O operation.
Severity High
Conditions of Occurrence The problem may occur when all following conditions are met.
(1)iSCSI I/F
(2) Login from 176 or more initiators per a port
(3)Execute VRRP switching
Cause Virtual MAC address of passing became invalid in login by the VRRP switching, and the
Nop-In command did not end. Therefore, the resource to execute Login processing by retry
before the interruption ended repeating retry of the NOP-In command was insufficient, and
the controller blockage was occurred.
Affected Products/Version DF800H/M/S, V3.2/A(0832/A) or later
Fixed Product/Version Version: 0890/A or later
Category iSCSI I/F
Changed Part MICRO-Disk

15 Subsystem-down when one controller fails while LUs are formatted or

parity correction is executed.
Phenomena The subsystem goes down when one controller fails while LUs are formatted or parity
correction is executed.
The following message is displayed "Resource release time-out was detected [Core].
Severity High
Conditions of Occurrence The problem may occur when all following conditions are met.
(1)Multi-core configuration installed (DF800H)
(2) The configuration information is being changed at the time of the following events
(i) The configuration information is being changed when LUs are formatted.
(ii)The configuration information is being changed when parity correction is executed.
(3)The other controller which does not handle the process (2) fails.

Cause Resource is obtained to make mutual exclusion between the controllers or the cores when
the configuration information for formatting LUs and parity correction is changed. And
there are cases where deadlock between the cores may occur in the process of recovering
the controller failure and then time-out of resource occurs due to the logic for avoiding the
dead-lock. And then the remaining controller comes to fail, which means both of the
controllers fail.
Affected Products/Version DF800H, First Version or later
Fixed Product/Version Version: 0890/A or later
Category Common
Changed Part MICRO-Disk

HDS Confidential 6 of 11
 16 Subsystem-down in booting after electrical power outage
Phenomena Phenomenon-1:
When more than one spare disk drive has been replaced in the past, subsystem outage may
occur with the following message in the power-on of subsystem after the electrical power
outage and cache memory volatilization.
WEB information message: "I6G100 The serial number of the HDU is different from the
configuration info", "HH9R00 Two or more HDUs have serial number problem"

Phenomenon-2:
When one spare disk drive has been replaced in the past, the blockade of this drive may
occur with the following message in the power-on of subsystem after the electrical power
outage and cache memory volatilization.
WEB information message: "I6GV00 Move drive (Unit-x1,HDU-y1) to slot (Unit-x2,
HDU-y2) because of serial number problem"
Severity High
Conditions of Occurrence When all of the following conditions are met, the phenomenon occurs.
(a) More than one spare disk drive is replaced. (in case of phenomenon-1)
One spare disk drive is replaced. (in case of phenomenon-2)
(b) The subsystem configuration information is not updated to the system disk of
subsystem after the replacement of (a).
(For example, LU creation, system parameter setting, host group option setting and
subsystem shutdown etc. are not executed.)
(c) The electrical power outage and cache memory volatilization occur under the condition
of (b).
(d) The power-on of subsystem is executed after the condition of (c).
Cause The firmware incorrectly checks out the spare disk drive by using the old subsystem
configuration information in the power-on of subsystem after the electrical power outage
and cache memory volatilization, because the firmware does not update the subsystem
configuration information to the system drives, when a spare disk drive is replaced.
Affected Products/Version DF800H/M/S, V3.1/A(0831/A) or later
Fixed Product/Version Version: 0890/A or later
Category Spare disk drive
Changed Part MICRO-Disk

17 Subsystem-down occurs when an ENC is pulled out.

Phenomena Subsystem down occurs when an ENC which installed in the enclosure with one or more
SATA drives is pulled out.
Severity High
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) One or more SATA drives are installed in the system.
(2) An ENC which installed in the enclosure with one or more SATA drives is pulled out.
The pulled ENC is not blockaded.
(This phenomenon doesn't occur in case that an ENC which is blockaded is pulled out.)
Cause This phenomenon occurs when the ENC is pulled out in the timing of executing SES access
from firmware to a pair ENC of pulled out ENC by way of pulled out ENC. The expected
behavior of the ENC which was executed SES access from firmware is to finish retrying
the response to firmware by two seconds. But the ENC firmware has a bug which is that
time out counter is cleared illegally and the tasks in the ENC which was executed SES
access continue to execute unexpectedly. So the number of tasks is over the regulation, the
ENC is blockaded and subsystem down occurs.
Affected Products/Version DF800H/M/S, First version or later
Fixed Product/Version Version: 0890/A or later
Category Backend
Changed Part MICRO-Disk

HDS Confidential 7 of 11
 18 WEB connection failure on failed CTL in DF800H with iSCSI I/F
Phenomena There is the case that the failed CTL cannot be connected by WEB in DF800H with iSCSI
I/F.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) DF800H
(2) iSCSI I/F
(3) Detecting the CTL failure
Cause Process for CTL failure halts inappropriately for uncorrectable error when one hardware-
reset and iSCSI register access occur simultaneously, then the CTL cannot connected by
WEB.
Affected Products/Version DF800H, V1.0/A(0810/A) or later
Fixed Product/Version Version: 0890/A or later
Category iSCSI
Changed Part MICRO-Disk

19 Controller 0 hung-up when starting the Maintenance Mode

Phenomena Letting the subsystem to enter the maintenance mode, the controller 0 does not reply to the
Web access and other operations.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) The system drives of the subsystem are SAS HDD
(2) Let the subsystem to enter the Maintenance Mode (See the Maintenance Manual).
Cause Due to the application of patches to the internal OS were incomplete on V6.0, the firmware
may access to the memory whose address is illegal on the SAS HDD access process in the
Maintenance Mode.
Affected Products/Version DF800H/M, V6.0/A(0860/A) or later
Fixed Product/Version Version: 0890/A or later
Category Common
Changed Part MICRO-Disk

20 Unable to access by HSNM2

Phenomena When creating a RAID Group made of the maximum number of HDDs of the model, the
subsystem cannot be accessed from HSNM2.
(HSNM2 Message: DMEA001163: The value received from the subsystem is invalid)
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) Creating a RAID Group made of the maximum number of HDDs of the model (e.g. 480
for DF800H). The RAID configuration is not RAID1 and not RAID0 (2D).
(2) After (1), refer RAID Group information from HSNM2.

Cause The process to get the information of all HDDs in a RAID Group has a bug on the
terminate condition to get information. If a RAID Group is made of the maximum number
of HDDs of the model, the process fail to terminate and the information to be sent to
HSNM2 becomes wrong.
Affected Products/Version DF800H/M/S, All version
Fixed Product/Version Version: 0890/A or later
Category Common
Changed Part MICRO-Disk

HDS Confidential 8 of 11
 21 Link-up failure during Array booting
Phenomena The link-up couldn't do after the boot operation of apparatus (PS-ON, Offline firmware
exchange, temporary controller failure).
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1)FC I/F
(2) The boot operation of apparatus (PS-ON, Offline firmware exchange, temporary
controller failure)
(3) The cable is connected.
(4)Loop Bypass signal had been accepted before light was output.
Cause When the apparatus is boot, light is output from the AMS side. The Link initialize is
executed at the case of the speed fixation. When the FC port accepts the Loop Bypass
signal, Link Initialize isn't executed. At this time, when the FC port accepts the Loop
Bypass signal, Link Initialize doesn't is executed.
Affected Products/Version DF800H/M/S, V3.2/A(0832/A) or later
Fixed Product/Version Version: 0890/A or later
Category FC I/F
Changed Part MICRO-Disk

22 Controller blockage is occurred after switch port enable/disable.

Phenomena When Enable/Disable of Switch port is switched, the controller blockage is occurred.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1)FC I/F
(2) The setting of the topology is Point to Point.
(3)Switch connection
Cause LS_RJT responds when the LISM frame is accepted at the opportunities other than the link
initialization at the Point to Point connection. An internal resource was insufficient
because of executing responded for the LISM frame, and the controller was blockaded.
Affected Products/Version DF800H/M/S, V3.2/A(0832/A) or later
Fixed Product/Version Version: 0890/A or later
Category FC I/F
Changed Part MICRO-Disk

23 Controller blockage occurred by pulling out the cable in SAN

Phenomena The controller blockage was occurred by pulling out the cable about the SAN environment
other than AMS-Switch connection.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1)FC I/F
(2) Reset is accepted to the number of 4096 or more in AMS2300 and the number of 2048
or more in AMS2100.
Cause Because there was a bug that mistakes the range of reset when the reset command is
received.
Affected Products/Version DF800H/M/S, V3.2/A(0832/A) or later
Fixed Product/Version Version: 0890/A or later
Category FC I/F
Changed Part MICRO-Disk

HDS Confidential 9 of 11
 24 WEB connection failure when getting the Simple Trace
Phenomena In DF800H, there might be the case that getting Simple Trace is failed then WEB cannot be
connected when the Simple Trace collection is executed on the failed CTL within 3min
after CTL failure.
Severity Low
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) DF800H
(2) Detecting CTL failure
(3) Getting Simple Trace within 3min after above (2)'s CTL failure.
Cause Both CTL failure process and Simple Trace collection process access same area in Flash
memory illegally, then both of them cannot use this area.
Affected Products/Version DF800H, V1.0/A(0810/A) or later
Fixed Product/Version Version: 0890/A or later
Category Common
Changed Part MICRO-Disk

25 Illegal event log message for I/F Slot#1 in DF800H with multi protocol
Phenomena I/F Slot number is shown illegally as #0 even though it is actually for #1 in DF800H with
multi protocol.
Severity Low
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) DF800H
(2) "CTL0-I/F Slot#1 is iSCSI, and CTL1-I/F Slot#1 is FC" or "CTL0-I/F Slot#1 is FC, and
CTL1-I/F Slot#1 is iSCSI"
(3) Turning on the Array
Cause In above case, fixed #0 is shown in every case.
Affected Products/Version DF800H, V6.0/A(0860/A) or later
Fixed Product/Version Version: 0890/A or later
Category Common
Changed Part MICRO-Disk

26 The contents of Audit Log is illegal

Phenomena When installing/de-installing a Program Product, the Audit Log should be "Start/NotStart"
as written in the user's guide, but the Audit Log actually issued is "Enable/Disable".
Severity Low
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) Audit Logging is enabled.
(2) Installing/De-installing a Program Product.
Cause On the management table for the Audit Log, the correspondence between the event code of
the installation of Program Products and the string to be displayed was wrong.
Affected Products/Version DF800H/M/S, SA8x0, All version
Fixed Product/Version Version: x890/A or later
Category Audit Log
Changed Part MICRO-Disk

HDS Confidential 10 of 11
 27 With PS off, controller blockage occurred
Phenomena PS off is executed, the controller blockage is occurred. However, PS off is completed.
Severity Low
Conditions of Occurrence The problem may occur when all following conditions are met.
(1)iSCSI I/F
(2)AMS2500
Cause It was a specification that stopped processing when Hard Reset was executed in the core
where iSCSI I/F was mounted when the PS off is executed. However, the apparatus could
not recognize that the controller blockage processing was executed and controller blockage
was occurred.
Affected Products/Version DF800H/M/S, V6.0/A(0860/A) or later
Fixed Product/Version Version: 0860/A or later
Category iSCSI I/F
Changed Part MICRO-Disk

28 Illegal message is displayed when ENC cable is connected incorrectly.

Phenomena When subsystem is booted up, the cables are connected incorrectly.
For example,
- Connection A: between controller enclosure and Unit02-ENC0.
- Connection B: between controller enclosure and Unit03-ENC0.
- Connection A and B are swapped each other.
Web massage shows that the connection of Unit02-ENC1 is incorrect instead of Unit02-
ENC0.
HH7700 Backend down[Cable error](Unit-02,ENC-1)

Severity Low
Conditions of Occurrence The problem will occur when all following conditions are met.
(1) Subsystem boot with illegal cable connected status
OR enclosure online addition with illegal cable connected status
OR power on about tray power saving with illegal cable connected status
(2) The connection for ENC#1 is correct. The connection for ENC#0 in the same enclosure
is incorrect.

Cause There is a bug about consistency detection logic for backend connection, so firmware
misjudges that the connection of ENC0 that is checked previously is "correct".
Affected Products/Version DF800H/M/S, V3.1/A(0831/A) or later
Fixed Product/Version Version: 0890/A or later
Category Backend
Changed Part MICRO-Disk

HDS Confidential 11 of 11