0 Bewertungen0% fanden dieses Dokument nützlich (0 Abstimmungen)
10 Ansichten1 Seite
This document summarizes changes in microcode version 50-04-47-00/00 released on 11/30/05. It addresses two issues: 1) A reserve conflict was reported wrongly during online path definition changes, which could cause servers to go down. 2) A device became inaccessible due to a reserve conflict during a microprogram exchange. Both issues were fixed in this new microcode version.
This document summarizes changes in microcode version 50-04-47-00/00 released on 11/30/05. It addresses two issues: 1) A reserve conflict was reported wrongly during online path definition changes, which could cause servers to go down. 2) A device became inaccessible due to a reserve conflict during a microprogram exchange. Both issues were fixed in this new microcode version.
This document summarizes changes in microcode version 50-04-47-00/00 released on 11/30/05. It addresses two issues: 1) A reserve conflict was reported wrongly during online path definition changes, which could cause servers to go down. 2) A device became inaccessible due to a reserve conflict during a microprogram exchange. Both issues were fixed in this new microcode version.
RELEASED 11/30/05 Newly supported features and functions for Version 50-04-47-00/00 NONE
The change of contents for Version 50-04-47-00/00
1 Reserve Conflict reported wrongly during online path definition change Phenomena When path definitions were changed online during an IO operation, a reserve conflict was reported wrongly in response to the IO. As a result, the server went down. As online path definition change was made, an inconsistency occurred in the relationship between a table controlling Reserve and another table controlling path definitions. A reserve conflict was reported wrongly since wrong Reserve information was referenced. Severity (High, Medium, Low) High Conditions of Occurrence With all conditions (A through D) met, this phenomenon might occur. A. RAID500 B. LUN installation/de-installation onto port where host IO is executing C. CHF PCB D. Configuration in which Persistent Reserve command is issued AIX+HDLM / MSCS+HDLM / Tru64+Cluster / (SUN with HA software) host is connected Affected Products/Version DKCMAIN: All Fixed Product/Version DKCMAIN: 50-04-47-00/00 Category OPEN Changed Part DKCMAIN
2 Device inaccessible due to Reserve Conflict during micro-
program exchange Phenomena When an I/O was issued from AIX during a Non-Stop SCSI micro- program exchange, a reserve conflict occurred. As a result, the host could not access the device. When a link failure occurred during a Non-Stop SCSI micro-program exchange, the MP that took over the reset process due to the failure could not release the reserve attribute on the target port. Severity (High, Medium, Low) High Conditions of Occurrence When all the conditions (A-D) are met, this phenomenon might occur. A. RAID500 B. Non-Stop SCSI mode micro-program exchange C. CHF PCB D. Host that issues a Reserve command is connected. AIX/MSCS/Tru64/(SUN with HA software) Affected Products/Version DKCMAIN: All Fixed Product/Version DKCMAIN: 50-04-47-00/00 Category OPEN Changed Part DKCMAIN