Scribd
Upload
43 views5 pages

Sms Code 1880a

sms

Uploaded by

imkzby
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
43 views5 pages

Sms Code 1880a

sms

Uploaded by

imkzby
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

SMS

MICROCODE VERSION 1880/A


RELEASED 11/13/2009

Newly supported features and functions for Version 1880/A

NONE

Improvements for Version 1880/A

1 2 Improvements
Contents 1) DMLU no longer a selectable LU
2) Improvement of failure search accuracy of SAS controller firmware

The change of contents for Version 1880/A

1 Host Access unavailable when firmware is exchanged


Phenomena In case that the system has SATA HDD and exchange of firmware or ENC replacement
has done in the system, if power off and on has not executed after exchange of firmware
or ENC replacement, there is a possibility that host access can’t be executed when next
exchange of firmware is done.
Severity High
Conditions of Occurrence The problem may occur when all following conditions are met.
A. Firmware version x865/A or later is used in the system.
B. The system has SATA HDD.
C. Exchange of firmware or ENC replacement has done in the system. The last operation
is one of the patterns below. (No problem if the last operation is that except the patterns
below. Or, no problem if exchange of firmware or ENC replacement has not completed
in the system.
- Firmware exchange:
x861/A or before -> x865/A or later
x862/A – x865/A -> x865/B or later
x865/B – x865/H -> x870/C or later
x870/C -> x872/A or later
- ENC replacement:
Firmware version when ENC replacement has done is x865/A or later.
D. Power off and on has not executed after condition C.
Affected Products/Version DF800H/M/S, SA8x0, Ver6.5/A(0865/A) or later
Fixed Product/Version Version: x872/G, x880/A or later
Category Backend
Changed Part MICRO-Disk

HDS Confidential 1 of 5
2 Reboot failure occurs and sequential shutdown sequence stops
Phenomena Failure of reboot occurs and temporary sequential shutdown sequence stops when Auto
Reboot is issued by SNM2 in case of controller blockade. And then, sequential shutdown
is executed, controller is blockaded with Micro program error [DMI] and subsystem
down occurs.
Severity High
Conditions of Occurrence The problem may occur when all following conditions are met.
(1)Controller is blockade. (No problem for Single controller configuration)
(2)Auto Reboot is ordered.
(3)Sequential shutdown is executed after failure of reboot ordering.
(4)In sequential shutdown, the status is one of them below.
- Snapshot key or TCE key is opened and DM-LU exists.
- True Copy key or Shadow Image key is opened and pair status of "PSUS" or "COPY"
or "PAIR" exist.
- HDP key is opened and DP pool exists.
- Volume Migration is executed.
- Simple DR is executed (SA8x0)
Affected Products/Version DF800H/M/S, SA8x0, First version or later
Fixed Product/Version Version: x880/A or later
Category Reboot
Changed Part MICRO-Disk

3 I/O performance reduction and illegal message


Phenomena I/O performance is reduced and illegal message is displayed repeatedly because route
diagnostic of both backend path is executed repeatedly in case that HDD for current
diagnostic target is blockaded during backend route diagnostic.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1)Timeout of multiple SATA HDD occur in the same backend path.
(2)Backend diagnostic is executed.
(3)HDD for current diagnostic target is blockaded between start of diagnostic for HDD
and start of diagnostic for another backend path, about 5 seconds.
Affected Products/Version DF800H/M/S, SA8x0, First version or later
Fixed Product/Version Version: x872/G, x880/A or later
Category Backend
Changed Part MICRO-Disk

4 Controller blockade with "Parity generation LA error [DRR]"


Phenomena Controller is blockaded with "Parity generation LA error [DRR]".
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1)The backend route failure occurred.
(2)SAS controller Firmware fails query task command.
Affected Products/Version DF800H/M/S, SA8x0, First version or later
Fixed Product/Version Version: x872/G, x880/A or later
Category Backend
Changed Part MICRO-Disk

HDS Confidential 2 of 5
5 Subsystem down when sequential shutdown and power on is executed
Phenomena Subsystem down may occur when sequential shutdown and power on is executed after
that controller blockade occurs by ENC failure about SA800.
Severity Medium
Conditions of Occurrence The problem will occur when all following conditions are met.
(1)SA8x0
(2) Controller blockade occurs by ENC failure.
(3)Sequential shutdown and power on is executed after (2).
Affected Products/Version SA8x0, 1850/A or later
Fixed Product/Version Version: 1880/A or later
Category Backend
Changed Part MICRO-Disk

6 Firmware update failure on subsystem with 0.0.0.0 subnet mask


Phenomena When updating firmware on the subsystem that the value of subnet mask of management
LAN is 0.0.0.0, the update fails. Then the controller is blockaded after rebooting. The
controller does not recover even it is replaced.
Or the controller is blockaded when the subsystem is rebooted after 0.0.0.0 was set to
subnet mask of management LAN. (If the values of subnet mask of both controllers were
0.0.0.0, the subsystem does not become "Subsystem Ready".)

Severity High
Conditions of Occurrence The problem may occur in each case:
Case (a)
The failure may occur when the followings conditions are met.
(1) The firmware version is less than V6.0/A.
(2) The value of subnet mask of management LAN is 0.0.0.0.
(3) Update the firmware to V6.0/A or later.
Case (b)
The failure may occur when the followings conditions are met.
(1) The firmware version is V6.0/A or later.
(2) Set 0.0.0.0 to the value of subnet mask of management LAN.
(3) Reboot the subsystem.
Affected Products/Version DF800H/M/S, SA8x0, Version 0860/A or later
Fixed Product/Version Version: x872/D or later
Category LAN
Changed Part MICRO-Disk

7 Path failover by HSRP (Hot Standby Routing Protocol (Cisco™))


Phenomena Path failover by HSRP (Hot Standby Routing Protocol (Cisco™)) in a network segment
is not available in ISCSI configuration which has redundant routers.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1)ISCSI I/F
(2) Redundant IP-SAN configuration by HSRP with Cisco's network router.
(3)Some network failure occurs. (Path failover is expected to be done.)
Affected Products/Version DF800H/M/S, SA8x0, First version or later
Fixed Product/Version Version: x872/D or later
Category ISCSI
Changed Part MICRO-Disk

8 Blockade of a controller "Micro program error [ERR]"


Phenomena When transfer length error occurs frequently in plural HDD and the occurrence of the
HDS Confidential 3 of 5
error on a controller beyond the predetermined threshold, the controller should be
determined to be the cause and be blockaded with "Backend error count of the CTL was
over the threshold [CODE-29] (CTL-xx) 」". But the controller is blockaded with "the
Controller is blockaded with Web message "Micro program error [ERR]".

Severity Low
Conditions of Occurrence The problem may occur when all following conditions are met.
- Failures (of HDD and controllers) which the firmware will increase the error threshold
counter on HDD and controllers occur frequently.
Affected Products/Version DF800H/M/S, SA8x0, Ver. x862/A or later
Fixed Product/Version Version: x872/D or later
Category Backend
Changed Part MICRO-Disk

9 Data inconsistency on CTL memory


Phenomena When CTL have different versions of firmware, some data inconsistency on a CTL
memory will be occur if a failure occur in the backend and a Read I/O to SATA HDD is
issued. According to which data is inconsistent, CTL blockade, Subsystem down etc. will
occur.
Severity High
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) CTL has different versions of firmware. (e.g. during the firmware update)
(2) A backend failure occurs. (As a result, CTL become cross-call status.)
(3) Read I/O to SATA HDD is issued.

Affected Products/Version SA8x0, First Version or later


Fixed Product/Version Version:1872/G or later
Category Common
Changed Part MICRO-Disk

10 CTL is blockaded with Micro program error[ISM] on ISCSI login


Phenomena CTL is blockaded with Micro program error[ISM] on ISCSI login
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) ISCSI I/F
(2) Duplicate ISCSI Logins issued from the same host back to back.

(If this failure occurs once per 24 hours, the CTL blockade will recover automatically by
rebooting.
But if this failure occurs more than once per 24 hours, the CTL blockade will not
recover automatically.)
Affected Products/Version DF800H/M/S, SA8x0, First Version or later
Fixed Product/Version Version: 0872CEA, x872/G or later
Category ISCSI
Changed Part MICRO-Disk

11 ISCSI port is not available as the port is not link up.


Phenomena ISCSI port is not available as the port is not link up.
Severity Medium
Conditions of Occurrence The problem may occur when all following conditions are met.
HDS Confidential 4 of 5
(1) ISCSI I/F
(2) An error occurs in an ISCSI protocol chip.
(3) A CTL detects the error and execute reset process to the ISCSI I/F and another CTL
also detects the error and executer reset process to the ISCSI I/F at the same time.
Affected Products/Version DF800H/M/S, SA8x0, First version or later
Fixed Product/Version Version: x872/G or later
Category ISCSI
Changed Part MICRO-Disk

12 Unable to get SNMP MIB of the array


Phenomena In some case, the response to the SNMP MIB GET request is not issued from the array.
Severity Low
Conditions of Occurrence The problem may occur when all following conditions are met.
(1) The array receives a connection request to TCP/199 port.
(2) Just after (1), the TCP/199 port receives RST packet (i.e. TCP reset) and the
connection of (1) is disconnected. (Port scan may cause (1) (2).)
(3) After (2), no accesses to TCP/199 port are received.
Affected Products/Version SA8x0, First Version or later
Fixed Product/Version Version: 1872/G or later
Category SNMP
Changed Part MICRO-Disk

HDS Confidential 5 of 5

You might also like